@ever-co/legal 0.1.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.
Files changed (146) hide show
  1. package/dist/content/aup/ever-corporate/en.html +667 -0
  2. package/dist/content/aup/ever-corporate/en.json +302 -0
  3. package/dist/content/aup/ever-demand/en.html +802 -0
  4. package/dist/content/aup/ever-demand/en.json +339 -0
  5. package/dist/content/aup/ever-rec/en.html +667 -0
  6. package/dist/content/aup/ever-rec/en.json +302 -0
  7. package/dist/content/aup/ever-teams/en.html +667 -0
  8. package/dist/content/aup/ever-teams/en.json +302 -0
  9. package/dist/content/aup/ever-works/en.html +667 -0
  10. package/dist/content/aup/ever-works/en.json +302 -0
  11. package/dist/content/aup/everiq/en.html +726 -0
  12. package/dist/content/aup/everiq/en.json +319 -0
  13. package/dist/content/aup/gauzy/en.html +715 -0
  14. package/dist/content/aup/gauzy/en.json +327 -0
  15. package/dist/content/aup/githands/en.html +864 -0
  16. package/dist/content/aup/githands/en.json +363 -0
  17. package/dist/content/aup/hust/en.html +781 -0
  18. package/dist/content/aup/hust/en.json +347 -0
  19. package/dist/content/aup/traduora/en.html +667 -0
  20. package/dist/content/aup/traduora/en.json +302 -0
  21. package/dist/content/cookies/ever-corporate/en.html +493 -0
  22. package/dist/content/cookies/ever-corporate/en.json +193 -0
  23. package/dist/content/cookies/ever-demand/en.html +633 -0
  24. package/dist/content/cookies/ever-demand/en.json +226 -0
  25. package/dist/content/cookies/ever-rec/en.html +564 -0
  26. package/dist/content/cookies/ever-rec/en.json +206 -0
  27. package/dist/content/cookies/ever-teams/en.html +549 -0
  28. package/dist/content/cookies/ever-teams/en.json +222 -0
  29. package/dist/content/cookies/ever-tech/en.html +469 -0
  30. package/dist/content/cookies/ever-tech/en.json +177 -0
  31. package/dist/content/cookies/ever-works/en.html +618 -0
  32. package/dist/content/cookies/ever-works/en.json +202 -0
  33. package/dist/content/cookies/everiq/en.html +437 -0
  34. package/dist/content/cookies/everiq/en.json +185 -0
  35. package/dist/content/cookies/gauzy/en.html +490 -0
  36. package/dist/content/cookies/gauzy/en.json +206 -0
  37. package/dist/content/cookies/githands/en.html +618 -0
  38. package/dist/content/cookies/githands/en.json +210 -0
  39. package/dist/content/cookies/hust/en.html +622 -0
  40. package/dist/content/cookies/hust/en.json +210 -0
  41. package/dist/content/cookies/traduora/en.html +580 -0
  42. package/dist/content/cookies/traduora/en.json +193 -0
  43. package/dist/content/dpa/ever-demand/en.html +1804 -0
  44. package/dist/content/dpa/ever-demand/en.json +628 -0
  45. package/dist/content/dpa/ever-rec/en.html +1963 -0
  46. package/dist/content/dpa/ever-rec/en.json +652 -0
  47. package/dist/content/dpa/ever-teams/en.html +1918 -0
  48. package/dist/content/dpa/ever-teams/en.json +648 -0
  49. package/dist/content/dpa/ever-works/en.html +1801 -0
  50. package/dist/content/dpa/ever-works/en.json +624 -0
  51. package/dist/content/dpa/gauzy/en.html +1836 -0
  52. package/dist/content/dpa/gauzy/en.json +632 -0
  53. package/dist/content/dpa/githands/en.html +1808 -0
  54. package/dist/content/dpa/githands/en.json +624 -0
  55. package/dist/content/dpa/hust/en.html +1804 -0
  56. package/dist/content/dpa/hust/en.json +632 -0
  57. package/dist/content/privacy/ever-corporate/en.html +1184 -0
  58. package/dist/content/privacy/ever-corporate/en.json +352 -0
  59. package/dist/content/privacy/ever-demand/en.html +1234 -0
  60. package/dist/content/privacy/ever-demand/en.json +364 -0
  61. package/dist/content/privacy/ever-rec/en.html +1250 -0
  62. package/dist/content/privacy/ever-rec/en.json +360 -0
  63. package/dist/content/privacy/ever-teams/en.html +1238 -0
  64. package/dist/content/privacy/ever-teams/en.json +368 -0
  65. package/dist/content/privacy/ever-tech/en.html +1127 -0
  66. package/dist/content/privacy/ever-tech/en.json +352 -0
  67. package/dist/content/privacy/ever-works/en.html +1284 -0
  68. package/dist/content/privacy/ever-works/en.json +364 -0
  69. package/dist/content/privacy/everiq/en.html +1172 -0
  70. package/dist/content/privacy/everiq/en.json +328 -0
  71. package/dist/content/privacy/gauzy/en.html +1281 -0
  72. package/dist/content/privacy/gauzy/en.json +356 -0
  73. package/dist/content/privacy/githands/en.html +1393 -0
  74. package/dist/content/privacy/githands/en.json +380 -0
  75. package/dist/content/privacy/hust/en.html +1359 -0
  76. package/dist/content/privacy/hust/en.json +368 -0
  77. package/dist/content/privacy/traduora/en.html +1146 -0
  78. package/dist/content/privacy/traduora/en.json +336 -0
  79. package/dist/content/refund/ever-works/en.html +595 -0
  80. package/dist/content/refund/ever-works/en.json +336 -0
  81. package/dist/content/refund/gauzy/en.html +595 -0
  82. package/dist/content/refund/gauzy/en.json +336 -0
  83. package/dist/content/refund/githands/en.html +647 -0
  84. package/dist/content/refund/githands/en.json +361 -0
  85. package/dist/content/refund/hust/en.html +595 -0
  86. package/dist/content/refund/hust/en.json +336 -0
  87. package/dist/content/security/ever-demand/en.html +900 -0
  88. package/dist/content/security/ever-demand/en.json +425 -0
  89. package/dist/content/security/ever-rec/en.html +768 -0
  90. package/dist/content/security/ever-rec/en.json +380 -0
  91. package/dist/content/security/ever-teams/en.html +768 -0
  92. package/dist/content/security/ever-teams/en.json +380 -0
  93. package/dist/content/security/ever-works/en.html +768 -0
  94. package/dist/content/security/ever-works/en.json +380 -0
  95. package/dist/content/security/gauzy/en.html +768 -0
  96. package/dist/content/security/gauzy/en.json +380 -0
  97. package/dist/content/security/githands/en.html +876 -0
  98. package/dist/content/security/githands/en.json +421 -0
  99. package/dist/content/security/hust/en.html +768 -0
  100. package/dist/content/security/hust/en.json +380 -0
  101. package/dist/content/subprocessors/ever-corporate/en.html +382 -0
  102. package/dist/content/subprocessors/ever-corporate/en.json +158 -0
  103. package/dist/content/subprocessors/ever-demand/en.html +452 -0
  104. package/dist/content/subprocessors/ever-demand/en.json +154 -0
  105. package/dist/content/subprocessors/ever-rec/en.html +439 -0
  106. package/dist/content/subprocessors/ever-rec/en.json +154 -0
  107. package/dist/content/subprocessors/ever-teams/en.html +477 -0
  108. package/dist/content/subprocessors/ever-teams/en.json +154 -0
  109. package/dist/content/subprocessors/ever-tech/en.html +335 -0
  110. package/dist/content/subprocessors/ever-tech/en.json +141 -0
  111. package/dist/content/subprocessors/ever-works/en.html +551 -0
  112. package/dist/content/subprocessors/ever-works/en.json +154 -0
  113. package/dist/content/subprocessors/everiq/en.html +296 -0
  114. package/dist/content/subprocessors/everiq/en.json +149 -0
  115. package/dist/content/subprocessors/gauzy/en.html +603 -0
  116. package/dist/content/subprocessors/gauzy/en.json +154 -0
  117. package/dist/content/subprocessors/githands/en.html +465 -0
  118. package/dist/content/subprocessors/githands/en.json +154 -0
  119. package/dist/content/subprocessors/hust/en.html +482 -0
  120. package/dist/content/subprocessors/hust/en.json +154 -0
  121. package/dist/content/subprocessors/traduora/en.html +362 -0
  122. package/dist/content/subprocessors/traduora/en.json +154 -0
  123. package/dist/content/tos/ever-corporate/en.html +973 -0
  124. package/dist/content/tos/ever-corporate/en.json +517 -0
  125. package/dist/content/tos/ever-demand/en.html +1598 -0
  126. package/dist/content/tos/ever-demand/en.json +783 -0
  127. package/dist/content/tos/ever-rec/en.html +1524 -0
  128. package/dist/content/tos/ever-rec/en.json +771 -0
  129. package/dist/content/tos/ever-teams/en.html +1551 -0
  130. package/dist/content/tos/ever-teams/en.json +779 -0
  131. package/dist/content/tos/ever-tech/en.html +762 -0
  132. package/dist/content/tos/ever-tech/en.json +421 -0
  133. package/dist/content/tos/ever-works/en.html +1552 -0
  134. package/dist/content/tos/ever-works/en.json +787 -0
  135. package/dist/content/tos/everiq/en.html +781 -0
  136. package/dist/content/tos/everiq/en.json +429 -0
  137. package/dist/content/tos/gauzy/en.html +1440 -0
  138. package/dist/content/tos/gauzy/en.json +755 -0
  139. package/dist/content/tos/githands/en.html +1542 -0
  140. package/dist/content/tos/githands/en.json +779 -0
  141. package/dist/content/tos/hust/en.html +1566 -0
  142. package/dist/content/tos/hust/en.json +787 -0
  143. package/dist/content/tos/traduora/en.html +1238 -0
  144. package/dist/content/tos/traduora/en.json +646 -0
  145. package/dist/index.json +26991 -0
  146. package/package.json +52 -0
