@ever-co/legal 0.4.1 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  <h1 id="privacy-policy" tabindex="-1">Privacy Policy</h1>
2
2
  <p><strong>Ever Gauzy</strong> — <a href="https://gauzy.co">gauzy.co</a></p>
3
- <p>Version 1.0.2 · In force from 2026-08-02</p>
3
+ <p>Version 1.0.3 · In force from 2026-10-24</p>
4
4
  <p>This notice explains what we do with personal data when you use Ever Gauzy Cloud and the websites,
5
5
  applications and application programming interfaces we make available at <a href="https://gauzy.co">gauzy.co</a>
6
6
  (together, the &quot;<strong>Service</strong>&quot;). It tells you what we collect, why, who else sees it, how long we keep it,
@@ -249,9 +249,14 @@ your result, and that is the end of it. If we ever want that to change, it will
249
249
  choose, described before you choose it.</li>
250
250
  <li><strong>We do not run advertising inside the Service.</strong> No third-party advertising, no behavioural ad
251
251
  targeting, no cross-site advertising identifiers in the product.</li>
252
- <li><strong>We do not record what you type.</strong> Where a product measures keyboard and mouse activity, it counts
253
- events over a period. <strong>There is no keylogger in our software. The content of your keystrokes is never
254
- captured, stored or transmitted.</strong></li>
252
+ <li><strong>We do not record what you type, except in one Ever Gauzy feature that is off by default.</strong> The web
253
+ application and the desktop timer at most count keyboard and mouse events over a period; they never record
254
+ which key was pressed. <strong>Where an organisation switches on keyboard and mouse tracking for the Ever Gauzy
255
+ background agent, the agent records the code of each key pressed, in the order pressed, and the screen
256
+ coordinates of mouse movements, and sends them to our servers, which store them with the activity record;
257
+ the API's request log may also keep a copy.</strong> Key codes identify physical keys rather than the characters
258
+ a keyboard layout produces, but a sequence of them can reveal what was typed, including passwords. The
259
+ annex to this notice describes the feature and how to keep it off.</li>
255
260
  <li><strong>We do not ask for special-category data</strong> — health, racial or ethnic origin, religious or philosophical
256
261
  beliefs, political opinions, trade union membership, sex life or sexual orientation, genetic or biometric
257
262
  data. There are no fields for it, we do not infer it, and we do not want it. The one honest caveat is
@@ -512,8 +517,9 @@ the background, and your employer can configure it so that you cannot quit it or
512
517
  screenshots and activity levels those platforms already took are imported into the workspace.</li>
513
518
  </ul>
514
519
  <h3 id="the-capture-features-one-by-one" tabindex="-1">The capture features, one by one</h3>
515
- <p>Every row below is off unless your organisation switches it on, and several of them require a plugin your
516
- organisation has to install before the setting exists at all.</p>
520
+ <p>Most rows below are off until your organisation switches them on, and several of them require a plugin your
521
+ organisation has to install before the setting exists at all. <strong>Two are not: screenshots are on by default,
522
+ and application and website usage is recorded whenever tracking runs</strong>, with no setting that turns it off.</p>
517
523
  <table>
518
524
  <thead>
519
525
  <tr>
@@ -534,23 +540,28 @@ organisation has to install before the setting exists at all.</p>
534
540
  <td>An organisation setting, with a per-person override</td>
535
541
  </tr>
536
542
  <tr>
543
+ <td>Keystroke sequence, background agent</td>
544
+ <td><strong>The code of every key pressed, in the order pressed, and the start and end screen coordinates of each mouse movement</strong>, sent to our servers and stored with the activity record; the API's request log may keep a copy</td>
545
+ <td>Recorded by the background agent whenever its keyboard and mouse tracking is on — the same setting as the activity rate, off by default</td>
546
+ </tr>
547
+ <tr>
537
548
  <td>Application usage</td>
538
549
  <td>The names of the applications in use and the titles of their windows, with the time spent in each</td>
