@ever-co/legal 0.4.0 → 0.5.0
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.
- package/dist/content/dpa/ever-async/en.html +16 -11
- package/dist/content/dpa/ever-async/en.json +4 -4
- package/dist/content/dpa/ever-demand/en.html +16 -11
- package/dist/content/dpa/ever-demand/en.json +4 -4
- package/dist/content/dpa/ever-rec/en.html +16 -11
- package/dist/content/dpa/ever-rec/en.json +4 -4
- package/dist/content/dpa/ever-teams/en.html +16 -11
- package/dist/content/dpa/ever-teams/en.json +4 -4
- package/dist/content/dpa/ever-works/en.html +16 -11
- package/dist/content/dpa/ever-works/en.json +4 -4
- package/dist/content/dpa/gauzy/en.html +27 -18
- package/dist/content/dpa/gauzy/en.json +4 -4
- package/dist/content/dpa/githands/en.html +16 -11
- package/dist/content/dpa/githands/en.json +4 -4
- package/dist/content/dpa/hust/en.html +16 -11
- package/dist/content/dpa/hust/en.json +4 -4
- package/dist/content/dpia/gauzy/en.html +453 -0
- package/dist/content/dpia/gauzy/en.json +97 -0
- package/dist/content/privacy/gauzy/en.html +57 -28
- package/dist/content/privacy/gauzy/en.json +4 -4
- package/dist/content/security/gauzy/en.html +3 -3
- package/dist/content/security/gauzy/en.json +4 -4
- package/dist/content/tos/githands/en.html +6 -6
- package/dist/content/tos/githands/en.json +3 -3
- package/dist/index.json +128 -32
- package/package.json +2 -2
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
<h1 id="data-processing-addendum" tabindex="-1">Data Processing Addendum</h1>
|
|
2
2
|
<p><strong>Ever Gauzy</strong> — <a href="https://gauzy.co">gauzy.co</a></p>
|
|
3
|
-
<p>Version 1.0.
|
|
3
|
+
<p>Version 1.0.3 · In force from 2026-10-24</p>
|
|
4
4
|
<p>This Data Processing Addendum ("<strong>Addendum</strong>") governs our processing of personal data <strong>on your behalf</strong>
|
|
5
5
|
when you use Ever Gauzy Cloud. It is agreed between you and <strong>Ever Technologies LTD</strong>, a company
|
|
6
6
|
registered in Bulgaria under company number 204599535, with its registered office
|
|
@@ -36,7 +36,7 @@ security and audit logs, and website analytics — which our
|
|
|
36
36
|
work, where you have enabled the features that capture it. Depending on the product and your
|
|
37
37
|
configuration this can include periodic screenshots and their thumbnails, screen recordings, webcam
|
|
38
38
|
stills, audio recordings, the names of applications and windows in use, visited website addresses and
|
|
39
|
-
their metadata, keyboard and mouse <strong>activity rates and event counts</strong> (
|
|
39
|
+
their metadata, keyboard and mouse <strong>activity rates and event counts</strong> (and, where keyboard and mouse tracking is on in the Ever Gauzy background agent, the sequence of key codes pressed and the screen coordinates of mouse movements), idle
|
|
40
40
|
time, time entries, and location where that feature is switched on. The product annex lists exactly what
|
|
41
41
|
Ever Gauzy can capture and what each control does.</li>
|
|
42
42
|
<li><strong>Monitored Individual</strong> — an employee, worker, contractor or other person whose Monitoring Data is
|
|
@@ -277,7 +277,8 @@ covert monitoring of workers carries criminal exposure as well as a regulatory o
|
|
|
277
277
|
<li>You will not send us Special Category Data, or personal data relating to criminal convictions and
|
|
278
278
|
offences, through any feature that is not designed to hold it. Where such data is incidentally caught —
|
|
279
279
|
a health portal visible in a screenshot, for example — you remain the controller of it, and you will use
|
|
280
|
-
the exclusion, masking, blur and pause controls the Service provides to reduce that risk
|
|
280
|
+
whichever of the exclusion, masking, blur and pause controls the Service provides to reduce that risk —
|
|
281
|
+
and where it provides none of them, the capture settings themselves.</li>
|
|
281
282
|
<li>You will not use the Service to process personal data of children where the product is not offered for
|
|
282
283
|
that purpose.</li>
|
|
283
284
|
</ul>
|
|
@@ -378,8 +379,9 @@ Service offers it;</li>
|
|
|
378
379
|
<li>keeping administrator credentials, API keys and integration tokens secret, and rotating them when a
|
|
379
380
|
person with access leaves;</li>
|
|
380
381
|
<li>the security of the devices your people use, including the devices on which any desktop agent runs; and</li>
|
|
381
|
-
<li><strong>the capture
|
|
382
|
-
taken is the strongest security measure available for
|
|
382
|
+
<li><strong>the capture settings you choose</strong>, including any retention, blur, masking, exclusion and pause
|
|
383
|
+
settings the product provides — a screenshot never taken is the strongest security measure available for
|
|
384
|
+
it, and that switch is on your side.</li>
|
|
383
385
|
</ul>
|
|
384
386
|
<p>Our <a href="https://gauzy.co/security">Security page</a> sets out this shared responsibility split in full.</p>
|
|
385
387
|
<h2 id="if-there-is-a-personal-data-breach" tabindex="-1">If there is a personal data breach</h2>
|
|
@@ -612,22 +614,24 @@ auditors. It contains:</p>
|
|
|
612
614
|
<ul>
|
|
613
615
|
<li><strong>The data categories captured, feature by feature</strong> — what each capture feature records, precisely, and
|
|
614
616
|
what it does not. Including the explicit negatives, because a negative commitment is worth more in an
|
|
615
|
-
assessment than a positive claim:
|
|
616
|
-
you configure.</li>
|
|
617
|
+
assessment than a positive claim: for example that the web application captures nothing, that the desktop timer never records which key was pressed, and that no device location is captured during time tracking.</li>
|
|
617
618
|
<li><strong>Capture frequency ranges</strong> — the minimum, maximum and default interval for every capture feature, and
|
|
618
619
|
what the interval means in records per person per day.</li>
|
|
619
620
|
<li><strong>Retention windows, as actual numbers.</strong> Our ceilings, our defaults, the range you can configure inside
|
|
620
|
-
them, and when the automatic
|
|
621
|
+
them, and when any automatic deletion runs — or, where the product has no automatic deletion, a plain
|
|
622
|
+
statement that it has none.</li>
|
|
621
623
|
<li><strong>Storage regions</strong> — where each category of Customer Personal Data is stored and processed, and where
|
|
622
624
|
backups are held.</li>
|
|
623
625
|
<li><strong>The Sub-processor list</strong> for the product, in the three tiers described in the sub-processing section,
|
|
624
626
|
with the categories of data each one receives.</li>
|
|
625
627
|
<li><strong>The transfer mechanism</strong> relied on for each Restricted Transfer, and the assessment behind it.</li>
|
|
626
628
|
<li><strong>The security measures</strong> in Schedule 2, mapped to the risks they address.</li>
|
|
627
|
-
<li><strong>A lever-to-risk map</strong> — every privacy control the product offers
|
|
628
|
-
|
|
629
|
-
|
|
630
|
-
|
|
629
|
+
<li><strong>A lever-to-risk map</strong> — every privacy control the product offers, set against the specific risk each one
|
|
630
|
+
mitigates and the residual risk it leaves, <strong>and the controls it does not offer</strong>. Depending on the product
|
|
631
|
+
those controls can include defaults that are off, per-user and per-team disable, the capture interval,
|
|
632
|
+
on-device blur, excluded applications and sites, masking, per-user pause, a retention ceiling, data-access
|
|
633
|
+
parity for the monitored person, and an audit log of privileged access; the pack says which of them the
|
|
634
|
+
product actually has.</li>
|
|
631
635
|
</ul>
|
|
632
636
|
<p><strong>It is free, it is public, and it does not require a sales conversation to obtain.</strong> Ask at
|
|
633
637
|
privacy@ever.co if you cannot find the current version, or want it in a form your own template can
|
|
@@ -955,7 +959,10 @@ work-related.</li>
|
|
|
955
959
|
enabled.</li>
|
|
956
960
|
<li><strong>Screen recordings</strong> — video of the screen, where enabled.</li>
|
|
957
961
|
<li><strong>Activity telemetry</strong> — counts and rates of keyboard and mouse events, an aggregate activity score,
|
|
958
|
-
idle and inactivity periods, and captures taken while a device sleeps where that setting is on
|
|
962
|
+
idle and inactivity periods, and captures taken while a device sleeps where that setting is on. Where the
|
|
963
|
+
background agent's keyboard and mouse tracking is on, also <strong>the sequence of key codes pressed and the
|
|
964
|
+
screen coordinates of mouse movements</strong>, stored with the activity record and possibly also in the API's
|
|
965
|
+
request log.</li>
|
|
959
966
|
<li><strong>Application and browsing telemetry</strong> — application names, window titles, visited URLs and fetched page
|
|
960
967
|
metadata, and where a browser integration is connected, tab counts and private-browsing indicators.</li>
|
|
961
968
|
<li><strong>Location</strong> — where enabled.</li>
|
|
@@ -982,9 +989,11 @@ that the description forms part of the contract, and so you can rely on them in
|
|
|
982
989
|
video independently.</li>
|
|
983
990
|
<li><strong>Frequency</strong> — how often a capture is taken, and whether the interval is fixed or randomised.</li>
|
|
984
991
|
<li><strong>Display scope</strong> — all connected displays, or only the active one.</li>
|
|
985
|
-
<li><strong>Blurring</strong> —
|
|
992
|
+
<li><strong>Blurring</strong> — not available: captured images are stored as they were taken.</li>
|
|
986
993
|
<li><strong>Idle and inactivity handling</strong> — including whether idle time is removed.</li>
|
|
987
|
-
<li><strong>Retention</strong> —
|
|
994
|
+
<li><strong>Retention</strong> — not available as a setting: captured media is kept until it is deleted, by you or by us on
|
|
995
|
+
your instruction. Deletion in the web application is a soft deletion until the record is permanently
|
|
996
|
+
deleted. The DPIA support pack sets out the detail.</li>
|
|
988
997
|
<li><strong>Visibility to the monitored person</strong> — whether an individual can see the data captured about them.</li>
|
|
989
998
|
<li><strong>Agent behaviour</strong> — including whether the monitored person may exit or sign out of the background
|
|
990
999
|
agent.</li>
|
|
@@ -1088,7 +1097,7 @@ and the law still protects them; and</li>
|
|
|
1088
1097
|
</tr>
|
|
1089
1098
|
<tr>
|
|
1090
1099
|
<td>Activity data, where the product provides it and you enable it</td>
|
|
1091
|
-
<td>Counts and rates of keyboard and mouse events, idle and away time, the names of applications and window titles in use, websites and page addresses visited, browser tab counts, private-browsing flags, presence and derived activity scores. <strong>The content of what is typed is not captured
|
|
1100
|
+
<td>Counts and rates of keyboard and mouse events, idle and away time, the names of applications and window titles in use, websites and page addresses visited, browser tab counts, private-browsing flags, presence and derived activity scores. <strong>The content of what is typed is not captured, except that the Ever Gauzy background agent, where keyboard and mouse tracking is on, records the sequence of key codes pressed and mouse coordinates, as the product annex describes</strong></td>
|
|
1092
1101
|
</tr>
|
|
1093
1102
|
<tr>
|
|
1094
1103
|
<td>Captured media, where the product provides it and you enable it</td>
|
|
@@ -1831,6 +1840,6 @@ are established. <strong>Our own authority is the Commission for Personal Data P
|
|
|
1831
1840
|
<a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. A data subject can
|
|
1832
1841
|
complain to the authority in their own country as well, and neither of us can require them to come through
|
|
1833
1842
|
us first.</p>
|
|
1834
|
-
<p>This document is version 1.0.
|
|
1835
|
-
<a href="https://gauzy.co">gauzy.co</a>, in force from 2026-
|
|
1843
|
+
<p>This document is version 1.0.3 of the Data Processing Addendum for
|
|
1844
|
+
<a href="https://gauzy.co">gauzy.co</a>, in force from 2026-10-24. Earlier versions, with the
|
|
1836
1845
|
dates they applied, are at <a href="https://gauzy.co/dpa">https://gauzy.co/dpa</a>.</p>
|