@@ -0,0 +1,1238 @@
1
+ <h1 id="privacy-policy" tabindex="-1">Privacy Policy</h1>
2
+ <p><strong>Ever Teams</strong> — <a href="https://ever.team">ever.team</a></p>
3
+ <p>Version 1.0.0 · In force from 2026-08-02</p>
4
+ <p>This notice explains what we do with personal data when you use Ever Teams Cloud and the websites,
5
+ applications and application programming interfaces we make available at <a href="https://ever.team">ever.team</a>
6
+ (together, the &quot;<strong>Service</strong>&quot;). It tells you what we collect, why, who else sees it, how long we keep it,
7
+ and what you can ask us to do about it.</p>
8
+ <p>We have written it to be read rather than to be defended. Where something is uncomfortable — data we hold
9
+ that you never gave us, or data your employer decides to collect through our software — we say so plainly
10
+ instead of burying it in a list.</p>
11
+ <h2 id="what-this-notice-covers" tabindex="-1">What this notice covers</h2>
12
+ <ul>
13
+ <li>The website at <a href="https://ever.team">ever.team</a> and the pages served from it.</li>
14
+ <li>The Ever Teams Cloud web application, together with any desktop application, mobile application or
15
+ browser extension we publish for it.</li>
16
+ <li>The application programming interfaces and integrations we operate for it.</li>
17
+ <li>The emails, notifications and support conversations that go with it.</li>
18
+ </ul>
19
+ <p>A product-specific annex appears later in this notice. It adds detail for Ever Teams — what it
20
+ actually collects, what is switched off by default, and which controls exist. It sits on top of this
21
+ notice rather than instead of it, and where it is more specific about Ever Teams, the annex governs.</p>
22
+ <h2 id="what-this-notice-does-not-cover" tabindex="-1">What this notice does not cover</h2>
23
+ <p><strong>Other companies' products.</strong> Other companies operate their own websites, products and services, and
24
+ publish their own privacy notices. This notice covers only what is listed above. If a service is not on
25
+ that list, this notice does not apply to it — whatever it looks like, and whoever links to it.</p>
26
+ <p><strong>Software you run yourself.</strong> Some of our software is published as open source and can be installed on
27
+ your own infrastructure. <strong>If you run your own deployment, you are the controller of the personal data in
28
+ it — not us.</strong> You choose its hosting, its storage, its email provider and every other component. We have
29
+ no access to that data, we do not process it, we are not your processor for it, and nothing in this notice
30
+ describes it. Telling your own users what happens in your deployment is your job, not ours.</p>
31
+ <p><strong>Sites we link to.</strong> The Service links out to third-party websites and services. Once you follow a link
32
+ away from us, the operator of that site decides what happens to your data. We do not control those sites,
33
+ we do not receive what you do on them, and we are not responsible for them. Read their notices, not this
34
+ one.</p>
35
+ <p><strong>Your organisation's own systems.</strong> Where your employer or another organisation uses the Service, it also
36
+ runs systems of its own. This notice covers our part. Its notice covers its part.</p>
37
+ <h2 id="who-we-are" tabindex="-1">Who we are</h2>
38
+ <p>The controller of the personal data described in this notice is <strong>Ever Technologies LTD</strong>, a company
39
+ registered in Bulgaria under company number 204599535, with its registered office
40
+ at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.</p>
41
+ <p>&quot;Controller&quot; is the legal term for the organisation that decides why personal data is used and how.
42
+ Wherever this notice says we make that decision, <strong>Ever Technologies LTD is the organisation accountable to
43
+ you</strong> — and to the Commission for Personal Data Protection (Комисия за защита на личните данни) (CPDP), which
44
+ is our lead supervisory authority.</p>
45
+ <p>Ever Technologies LTD operates Ever Teams Cloud and is the company you contract with for it. There
46
+ is no other operator behind us and no second company you have to chase to get an answer.</p>
47
+ <p>You can reach us about anything in this notice at privacy@ever.co, or by post at the registered office
48
+ above.</p>
49
+ <p>There are parts of this notice where we are deliberately <strong>not</strong> the controller: where a customer puts
50
+ personal data about its own people into the Service, that customer decides, and we act on its instructions.
51
+ That split matters, so it has its own section below.</p>
52
+ <h2 id="other-companies-in-our-group" tabindex="-1">Other companies in our group</h2>
53
+ <p>There is one other company in our group, and its role is narrow enough to state in a sentence.</p>
54
+ <p><strong>Ever Co. LTD</strong>, a company registered in Israel under company number
55
+ 515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, owns the intellectual
56
+ property in the software. Ever Technologies LTD operates the Service under licence from it.</p>
57
+ <p>That is the entire relationship. Its consequences are worth stating positively rather than leaving you to
58
+ work them out:</p>
59
+ <ul>
60
+ <li><strong>Ever Co. LTD does not access personal data held in the Service.</strong> No administration console,
61
+ no production database, no support tooling, no backups, no error reports.</li>
62
+ <li>It is <strong>not a controller</strong> of that data, <strong>not a processor</strong> of it, and <strong>not a sub-processor</strong>. It does
63
+ not appear on our sub-processor list, because there is nothing for it to appear against.</li>
64
+ <li><strong>No personal data is transferred to it.</strong> No international transfer to Israel arises out of
65
+ your use of the Service, because none happens.</li>
66
+ </ul>
67
+ <p>Owning software is not the same as having access to the data that software holds, and we have kept the two
68
+ apart on purpose.</p>
69
+ <p>If that ever changes — if Ever Co. LTD were to take on any role involving personal data from the
70
+ Service — we would update this notice before it happened, name the role, disclose the transfer and the
71
+ safeguard we relied on, and add it to our sub-processor list. <strong>Until you read that here, none of it is
72
+ happening.</strong></p>
73
+ <h2 id="data-protection-contact" tabindex="-1">Data protection contact</h2>
74
+ <p><strong>We have not designated a Data Protection Officer.</strong> Article 13(1)(b) of the GDPR asks a controller to
75
+ publish a Data Protection Officer's contact details where one has been designated. None has been designated
76
+ at Ever Technologies LTD, so there are none to publish. We would rather tell you that outright than let a
77
+ mailbox name imply otherwise. We keep the question under review, and if it changes we will publish the
78
+ details here.</p>
79
+ <p>What we do publish is a contact route that is monitored and acted on. <strong>Privacy questions and requests to
80
+ exercise your rights are handled through these addresses:</strong></p>
81
+ <ul>
82
+ <li><strong>privacy@ever.co</strong> — use this for anything about this notice, about the personal data we hold, or to
83
+ make a request under any of your rights.</li>
84
+ <li><strong>dpo@ever.co</strong> — an alias that reaches the same people. It exists because procurement forms,
85
+ security questionnaires and privacy tooling routinely expect an address in that form. <strong>It is a routing
86
+ alias, not an office. Nothing about it means a Data Protection Officer has been designated.</strong></li>
87
+ </ul>
88
+ <p>You can also write to us by post at the registered office given above.</p>
89
+ <p>We will acknowledge your message, and we will answer a request to exercise your rights within one month —
90
+ the deadline the GDPR sets. Where a request is genuinely complex, or where you have made several, we may
91
+ extend that by up to two further months. If we do, we will tell you inside the first month and explain
92
+ why.</p>
93
+ <h2 id="who-decides-what-controller-and-processor" tabindex="-1">Who decides what: controller and processor</h2>
94
+ <p>Data protection law splits responsibility in two. The <strong>controller</strong> decides why personal data is used and
95
+ how. The <strong>processor</strong> only acts on the controller's instructions. Which of the two we are is not a
96
+ formality — it decides who you go to, who has to answer you, and who is accountable when something goes
97
+ wrong.</p>
98
+ <p>Our position depends on whose data it is. There are three cases. We set them out here, in the privacy
99
+ notice, rather than leaving them to a data processing agreement, because the person most affected by the
100
+ second case is usually the person least likely to read a contract.</p>
101
+ <h3 id="1-our-own-relationship-with-you-we-are-the-controller" tabindex="-1">1. Our own relationship with you — we are the controller</h3>
102
+ <p>Where we decide, we are accountable. <strong>We are the controller</strong> for:</p>
103
+ <ul>
104
+ <li>registration and account identity — the name, email address and credentials used to create and hold an
105
+ account;</li>
106
+ <li>billing, payments, invoices, tax records and collections;</li>
107
+ <li>support conversations, including the tickets, emails, chats and attachments themselves;</li>
108
+ <li>security, fraud prevention, abuse handling and audit logging;</li>
109
+ <li>our own websites and their analytics, our newsletters, and our marketing to prospective customers; and</li>
110
+ <li>running our business — accounting, insurance, professional advice, and defending claims.</li>
111
+ </ul>
112
+ <p>Everything in this notice about purposes, legal bases, retention, transfers and your rights applies to this
113
+ first case directly, and you exercise those rights against us.</p>
114
+ <h3 id="2-personal-data-a-customer-puts-into-the-service-about-its-own-people-the-customer-is-the-controller" tabindex="-1">2. Personal data a customer puts into the Service about its own people — the customer is the controller</h3>
115
+ <p>When an organisation subscribes to the Service and uses it to run its business, the personal data it puts
116
+ in is <strong>its</strong> data. It decides what to collect, which features to switch on, why, and for how long to keep
117
+ it. <strong>We process that data only on that organisation's instructions.</strong> For it, the organisation is the
118
+ controller and we are the processor.</p>
119
+ <p>This covers the ordinary contents of a workspace — employee and contractor records, contact details,
120
+ projects, tasks, documents and messages. It also covers the parts that matter most, where a product
121
+ provides them and the customer has enabled them:</p>
122
+ <ul>
123
+ <li><strong>time-tracking data</strong> — timers, timesheets, time entries and the records behind them;</li>
124
+ <li><strong>activity data</strong> — how much keyboard and mouse activity occurred in a period, idle time, and which
125
+ applications and websites were in use;</li>
126
+ <li><strong>screen and media capture</strong> — periodic screenshots and, where separately switched on, webcam stills,
127
+ audio recordings and screen recordings.</li>
128
+ </ul>
129
+ <p><strong>We do not decide to collect any of this. The customer does.</strong> We build the features, we document what
130
+ each one captures and what each control does, and we run them exactly as the customer configures them. We
131
+ do not use that data for our own purposes, we do not use it to train models, and we do not look at it
132
+ except where we must in order to run, secure or support the Service.</p>
133
+ <p>What Ever Teams can capture, what is off by default, and which controls exist is set out in the annex
134
+ later in this notice.</p>
135
+ <h3 id="3-data-a-customer-holds-about-its-own-clients-and-end-users-the-customer-is-the-controller" tabindex="-1">3. Data a customer holds about its own clients and end users — the customer is the controller</h3>
136
+ <p>Where a customer uses the Service to serve its own clients, members, applicants, patients or website
137
+ visitors, that data sits in the same arrangement as case 2. The customer is the controller, we are the
138
+ processor, and the customer owes those people the notice and the answers. If you have dealt with an
139
+ organisation and want to know what it holds about you, ask that organisation.</p>
140
+ <h3 id="if-you-are-monitored-at-work-this-part-is-for-you" tabindex="-1">If you are monitored at work, this part is for you</h3>
141
+ <p>We would rather tell you directly than make you work it out from a contract you have never seen.</p>
142
+ <p><strong>Your employer decides what is captured. We do not.</strong> Screenshots, activity rates, application and website
143
+ usage, webcam stills, audio, screen recordings — each of these is a setting your employer switches on or
144
+ leaves off, for the organisation and, where the product allows it, for individual people. We cannot switch
145
+ them on for your employer, and we do not switch them on for ourselves.</p>
146
+ <p><strong>Your employer is the controller of that data.</strong> That means your employer, not us:</p>
147
+ <ul>
148
+ <li>must have a lawful basis for monitoring you, under the GDPR and under its own national employment law,
149
+ which differs sharply from country to country;</li>
150
+ <li>must tell you, before it starts, what is captured, how often, why, and how long it is kept;</li>
151
+ <li>must carry out a data protection impact assessment where one is required, and act on what it finds;</li>
152
+ <li>must consult a works council, employee representatives or a trade union where its national law requires
153
+ that; and</li>
154
+ <li>must answer your requests about that data.</li>
155
+ </ul>
156
+ <p><strong>We make no claim that monitoring employees is lawful across the European Union, because it is not.</strong> Some
157
+ countries restrict it tightly, some require consultation before it starts, and some prohibit particular
158
+ forms of it outright. Whether your employer's use of these features is lawful where you work is your
159
+ employer's responsibility. We require every customer to confirm to us that it has dealt with each of the
160
+ points above before it uses these features.</p>
161
+ <p><strong>How to exercise your rights over monitoring data.</strong> Send your request to your employer — it holds the
162
+ data and it has to answer you. If you send it to us instead, we will not ignore it:</p>
163
+ <ul>
164
+ <li>we will forward it promptly to the customer whose workspace holds the data;</li>
165
+ <li>we will tell you that we have done so, and to whom, so you are not left waiting on silence; and</li>
166
+ <li>we will help that customer find, correct, export or delete the data, which is what our contract with it
167
+ requires of us.</li>
168
+ </ul>
169
+ <p><strong>What we will not do is release one organisation's data to someone else on request.</strong> We cannot verify an
170
+ employment relationship from the outside, and handing over a workspace's contents to a person the customer
171
+ has not authorised would be a breach in its own right. That restraint protects you as much as it
172
+ constrains you.</p>
173
+ <p>If you think your employer is monitoring you unlawfully, you can complain to the data protection authority
174
+ in your own country, and to your national labour authority. You do not need our permission, and you do not
175
+ need to come through us first.</p>
176
+ <h2 id="personal-data-we-collect" tabindex="-1">Personal data we collect</h2>
177
+ <p>We group this by where the data comes from, because that is what determines what we know about you and what
178
+ we owe you.</p>
179
+ <p>Not every category applies to every product, plan or user. This section describes the shape of what we
180
+ collect; the annex later in this notice lists what Ever Teams actually collects.</p>
181
+ <h3 id="what-you-give-us" tabindex="-1">What you give us</h3>
182
+ <ul>
183
+ <li><strong>Account identity</strong> — your name, username, email address, password (held only as a hash), profile
184
+ picture, job title, preferred language and time zone.</li>
185
+ <li><strong>Organisation details</strong> — the organisation you belong to, your team, your role and permissions within
186
+ it, and who invited you.</li>
187
+ <li><strong>Contact details</strong> — email address, telephone number and postal address, where you provide them.</li>
188
+ <li><strong>Billing details</strong> — billing name and address, VAT or tax identification number, the plan you are on,
189
+ invoices and payment history. <strong>We do not receive or hold your full card number</strong> — that goes straight to
190
+ our payment processor.</li>
191
+ <li><strong>Support correspondence</strong> — the tickets, emails, chat messages, screenshots and files you send when you
192
+ ask for help, and our replies.</li>
193
+ <li><strong>Content you submit</strong> — everything you or your organisation puts into the Service: documents, tasks,
194
+ projects, records, messages and uploads. Where that content belongs to your organisation, we hold it as
195
+ processor, not as controller.</li>
196
+ <li><strong>Anything else you volunteer</strong> — survey answers, feedback, event registrations, newsletter sign-ups, and
197
+ whatever you choose to write to us.</li>
198
+ </ul>
199
+ <h3 id="what-we-collect-automatically-when-you-use-the-service" tabindex="-1">What we collect automatically when you use the Service</h3>
200
+ <ul>
201
+ <li><strong>Device and browser data</strong> — device type, operating system, browser and version, screen size, language,
202
+ and the version of our application you are running.</li>
203
+ <li><strong>Connection data</strong> — your IP address, and the approximate location it indicates. <strong>That is
204
+ city-or-region level, derived from the IP address</strong>, and it is not satellite positioning. Where a
205
+ specific feature collects precise location, it says so.</li>
206
+ <li><strong>Usage data</strong> — pages and screens viewed, features used, actions taken, navigation paths, timestamps and
207
+ the page that referred you.</li>
208
+ <li><strong>Logs</strong> — server and application logs of requests, errors, response times, sign-ins, failed sign-ins and
209
+ administrative actions, with the identifiers needed to tie an entry to an account.</li>
210
+ <li><strong>Diagnostics</strong> — crash reports, stack traces and performance traces. These can incidentally contain
211
+ whatever was in the request that failed.</li>
212
+ <li><strong>Cookies and similar technologies</strong> — cookies, local storage, pixels, software development kit
213
+ identifiers and comparable device storage. What each is for, and which ones need your consent, is in our
214
+ <a href="https://ever.team/cookies">Cookie Policy</a>.</li>
215
+ </ul>
216
+ <h3 id="what-we-receive-from-other-people" tabindex="-1">What we receive from other people</h3>
217
+ <ul>
218
+ <li><strong>Identity providers</strong> — if you sign in with a third-party account, we receive that account's identifier,
219
+ your email address, your display name and usually your profile picture, plus confirmation that the
220
+ sign-in succeeded. <strong>We never receive your password for it.</strong></li>
221
+ <li><strong>Payment processors</strong> — whether a payment succeeded or failed, the payment method type, the last four
222
+ digits and expiry of a card, the billing country, and any dispute or chargeback.</li>
223
+ <li><strong>Integrations you or your administrator connect</strong> — whatever the connected service returns within the
224
+ permissions granted. That varies by integration and is shown to you when you authorise it.</li>
225
+ <li><strong>Your organisation</strong> — where an administrator creates your account, invites you, sets your role or
226
+ imports records about you.</li>
227
+ <li><strong>Other sources</strong>, where a particular product uses them. Those are set out in the next section and in the
228
+ annex.</li>
229
+ </ul>
230
+ <h3 id="what-you-have-to-give-us" tabindex="-1">What you have to give us</h3>
231
+ <p>Some of it is unavoidable. Without account identity we cannot create an account for you; without billing
232
+ details we cannot take payment for a paid plan; without certain records we cannot meet our own legal
233
+ obligations. Where data is necessary in that sense, <strong>not providing it means we cannot provide that part of
234
+ the Service</strong> — but nothing worse follows.</p>
235
+ <p>Everything else — an optional profile field, a newsletter subscription, an integration you could simply not
236
+ connect — is genuinely optional, and declining it costs you nothing.</p>
237
+ <h2 id="data-we-do-not-collect" tabindex="-1">Data we do not collect</h2>
238
+ <p>Shorter than the previous section, and just as binding. These are commitments about how the Service is
239
+ built, not aspirations.</p>
240
+ <ul>
241
+ <li><strong>We do not sell personal data.</strong> Not to data brokers, not to advertisers, not to anyone — and not under
242
+ the broader definitions of &quot;sell&quot; or &quot;share&quot; used outside the European Union.</li>
243
+ <li><strong>We do not buy marketing lists.</strong> If we contact you about our products it is because you gave us your
244
+ details, or because you are already a customer. We do not purchase your name from someone else in order
245
+ to email you.</li>
246
+ <li><strong>We do not use your content to train machine-learning models</strong> — not for our own purposes, and not for
247
+ the benefit of other customers. Where a product has an AI feature, it processes your content to produce
248
+ your result, and that is the end of it. If we ever want that to change, it will be an opt-in you actively
249
+ choose, described before you choose it.</li>
250
+ <li><strong>We do not run advertising inside the Service.</strong> No third-party advertising, no behavioural ad
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>
255
+ <li><strong>We do not ask for special-category data</strong> — health, racial or ethnic origin, religious or philosophical
256
+ beliefs, political opinions, trade union membership, sex life or sexual orientation, genetic or biometric
257
+ data. There are no fields for it, we do not infer it, and we do not want it. The one honest caveat is
258
+ about what can end up inside a screenshot, and it has its own section below.</li>
259
+ <li><strong>We do not store full card numbers or card security codes.</strong> Those are entered on our payment
260
+ processor's systems and never reach ours.</li>
261
+ <li><strong>We do not collect precise location by default.</strong> Where a product uses location at all, it is because a
262
+ specific feature needs it, and that feature says so.</li>
263
+ </ul>
264
+ <p>If you find any of this to be untrue of something we ship, tell us at privacy@ever.co. We will treat it
265
+ as a defect in the product, not as a disagreement about wording.</p>
266
+ <h2 id="where-data-comes-from-when-it-does-not-come-from-you" tabindex="-1">Where data comes from when it does not come from you</h2>
267
+ <p>Not all of the personal data we hold came from you. Article 14 of the GDPR requires us to tell you where it
268
+ came from, and this section does that.</p>
269
+ <ul>
270
+ <li><strong>Your employer, or the administrator of your workspace.</strong> Where an organisation subscribes to the
271
+ Service, an administrator creates accounts, invites people, sets roles and imports records. That supplies
272
+ your name, work email address, job title, team, role and permissions, and whatever else the organisation
273
+ chooses to hold about you in its workspace. <strong>For that data the organisation is the controller</strong>, as set
274
+ out above.</li>
275
+ <li><strong>Identity providers.</strong> If you sign in with a third-party account, that provider supplies the account
276
+ identifier, your email address, your display name and usually a profile picture, and confirms the sign-in
277
+ succeeded. It supplies nothing else, and never a password.</li>
278
+ <li><strong>Integrations you or your administrator connect.</strong> A connected service supplies whatever the permissions
279
+ you granted allow — for example issues and repositories from a code host, messages and channel names from
280
+ a chat tool, calendar entries, contacts, or records from another business system. The scope is shown when
281
+ the connection is authorised, and it can be revoked in the same place.</li>
282
+ <li><strong>Payment processors and resellers.</strong> They supply the outcome of a payment, the payment method type, the
283
+ last four digits and expiry of a card, the billing country, and any dispute or chargeback. They do not
284
+ pass us the card itself.</li>
285
+ <li><strong>Publicly available sources, where a product builds profiles from them.</strong> Some products work with
286
+ information people have published themselves — a public code-hosting profile, a public company page, a
287
+ public professional listing. Where a product does this, the annex names the categories taken and the
288
+ sources they came from, explains the basis we rely on, and says how to object. <strong>If we hold a profile
289
+ about you that you never gave us, you can object to it and we will act on that.</strong></li>
290
+ <li><strong>Service providers acting for us.</strong> Fraud and abuse signals, delivery and bounce information from the
291
+ systems that send our email, and security intelligence about addresses and networks.</li>
292
+ </ul>
293
+ <p>Where we are the controller of personal data that did not come from you, we will tell you within a
294
+ reasonable period and at the latest within one month of obtaining it — or, if we use it to contact you, at
295
+ that first contact. Where informing every individual separately would take disproportionate effort, this
296
+ notice and its annex are the public information we provide instead, which is what Article 14(5)(b) allows.</p>
297
+ <h2 id="why-we-use-personal-data-and-on-what-legal-basis" tabindex="-1">Why we use personal data, and on what legal basis</h2>
298
+ <p>Article 6 of the GDPR requires a lawful basis for each purpose. So this is one row per purpose, rather than
299
+ a general list of all six bases — you can check us against each line.</p>
300
+ <table>
301
+ <thead>
302
+ <tr>
303
+ <th>Purpose</th>
304
+ <th>Personal data used</th>
305
+ <th>Lawful basis</th>
306
+ </tr>
307
+ </thead>
308
+ <tbody>
309
+ <tr>
310
+ <td>Providing Ever Teams Cloud: creating and running your account, signing you in, delivering the features you use, and keeping your data available to you</td>
311
+ <td>Account identity, organisation and role, credentials, content you submit, device and connection data</td>
312
+ <td><strong>Contract</strong> — Art 6(1)(b). Necessary to perform our agreement with you</td>
313
+ </tr>
314
+ <tr>
315
+ <td>Taking payment: invoicing, collecting fees, applying refunds, chasing non-payment</td>
316
+ <td>Billing details, plan and subscription data, invoices, payment outcomes</td>
317
+ <td><strong>Contract</strong> — Art 6(1)(b)</td>
318
+ </tr>
319
+ <tr>
320
+ <td>Keeping accounting, tax and invoicing records</td>
321
+ <td>Invoices, payment records, billing identity</td>
322
+ <td><strong>Legal obligation</strong> — Art 6(1)(c), under tax and accounting law</td>
323
+ </tr>
324
+ <tr>
325
+ <td>Support: answering your questions, investigating faults and reproducing problems you report</td>
326
+ <td>Support correspondence, account identity, logs and diagnostics, and whatever you point us at</td>
327
+ <td><strong>Contract</strong> — Art 6(1)(b) where you are a customer. <strong>Legitimate interests</strong> — Art 6(1)(f) where you are not, so that we can answer anyone who writes to us</td>
328
+ </tr>
329
+ <tr>
330
+ <td>Security and abuse prevention: authentication, rate limiting, bot and fraud detection, investigating misuse, protecting accounts and infrastructure</td>
331
+ <td>Account identity, IP address, device data, request logs, sign-in and failed sign-in records</td>
332
+ <td><strong>Legitimate interests</strong> — Art 6(1)(f) in keeping the Service and the people who use it safe</td>
333
+ </tr>
334
+ <tr>
335
+ <td>Keeping the Service running: monitoring, error tracking, debugging, capacity planning and backups</td>
336
+ <td>Logs, diagnostics, usage data, account identifiers</td>
337
+ <td><strong>Legitimate interests</strong> — Art 6(1)(f) in operating a reliable service</td>
338
+ </tr>
339
+ <tr>
340
+ <td>Understanding how the Service is used, so we can improve it</td>
341
+ <td>Usage events, feature interactions, device and browser data, aggregated statistics</td>
342
+ <td><strong>Legitimate interests</strong> — Art 6(1)(f). <strong>Consent</strong> — Art 6(1)(a) wherever cookies or similar device storage are involved, as set out in our <a href="https://ever.team/cookies">Cookie Policy</a></td>
343
+ </tr>
344
+ <tr>
345
+ <td>Marketing to people who are not yet customers: newsletters, product announcements and events</td>
346
+ <td>Contact details, marketing preferences, whether you opened or clicked a message</td>
347
+ <td><strong>Consent</strong> — Art 6(1)(a), which you can withdraw at any time</td>
348
+ </tr>
349
+ <tr>
350
+ <td>Marketing our own similar products to an existing customer who gave us their address during a sale, with an opt-out in every message</td>
351
+ <td>Contact details, the products you already have</td>
352
+ <td><strong>Legitimate interests</strong> — Art 6(1)(f), relying on the narrow existing-customer exception in the ePrivacy rules</td>
353
+ </tr>
354
+ <tr>
355
+ <td>Meeting legal obligations: responding to lawful requests from authorities, sanctions and export-control checks, statutory record-keeping, and our own data protection duties</td>
356
+ <td>Whatever the specific obligation requires, and no more</td>
357
+ <td><strong>Legal obligation</strong> — Art 6(1)(c)</td>
358
+ </tr>
359
+ <tr>
360
+ <td>Establishing, exercising or defending legal claims, and handling complaints, disputes, audits, insurance and corporate transactions</td>
361
+ <td>Account and billing records, correspondence, and the logs relevant to the matter</td>
362
+ <td><strong>Legitimate interests</strong> — Art 6(1)(f) in protecting our legal position</td>
363
+ </tr>
364
+ </tbody>
365
+ </table>
366
+ <p>Two things this table deliberately does not cover.</p>
367
+ <p><strong>Where we act as processor</strong>, the lawful basis is not ours to pick. The customer that put the data into
368
+ the Service decides the purpose and must have its own basis for it. See the controller and processor
369
+ section above.</p>
370
+ <p><strong>Where we rely on your consent</strong>, you can withdraw it at any time, and withdrawing it is as easy as giving
371
+ it. Withdrawing consent does not make earlier processing unlawful — it stops the processing from that point
372
+ on.</p>
373
+ <h2 id="the-legitimate-interests-we-rely-on" tabindex="-1">The legitimate interests we rely on</h2>
374
+ <p>Where the table above says &quot;legitimate interests&quot;, the law requires us to tell you what that interest
375
+ actually is — not simply to name the basis and move on. For each one we have asked three questions: what is
376
+ the interest, is the processing genuinely necessary for it, and is it fair to you. That last question is
377
+ the balancing test, and we keep a written record of it.</p>
378
+ <h3 id="keeping-the-service-and-its-users-secure" tabindex="-1">Keeping the Service and its users secure</h3>
379
+ <ul>
380
+ <li><strong>The interest:</strong> preventing unauthorised access, account takeover, fraud, spam, denial-of-service and
381
+ abuse of the Service.</li>
382
+ <li><strong>Why the processing is necessary:</strong> you cannot see an attack without looking at the traffic. Sign-in
383
+ records, IP addresses, device data and request logs are what make an intrusion visible at all.</li>
384
+ <li><strong>Why it does not override your rights:</strong> the data is limited to what security work needs, it is kept for
385
+ a bounded period, and the benefit goes to the same accounts and the same people whose data is used. Nobody
386
+ reasonably expects a service to be run without security logging.</li>
387
+ </ul>
388
+ <h3 id="keeping-the-service-running" tabindex="-1">Keeping the Service running</h3>
389
+ <ul>
390
+ <li><strong>The interest:</strong> operating a reliable service — monitoring, error tracking, debugging, capacity planning
391
+ and backups.</li>
392
+ <li><strong>Why the processing is necessary:</strong> faults surface in logs, and a crash report is only useful if it
393
+ records what was happening when the crash occurred.</li>
394
+ <li><strong>Why it does not override your rights:</strong> it is operational data, kept for short periods, used to fix
395
+ software rather than to form views about people, and reachable only by the staff who need it.</li>
396
+ </ul>
397
+ <h3 id="understanding-how-the-service-is-used" tabindex="-1">Understanding how the Service is used</h3>
398
+ <ul>
399
+ <li><strong>The interest:</strong> knowing which features are used, where people get stuck, and what to build or fix next.</li>
400
+ <li><strong>Why the processing is necessary:</strong> the alternative is guessing. Aggregate usage data is the only
401
+ practical way to see this without interrogating every user.</li>
402
+ <li><strong>Why it does not override your rights:</strong> we analyse it in aggregate rather than to make decisions about
403
+ you individually, and wherever cookies or similar device storage are involved we ask for your consent
404
+ instead of relying on this interest at all.</li>
405
+ </ul>
406
+ <h3 id="answering-people-who-write-to-us-without-an-account" tabindex="-1">Answering people who write to us without an account</h3>
407
+ <ul>
408
+ <li><strong>The interest:</strong> replying to a question from someone who is not a customer.</li>
409
+ <li><strong>Why the processing is necessary:</strong> we cannot answer you without keeping your message and your address.</li>
410
+ <li><strong>Why it does not override your rights:</strong> you chose to contact us, we use it only to answer, and we keep
411
+ it no longer than the matter and any follow-up require.</li>
412
+ </ul>
413
+ <h3 id="telling-existing-customers-about-our-own-similar-products" tabindex="-1">Telling existing customers about our own similar products</h3>
414
+ <ul>
415
+ <li><strong>The interest:</strong> letting people who already buy from us know about the products next to the one they
416
+ bought.</li>
417
+ <li><strong>Why the processing is necessary:</strong> it uses the address they gave us during that sale, and there is no
418
+ less intrusive way to reach them.</li>
419
+ <li><strong>Why it does not override your rights:</strong> it is confined to our own similar products, every message
420
+ carries a one-click opt-out, and an opt-out is acted on immediately and permanently.</li>
421
+ </ul>
422
+ <h3 id="running-and-protecting-our-business" tabindex="-1">Running and protecting our business</h3>
423
+ <ul>
424
+ <li><strong>The interest:</strong> accounting, audit, insurance, professional advice, complaints, disputes, enforcing our
425
+ terms, and evaluating or completing a corporate transaction.</li>
426
+ <li><strong>Why the processing is necessary:</strong> these are ordinary obligations of operating a company, and each one
427
+ needs the records that relate to it.</li>
428
+ <li><strong>Why it does not override your rights:</strong> the data is confined to the matter in hand, access is narrow,
429
+ and a great deal of it we are required to keep in any event.</li>
430
+ </ul>
431
+ <h3 id="your-right-to-object" tabindex="-1">Your right to object</h3>
432
+ <p><strong>You can object to any processing we base on legitimate interests, at any time, by writing to
433
+ privacy@ever.co.</strong> Tell us which processing, and where you can, why — your particular situation is part
434
+ of the balance. We will stop unless we can show compelling legitimate grounds that override your interests,
435
+ rights and freedoms, or unless we need the data to establish, exercise or defend legal claims.</p>
436
+ <p><strong>If you object to direct marketing there is no balancing at all. We stop.</strong> That right is absolute.</p>
437
+ <p>You can also ask us for a summary of the balancing test behind any interest listed above, and we will give
438
+ you one.</p>
439
+ <h2 id="special-categories-of-data" tabindex="-1">Special categories of data</h2>
440
+ <p>Some personal data carries extra protection under Article 9 of the GDPR: data revealing racial or ethnic
441
+ origin, political opinions, religious or philosophical beliefs or trade union membership, and genetic data,
442
+ biometric data used to identify someone, data concerning health, and data about a person's sex life or
443
+ sexual orientation. Data about criminal convictions and offences is restricted separately, under Article 10.</p>
444
+ <p><strong>We do not seek any of it.</strong> We do not ask for it at sign-up, in billing or in support. There are no
445
+ fields for it, we do not infer it, and we do not enrich profiles with it. Please do not send it to us in a
446
+ support ticket either — if you need to show us something sensitive to get help, redact it first.</p>
447
+ <h3 id="the-honest-caveat-incidental-capture" tabindex="-1">The honest caveat: incidental capture</h3>
448
+ <p>Where a customer switches on screen capture, webcam capture or audio capture, <strong>what gets captured is
449
+ whatever is there</strong>. A screenshot taken while someone has a hospital appointment email open captures health
450
+ data. A webcam still can show a religious head covering. An audio recording can pick up a background
451
+ conversation that has nothing to do with work.</p>
452
+ <p>That is not a theoretical risk and we will not present it as one. It is a direct consequence of capturing a
453
+ screen or a room on a timer, and it is true of every product that does it, ours included.</p>
454
+ <h3 id="whose-responsibility-it-is" tabindex="-1">Whose responsibility it is</h3>
455
+ <p><strong>The customer that switches these features on is the controller of what they capture</strong>, including anything
456
+ special-category that comes with it. So the customer, not us:</p>
457
+ <ul>
458
+ <li>decides whether to enable capture at all, and has to judge whether the benefit justifies the intrusion;</li>
459
+ <li>must carry out a data protection impact assessment before starting, and act on what it finds — capture of
460
+ this kind will normally require one;</li>
461
+ <li>must have a lawful basis, and where special-category data is realistically in scope must also satisfy
462
+ Article 9(2), which an employee's consent rarely does on its own, because of the imbalance between
463
+ employer and employee;</li>
464
+ <li>must configure the product to reduce that risk rather than accept it; and</li>
465
+ <li>must deal with what has been captured, including deleting a capture that should never have been taken.</li>
466
+ </ul>
467
+ <p>We are the processor for it. We do not decide to capture anything, we do not review captures for our own
468
+ purposes, and we act on the customer's configuration and instructions.</p>
469
+ <h3 id="the-levers-and-using-them" tabindex="-1">The levers, and using them</h3>
470
+ <p>Where a product offers screen or media capture, it also offers controls that materially reduce this risk.
471
+ Depending on the product, those include:</p>
472
+ <ul>
473
+ <li>switching capture off entirely, for the whole organisation or for an individual person;</li>
474
+ <li>switching off the more intrusive capture types — webcam stills, audio and screen recording — while
475
+ keeping the rest;</li>
476
+ <li>reducing how often captures are taken;</li>
477
+ <li>blurring captured images;</li>
478
+ <li>shortening how long captures are kept, and deleting them automatically at the end of that period;</li>
479
+ <li>letting people see what has been captured about them; and</li>
480
+ <li>deleting an individual capture.</li>
481
+ </ul>
482
+ <p><strong>If you are a customer, these are yours to set, and the defaults are not a recommendation.</strong> Choose the
483
+ least intrusive configuration that meets the purpose you actually have, and write down why you chose it.
484
+ That record is what a supervisory authority will ask for.</p>
485
+ <p><strong>If you are being monitored and something sensitive has been captured, ask your employer to delete it.</strong>
486
+ Your employer can do that in the product. If you tell us instead, we will forward your request and help
487
+ your employer act on it, as described in the controller and processor section above.</p>
488
+ <p>Which of these controls Ever Teams provides, and what its defaults are, is set out in the annex later
489
+ in this notice.</p>
490
+ <h2 id="annex-ever-teams" tabindex="-1">Annex — Ever Teams</h2>
491
+ <p>Everything above applies to Ever Teams Cloud. This annex is the part that is only true of this
492
+ product: where your data physically lives, exactly what the monitoring features capture, who receives it,
493
+ and the four groups of people we hold data about who never signed up for anything.</p>
494
+ <h3 id="ever-teams-has-no-database-of-its-own" tabindex="-1">Ever Teams has no database of its own</h3>
495
+ <p>This is the first thing to know, because everything else follows from it.</p>
496
+ <p><strong>Ever Teams is a front end. The system of record is the Ever Gauzy platform, which we also operate.</strong>
497
+ When you register at app.ever.team, one server-side sequence creates a user, a tenant, an organisation, an
498
+ employee record and a team <strong>inside that platform</strong> — reached at api.ever.team — and from that moment every
499
+ task, comment, timer, time log, time slot, screenshot and activity record you produce is stored there.</p>
500
+ <p>What that means in practice:</p>
501
+ <ul>
502
+ <li><strong>Ever Technologies LTD is the controller and operator of both.</strong> The company you deal with does not change
503
+ depending on which front door you came through.</li>
504
+ <li><strong>The platform is multi-tenant.</strong> Your workspace is one tenant among others in a shared system, and the
505
+ separation between them is enforced in software rather than by giving each customer its own machine.</li>
506
+ <li><strong>If your organisation also uses our other products on that platform, it is the same estate</strong> — the same
507
+ database, the same object storage, the same backups. Read this annex alongside the annex published for
508
+ any other Ever product you use.</li>
509
+ <li>The clients — web, desktop, mobile, browser extension — hold sign-in tokens and preferences on your
510
+ device and pass everything else through to the platform.</li>
511
+ </ul>
512
+ <h3 id="what-this-product-captures-about-a-person-who-is-being-tracked" tabindex="-1">What this product captures about a person who is being tracked</h3>
513
+ <p>Only if the organisation running the workspace has switched it on. The controls are in the next section.</p>
514
+ <ul>
515
+ <li><strong>Time entries</strong> — timer start and stop, duration, the project and task, whether the entry was typed in by
516
+ hand and any reason given for it, and <strong>which client it came from</strong>: the web application, the desktop
517
+ application, the mobile application, the browser extension, or a record imported from Upwork or Hubstaff.</li>
518
+ <li><strong>Ten-minute time slots.</strong> Tracked time is divided into slots of ten minutes, and each slot carries
519
+ <strong>keyboard, mouse and overall activity percentages</strong> and idle time. This is the unit the whole monitoring
520
+ surface is built around.</li>
521
+ <li><strong>Screenshots.</strong> Periodic captures of the screen, each stored with the time it was taken and the
522
+ applications that were in view, and <strong>shown to managers against the ten-minute slot they belong to</strong>.</li>
523
+ <li><strong>Applications and websites.</strong> The applications in use and the web addresses visited, held with the page
524
+ title, the page description and the preview image the page itself supplies.</li>
525
+ <li><strong>Presence</strong> — whether a person is online, away, and whether their timer is running.</li>
526
+ </ul>
527
+ <p>Alongside that, the employee record on the platform holds workforce fields the organisation fills in: job
528
+ information, team and role, start and end dates, offer, acceptance and rejection dates, <strong>pay-adjacent
529
+ figures such as bill rate, minimum billing rate and averaged income, expense and bonus values</strong>, and links
530
+ to external profiles — LinkedIn, GitHub, GitLab, Upwork, Stack Overflow and social accounts — where the
531
+ organisation records them.</p>
532
+ <h3 id="the-controls-and-who-holds-them" tabindex="-1">The controls, and who holds them</h3>
533
+ <p>Each of these is a setting on the organisation or on an individual employee record, <strong>held by the
534
+ organisation, not by the person being tracked</strong>:</p>
535
+ <ul>
536
+ <li>tracking on or off, for the organisation and for each employee individually;</li>
537
+ <li>screenshot capture on or off, for each employee individually;</li>
538
+ <li>tracking of inactivity on or off;</li>
539
+ <li>whether a person may add time by hand, edit time, or delete time.</li>
540
+ </ul>
541
+ <p><strong>A tracked person cannot switch capture off for themselves.</strong> The toggles live on their employee record and
542
+ the organisation controls them. What a tracked person can do is see their own data: the screenshots and
543
+ activity recorded against you appear on your own profile in the application.</p>
544
+ <p><strong>Where a control is not listed here, do not assume it exists.</strong> If you are an administrator planning a
545
+ deployment around a particular safeguard — masking, blurring, an excluded-application list, a capture-free
546
+ window — write to privacy@ever.co and ask us what the product can actually do before you rely on it in
547
+ a notice to your people.</p>
548
+ <h3 id="screenshots-are-assessed-automatically" tabindex="-1">Screenshots are assessed automatically</h3>
549
+ <p>Each screenshot can carry a flag recording whether the image was assessed as work-related. <strong>That assessment
550
+ is made by automated image analysis, not by a person looking at the picture.</strong></p>
551
+ <ul>
552
+ <li>It is a signal, not a finding, and it is not a decision about anybody.</li>
553
+ <li>It can be wrong, and it is wrong in the ways image analysis is usually wrong: it does not know what your
554
+ job is, what the tab was for, or why it was open.</li>
555
+ <li><strong>It must not be used as the sole basis for a decision about a person.</strong> Our Terms of Service and
556
+ Acceptable Use Policy both require a human being with real discretion to make that call.</li>
557
+ <li>If you are tracked and you want an assessment reviewed by a person, ask the organisation that holds the
558
+ workspace — it is the controller. Tell us at privacy@ever.co as well and we will help them find the
559
+ record.</li>
560
+ </ul>
561
+ <h3 id="screenshots-do-not-stay-only-on-our-own-hardware" tabindex="-1">Screenshots do not stay only on our own hardware</h3>
562
+ <p>Most of what this product holds sits on infrastructure we run ourselves. <strong>Screenshots do not, and we will
563
+ not pretend otherwise.</strong></p>
564
+ <p>Screenshots, profile photographs and file attachments are written through the platform's file-asset service
565
+ to a third-party object-storage provider. The provider is named in the always-engaged tier of our
566
+ <a href="https://ever.team/subprocessors">Sub-processor List</a>, with its location and the data it receives.</p>
567
+ <p>We say this in terms because a monitoring product that told you captures never leave its own hardware would
568
+ be making the single most reassuring claim available to it, and it would not be true.</p>
569
+ <h3 id="people-we-hold-data-about-who-never-signed-up" tabindex="-1">People we hold data about who never signed up</h3>
570
+ <p>Four groups, all of whom are covered by Article 14 GDPR. We could not give any of them individual notice in
571
+ advance, and this section is the notice the law expects instead.</p>
572
+ <p><strong>1. People who were invited.</strong> An administrator types an email address and a full name into the invitation
573
+ form and we send that person an email. <strong>We hold their name, their email address, who invited them and to
574
+ which workspace, before they have any relationship with us at all.</strong> The source is the customer that invited
575
+ them. An invitation stays valid until it is accepted or the organisation revokes it. If you have received one
576
+ and want your address removed, reply to us at privacy@ever.co and we will delete it and tell the customer
577
+ to stop.</p>
578
+ <p><strong>2. People whose GitHub activity was imported.</strong> Where an administrator installs our GitHub integration,
579
+ repositories and issues are synchronised into tasks. That brings in the account names, display names and —
580
+ where the platform exposes them — the email addresses of <strong>everyone who contributed to those repositories or
581
+ filed those issues</strong>, most of whom have never used Ever Teams. The source is GitHub, at the customer's
582
+ instruction, within the permissions the customer granted.</p>
583
+ <p><strong>3. Workers whose time records were imported.</strong> A time entry can be recorded as having come from Upwork or
584
+ from Hubstaff. Where a customer imports those, we hold work records about people whose relationship is with
585
+ that customer and that platform, not with us.</p>
586
+ <p><strong>4. People who appear inside a capture.</strong> A screenshot of somebody's screen routinely contains other
587
+ people — a colleague on a call, a customer's record, a name in an email, a patient, a correspondent. The
588
+ visited-address log contains the same by implication. <strong>These people are data subjects and the law protects
589
+ them, and we have no way to identify them or to reach them.</strong> We hold no contact details for them and no
590
+ means of working out who they are from an image, which is why individual notice would take disproportionate
591
+ effort within the meaning of Article 14(5)(b) and why this public section exists instead.</p>
592
+ <p>For all four groups: <strong>the customer whose workspace holds the data is the controller of it.</strong> Write to
593
+ privacy@ever.co and we will route your request to that customer, tell you that we have done so, and help
594
+ them find, correct or delete what they hold.</p>
595
+ <h3 id="analytics-on-this-product-carries-your-name-not-a-number" tabindex="-1">Analytics on this product carries your name, not a number</h3>
596
+ <p>We would rather you read this here than find it in a network trace.</p>
597
+ <ul>
598
+ <li><strong>Product analytics.</strong> Each time you open a page in the signed-in application, our analytics provider
599
+ receives <strong>your user id, your email address, your full name and your organisation's tenant name and id</strong>,
600
+ along with the page. That is not pseudonymous telemetry — it identifies you directly. It is consent-gated
601
+ as analytics in our <a href="https://ever.team/cookies">Cookie Policy</a>, and refusing analytics stops it.</li>
602
+ <li><strong>Error reporting.</strong> Errors are reported with your user id and email address attached, so that a report can
603
+ be tied back to the account that hit the fault.</li>
604
+ <li><strong>Session replay.</strong> Our error-reporting provider records a reconstruction of the interface for a sample of
605
+ sessions and for every session that produced an error. <strong>Text is masked and media is blocked before it
606
+ leaves your browser, which reduces what is captured — it does not reduce it to nothing.</strong> It is
607
+ consent-gated, and it is treated as analytics rather than as necessary diagnostics for that reason.</li>
608
+ </ul>
609
+ <p>Both providers are in the always-engaged tier of our <a href="https://ever.team/subprocessors">Sub-processor List</a>.</p>
610
+ <h3 id="the-four-places-you-might-be-running-this-product" tabindex="-1">The four places you might be running this product</h3>
611
+ <ul>
612
+ <li><strong>The web application</strong> at app.ever.team. Sign-in tokens and workspace context are held in cookies on the
613
+ ever.team domain — the <a href="https://ever.team/cookies">Cookie Policy</a> lists them individually.</li>
614
+ <li><strong>The desktop application</strong>, which wraps the same web application. It fetches its webfonts from Google's
615
+ font service, which discloses your device's IP address to Google.</li>
616
+ <li><strong>The mobile application</strong> for iOS and Android. It checks for a JavaScript bundle update each time it
617
+ launches, which sends your device's IP address, platform, operating-system version and application version
618
+ to the update service. It asks for camera and photo-library access so that you can attach images; it does
619
+ not capture screenshots from a phone.</li>
620
+ <li><strong>The browser extension.</strong> This one needs its own paragraph.</li>
621
+ </ul>
622
+ <p><strong>The browser extension is published with permission to run on every https site your browser visits.</strong> That
623
+ is as broad as a browser permission gets. It is broad because the extension has to be able to start and stop
624
+ a timer and record activity wherever the work is happening, and a narrower permission would break that — but
625
+ the technical reach is the reach, whatever the reason for it. <strong>Any page the person on that device opens is
626
+ within it, including their bank, their doctor and their personal mail.</strong> The extension does not send anything
627
+ to a third-party analytics service, and it stores a sign-in token and the active timer context locally; it
628
+ does load a webfont from Google's font service, which discloses the IP address. If you are deploying it to
629
+ somebody else's device, our Acceptable Use Policy sets out what you must have done first.</p>
630
+ <h3 id="meetings-whiteboards-and-boards" tabindex="-1">Meetings, whiteboards and boards</h3>
631
+ <ul>
632
+ <li><strong>Video meetings</strong> run on a Jitsi server we operate at meet.ever.team. <strong>Meeting audio and video are not
633
+ routed to a third-party meeting service.</strong></li>
634
+ <li><strong>Whiteboards.</strong> The board documents themselves are held on services we run. <strong>Images you paste or upload
635
+ into a board are stored with Google's Firebase Cloud Storage instead</strong> — a different place from everything
636
+ else in the product, and the reason Firebase appears in our sub-processor list.</li>
637
+ </ul>
638
+ <h3 id="the-ai-assistant-and-the-chatgpt-connector" tabindex="-1">The AI assistant and the ChatGPT connector</h3>
639
+ <ul>
640
+ <li><strong>The in-product assistant runs on a key you supply</strong>, for a provider you choose, and it will accept a
641
+ custom endpoint address as well as the named providers. <strong>When you use it, you are the one contracting with
642
+ that provider.</strong> Your prompts and the assistant's replies go to them under your agreement with them, not
643
+ ours; they are not our sub-processor and they are not on our list. The AI section of our
644
+ <a href="https://ever.team/tos">Terms of Service</a> sets out what follows from that.</li>
645
+ <li><strong>The ChatGPT connector</strong> lets you link your own ChatGPT account to Ever Teams. Connecting it causes
646
+ your tasks, projects and team data to be read into that account, under OpenAI's terms, at your election.
647
+ Only connect it for data you are entitled to send there — and if you are a workspace member rather than the
648
+ administrator, check that your organisation is content for you to.</li>
649
+ </ul>
650
+ <h3 id="a-team-page-can-be-public-and-a-new-team-starts-that-way" tabindex="-1">A team page can be public, and a new team starts that way</h3>
651
+ <p>Team information can be published so that a page about it is readable <strong>without signing in</strong>, and <strong>a team
652
+ created during registration is public by default</strong>. An administrator can change that.</p>
653
+ <p>If you are a member of a team and you do not want to appear on a page anybody can read, ask your
654
+ administrator to make the team private. Tell us at privacy@ever.co as well and we will route it and
655
+ follow it up.</p>
656
+ <h3 id="how-to-sign-in-and-what-we-hold-as-a-result" tabindex="-1">How to sign in, and what we hold as a result</h3>
657
+ <p>Self-serve sign-up does not ask you to choose a password. We create the account and you sign in with a code
658
+ sent to your email address, or with a social account you already have. <strong>Whoever controls that mailbox
659
+ controls the account</strong>, so the security of the mailbox is doing real work here.</p>
660
+ <h3 id="how-long-the-monitoring-data-is-kept" tabindex="-1">How long the monitoring data is kept</h3>
661
+ <p><strong>The organisation that owns the workspace sets the retention of its time, activity and screenshot records
662
+ — we do not.</strong> Deleting a time entry removes the slots and screenshots attached to it. Removing a person from
663
+ a team does not delete what was already captured about them: those records belong to the organisation. When
664
+ the organisation's workspace is deleted, its captures go with it, subject to the backup cycle in the
665
+ retention section above.</p>
666
+ <p>If you are an administrator, <strong>set that retention to match what you told your people you would keep</strong>, and
667
+ ask us at privacy@ever.co if the control you need is not in front of you. The retention periods for the
668
+ data we hold as controller — your account, our logs, our support correspondence — are in the table above and
669
+ are unchanged for this product.</p>
670
+ <h2 id="cookies-and-similar-technologies" tabindex="-1">Cookies and similar technologies</h2>
671
+ <p>Cookies, local storage, pixels, software development kits and similar technologies get their own document,
672
+ because they need more detail than a summary can carry. What each one is, what it does, how long it lasts,
673
+ who operates it and how to refuse it is set out in our <a href="https://ever.team/cookies">Cookie Policy</a>.</p>
674
+ <p>In short, we sort them into four categories:</p>
675
+ <ul>
676
+ <li><strong>Strictly necessary</strong> — needed to deliver what you asked for: signing you in, holding your session,
677
+ routing traffic, remembering your cookie choice itself, and protecting forms and sign-in against
678
+ automated abuse. These are not optional, and we do not ask for consent to them.</li>
679
+ <li><strong>Preferences</strong> — remember choices you have made, such as language, region and interface settings.</li>
680
+ <li><strong>Analytics</strong> — help us understand how the Service is used so we can improve it.</li>
681
+ <li><strong>Marketing</strong> — measure our campaigns and help us understand which organisations take an interest in us.</li>
682
+ </ul>
683
+ <p><strong>Nothing in the preferences, analytics or marketing categories is placed or read on your device until you
684
+ agree to it.</strong> You can accept everything, refuse everything, or choose category by category, and refusing
685
+ takes exactly as few clicks as accepting.</p>
686
+ <h3 id="changing-your-mind" tabindex="-1">Changing your mind</h3>
687
+ <p>Your choices are not permanent. A <strong>Cookie preferences</strong> link sits in the footer of every page on
688
+ <a href="https://ever.team">ever.team</a> and reopens the same panel you saw the first time. Change a category
689
+ there and it takes effect immediately, for the future. Withdrawing is as easy as agreeing, and nothing
690
+ about the Service is withheld from you for refusing.</p>
691
+ <p>One analytics tool runs without consent, because it is configured so that it stores and reads nothing on
692
+ your device and never builds a persistent identifier for you. That is a conditional position, not a
693
+ permanent one: the <a href="https://ever.team/cookies">Cookie Policy</a> names the tool, describes the exact
694
+ configuration we rely on, and says what happens if any part of that configuration ever changes.</p>
695
+ <h2 id="who-receives-your-personal-data" tabindex="-1">Who receives your personal data</h2>
696
+ <p>We disclose personal data only to the categories of recipient below, and only as much as each one needs to
697
+ do the job it is there for.</p>
698
+ <ul>
699
+ <li><strong>Service providers acting as our processors</strong> — hosting and infrastructure, storage, content delivery,
700
+ email delivery, error monitoring, product analytics, customer support tooling and similar. They act on
701
+ our documented instructions under a written contract that meets Article 28 GDPR, they are bound to
702
+ confidentiality and appropriate security, and <strong>they may not use your data for their own purposes</strong>.</li>
703
+ <li><strong>Payment processors</strong> — to take payment, issue invoices and handle refunds and disputes. For their own
704
+ regulated obligations — fraud prevention, anti-money-laundering, card-scheme rules — they act as
705
+ controllers in their own right, and their own privacy notice governs that part.</li>
706
+ <li><strong>Professional advisers</strong> — lawyers, accountants, auditors and insurers, bound by professional
707
+ confidentiality, where we need advice or have to evidence that we have complied with something.</li>
708
+ <li><strong>Public authorities, courts and regulators</strong> — where the law requires us to disclose, or where we need
709
+ to establish, exercise or defend a legal claim. We check that a request has a proper legal basis and is
710
+ no wider than it needs to be, we push back where it is not, and we tell you about it unless we are
711
+ legally prohibited from doing so.</li>
712
+ <li><strong>An acquirer or successor</strong> — if we are reorganised, merged or sold, or if part of the business changes
713
+ hands, personal data may pass to the acquirer as part of that transaction. The acquirer is bound by this
714
+ policy or by a notice at least as protective, and we will tell you before anything about the handling of
715
+ your data changes.</li>
716
+ </ul>
717
+ <h3 id="the-sub-processors-we-engage-for-the-hosted-service" tabindex="-1">The sub-processors we engage for the hosted Service</h3>
718
+ <p>These providers are engaged for the hosted Service as it is delivered to everyone. They are the ones your
719
+ data is most likely to reach.</p>
720
+ <table>
721
+ <thead>
722
+ <tr>
723
+ <th>Sub-processor</th>
724
+ <th>Purpose</th>
725
+ <th>Location</th>
726
+ <th>Personal data</th>
727
+ </tr>
728
+ </thead>
729
+ <tbody>
730
+ <tr>
731
+ <td>Cloudflare, Inc.</td>
732
+ <td>Authoritative DNS, reverse proxy, TLS termination, content delivery and web application firewall in front of every ever.team hostname — the application, the API, the boards, the meeting server, the documentation and the websites. All traffic to Ever Teams passes through it. Cloudflare Turnstile is also one of the bot-protection providers the sign-up form can be configured to use.</td>
733
+ <td>United States, with processing at edge locations worldwide including inside the EEA</td>
734
+ <td>IP address, request URL and headers, user agent, cookies in transit, bot-protection signals</td>
735
+ </tr>
736
+ <tr>
737
+ <td>Google Ireland Limited (reCAPTCHA)</td>
738
+ <td>Bot protection on sign-up, sign-in and newsletter forms. The widget loads from Google in your browser and our server verifies the resulting token with Google. This is the bot-protection provider configured today. Strictly necessary — it loads without asking you, for the reasons given in the cookie categories section.</td>
739
+ <td>Ireland and the United States</td>
740
+ <td>IP address, user agent, mouse, touch and timing signals, reCAPTCHA cookies</td>
741
+ </tr>
742
+ <tr>
743
+ <td>Functional Software, Inc. d/b/a Sentry</td>
744
+ <td>Error and crash reporting and performance tracing for the web application, the mobile and desktop applications, the boards application and the websites. This is Sentry's hosted service with ingest in the United States, not a Sentry instance we run. It also records session replay — a masked reconstruction of the interface — for a sample of sessions and for sessions that produced an error; replay is consent-gated.</td>
745
+ <td>United States</td>
746
+ <td>IP address, user id and email address attached to an error, browser, operating system, device model and application version, the page or route in use, stack traces and request breadcrumbs, masked session replay recordings</td>
747
+ </tr>
748
+ <tr>
749
+ <td>Jitsu Labs, Inc.</td>
750
+ <td>Product analytics for the signed-in application. On each page you open it receives an identify event carrying your user id, email address and full name together with your organisation's tenant name and id, plus the page you navigated to. Its cookie is set on the ever.team domain, so it looks first-party to a scanner although the recipient is not us. Consent-gated as analytics.</td>
751
+ <td>United States</td>
752
+ <td>user id, email address, full name, tenant and organisation name and id, page URL and navigation history, IP address</td>
753
+ </tr>
754
+ <tr>
755
+ <td>ActiveCampaign, LLC (Postmark)</td>
756
+ <td>Transactional email delivery for the application — team invitations, email verification, sign-in codes and email-change confirmations. Every message the product sends you leaves through it.</td>
757
+ <td>United States</td>
758
+ <td>recipient email address, recipient and inviter name, message subject and body, including invitation links and sign-in codes, delivery, bounce and open metadata</td>
759
+ </tr>
760
+ <tr>
761
+ <td>Chatwoot Inc.</td>
762
+ <td>The in-application support chat widget, loaded from Chatwoot's hosted service at app.chatwoot.com — not the Chatwoot instance we run for other purposes. Consent-gated as a functional widget.</td>
763
+ <td>United States</td>
764
+ <td>support conversation content, name and email address if you supply them in the widget, IP address, browser, operating system and current page URL</td>
765
+ </tr>
766
+ <tr>
767
+ <td>Wasabi Technologies, Inc.</td>
768
+ <td>Object storage behind the platform's file-asset service. This is where avatars, task attachments and time-tracker SCREENSHOTS are written when the platform's file provider is set to Wasabi. Which provider is in the path is our configuration, not a setting you control — so we list both.</td>
769
+ <td>United States</td>
770
+ <td>screen captures of a monitored person's screen, profile photographs, task and message attachments</td>
771
+ </tr>
772
+ <tr>
773
+ <td>Cloudinary Ltd.</td>
774
+ <td>The alternative image store and delivery network behind the same platform file-asset service, holding the same categories of file as Wasabi. Listed for the same reason: which of the two is in the path is our configuration, not yours.</td>
775
+ <td>United States</td>
776
+ <td>screen captures of a monitored person's screen, profile photographs, task and message attachments, IP address of anyone fetching an image</td>
777
+ </tr>
778
+ <tr>
779
+ <td>Google LLC (Google Fonts)</td>
780
+ <td>Webfont delivery to the Ever Teams desktop application, the browser extension and the server-side PDF report renderer. The signed-in web application serves its fonts from our own infrastructure and does not contact this provider.</td>
781
+ <td>United States</td>
782
+ <td>IP address of the device fetching the font, user agent</td>
783
+ </tr>
784
+ <tr>
785
+ <td>650 Industries, Inc. (Expo)</td>
786
+ <td>Build service and over-the-air update delivery for the Ever Teams mobile application, which checks for a new JavaScript bundle each time it launches. Mobile application only — it is not involved if you use the web application.</td>
787
+ <td>United States</td>
788
+ <td>device IP address, platform, operating system version, application and runtime version, update channel, Expo installation identifier</td>
789
+ </tr>
790
+ <tr>
791
+ <td>iubenda s.r.l.</td>
792
+ <td>Cookie-consent banner and storage of your consent choice on the ever.team and apps.ever.team websites. It is not used inside the signed-in application.</td>
793
+ <td>Italy</td>
794
+ <td>IP address, consent choices, user agent, page URL</td>
795
+ </tr>
796
+ </tbody>
797
+ </table>
798
+ <p>The full and current list, including everything below, is published at
799
+ <a href="https://ever.team/subprocessors">https://ever.team/subprocessors</a>, together with the notice period and
800
+ objection procedure that apply when we add or replace one.</p>
801
+ <h3 id="three-tiers-and-why-the-difference-matters" tabindex="-1">Three tiers, and why the difference matters</h3>
802
+ <p>A single flat list of every vendor that appears anywhere in our software would be both inaccurate and
803
+ misleading, so the sub-processor page is split into three tiers. They mean genuinely different things.</p>
804
+ <ul>
805
+ <li><strong>Always engaged.</strong> The providers above. If you use the hosted Service, these are in the path.</li>
806
+ <li><strong>Engaged only if you turn something on.</strong> Optional integrations, connectors and features. A provider in
807
+ this tier is engaged only when you or your workspace administrator enables the specific feature or
808
+ connects the specific account it belongs to. Enable nothing and it is never involved. The list says which
809
+ feature or setting activates each one.</li>
810
+ <li><strong>Self-hosted deployments only.</strong> Several of our products are published as open source and can be run on
811
+ your own infrastructure. In that case <strong>you</strong> choose the database, object storage, email relay, AI
812
+ provider and everything else, using your own credentials. Those providers appear in the list so you can
813
+ see what the software can be pointed at — but they are <strong>your</strong> providers, not ours. <strong>We process nothing
814
+ in a deployment you run, we are not your processor for it, and the commitments in this policy do not
815
+ describe it.</strong></li>
816
+ </ul>
817
+ <h3 id="we-do-not-sell-your-personal-data" tabindex="-1">We do not sell your personal data</h3>
818
+ <p>We do not sell personal data, and we do not share it for cross-context behavioural advertising. We do not
819
+ supply it to data brokers, we do not trade it for services, and we do not permit any provider we engage to
820
+ use it to build advertising or interest profiles, on our sites or anywhere else.</p>
821
+ <h2 id="sending-personal-data-outside-the-eea" tabindex="-1">Sending personal data outside the EEA</h2>
822
+ <p>Most of the personal data we hold stays inside the European Economic Area, on infrastructure we operate
823
+ ourselves. Some of it does not: a number of the providers we engage are established outside the EEA —
824
+ principally in the United States — and some of them route, cache or store data on servers outside it.</p>
825
+ <p>Where that happens, the transfer needs a lawful mechanism under Chapter V GDPR. We use one of the
826
+ following for every transfer, and the sub-processor page names the destination country and the mechanism
827
+ provider by provider.</p>
828
+ <h3 id="adequacy" tabindex="-1">Adequacy</h3>
829
+ <p>Where the European Commission has decided that a country provides an adequate level of protection, the
830
+ transfer relies on that decision and needs nothing further. Adequacy decisions are kept under review by
831
+ the Commission and can be amended, suspended or repealed, so we monitor them rather than treat them as
832
+ permanent.</p>
833
+ <h3 id="providers-in-the-united-states" tabindex="-1">Providers in the United States</h3>
834
+ <p>For a US provider we rely on one of two things.</p>
835
+ <ul>
836
+ <li><strong>The EU–US Data Privacy Framework</strong>, but only where that provider is <em>actively self-certified</em> under it
837
+ for the type of data concerned. We check the official Data Privacy Framework list when we engage a
838
+ provider and re-check it periodically. <strong>We do not claim the Framework for a provider that has not
839
+ certified, or whose certification has lapsed.</strong></li>
840
+ <li><strong>Standard Contractual Clauses</strong> — the clauses approved by the European Commission in Implementing
841
+ Decision (EU) 2021/914, with the modules that match the relationship, together with a transfer impact
842
+ assessment and supplementary measures: encryption in transit and at rest, minimising what is sent in the
843
+ first place, contractual limits on onward disclosure, and a commitment from the provider to notify and
844
+ where possible challenge a government access request.</li>
845
+ </ul>
846
+ <p><strong>We keep Standard Contractual Clauses in place as the standing mechanism</strong>, including for providers that
847
+ are also certified under the Framework. That is deliberate, and here is the honest reason.</p>
848
+ <p>The Commission's adequacy decision for the Framework, adopted on 10 July 2023, is currently valid. It was
849
+ challenged, and on 3 September 2025 the General Court of the European Union dismissed that challenge in
850
+ <em>Latombe</em> (Case T-553/23). <strong>That is not the end of it</strong> — an appeal is pending before the Court of
851
+ Justice as Case C-703/25 P, and the two arrangements that preceded this one were each struck down by the
852
+ same court. So we treat the Framework as a mechanism under review rather than a settled answer, and we
853
+ keep a second mechanism standing behind it so that a change in the law is a paperwork event for us and not
854
+ an interruption for you.</p>
855
+ <h3 id="other-countries" tabindex="-1">Other countries</h3>
856
+ <p>For a transfer to any other country without an adequacy decision, we use Standard Contractual Clauses with
857
+ the same assessment and supplementary measures. Where a transfer is to the United Kingdom or Switzerland,
858
+ the corresponding UK and Swiss additions are applied to those clauses.</p>
859
+ <p>We rely on an Article 49 derogation — for example, a transfer that is strictly necessary to perform a
860
+ contract you have asked us to perform — only in a specific, occasional case where no other mechanism fits.
861
+ It is not a routine mechanism for us, and we do not use it to run a regular data flow.</p>
862
+ <h3 id="getting-a-copy-of-the-safeguards" tabindex="-1">Getting a copy of the safeguards</h3>
863
+ <p>You are entitled to see the safeguards we rely on. Write to privacy@ever.co naming the provider or the
864
+ transfer you are asking about, and we will send you a copy of the relevant clauses and tell you which
865
+ modules apply. We may redact commercial terms such as pricing and service levels; we do not redact the
866
+ data protection terms, which are the part that concerns you.</p>
867
+ <h2 id="how-long-we-keep-personal-data" tabindex="-1">How long we keep personal data</h2>
868
+ <p>&quot;As long as necessary&quot; is not an answer, so here are the actual periods. Each one runs from the event in
869
+ the middle column, and at the end of it we delete the data or irreversibly anonymise it.</p>
870
+ <table>
871
+ <thead>
872
+ <tr>
873
+ <th>What we hold</th>
874
+ <th>How long we keep it</th>
875
+ <th>Why that period</th>
876
+ </tr>
877
+ </thead>
878
+ <tbody>
879
+ <tr>
880
+ <td>Account and profile data — name, email address, workspace membership, settings</td>
881
+ <td>For as long as the account is open, then deleted within <strong>30 days</strong> of closure</td>
882
+ <td>We need it to give you the account; after that we do not</td>
883
+ </tr>
884
+ <tr>
885
+ <td>Content and files you put into the Service</td>
886
+ <td>For as long as the account is open; after it ends, available for export for <strong>30 days</strong>, then deleted</td>
887
+ <td>You decide what is in it — see below</td>
888
+ </tr>
889
+ <tr>
890
+ <td>Invoices, payment records and the tax data attached to them</td>
891
+ <td><strong>10 years</strong> from the end of the accounting year in which the transaction fell</td>
892
+ <td>Accounting and tax law in Bulgaria requires it, and we cannot shorten it at your request</td>
893
+ </tr>
894
+ <tr>
895
+ <td>Record that you accepted our terms — version, date, method</td>
896
+ <td><strong>5 years</strong> after the agreement ends</td>
897
+ <td>The general limitation period for a claim under the contract</td>
898
+ </tr>
899
+ <tr>
900
+ <td>Support correspondence and tickets</td>
901
+ <td><strong>24 months</strong> from the last message in the thread</td>
902
+ <td>Long enough to handle a recurring problem and a follow-up; not longer</td>
903
+ </tr>
904
+ <tr>
905
+ <td>Security, access and audit logs</td>
906
+ <td><strong>12 months</strong></td>
907
+ <td>Investigating unauthorised access, and evidencing that we did</td>
908
+ </tr>
909
+ <tr>
910
+ <td>Application and error logs, crash reports, diagnostics</td>
911
+ <td><strong>90 days</strong></td>
912
+ <td>Fixing what broke; they lose value quickly</td>
913
+ </tr>
914
+ <tr>
915
+ <td>Marketing contact records and the evidence of your consent</td>
916
+ <td>Until you object or withdraw. We then remove you from the lists and keep only a suppression record — your email address and the date — so that we do not contact you again</td>
917
+ <td>An unsubscribe that forgets you is not an unsubscribe</td>
918
+ </tr>
919
+ <tr>
920
+ <td>Cookie and consent choices</td>
921
+ <td>As stated in the <a href="https://ever.team/cookies">Cookie Policy</a>, which gives the lifetime of each entry</td>
922
+ <td>It belongs with the technology it describes</td>
923
+ </tr>
924
+ <tr>
925
+ <td>Backups</td>
926
+ <td>Each backup ages out on its own rolling cycle, within <strong>30 days</strong></td>
927
+ <td>Recovering from failure and ransomware, without becoming a second archive</td>
928
+ </tr>
929
+ <tr>
930
+ <td>Anything we are required to preserve for a legal claim, investigation or regulatory request</td>
931
+ <td>Until the claim, investigation or request ends, including any appeal period</td>
932
+ <td>We are not allowed to delete evidence, and neither are you</td>
933
+ </tr>
934
+ </tbody>
935
+ </table>
936
+ <h3 id="data-that-belongs-to-one-of-our-customers" tabindex="-1">Data that belongs to one of our customers</h3>
937
+ <p>For personal data held inside a customer's workspace — including anything the Service captures about that
938
+ customer's own personnel — <strong>the customer sets the retention period, not us</strong>. We are their processor for
939
+ it. The defaults and the limits of what they can configure are described in the product annex to this
940
+ policy.</p>
941
+ <p>We delete that data when the customer instructs us to, or at the end of the export window after their
942
+ agreement ends, whichever comes first. If you are one of their people and you want their data about you
943
+ deleted sooner, ask them — see the section on your rights, which explains how we route that.</p>
944
+ <h3 id="what-delete-means-here" tabindex="-1">What &quot;delete&quot; means here</h3>
945
+ <p>Deletion is applied to live systems straight away. Backup copies are not individually edited — doing so
946
+ would defeat what a backup is for — so a deleted record persists in backups until that backup ages out on
947
+ the cycle above, at most 30 days. During that window the data is not used for anything, and <strong>we do not
948
+ restore a backup to bring back data someone asked us to delete</strong>; a backup is restored only to recover a
949
+ whole system after a failure.</p>
950
+ <p>Where we can keep something useful without keeping you identifiable, we anonymise instead of deleting —
951
+ aggregate usage counts, for example. Once anonymised the data is no longer personal data, and it is not
952
+ possible for us to re-identify you from it.</p>
953
+ <h2 id="how-we-protect-personal-data" tabindex="-1">How we protect personal data</h2>
954
+ <p>We take the measures Article 32 GDPR requires: technical and organisational safeguards appropriate to the
955
+ risk, reviewed as the risk changes. In practice that means the following.</p>
956
+ <ul>
957
+ <li><strong>Encryption in transit.</strong> Traffic to and from the Service travels over TLS. HTTPS is enforced, and
958
+ plain HTTP requests are redirected rather than served.</li>
959
+ <li><strong>Encryption at rest.</strong> The storage holding customer content, databases and backups is encrypted at
960
+ rest, and particularly sensitive values — credentials, tokens and keys — are additionally encrypted at
961
+ the application layer rather than stored in readable form.</li>
962
+ <li><strong>Access control and least privilege.</strong> Access to production systems is limited to the people whose job
963
+ needs it, granted by named individual accounts rather than shared logins, protected by multi-factor
964
+ authentication, scoped to the narrowest role that works, and reviewed and revoked when a role changes or
965
+ someone leaves.</li>
966
+ <li><strong>Network segmentation.</strong> Databases, storage and internal services sit on segmented internal networks
967
+ and are not exposed to the public internet. Administrative interfaces are not publicly reachable.</li>
968
+ <li><strong>Logging.</strong> Administrative and security-relevant events are logged, retained for the period in the
969
+ retention section, and monitored so that unusual activity raises an alert rather than sitting unread.</li>
970
+ <li><strong>Backups.</strong> Data is backed up regularly, held on separate infrastructure from the live systems, and
971
+ restores are tested — an untested backup is a guess, not a control.</li>
972
+ <li><strong>Vulnerability management.</strong> Dependencies are scanned, code is analysed automatically before it ships,
973
+ security patches are applied on a defined schedule with a faster path for serious issues, and we operate
974
+ a responsible disclosure route so that anyone who finds a problem can tell us.</li>
975
+ <li><strong>Personnel.</strong> Everyone with access is bound by written confidentiality obligations that outlast their
976
+ engagement, works on a need-to-know basis, and has access removed when it is no longer needed.</li>
977
+ <li><strong>Providers.</strong> We assess a provider before we engage it, contract with it under Article 28 GDPR, and
978
+ hold it to security obligations at least as strict as our own.</li>
979
+ </ul>
980
+ <p>Our <a href="https://ever.team/security">Security page</a> sets out the detail, including which measure applies to
981
+ which part of the Service, our incident response process, and the shared responsibility split between what
982
+ we secure and what you secure.</p>
983
+ <h3 id="what-we-do-not-claim" tabindex="-1">What we do not claim</h3>
984
+ <p><strong>We do not hold a SOC 2 report and we are not certified to ISO/IEC 27001, and we do not claim either.</strong>
985
+ If anything you read or are told suggests otherwise, it is wrong, and we would like to know where it came
986
+ from. Where we describe a practice on this page or on the Security page, we describe something we actually
987
+ do; where we adopt a framework as a reference without being audited against it, we say so plainly rather
988
+ than implying a certification.</p>
989
+ <h3 id="no-system-is-perfectly-secure" tabindex="-1">No system is perfectly secure</h3>
990
+ <p><strong>No service, ours included, can be made completely secure, and anyone who tells you otherwise is
991
+ selling something.</strong> What we can honestly promise is that we take the measures above seriously, that we
992
+ keep them under review, and that if a personal data breach affects you we will act on it: we notify the
993
+ CPDP where the law requires it, within the deadline it sets, and we
994
+ tell affected people directly without undue delay where the breach is likely to result in a high risk to
995
+ them.</p>
996
+ <p>Your part matters too. Use a strong and unique password, turn on multi-factor authentication where it is
997
+ offered, keep your devices patched, and do not share credentials or access tokens. If you think an account
998
+ has been compromised, tell us at privacy@ever.co immediately.</p>
999
+ <h2 id="your-rights-over-your-personal-data" tabindex="-1">Your rights over your personal data</h2>
1000
+ <p>Where we are the controller, the GDPR gives you the rights below. They are yours to use, you do not have
1001
+ to explain why you are using them, and using one costs you nothing.</p>
1002
+ <ul>
1003
+ <li><strong>Access</strong> — ask whether we hold personal data about you and, if we do, get a copy of it together with
1004
+ the information in this policy about how it is used. (Article 15)</li>
1005
+ <li><strong>Rectification</strong> — have inaccurate data corrected and incomplete data completed. Much of this you can
1006
+ do yourself in your account settings, which is faster than asking us. (Article 16)</li>
1007
+ <li><strong>Erasure</strong> — have data deleted where we no longer need it for the purpose we collected it for, where
1008
+ you withdraw the consent it rested on, or where we have processed it unlawfully. (Article 17)</li>
1009
+ <li><strong>Restriction</strong> — have us pause processing while a dispute is sorted out: while we check an accuracy
1010
+ challenge, for example, or while we consider an objection. We keep the data but stop using it.
1011
+ (Article 18)</li>
1012
+ <li><strong>Portability</strong> — receive the data you gave us, in a structured, commonly used, machine-readable format,
1013
+ and have it sent to another provider where that is technically feasible. This applies to data processed
1014
+ by automated means on the basis of your consent or a contract with you. (Article 20)</li>
1015
+ <li><strong>Objection</strong> — object to processing we base on our legitimate interests. We then stop unless we can
1016
+ demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or unless
1017
+ we need the data for a legal claim. (Article 21(1))</li>
1018
+ <li><strong>Objection to direct marketing</strong> — <strong>absolute, and there is nothing to weigh.</strong> If you tell us to stop
1019
+ using your data for direct marketing, including any profiling connected to it, we stop. No balancing
1020
+ test, no grace period, no exceptions. (Article 21(2))</li>
1021
+ </ul>
1022
+ <p>You also have the right to withdraw consent where consent is what we rely on, which has its own section
1023
+ below, and the right to complain to a supervisory authority, which has the section after that.</p>
1024
+ <p>Some of these rights have limits written into the law itself. Erasure does not override an obligation to
1025
+ keep invoices for the statutory accounting period, and portability does not extend to data we inferred or
1026
+ generated rather than received from you. <strong>Where we cannot do all of what you ask, we will tell you which
1027
+ part we cannot do and why</strong>, rather than declining as a whole.</p>
1028
+ <h3 id="how-to-make-a-request" tabindex="-1">How to make a request</h3>
1029
+ <p>Write to privacy@ever.co. Tell us which right you are using and enough about yourself for us to find
1030
+ the right records — the email address on the account is usually enough. You can also write to us by post
1031
+ at the address at the end of this policy.</p>
1032
+ <ul>
1033
+ <li><strong>It is free.</strong> We charge nothing for a request. If a request is manifestly unfounded or excessive,
1034
+ particularly because it repeats one we have already answered, the law lets us charge a reasonable fee
1035
+ based on our administrative cost or refuse it. If we ever do either, we will explain why and tell you
1036
+ how to challenge that decision.</li>
1037
+ <li><strong>We answer within one month</strong> of receiving the request. Where a request is complex, or where you have
1038
+ made several, we may extend that by up to two further months — and if we do, <strong>we will tell you within
1039
+ the first month, and tell you why</strong>.</li>
1040
+ <li><strong>We check who you are</strong> before we hand over personal data, because the alternative is handing your data
1041
+ to someone who claims to be you. We ask for the least that makes us confident, usually a reply from the
1042
+ email address already on the account. We ask for an identity document only where nothing lighter works,
1043
+ and anything you send us for verification is used for that and nothing else, then deleted.</li>
1044
+ </ul>
1045
+ <h3 id="if-your-data-sits-in-a-customers-workspace" tabindex="-1">If your data sits in a customer's workspace</h3>
1046
+ <p><strong>This is the most important paragraph on this page for many of the people who read it.</strong></p>
1047
+ <p>A large part of the personal data in the Service was put there by one of our customers — your employer,
1048
+ the organisation whose workspace you belong to, or the operator of a site built on our platform. Where the
1049
+ Service captures data about how an organisation's own personnel work, that data belongs to that
1050
+ organisation's workspace.</p>
1051
+ <p><strong>For that data the customer is the controller and we are only their processor.</strong> We process it on their
1052
+ documented instructions and for no purpose of our own, so the law directs your request to them, not to us.
1053
+ Practically:</p>
1054
+ <ul>
1055
+ <li><strong>Send your request to that organisation.</strong> They decide it, and they are the ones who have to answer you
1056
+ within the deadline.</li>
1057
+ <li><strong>If you send it to us instead, we will not ignore it.</strong> We will forward it to the relevant customer
1058
+ promptly, tell you that we have done so, and assist them in answering it as our Data Processing Addendum
1059
+ requires.</li>
1060
+ <li><strong>We will not decide the request ourselves, and we will not delete, correct or hand over data from a
1061
+ customer's workspace without their instruction</strong> — unless a law that applies to us requires it. That is
1062
+ not us being unhelpful: acting on a workspace's data without the controller's instruction is precisely
1063
+ what a processor is not allowed to do.</li>
1064
+ </ul>
1065
+ <p>If you are not sure which of the two situations you are in, ask us at privacy@ever.co and we will tell
1066
+ you, and point you to the right organisation if it is not us.</p>
1067
+ <h2 id="withdrawing-your-consent" tabindex="-1">Withdrawing your consent</h2>
1068
+ <p>Where we rely on your consent for something, <strong>you can withdraw it at any time, and withdrawing is as easy
1069
+ as giving it</strong>. You do not have to give a reason, and we do not ask you to justify it.</p>
1070
+ <p>Withdrawing consent stops the processing from that point onwards. <strong>It does not make what we did before
1071
+ unlawful</strong> — processing carried out while your consent was in force stays lawful, and withdrawal does not
1072
+ undo it. What it does mean is that we stop, and that we do not start again unless you tell us to.</p>
1073
+ <h3 id="how-to-withdraw-purpose-by-purpose" tabindex="-1">How to withdraw, purpose by purpose</h3>
1074
+ <ul>
1075
+ <li><strong>Cookies and similar technologies</strong> — open the <strong>Cookie preferences</strong> link in the footer of any page on
1076
+ <a href="https://ever.team">ever.team</a>, turn off the categories you no longer want, and save. The change
1077
+ takes effect immediately. Details are in our <a href="https://ever.team/cookies">Cookie Policy</a>.</li>
1078
+ <li><strong>Marketing emails</strong> — use the unsubscribe link at the bottom of any message we send you, or write to
1079
+ privacy@ever.co and ask us to stop. Either route works, and the unsubscribe link does not require
1080
+ you to sign in or find your password first.</li>
1081
+ <li><strong>Optional features and integrations you switched on</strong> — turn the feature off, or disconnect the
1082
+ connected account, in your settings. If you cannot find the switch, ask us at privacy@ever.co and we
1083
+ will turn it off for you.</li>
1084
+ </ul>
1085
+ <p>If you have consented to something not listed here, write to privacy@ever.co naming it, and we will
1086
+ act on it the same way.</p>
1087
+ <h3 id="what-happens-next" tabindex="-1">What happens next</h3>
1088
+ <p>We stop the processing, and we remove you from the relevant list or turn the relevant feature off. We keep
1089
+ the minimum record needed to show that you consented and that you withdrew, because being able to evidence
1090
+ consent is itself a legal requirement — for how long, see the retention section.</p>
1091
+ <p><strong>We will not quietly move the same processing onto a different legal basis to keep it running.</strong> If some
1092
+ part of what you asked us to stop genuinely rests on another basis as well — an invoice we are required to
1093
+ keep, for example — we will tell you which part and why, rather than leaving you to discover it.</p>
1094
+ <p>Most of what we do is not based on consent at all. It rests on performing our contract with you, on legal
1095
+ obligations, or on legitimate interests. <strong>Withdrawing consent therefore does not close your account or
1096
+ switch off the Service</strong> — it affects only the things you consented to.</p>
1097
+ <h2 id="complaining-to-a-supervisory-authority" tabindex="-1">Complaining to a supervisory authority</h2>
1098
+ <p>If you think we have handled your personal data badly or unlawfully, <strong>you have the right to complain to a
1099
+ data protection supervisory authority</strong>. That right is yours regardless of anything else in this policy.</p>
1100
+ <p>We would like the chance to put it right first. Write to privacy@ever.co, tell us what went wrong, and
1101
+ we will look into it and come back to you. In most cases that is the quickest way to get the outcome you
1102
+ actually want. <strong>You are not required to do this, and it is not a condition of complaining</strong> — you can go
1103
+ straight to an authority, and you can do it at any point, including while we are still dealing with your
1104
+ complaint.</p>
1105
+ <h3 id="our-lead-supervisory-authority" tabindex="-1">Our lead supervisory authority</h3>
1106
+ <p>We are established in Bulgaria, so our lead authority is the
1107
+ <strong>Commission for Personal Data Protection (Комисия за защита на личните данни)</strong> — the CPDP. Its website,
1108
+ including its complaint form and current contact details, is at
1109
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>.</p>
1110
+ <h3 id="you-can-also-complain-closer-to-home" tabindex="-1">You can also complain closer to home</h3>
1111
+ <p>Under Article 77 GDPR you may lodge your complaint with the supervisory authority in the EU or EEA country:</p>
1112
+ <ul>
1113
+ <li>where you live;</li>
1114
+ <li>where you work; or</li>
1115
+ <li>where the thing you are complaining about took place.</li>
1116
+ </ul>
1117
+ <p>You do not have to use ours, and you do not need our agreement to use another one. If you complain to your
1118
+ local authority, it will co-operate with ours through the mechanism the GDPR sets up for exactly this
1119
+ situation, so nothing is lost by choosing whichever is easiest for you.</p>
1120
+ <p>You also have the right to an effective judicial remedy — against a supervisory authority's decision, and
1121
+ against us directly — in the courts of the country where you live or where we are established. Complaining
1122
+ to an authority does not use up that right.</p>
1123
+ <h2 id="automated-decision-making-and-profiling" tabindex="-1">Automated decision-making and profiling</h2>
1124
+ <p><strong>We do not make decisions about you that produce legal effects concerning you, or that similarly
1125
+ significantly affect you, based solely on automated processing.</strong> No algorithm of ours decides whether you
1126
+ are hired, paid, promoted, disciplined, dismissed, given credit, or charged a different price. Where a
1127
+ decision of that kind is made about you by an organisation using the Service, a person at that
1128
+ organisation makes it.</p>
1129
+ <p>We do use automated rules to detect fraud, spam, abuse and attacks against the Service — rate limits,
1130
+ anomaly detection, and similar. Those rules can block a request or temporarily restrict an account. If one
1131
+ of them affects you, write to privacy@ever.co and a person will review it.</p>
1132
+ <h3 id="where-a-customer-turns-on-ai-features-be-aware-of-this" tabindex="-1">Where a customer turns on AI features, be aware of this</h3>
1133
+ <p>This is the part worth reading carefully, because it is easy to misunderstand.</p>
1134
+ <p>Some of our products capture activity data on behalf of a customer — an employer, typically — and some of
1135
+ them offer optional AI features on top of it. <strong>Where a customer enables those features, the Service can
1136
+ generate automated assessments of the activity it captures.</strong> The clearest example: classifying whether
1137
+ the content of a captured screen appears to be work-related. Other examples include scoring or summarising
1138
+ captured activity and grouping it into categories.</p>
1139
+ <p>Four things follow, and we would rather state them plainly than let them be discovered later.</p>
1140
+ <ul>
1141
+ <li><strong>The output goes to the customer, not to us.</strong> It is presented to the organisation whose workspace the
1142
+ data belongs to. <strong>That organisation is the controller of it, and we are only its processor.</strong></li>
1143
+ <li><strong>The customer decides what, if anything, to do with it.</strong> We do not act on these assessments, we do not
1144
+ use them for any purpose of our own, and we do not share them with anyone else.</li>
1145
+ <li><strong>These outputs are not decisions, and must not be used as if they were.</strong> An automated assessment is an
1146
+ input to a human judgement. <strong>Our terms require the customer not to treat an output of the Service as an
1147
+ automated decision about a person, and to apply meaningful human review before acting on one.</strong> Whether
1148
+ any particular use is lawful where that customer operates — including the lawful basis for it, the
1149
+ notices it has to give, any impact assessment it has to carry out, and any consultation with employee
1150
+ representatives it has to run — is that customer's responsibility to determine, not ours.</li>
1151
+ <li><strong>They can be wrong.</strong> A classifier reading a screen has no idea what your job is. It can label genuine
1152
+ work as unrelated, and it can miss the opposite. Anyone relying on one of these outputs should treat it
1153
+ as a rough signal, and we say so to our customers as well as to you.</li>
1154
+ </ul>
1155
+ <h3 id="if-an-assessment-about-you-has-been-generated" tabindex="-1">If an assessment about you has been generated</h3>
1156
+ <p>Ask the organisation whose workspace holds the data — normally your employer. You can ask them for human
1157
+ involvement, for an explanation of how the assessment was reached, to express your point of view, and to
1158
+ contest the result. They are the controller, so they are the ones who have to answer.</p>
1159
+ <p>If you send that request to us, we will forward it to them promptly, tell you we have done so, and assist
1160
+ them in answering it. See the routing paragraph in the section on your rights, which explains why we
1161
+ cannot decide it ourselves.</p>
1162
+ <h2 id="children" tabindex="-1">Children</h2>
1163
+ <p><strong>The Service is not directed at children, and we do not knowingly collect personal data from them.</strong> It
1164
+ is a business product, bought by organisations and used by the people who work in them. We do not design
1165
+ it for children, we do not market it to them, and we do not offer accounts to them.</p>
1166
+ <p>Where consent is the basis for an online service offered directly to a child, the GDPR sets the age at
1167
+ which the child can consent alone. <strong>In Bulgaria that age is 14.</strong> Other EU and EEA countries set
1168
+ it anywhere between 13 and 16, and the age in the country where the child lives is the one that applies.
1169
+ Below that age, consent has to come from — or be authorised by — a holder of parental responsibility.
1170
+ Because we do not offer the Service to children, we do not operate a parental consent mechanism, and a
1171
+ child under the applicable age should not create an account or submit personal data to us.</p>
1172
+ <h3 id="if-a-childs-data-has-reached-us" tabindex="-1">If a child's data has reached us</h3>
1173
+ <p>Tell us. Write to privacy@ever.co with enough detail for us to find the record — an email address, an
1174
+ account name, or the page where the data was submitted. You do not need to prove anything first, and you
1175
+ do not need to be the child's parent to report it.</p>
1176
+ <p>We will check, and where we confirm that we hold personal data collected from a child without proper
1177
+ authorisation, <strong>we will delete it without undue delay</strong>, keeping only what a law that applies to us
1178
+ requires us to keep.</p>
1179
+ <p>If the data sits inside one of our customers' workspaces rather than in our own records, the customer is
1180
+ the controller of it. Tell them as well, and tell us — we will forward your report to them and press for
1181
+ it to be dealt with, as the routing paragraph in the section on your rights describes.</p>
1182
+ <h2 id="links-and-content-from-other-sites" tabindex="-1">Links and content from other sites</h2>
1183
+ <p>Our websites and the Service link to services we do not run, and some pages embed content that other
1184
+ people host — videos, maps, code repositories, documentation and similar.</p>
1185
+ <p>Following a link takes you somewhere this policy does not reach. Loading embedded content means the
1186
+ provider hosting it receives data directly from your browser, typically your IP address, your device and
1187
+ browser details, and the page you were on, and it may set its own cookies.</p>
1188
+ <p><strong>We do not control those services, and this policy does not apply to them.</strong> What they collect and what
1189
+ they do with it is governed by their own privacy notice, which is the one to read before you use them.
1190
+ Where embedded content is not strictly necessary to deliver a page, we load it only once you have agreed
1191
+ to the relevant cookie category — see our <a href="https://ever.team/cookies">Cookie Policy</a>.</p>
1192
+ <p>A link is not an endorsement. If a link from our site takes you somewhere that mishandles your data, we
1193
+ would like to know at privacy@ever.co so we can reconsider carrying it.</p>
1194
+ <h2 id="changes-to-this-policy" tabindex="-1">Changes to this policy</h2>
1195
+ <p>This policy changes when the Service changes, when we engage or replace a provider, or when the law moves.
1196
+ We would rather update it than let it drift out of date and quietly stop being true.</p>
1197
+ <p>Every version carries a version number and the date it takes effect, shown at the top of the page. <strong>This
1198
+ is version 1.0.0, in force from 2026-08-02.</strong></p>
1199
+ <h3 id="how-we-tell-you" tabindex="-1">How we tell you</h3>
1200
+ <ul>
1201
+ <li><strong>Minor changes</strong> — clarifying wording, correcting a mistake, adding a provider of a kind already
1202
+ described — are published with a new version number and a new effective date. We do not send a separate
1203
+ notice for these.</li>
1204
+ <li><strong>Material changes</strong> — a new purpose, a new category of personal data, a new category of recipient, a
1205
+ longer retention period, a change to how you exercise your rights, or a change to the legal basis we
1206
+ rely on — are notified <strong>at least 30 days before they take effect</strong>, by email to account holders and by
1207
+ a notice on the site. That gives you time to read them and to act before they apply.</li>
1208
+ <li><strong>Changes that need your consent</strong> are not made by publishing a new version. We ask you, and we treat
1209
+ silence as a no.</li>
1210
+ </ul>
1211
+ <p>This policy is a notice, not a contract. <strong>We do not ask you to accept it</strong>, and continuing to use the
1212
+ Service is not us collecting your agreement to it. Where we genuinely need your agreement to something, we
1213
+ ask for it separately and record it.</p>
1214
+ <h3 id="previous-versions-stay-available" tabindex="-1">Previous versions stay available</h3>
1215
+ <p>We do not overwrite the past. <strong>Every version of this policy that we have published remains available</strong>,
1216
+ with the dates it was in force, from the version history linked at the foot of
1217
+ <a href="https://ever.team/privacy">https://ever.team/privacy</a>. If you want to know what we said about your data on a
1218
+ particular date, that is where to look — and if you cannot find it, ask us at privacy@ever.co and we
1219
+ will send it to you.</p>
1220
+ <h2 id="how-to-contact-us" tabindex="-1">How to contact us</h2>
1221
+ <p>The controller for the personal data described in this policy is <strong>Ever Technologies LTD</strong>, registered in
1222
+ Bulgaria under company number 204599535, with its registered office at
1223
+ Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.</p>
1224
+ <ul>
1225
+ <li><strong>Privacy questions, and any request about your personal data</strong> — privacy@ever.co</li>
1226
+ <li><strong>Data protection correspondence</strong> — dpo@ever.co</li>
1227
+ </ul>
1228
+ <p>Both addresses are monitored by the same people, and either will reach us. By post, write to the registered
1229
+ office above and mark the letter for the attention of the privacy team. We correspond in English.</p>
1230
+ <p><strong>We have not designated a Data Protection Officer under Article 37 GDPR.</strong> The dpo@ever.co address is
1231
+ a contact channel, not a designation, and we will not describe it as one. If that position changes, this
1232
+ policy will say so and will give the designated office's contact details.</p>
1233
+ <p>If your question is about personal data held inside one of our customers' workspaces, that customer is the
1234
+ controller and the request goes to them — see the routing paragraph in the section on your rights. Write to
1235
+ us anyway if you are unsure, and we will tell you who to ask.</p>
1236
+ <p>This document is version 1.0.0 of the Privacy Policy for
1237
+ <a href="https://ever.team">ever.team</a>, in force from 2026-08-02. Earlier versions, with the
1238
+ dates they applied, are at <a href="https://ever.team/privacy">https://ever.team/privacy</a>.</p>