539
- <td>An organisation setting</td>
550
+ <td>Recorded whenever tracking runs; no setting turns it off</td>
540
551
  </tr>
541
552
  <tr>
542
553
  <td>Website usage</td>
543
554
  <td>The web addresses visited, together with page details we fetch for them — title, description and preview image</td>
544
- <td>An organisation setting</td>
555
+ <td>Recorded whenever tracking runs; no setting turns it off</td>
545
556
  </tr>
546
557
  <tr>
547
558
  <td>Screenshots</td>
548
- <td>Images of the screen at full resolution, with a thumbnail, the list of applications visible in the image, and the time slot it belongs to. Either the active display only or <strong>every connected display</strong></td>
549
- <td>An organisation setting, with a per-person override</td>
559
+ <td>Images of the screen at full resolution, with a thumbnail, the list of applications visible in the image, and the time slot it belongs to. Either the active display only or <strong>every connected display</strong>, which is the default</td>
560
+ <td><strong>On by default.</strong> An organisation setting, with a per-person override</td>
550
561
  </tr>
551
562
  <tr>
552
563
  <td>Randomised capture</td>
553
- <td>The same screenshots, taken at unpredictable moments within the interval instead of on a fixed schedule</td>
564
+ <td>The same screenshots, taken at unpredictable moments instead of on a fixed schedule. In the desktop timer each capture falls within the interval; in the background agent the gap is drawn from 1, 3, 5 or 10 minutes whatever the interval, so captures can be more frequent than the interval suggests</td>
554
565
  <td>A separate setting on top of screenshots</td>
555
566
  </tr>
556
567
  <tr>
@@ -610,8 +621,12 @@ organisation has to install before the setting exists at all.</p>
610
621
  expressed against a maximum</strong>. It is not a measure of thinking, reading, attending a meeting, or doing
611
622
  anything a keyboard is not involved in — and a high figure is not evidence of good work any more than a low
612
623
  one is evidence of bad work.</p>
613
- <p>Nothing about the content of the input is captured. <strong>What is typed is not recorded</strong>, in any field, in any
614
- application, at any setting. The product counts that a key was pressed; it does not know which key.</p>
624
+ <p>The desktop timer counts input; it does not know which key was pressed. <strong>The background agent is different
625
+ when its keyboard and mouse tracking is on: it records the code of every key pressed, in the order pressed,
626
+ together with mouse movement coordinates, and sends them to our servers, which store them with the activity
627
+ record. The API's request log may also keep a copy.</strong> Key codes identify physical keys rather than the characters a
628
+ keyboard layout produces, but a sequence of them can reveal what was typed, including passwords. With that
629
+ setting off, which is the default, the agent records no keyboard or mouse data at all.</p>
615
630
  <h3 id="where-captured-material-goes" tabindex="-1">Where captured material goes</h3>
616
631
  <ul>
617
632
  <li><strong>It is stored as an object</strong> — the image, audio or video file, plus a thumbnail for images — and linked
@@ -634,17 +649,25 @@ activity counting.</li>
634
649
  even where the organisation has them on.</li>
635
650
  <li><strong>An enforcement switch.</strong> An organisation can mark its timer policy as enforced, which makes the
636
651
  organisation-level settings override individual ones. Turning this on removes the per-person exceptions.</li>
637
- <li><strong>Capture frequency</strong>, and whether the interval is fixed or randomised.</li>
652
+ <li><strong>Capture frequency</strong>, and whether the interval is fixed or randomised. The organisation's values reach the
653
+ desktop timer only while the timer policy is enforced; the background agent uses its own interval.</li>
638
654
  <li><strong>Active display only, instead of every display.</strong> A person with three monitors is otherwise captured
639
655
  three times over.</li>
640
- <li><strong>Blurring of captured images</strong>, so that a screenshot shows the shape of the work without its contents.</li>
641
- <li><strong>Keyboard and mouse counting off</strong>, independently of screenshots.</li>
656
+ <li><strong>No blurring.</strong> Ever Gauzy does not blur or mask captured images: a screenshot shows everything that
657
+ was on the screen. Switching screenshots off, or capturing the active display only, are the controls that
658
+ reduce what is seen.</li>
659
+ <li><strong>Keyboard and mouse counting off</strong>, independently of screenshots. In the background agent this also stops
660
+ the keystroke sequence described above.</li>
642
661
  <li><strong>Capture while asleep off</strong>, so that nothing is taken while the device is locked.</li>
643
662
  <li><strong>The inactivity limit and the activity-proof window</strong>, which decide when a person is treated as idle and
644
663
  how long they have to confirm otherwise, and whether idle time is removed from the timesheet.</li>
645
- <li><strong>Retention</strong>, so that captures are deleted automatically after the period your organisation sets.</li>
646
- <li><strong>Deletion of an individual capture.</strong> A single screenshot can be deleted, along with its thumbnail —
647
- this is the route for a capture that caught something it should not have.</li>
664
+ <li><strong>No automatic retention period.</strong> Ever Gauzy has no setting that deletes captures after a period;
665
+ they are kept until they are deleted. A retention period your organisation decides on is applied by
666
+ deleting on that schedule, or by asking us to.</li>
667
+ <li><strong>Deletion of an individual capture.</strong> A single screenshot can be deleted — this is the route for a capture
668
+ that caught something it should not have. In the web application that deletion hides the screenshot at
669
+ once but is a soft deletion: the image and its thumbnail stay in storage until the record is permanently
670
+ deleted, which we do on request.</li>
648
671
  <li><strong>Visibility to the person captured</strong>, so that people can see their own screenshots, their own activity
649
672
  figures and their own time entries.</li>
650
673
  <li><strong>Agent exit and sign-out.</strong> Two settings decide whether a person can quit the background agent and
@@ -704,13 +727,17 @@ the consent position for each, in our <a href="https://gauzy.co/cookies">Cookie
704
727
  which sees the IP address and browser of whoever downloads them.</li>
705
728
  </ul>
706
729
  <h3 id="retention-inside-a-workspace" tabindex="-1">Retention inside a workspace</h3>
707
- <p>We apply the retention your organisation configures. <strong>Captured media is the category to set deliberately</strong>:
730
+ <p>Ever Gauzy has no retention setting for captured media today, so nothing is deleted automatically:
731
+ captures are kept until your organisation deletes them, or asks us to. <strong>Captured media is the category to
732
+ decide deliberately</strong>:
708
733
  screenshots, webcam stills, audio and video accumulate quickly, they are the most intrusive thing the
709
734
  product holds, and keeping them longer than the purpose needs is the failure a supervisory authority looks
710
735
  for first. Timesheets and time logs usually need to outlive the captures behind them, because they feed
711
736
  payroll and invoicing, and they can be kept while the media is deleted.</p>
712
- <p>Deleting a workspace record deletes it from our live systems immediately; the backup position is in the
713
- retention section above.</p>
737
+ <p>Deleting a screenshot, a time slot or a time entry in the web application hides it at once, but it is a soft
738
+ deletion: the record, and for a screenshot its stored image and thumbnail, stay on our live systems until they
739
+ are permanently deleted. Ask us at privacy@ever.co and we will delete them permanently. The backup position
740
+ is in the retention section above.</p>
714
741
  <h3 id="if-you-are-being-monitored-with-ever-gauzy-read-this" tabindex="-1">If you are being monitored with Ever Gauzy, read this</h3>
715
742
  <p><strong>Your employer chose every setting described in this annex. We did not, and we cannot change one for
716
743
  them.</strong></p>
@@ -724,11 +751,13 @@ answer before capture starts, not after.</li>
724
751
  how often they are taken, whether they are random, whether every monitor is captured, whether capture
725
752
  continues while the machine is locked, and whether the camera, the microphone or screen recording are in
726
753
  use. Those last three are separate features and require a separate decision by your employer.</li>
727
- <li><strong>What is typed is never captured.</strong> There is no keylogger in this software.</li>
754
+ <li><strong>Ask whether keyboard and mouse tracking is on in the background agent.</strong> With it on, the agent records
755
+ which keys you press, in order — enough to reconstruct much of what you type. With it off, which is the
756
+ default, it records no keyboard or mouse data. The desktop timer does not record which keys you press.</li>
728
757
  <li><strong>You may be able to see your own data in the product</strong>, where your employer has enabled that. If you can
729
758
  see your own screenshots, you can check what is being taken rather than imagine it.</li>
730
759
  <li><strong>A capture that caught something private can be deleted.</strong> Your employer can delete an individual
731
- screenshot. Ask them to.</li>
760
+ screenshot. Ask them to, and to make sure it is deleted permanently rather than only hidden.</li>
732
761
  <li><strong>If you believe you are being monitored covertly</strong> — that capture is running and you were never told —
733
762
  write to abuse@ever.co. You do not need to be our customer, we keep the identity of a reporter
734
763
  confidential, and the enforcement section of our <a href="https://gauzy.co/aup">Acceptable Use Policy</a> sets out
@@ -1070,7 +1099,7 @@ policy.</p>
1070
1099
  agreement ends, whichever comes first. If you are one of their people and you want their data about you
1071
1100
  deleted sooner, ask them — see the section on your rights, which explains how we route that.</p>
1072
1101
  <h3 id="what-delete-means-here" tabindex="-1">What &quot;delete&quot; means here</h3>
1073
- <p>Deletion is applied to live systems straight away. Backup copies are not individually edited — doing so
1102
+ <p>Deletion is applied to live systems straight away, with one exception in Ever Gauzy: deleting a screenshot, a time slot or a time entry in the web application is a soft deletion, which hides it at once but leaves the record, and for a screenshot its stored image and thumbnail, on our live systems until it is permanently deleted. The product annex explains it, and we delete permanently on request. Backup copies are not individually edited — doing so
1074
1103
  would defeat what a backup is for — so a deleted record persists in backups until that backup ages out on
1075
1104
  the cycle above, at most 30 days. During that window the data is not used for anything, and <strong>we do not
1076
1105
  restore a backup to bring back data someone asked us to delete</strong>; a backup is restored only to recover a
@@ -1323,7 +1352,7 @@ would like to know at privacy@ever.co so we can reconsider carrying it.</p>
1323
1352
  <p>This policy changes when the Service changes, when we engage or replace a provider, or when the law moves.
1324
1353
  We would rather update it than let it drift out of date and quietly stop being true.</p>
1325
1354
  <p>Every version carries a version number and the date it takes effect, shown at the top of the page. <strong>This
1326
- is version 1.0.2, in force from 2026-08-02.</strong></p>
1355
+ is version 1.0.3, in force from 2026-10-24.</strong></p>
1327
1356
  <h3 id="how-we-tell-you" tabindex="-1">How we tell you</h3>
1328
1357
  <ul>
1329
1358
  <li><strong>Minor changes</strong> — clarifying wording, correcting a mistake, adding a provider of a kind already
@@ -1361,6 +1390,6 @@ policy will say so and will give the designated office's contact details.</p>
1361
1390
  <p>If your question is about personal data held inside one of our customers' workspaces, that customer is the
1362
1391
  controller and the request goes to them — see the routing paragraph in the section on your rights. Write to
1363
1392
  us anyway if you are unsure, and we will tell you who to ask.</p>
1364
- <p>This document is version 1.0.2 of the Privacy Policy for
1365
- <a href="https://gauzy.co">gauzy.co</a>, in force from 2026-08-02. Earlier versions, with the
1393
+ <p>This document is version 1.0.3 of the Privacy Policy for
1394
+ <a href="https://gauzy.co">gauzy.co</a>, in force from 2026-10-24. Earlier versions, with the
1366
1395
  dates they applied, are at <a href="https://gauzy.co/privacy">https://gauzy.co/privacy</a>.</p>