@ever-co/legal 0.1.2 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (88) hide show
  1. package/dist/content/aup/ever-async/en.html +778 -0
  2. package/dist/content/aup/ever-async/en.json +343 -0
  3. package/dist/content/aup/hust/en.html +9 -0
  4. package/dist/content/aup/hust/en.json +2 -2
  5. package/dist/content/cookies/ever-async/en.html +457 -0
  6. package/dist/content/cookies/ever-async/en.json +185 -0
  7. package/dist/content/cookies/ever-demand/en.html +5 -2
  8. package/dist/content/cookies/ever-demand/en.json +2 -2
  9. package/dist/content/cookies/ever-rec/en.html +5 -2
  10. package/dist/content/cookies/ever-rec/en.json +2 -2
  11. package/dist/content/cookies/ever-teams/en.html +5 -2
  12. package/dist/content/cookies/ever-teams/en.json +2 -2
  13. package/dist/content/cookies/ever-works/en.html +5 -2
  14. package/dist/content/cookies/ever-works/en.json +2 -2
  15. package/dist/content/cookies/gauzy/en.html +5 -2
  16. package/dist/content/cookies/gauzy/en.json +2 -2
  17. package/dist/content/cookies/githands/en.html +5 -2
  18. package/dist/content/cookies/githands/en.json +2 -2
  19. package/dist/content/cookies/hust/en.html +5 -2
  20. package/dist/content/cookies/hust/en.json +2 -2
  21. package/dist/content/dpa/ever-async/en.html +1848 -0
  22. package/dist/content/dpa/ever-async/en.json +640 -0
  23. package/dist/content/privacy/ever-async/en.html +1350 -0
  24. package/dist/content/privacy/ever-async/en.json +364 -0
  25. package/dist/content/privacy/ever-corporate/en.html +86 -3
  26. package/dist/content/privacy/ever-corporate/en.json +2 -2
  27. package/dist/content/privacy/ever-demand/en.html +99 -2
  28. package/dist/content/privacy/ever-demand/en.json +2 -2
  29. package/dist/content/privacy/ever-rec/en.html +110 -3
  30. package/dist/content/privacy/ever-rec/en.json +2 -2
  31. package/dist/content/privacy/ever-teams/en.html +97 -1
  32. package/dist/content/privacy/ever-teams/en.json +2 -2
  33. package/dist/content/privacy/ever-tech/en.html +86 -3
  34. package/dist/content/privacy/ever-tech/en.json +2 -2
  35. package/dist/content/privacy/ever-works/en.html +74 -5
  36. package/dist/content/privacy/ever-works/en.json +2 -2
  37. package/dist/content/privacy/everiq/en.html +107 -0
  38. package/dist/content/privacy/everiq/en.json +2 -2
  39. package/dist/content/privacy/gauzy/en.html +88 -3
  40. package/dist/content/privacy/gauzy/en.json +2 -2
  41. package/dist/content/privacy/githands/en.html +83 -2
  42. package/dist/content/privacy/githands/en.json +2 -2
  43. package/dist/content/privacy/hust/en.html +186 -37
  44. package/dist/content/privacy/hust/en.json +3 -3
  45. package/dist/content/privacy/traduora/en.html +93 -0
  46. package/dist/content/privacy/traduora/en.json +2 -2
  47. package/dist/content/refund/ever-rec/en.html +595 -0
  48. package/dist/content/refund/ever-rec/en.json +336 -0
  49. package/dist/content/security/ever-async/en.html +853 -0
  50. package/dist/content/security/ever-async/en.json +417 -0
  51. package/dist/content/security/ever-corporate/en.html +768 -0
  52. package/dist/content/security/ever-corporate/en.json +380 -0
  53. package/dist/content/security/ever-tech/en.html +768 -0
  54. package/dist/content/security/ever-tech/en.json +380 -0
  55. package/dist/content/security/traduora/en.html +768 -0
  56. package/dist/content/security/traduora/en.json +380 -0
  57. package/dist/content/subprocessors/ever-async/en.html +852 -0
  58. package/dist/content/subprocessors/ever-async/en.json +166 -0
  59. package/dist/content/subprocessors/ever-corporate/en.html +403 -9
  60. package/dist/content/subprocessors/ever-corporate/en.json +6 -2
  61. package/dist/content/subprocessors/ever-demand/en.html +443 -13
  62. package/dist/content/subprocessors/ever-demand/en.json +6 -2
  63. package/dist/content/subprocessors/ever-rec/en.html +493 -10
  64. package/dist/content/subprocessors/ever-rec/en.json +6 -2
  65. package/dist/content/subprocessors/ever-teams/en.html +435 -8
  66. package/dist/content/subprocessors/ever-teams/en.json +6 -2
  67. package/dist/content/subprocessors/ever-tech/en.html +443 -9
  68. package/dist/content/subprocessors/ever-tech/en.json +6 -2
  69. package/dist/content/subprocessors/ever-works/en.html +354 -13
  70. package/dist/content/subprocessors/ever-works/en.json +6 -2
  71. package/dist/content/subprocessors/everiq/en.html +484 -3
  72. package/dist/content/subprocessors/everiq/en.json +6 -2
  73. package/dist/content/subprocessors/gauzy/en.html +353 -20
  74. package/dist/content/subprocessors/gauzy/en.json +6 -2
  75. package/dist/content/subprocessors/githands/en.html +451 -13
  76. package/dist/content/subprocessors/githands/en.json +6 -2
  77. package/dist/content/subprocessors/hust/en.html +502 -12
  78. package/dist/content/subprocessors/hust/en.json +14 -2
  79. package/dist/content/subprocessors/traduora/en.html +461 -4
  80. package/dist/content/subprocessors/traduora/en.json +6 -2
  81. package/dist/content/tos/ever-async/en.html +1350 -0
  82. package/dist/content/tos/ever-async/en.json +687 -0
  83. package/dist/content/tos/ever-rec/en.html +40 -11
  84. package/dist/content/tos/ever-rec/en.json +5 -5
  85. package/dist/content/tos/hust/en.html +32 -8
  86. package/dist/content/tos/hust/en.json +10 -2
  87. package/dist/index.json +12493 -8166
  88. package/package.json +1 -1
@@ -0,0 +1,1350 @@
1
+ <h1 id="privacy-policy" tabindex="-1">Privacy Policy</h1>
2
+ <p><strong>Ever Async</strong> — <a href="https://async.ever.co">async.ever.co</a></p>
3
+ <p>Version 1.0.2 · In force from 2026-08-02</p>
4
+ <p>This notice explains what we do with personal data when you use the Ever Async hosted service and the websites,
5
+ applications and application programming interfaces we make available at <a href="https://async.ever.co">async.ever.co</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://async.ever.co">async.ever.co</a> and the pages served from it.</li>
14
+ <li>The the Ever Async hosted service 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 Async — 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 Async, 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 the Ever Async hosted service 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 Async 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 Async 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://async.ever.co/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 the Ever Async hosted service: 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://async.ever.co/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 Async provides, and what its defaults are, is set out in the annex later
489
+ in this notice.</p>
490
+ <h2 id="ever-async-what-actually-happens-to-what-people-write" tabindex="-1">Ever Async: what actually happens to what people write</h2>
491
+ <p><strong>Where this annex and a general section above differ, this annex is the accurate one for
492
+ Ever Async.</strong></p>
493
+ <p>Ever Async sits between a team's chat platform and its work tools. When a conversation is connected,
494
+ <strong>every message posted in it passes through our pipeline</strong> — classified, then enriched by fanning the
495
+ references it contains out to the connectors, then either acted on or dropped. So the honest starting
496
+ point is that this product sees a whole channel, including the parts of it that have nothing to do with
497
+ work, and including messages from people who never signed up for anything.</p>
498
+ <p>The rest of this annex is about what happens to that text afterwards, and the answer is unusual enough to
499
+ lead with.</p>
500
+ <h3 id="a-message-body-is-written-to-disk-for-150-seconds-and-only-when-a-nudge-is-pending" tabindex="-1">A message body is written to disk for 150 seconds, and only when a nudge is pending</h3>
501
+ <p><strong>There is no message-text column in our database.</strong> The events table stores a tenant, a channel, a
502
+ conversation, a message identifier, a thread root, an author identifier, an edit flag and a timestamp —
503
+ and no text. The nudges table stores an author identifier and a timestamp. The contexts table stores a
504
+ count.</p>
505
+ <p><strong>There is exactly one exception, and it is the whole of it.</strong> When the product decides to nudge someone,
506
+ it schedules the nudge and waits — 150 seconds in every environment we run — so the author has a chance to
507
+ fix the message themselves. The suggested rewrite is generated when the nudge fires rather than when it is
508
+ scheduled, so <strong>the original message text is held in the pending-nudge record for that window</strong>. It is
509
+ deleted when the nudge fires, and deleted when the author self-corrects and the nudge is cancelled.</p>
510
+ <p>That is the only place a chat message body persists. Everything else about a message is metadata: who
511
+ posted, where, when, whether it was an edit, and what was extracted from it.</p>
512
+ <p><strong>We are not claiming the text is never processed</strong> — it is, in memory, for every observed message, and it
513
+ is sent to a model provider under the conditions below. We are claiming it is not kept, and the storage
514
+ layer is where you can check that.</p>
515
+ <h3 id="the-other-half-of-the-truth-nothing-expires-on-its-own" tabindex="-1">The other half of the truth: nothing expires on its own</h3>
516
+ <p><strong>There is no retention job in Ever Async today.</strong> No scheduled purge, no age-based delete, nothing
517
+ that prunes an old row. The events, seen-event, nudge and context tables grow without bound and are
518
+ deleted only when the tenant is deleted.</p>
519
+ <p>We could print a tidy retention period here. It would not be enforced by anything, and a retention promise
520
+ the code does not keep is worse than an uncomfortable fact. <strong>The metadata described above is kept until
521
+ the tenant is deleted, and there is no automatic expiry.</strong> Introducing one is work we intend to do, and
522
+ when it exists this table will say what it does.</p>
523
+ <h3 id="what-is-held-grouped-by-where-it-comes-from" tabindex="-1">What is held, grouped by where it comes from</h3>
524
+ <ul>
525
+ <li><strong>From every message in a connected conversation</strong> — the plain-text body, in transit through the
526
+ pipeline; the author's chat user identifier; the identifiers of anyone they mentioned; any URLs they
527
+ posted and the references extracted from the message; the workspace or guild identifier, the
528
+ conversation identifier, the message identifier and the thread root; the timestamp and whether it was an
529
+ edit.</li>
530
+ <li><strong>In memory only, never written to a table</strong> — the author's display name and whether the account is a
531
+ bot.</li>
532
+ <li><strong>From a pending nudge</strong> — the original message text, for the grace window described above.</li>
533
+ <li><strong>From the connectors</strong> — what they return: pull request, issue and task titles, states and URLs, and
534
+ the names of their authors and assignees.</li>
535
+ <li><strong>From counters</strong> — per-tenant totals of messages observed, nudges sent and context items attached.</li>
536
+ <li><strong>From sign-in</strong> — see the next section, because it is shorter than you expect.</li>
537
+ <li><strong>From the workspace itself</strong> — the tenant record, memberships and roles, the workspace binding, the
538
+ policy settings and the charter text.</li>
539
+ </ul>
540
+ <h3 id="sign-in-holds-less-than-almost-any-product-we-run" tabindex="-1">Sign-in holds less than almost any product we run</h3>
541
+ <p><strong>There is no email column anywhere in the schema.</strong> That is not a rounding of the truth, it is the shape
542
+ of the database.</p>
543
+ <ul>
544
+ <li><strong>Single sign-on.</strong> Where you sign in through Slack, Discord, GitHub, Google or Ever Gauzy, the provider
545
+ returns a provider user identifier, a verified email address and a display name. <strong>The email address and
546
+ the name are held in an in-memory session and are lost when the process restarts.</strong> The only piece that
547
+ reaches a database is the provider user identifier, on the memberships record with the tenant and the
548
+ roles.</li>
549
+ <li><strong>Local accounts.</strong> These are supplied to the deployment as an environment variable containing an email
550
+ address and an Argon2id password hash. They are never written to a database.</li>
551
+ <li><strong>API tokens.</strong> Static tokens of the form user id, role and secret, also supplied as an environment
552
+ variable.</li>
553
+ </ul>
554
+ <p>The practical consequence: <strong>we usually cannot tell you a person's email address from our own records,
555
+ because we do not have it.</strong> A rights request that identifies a person by email may need the chat user
556
+ identifier as well, and we will say so rather than guess.</p>
557
+ <h3 id="the-gauzy-user-map-a-chat-identity-wired-to-an-employee-record" tabindex="-1">The Gauzy user map: a chat identity wired to an employee record</h3>
558
+ <p><strong>This is the sharpest disclosure in the product, so it has its own heading.</strong></p>
559
+ <p>The Ever Gauzy connector takes a static map from a chat user identifier to an Ever Gauzy employee
560
+ identifier. <strong>It is a direct link between somebody's chat account and their HR record</strong>, configured by an
561
+ administrator, without the employee being asked or necessarily told. It is what makes a phrase like &quot;my
562
+ last task&quot; resolvable.</p>
563
+ <ul>
564
+ <li><strong>The customer configures it, and the customer is the controller of it.</strong> We hold the map because they
565
+ put it in their configuration.</li>
566
+ <li><strong>Once a request crosses into Ever Gauzy, that is a separate service</strong> with its own privacy notice, and
567
+ that notice governs what happens there.</li>
568
+ <li>If a map entry about you exists and you did not know, <strong>ask the organisation that runs the workspace
569
+ first</strong> — it is theirs. Write to privacy@ever.co if that gets you nowhere and we will help you reach
570
+ them.</li>
571
+ </ul>
572
+ <p>Not configured, no map, no linkage: the connector simply does not resolve personal references.</p>
573
+ <h3 id="what-leaves-for-a-model-provider-and-exactly-when" tabindex="-1">What leaves for a model provider, and exactly when</h3>
574
+ <p>The prompt is not a mystery: <strong>the classification prompt embeds the message text verbatim</strong> alongside a
575
+ link count and a mention count, and the rewrite prompt adds the resolved context items and <strong>the
576
+ workspace's charter</strong>.</p>
577
+ <table>
578
+ <thead>
579
+ <tr>
580
+ <th>Configuration</th>
581
+ <th>Does the message text leave?</th>
582
+ </tr>
583
+ </thead>
584
+ <tbody>
585
+ <tr>
586
+ <td>No <code>[llm]</code> provider configured</td>
587
+ <td><strong>No.</strong> Classification runs on plain heuristics and nothing is sent anywhere</td>
588
+ </tr>
589
+ <tr>
590
+ <td>Provider configured, sensitivity <strong>conservative</strong></td>
591
+ <td><strong>No.</strong> The model is never consulted at this setting</td>
592
+ </tr>
593
+ <tr>
594
+ <td>Provider configured, sensitivity <strong>balanced</strong> or <strong>high</strong></td>
595
+ <td><strong>Yes</strong> — but only for the ambiguous middle of the classifier's range, and only to the provider you configured</td>
596
+ </tr>
597
+ <tr>
598
+ <td>Provider is a local runtime you run</td>
599
+ <td><strong>No.</strong> The text stays inside the deployment</td>
600
+ </tr>
601
+ </tbody>
602
+ </table>
603
+ <p>Two things follow that people do not expect:</p>
604
+ <ul>
605
+ <li><strong>The charter goes with every one of those calls.</strong> A team that writes customer names, staff names or
606
+ case references into its charter sends them to its model provider on every classification. Write the
607
+ charter as though it were the prompt, because it is.</li>
608
+ <li><strong>The routing can be indirect.</strong> A model router forwards the request to whichever upstream provider the
609
+ selected model resolves to, and the generic compatible-endpoint adapter will send to any base URL an
610
+ operator configures. Each named provider is in the <a href="https://async.ever.co/subprocessors">Sub-processor List</a>
611
+ with its location and its transfer mechanism, and some of those mechanisms read <strong>&quot;To be confirmed&quot;</strong> —
612
+ which is us saying we have not yet evidenced one, rather than us implying we have.</li>
613
+ </ul>
614
+ <p><strong>We do not use your messages, your prompts or the output to train models</strong>, and our contracts with the
615
+ providers we engage prohibit them from doing so.</p>
616
+ <h3 id="what-is-running-on-the-hosted-service-today" tabindex="-1">What is running on the hosted service today</h3>
617
+ <p>Because it changes the answer to nearly every question above, it is worth stating rather than leaving to
618
+ be inferred: <strong>in the environments we operate today, no chat platform is connected, no connector is
619
+ configured, no model provider is configured and no notification provider is configured.</strong> The service runs
620
+ with authentication on, a local database, and sensitivity set to conservative.</p>
621
+ <p>So today, on our hosted service, <strong>no chat message data flows at all.</strong> That will change the moment a
622
+ workspace connects, which is exactly when everything above starts to apply. It is also why our
623
+ sub-processor list has only three entries in its always-engaged tier, and why the rest are in the tier
624
+ that depends on what you switch on.</p>
625
+ <h3 id="people-in-a-connected-channel-who-never-signed-up" tabindex="-1">People in a connected channel who never signed up</h3>
626
+ <p>Almost everyone whose data this product touches is in this position: they posted in a channel their
627
+ employer connected. Article 14 of the GDPR entitles them to be told, and this section is that notice as
628
+ well as an explanation to the customer.</p>
629
+ <ul>
630
+ <li><strong>What is held about you.</strong> Your chat user identifier, the fact and timing of your messages in a
631
+ connected conversation, the references and links inside them, who you mentioned, and — for at most the
632
+ grace window, and only if a nudge was scheduled — the text of the message itself.</li>
633
+ <li><strong>Where it came from.</strong> Your employer's or your community's chat workspace, connected by an
634
+ administrator of it. <strong>We did not obtain it from you.</strong></li>
635
+ <li><strong>Who decides.</strong> The organisation that connected the workspace is the controller. We are its processor.
636
+ <strong>Ask it first</strong>, and our <a href="https://async.ever.co/dpa">Data Processing Addendum</a> is what obliges it to answer.</li>
637
+ <li><strong>What it is for.</strong> Attaching context to a conversation and privately suggesting a clearer message to
638
+ the person who wrote it.</li>
639
+ <li><strong>The nudge is private.</strong> It goes to you and to nobody else. No manager sees it, there is no report of
640
+ who was nudged how often beyond a per-tenant count, and nothing is escalated.</li>
641
+ </ul>
642
+ <p>If a request reaches us directly we will forward it to the organisation, tell you who they are so you can
643
+ pursue it, and assist them — but <strong>we will not decide it for you or for them</strong>. Write to
644
+ privacy@ever.co; you do not need an account and it costs nothing.</p>
645
+ <h3 id="special-categories-and-why-we-do-not-pretend-to-filter" tabindex="-1">Special categories, and why we do not pretend to filter</h3>
646
+ <p>A chat channel cannot be filtered in advance. <strong>Health, religion, politics, trade union matters and purely
647
+ private business will appear in a connected conversation</strong>, because that is what channels contain. The
648
+ product does not seek any of it, does not classify it and <strong>does not detect and strip it</strong> — saying
649
+ otherwise would be untrue.</p>
650
+ <p>The protections that actually exist are the ones described above: the body is not stored, the metadata is
651
+ narrow, and which conversations are connected is a choice the customer makes. Connecting a general channel
652
+ rather than a work-tracking one is the decision that matters most here.</p>
653
+ <h3 id="how-long-we-keep-the-things-that-are-specific-to-this-product" tabindex="-1">How long we keep the things that are specific to this product</h3>
654
+ <p>These sit alongside the general retention table above; where both could apply, the shorter period wins.</p>
655
+ <table>
656
+ <thead>
657
+ <tr>
658
+ <th>What</th>
659
+ <th>How long</th>
660
+ </tr>
661
+ </thead>
662
+ <tbody>
663
+ <tr>
664
+ <td>The text of a chat message</td>
665
+ <td><strong>Not stored.</strong> In memory during processing only</td>
666
+ </tr>
667
+ <tr>
668
+ <td>The text of a message with a nudge pending</td>
669
+ <td><strong>The grace window — 150 seconds in every environment we run</strong> — then deleted when the nudge fires or is cancelled</td>
670
+ </tr>
671
+ <tr>
672
+ <td>Event metadata: author id, conversation, message id, thread root, edit flag, timestamp</td>
673
+ <td>Until the tenant is deleted. <strong>There is no automatic expiry today</strong></td>
674
+ </tr>
675
+ <tr>
676
+ <td>Deduplication records of messages already seen</td>
677
+ <td>Until the tenant is deleted</td>
678
+ </tr>
679
+ <tr>
680
+ <td>Nudge records: author id and timestamp</td>
681
+ <td>Until the tenant is deleted</td>
682
+ </tr>
683
+ <tr>
684
+ <td>Context records: a count of items attached</td>
685
+ <td>Until the tenant is deleted</td>
686
+ </tr>
687
+ <tr>
688
+ <td>Per-tenant counters</td>
689
+ <td>Until the tenant is deleted</td>
690
+ </tr>
691
+ <tr>
692
+ <td>Sign-in session, including verified email address and display name</td>
693
+ <td><strong>In memory only</strong> — lost when the process restarts or you sign out</td>
694
+ </tr>
695
+ <tr>
696
+ <td>Membership record: provider user id, tenant, roles</td>
697
+ <td>Until removed from the workspace, or until the tenant is deleted</td>
698
+ </tr>
699
+ <tr>
700
+ <td>Charter text, policy settings and workspace bindings</td>
701
+ <td>Until changed or until the tenant is deleted</td>
702
+ </tr>
703
+ <tr>
704
+ <td>The Gauzy user map</td>
705
+ <td>Until the customer changes it or the tenant is deleted</td>
706
+ </tr>
707
+ <tr>
708
+ <td>Credentials for a connector or a model provider</td>
709
+ <td>Until the customer removes them</td>
710
+ </tr>
711
+ </tbody>
712
+ </table>
713
+ <p>Deleting a tenant deletes everything above for that tenant. Backups age out on the cycle in the general
714
+ retention table and are not restored to bring back something we were asked to delete.</p>
715
+ <h3 id="what-is-deliberately-not-here" tabindex="-1">What is deliberately not here</h3>
716
+ <p>Stated affirmatively rather than left to be inferred from an absence, because an absence is not evidence:</p>
717
+ <ul>
718
+ <li><strong>No analytics.</strong> Not a third-party tag, and not the first-party cookieless tool some of our other
719
+ products run. Nothing measures your use of this product.</li>
720
+ <li><strong>No error tracking or session replay.</strong> No crash reporter, no performance monitor, no reconstruction of
721
+ what was on anyone's screen.</li>
722
+ <li><strong>No advertising, no retargeting, no enrichment, no data broker.</strong> Nothing about a message, an author or
723
+ a workspace is used to target anything, anywhere.</li>
724
+ <li><strong>No profiling of individuals.</strong> There is no score, no ranking and no per-person record of behaviour
725
+ beyond the metadata listed above. The classifier judges a message, not a person.</li>
726
+ <li><strong>No human reading your channels.</strong> Nobody here reads a connected conversation, except where you ask us
727
+ for support and point us at something specific, or where we must to investigate a security incident or
728
+ comply with a legal obligation — and in the last case we tell you unless we are prohibited from doing
729
+ so.</li>
730
+ </ul>
731
+ <p>If any of that changes, it is named in this annex before it runs, not after.</p>
732
+ <h3 id="exercising-your-rights-here-honestly-stated" tabindex="-1">Exercising your rights here, honestly stated</h3>
733
+ <ul>
734
+ <li><strong>The narrow schema helps you.</strong> There is very little to export, and a tenant delete really does remove
735
+ it.</li>
736
+ <li><strong>There is no self-service delete button today, and we are not going to pretend otherwise.</strong> Write to
737
+ privacy@ever.co and we will do it and answer you within one month.</li>
738
+ <li><strong>Where an organisation connected the workspace, most requests belong to that organisation</strong>, and we
739
+ route them there. The rights section above explains that routing; this annex is where you can see why it
740
+ applies to nearly everyone whose data is in this product.</li>
741
+ </ul>
742
+ <h2 id="cookies-and-similar-technologies" tabindex="-1">Cookies and similar technologies</h2>
743
+ <p>Cookies, local storage, pixels, software development kits and similar technologies get their own document,
744
+ because they need more detail than a summary can carry. What each one is, what it does, how long it lasts,
745
+ who operates it and how to refuse it is set out in our <a href="https://async.ever.co/cookies">Cookie Policy</a>.</p>
746
+ <p>In short, we sort them into four categories:</p>
747
+ <ul>
748
+ <li><strong>Strictly necessary</strong> — needed to deliver what you asked for: signing you in, holding your session,
749
+ routing traffic, remembering your cookie choice itself, and protecting forms and sign-in against
750
+ automated abuse. These are not optional, and we do not ask for consent to them.</li>
751
+ <li><strong>Preferences</strong> — remember choices you have made, such as language, region and interface settings.</li>
752
+ <li><strong>Analytics</strong> — help us understand how the Service is used so we can improve it.</li>
753
+ <li><strong>Marketing</strong> — measure our campaigns and help us understand which organisations take an interest in us.</li>
754
+ </ul>
755
+ <p><strong>Nothing in the preferences, analytics or marketing categories is placed or read on your device until you
756
+ agree to it.</strong> You can accept everything, refuse everything, or choose category by category, and refusing
757
+ takes exactly as few clicks as accepting.</p>
758
+ <h3 id="changing-your-mind" tabindex="-1">Changing your mind</h3>
759
+ <p>Your choices are not permanent. A <strong>Cookie preferences</strong> link sits in the footer of every page on
760
+ <a href="https://async.ever.co">async.ever.co</a> and reopens the same panel you saw the first time. Change a category
761
+ there and it takes effect immediately, for the future. Withdrawing is as easy as agreeing, and nothing
762
+ about the Service is withheld from you for refusing.</p>
763
+ <p>One analytics tool runs without consent, because it is configured so that it stores and reads nothing on
764
+ your device and never builds a persistent identifier for you. That is a conditional position, not a
765
+ permanent one: the <a href="https://async.ever.co/cookies">Cookie Policy</a> names the tool, describes the exact
766
+ configuration we rely on, and says what happens if any part of that configuration ever changes.</p>
767
+ <h2 id="who-receives-your-personal-data" tabindex="-1">Who receives your personal data</h2>
768
+ <p>We disclose personal data only to the categories of recipient below, and only as much as each one needs to
769
+ do the job it is there for.</p>
770
+ <ul>
771
+ <li><strong>Service providers acting as our processors</strong> — hosting and infrastructure, storage, content delivery,
772
+ email delivery, error monitoring, product analytics, customer support tooling and similar. They act on
773
+ our documented instructions under a written contract that meets Article 28 GDPR, they are bound to
774
+ confidentiality and appropriate security, and <strong>they may not use your data for their own purposes</strong>.</li>
775
+ <li><strong>Payment processors</strong> — to take payment, issue invoices and handle refunds and disputes. For their own
776
+ regulated obligations — fraud prevention, anti-money-laundering, card-scheme rules — they act as
777
+ controllers in their own right, and their own privacy notice governs that part.</li>
778
+ <li><strong>Professional advisers</strong> — lawyers, accountants, auditors and insurers, bound by professional
779
+ confidentiality, where we need advice or have to evidence that we have complied with something.</li>
780
+ <li><strong>Public authorities, courts and regulators</strong> — where the law requires us to disclose, or where we need
781
+ to establish, exercise or defend a legal claim. We check that a request has a proper legal basis and is
782
+ no wider than it needs to be, we push back where it is not, and we tell you about it unless we are
783
+ legally prohibited from doing so.</li>
784
+ <li><strong>An acquirer or successor</strong> — if we are reorganised, merged or sold, or if part of the business changes
785
+ hands, personal data may pass to the acquirer as part of that transaction. The acquirer is bound by this
786
+ policy or by a notice at least as protective, and we will tell you before anything about the handling of
787
+ your data changes.</li>
788
+ </ul>
789
+ <h3 id="the-sub-processors-we-engage-for-the-hosted-service" tabindex="-1">The sub-processors we engage for the hosted Service</h3>
790
+ <p>These providers are engaged for the hosted Service as it is delivered to everyone. They are the ones your
791
+ data is most likely to reach.</p>
792
+ <table>
793
+ <thead>
794
+ <tr>
795
+ <th>Sub-processor</th>
796
+ <th>Purpose</th>
797
+ <th>Location</th>
798
+ <th>Transfer mechanism</th>
799
+ <th>Personal data</th>
800
+ </tr>
801
+ </thead>
802
+ <tbody>
803
+ <tr>
804
+ <td>Cloudflare, Inc.</td>
805
+ <td>Authoritative DNS, reverse proxy and TLS termination for every Ever Async hostname — the marketing site, the dashboard, the API and the webhook ingress. TLS is terminated at the edge and there is no certificate in our own pods, so every request to the Service passes through it and no setting removes it.</td>
806
+ <td>United States, with your connection terminated at the edge location nearest to you</td>
807
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
808
+ <td>IP address, TLS and connection metadata, request URLs and headers, user agent, cookies in transit</td>
809
+ </tr>
810
+ <tr>
811
+ <td>GitHub, Inc. (a Microsoft Corporation company)</td>
812
+ <td>Holds the source, runs the build, and is the container registry the running images are pulled from (ghcr.io/ever-co/everasync and ghcr.io/ever-co/everasync-docs). This is how the Service is built and shipped rather than where message data lives — but it is a genuine third party and it is disclosed as one.</td>
813
+ <td>United States, with global edge delivery for registry and release downloads</td>
814
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
815
+ <td>source, build, release and deployment metadata, developer and automation account identifiers, IP address and user agent of anyone pulling an image or a release</td>
816
+ </tr>
817
+ <tr>
818
+ <td>Cloudflare, Inc. (R2 object storage)</td>
819
+ <td>Third tier of our backup chain, holding the off-site copy of the volumes this product's database sits on. Everything bound for it is encrypted by us before it leaves our network, so the provider holds ciphertext and no key and cannot read what it stores.</td>
820
+ <td>Cloudflare R2 buckets</td>
821
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
822
+ <td>client-side encrypted backup archives only, which no third party can read, the archives derive from every category of data the Service holds</td>
823
+ </tr>
824
+ <tr>
825
+ <td>Cloudflare, Inc. (Turnstile)</td>
826
+ <td>Checks that the person completing registration, onboarding or an anonymous flow is not a bot; on ever-works the API refuses the anonymous flow when no CAPTCHA provider is configured, which is why it is unconditional there.</td>
827
+ <td>United States</td>
828
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
829
+ <td>IP address, user agent and device signals, mouse, touch and timing interaction signals, Turnstile challenge cookie</td>
830
+ </tr>
831
+ <tr>
832
+ <td>Clerk, Inc.</td>
833
+ <td>Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name.</td>
834
+ <td>United States</td>
835
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
836
+ <td>name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored</td>
837
+ </tr>
838
+ <tr>
839
+ <td>Tavily</td>
840
+ <td>The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain.</td>
841
+ <td>United States</td>
842
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
843
+ <td>search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata</td>
844
+ </tr>
845
+ <tr>
846
+ <td>ui-avatars.com</td>
847
+ <td>Generates placeholder avatars where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser.</td>
848
+ <td>UNKNOWN - not published by the provider</td>
849
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
850
+ <td>the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent</td>
851
+ </tr>
852
+ <tr>
853
+ <td>Prospect One sp. z o.o. (jsDelivr)</td>
854
+ <td>Serves the Lottie animation runtime hard-coded into the ever-works login and register pages, so every person who opens the login page hands their IP to it before authenticating.</td>
855
+ <td>Poland (operator); delivery worldwide</td>
856
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
857
+ <td>IP address, user agent, referring page URL</td>
858
+ </tr>
859
+ <tr>
860
+ <td>UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified</td>
861
+ <td>Second permitted origin for the Lottie animation runtime on the ever-works login and register pages.</td>
862
+ <td>United States (unverified)</td>
863
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
864
+ <td>IP address, user agent, referring page URL</td>
865
+ </tr>
866
+ <tr>
867
+ <td>ActiveCampaign, LLC (Postmark)</td>
868
+ <td>Relays every transactional email a product sends - account invitations, verification and sign-in codes, invoices, approvals - and on ever.co also carries contact-form enquiries with PDF attachments, so CVs and the third parties named inside them reach a US processor.</td>
869
+ <td>United States</td>
870
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
871
+ <td>recipient name and email address, full message subject and body - invitations, verification and sign-in codes, invoices, timesheets, HR and approval content, free-text enquiry content and attached CVs from website contact forms, anyone NAMED inside that free text or attachment, delivery, bounce and open metadata</td>
872
+ </tr>
873
+ <tr>
874
+ <td>Resend, Inc.</td>
875
+ <td>Sends transactional mail for the products and domains configured against it, relaying onward through Amazon SES.</td>
876
+ <td>United States</td>
877
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
878
+ <td>recipient name and email address, message subject and body, delivery and bounce metadata</td>
879
+ </tr>
880
+ <tr>
881
+ <td>Google Ireland Limited (Google Workspace)</td>
882
+ <td>Hosts the corporate mailboxes that receive every support, privacy and rights request our own documents tell data subjects to write to, plus the recruitment mailbox that holds candidate CVs.</td>
883
+ <td>Ireland (contracting) / United States and global (Google LLC)</td>
884
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
885
+ <td>all inbound and outbound company email, support, DSAR and privacy correspondence with data subjects, candidate CVs and application correspondence (ever-tech careers), customer and supplier correspondence and attachments</td>
886
+ </tr>
887
+ <tr>
888
+ <td>Functional Software, Inc. d/b/a Sentry</td>
889
+ <td>Captures application errors, performance traces and - on the tenant site template - masked session replays, attaching the reporting user's identity and IP to each event.</td>
890
+ <td>United States</td>
891
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
892
+ <td>IP address, device and OS details, user id and email attached to an error event or set on the scope, URLs, route params, query strings and stack traces, which can carry request fragments and local variables, masked session replay recordings (maskAllText, blockAllMedia), desktop and mobile crash dumps</td>
893
+ </tr>
894
+ <tr>
895
+ <td>Langfuse GmbH</td>
896
+ <td>Stores the full prompts and completions of AI features together with model, latency and cost metadata, so that agent behaviour can be traced and scored.</td>
897
+ <td>Germany</td>
898
+ <td>None needed — established in the EEA</td>
899
+ <td>full prompt and completion text, which can contain user-authored content and personal data, user and session identifiers, model, latency, token and cost metadata, developer scoring outputs</td>
900
+ </tr>
901
+ <tr>
902
+ <td>Google Ireland Limited (reCAPTCHA)</td>
903
+ <td>Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made.</td>
904
+ <td>Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC)</td>
905
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
906
+ <td>IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com</td>
907
+ </tr>
908
+ </tbody>
909
+ </table>
910
+ <p>The full and current list, including everything below, is published at
911
+ <a href="https://async.ever.co/subprocessors">https://async.ever.co/subprocessors</a>, together with the notice period and
912
+ objection procedure that apply when we add or replace one.</p>
913
+ <h3 id="three-tiers-and-why-the-difference-matters" tabindex="-1">Three tiers, and why the difference matters</h3>
914
+ <p>A single flat list of every vendor that appears anywhere in our software would be both inaccurate and
915
+ misleading, so the sub-processor page is split into three tiers. They mean genuinely different things.</p>
916
+ <ul>
917
+ <li><strong>Always engaged.</strong> The providers above. If you use the hosted Service, these are in the path.</li>
918
+ <li><strong>Engaged only if you turn something on.</strong> Optional integrations, connectors and features. A provider in
919
+ this tier is engaged only when you or your workspace administrator enables the specific feature or
920
+ connects the specific account it belongs to. Enable nothing and it is never involved. The list says which
921
+ feature or setting activates each one.</li>
922
+ <li><strong>Self-hosted deployments only.</strong> Several of our products are published as open source and can be run on
923
+ your own infrastructure. In that case <strong>you</strong> choose the database, object storage, email relay, AI
924
+ provider and everything else, using your own credentials. Those providers appear in the list so you can
925
+ see what the software can be pointed at — but they are <strong>your</strong> providers, not ours. <strong>We process nothing
926
+ in a deployment you run, we are not your processor for it, and the commitments in this policy do not
927
+ describe it.</strong></li>
928
+ </ul>
929
+ <h3 id="we-do-not-sell-your-personal-data" tabindex="-1">We do not sell your personal data</h3>
930
+ <p>We do not sell personal data, and we do not share it for cross-context behavioural advertising. We do not
931
+ supply it to data brokers, we do not trade it for services, and we do not permit any provider we engage to
932
+ use it to build advertising or interest profiles, on our sites or anywhere else.</p>
933
+ <h2 id="sending-personal-data-outside-the-eea" tabindex="-1">Sending personal data outside the EEA</h2>
934
+ <p>Most of the personal data we hold stays inside the European Economic Area, on infrastructure we operate
935
+ ourselves. Some of it does not: a number of the providers we engage are established outside the EEA —
936
+ principally in the United States — and some of them route, cache or store data on servers outside it.</p>
937
+ <p>Where that happens, the transfer needs a lawful mechanism under Chapter V GDPR. We use one of the
938
+ following for every transfer, and the sub-processor page names the destination country and the mechanism
939
+ provider by provider.</p>
940
+ <h3 id="adequacy" tabindex="-1">Adequacy</h3>
941
+ <p>Where the European Commission has decided that a country provides an adequate level of protection, the
942
+ transfer relies on that decision and needs nothing further. Adequacy decisions are kept under review by
943
+ the Commission and can be amended, suspended or repealed, so we monitor them rather than treat them as
944
+ permanent.</p>
945
+ <h3 id="providers-in-the-united-states" tabindex="-1">Providers in the United States</h3>
946
+ <p>For a US provider we rely on one of two things.</p>
947
+ <ul>
948
+ <li><strong>The EU–US Data Privacy Framework</strong>, but only where that provider is <em>actively self-certified</em> under it
949
+ for the type of data concerned. We check the official Data Privacy Framework list when we engage a
950
+ provider and re-check it periodically. <strong>We do not claim the Framework for a provider that has not
951
+ certified, or whose certification has lapsed.</strong></li>
952
+ <li><strong>Standard Contractual Clauses</strong> — the clauses approved by the European Commission in Implementing
953
+ Decision (EU) 2021/914, with the modules that match the relationship, together with a transfer impact
954
+ assessment and supplementary measures: encryption in transit and at rest, minimising what is sent in the
955
+ first place, contractual limits on onward disclosure, and a commitment from the provider to notify and
956
+ where possible challenge a government access request.</li>
957
+ </ul>
958
+ <p><strong>We keep Standard Contractual Clauses in place as the standing mechanism</strong>, including for providers that
959
+ are also certified under the Framework. That is deliberate, and here is the honest reason.</p>
960
+ <p>The Commission's adequacy decision for the Framework, adopted on 10 July 2023, is currently valid. It was
961
+ challenged, and on 3 September 2025 the General Court of the European Union dismissed that challenge in
962
+ <em>Latombe</em> (Case T-553/23). <strong>That is not the end of it</strong> — an appeal is pending before the Court of
963
+ Justice as Case C-703/25 P, and the two arrangements that preceded this one were each struck down by the
964
+ same court. So we treat the Framework as a mechanism under review rather than a settled answer, and we
965
+ keep a second mechanism standing behind it so that a change in the law is a paperwork event for us and not
966
+ an interruption for you.</p>
967
+ <h3 id="other-countries" tabindex="-1">Other countries</h3>
968
+ <p>For a transfer to any other country without an adequacy decision, we use Standard Contractual Clauses with
969
+ the same assessment and supplementary measures. Where a transfer is to the United Kingdom or Switzerland,
970
+ the corresponding UK and Swiss additions are applied to those clauses.</p>
971
+ <p>We rely on an Article 49 derogation — for example, a transfer that is strictly necessary to perform a
972
+ contract you have asked us to perform — only in a specific, occasional case where no other mechanism fits.
973
+ It is not a routine mechanism for us, and we do not use it to run a regular data flow.</p>
974
+ <h3 id="getting-a-copy-of-the-safeguards" tabindex="-1">Getting a copy of the safeguards</h3>
975
+ <p>You are entitled to see the safeguards we rely on. Write to privacy@ever.co naming the provider or the
976
+ transfer you are asking about, and we will send you a copy of the relevant clauses and tell you which
977
+ modules apply. We may redact commercial terms such as pricing and service levels; we do not redact the
978
+ data protection terms, which are the part that concerns you.</p>
979
+ <h2 id="how-long-we-keep-personal-data" tabindex="-1">How long we keep personal data</h2>
980
+ <p>&quot;As long as necessary&quot; is not an answer, so here are the actual periods. Each one runs from the event in
981
+ the middle column, and at the end of it we delete the data or irreversibly anonymise it.</p>
982
+ <table>
983
+ <thead>
984
+ <tr>
985
+ <th>What we hold</th>
986
+ <th>How long we keep it</th>
987
+ <th>Why that period</th>
988
+ </tr>
989
+ </thead>
990
+ <tbody>
991
+ <tr>
992
+ <td>Account and profile data — name, email address, workspace membership, settings</td>
993
+ <td>For as long as the account is open, then deleted within <strong>30 days</strong> of closure</td>
994
+ <td>We need it to give you the account; after that we do not</td>
995
+ </tr>
996
+ <tr>
997
+ <td>Content and files you put into the Service</td>
998
+ <td>For as long as the account is open; after it ends, available for export for <strong>30 days</strong>, then deleted</td>
999
+ <td>You decide what is in it — see below</td>
1000
+ </tr>
1001
+ <tr>
1002
+ <td>Invoices, payment records and the tax data attached to them</td>
1003
+ <td><strong>10 years</strong> from the end of the accounting year in which the transaction fell</td>
1004
+ <td>Accounting and tax law in Bulgaria requires it, and we cannot shorten it at your request</td>
1005
+ </tr>
1006
+ <tr>
1007
+ <td>Record that you accepted our terms — version, date, method</td>
1008
+ <td><strong>5 years</strong> after the agreement ends</td>
1009
+ <td>The general limitation period for a claim under the contract</td>
1010
+ </tr>
1011
+ <tr>
1012
+ <td>Support correspondence and tickets</td>
1013
+ <td><strong>24 months</strong> from the last message in the thread</td>
1014
+ <td>Long enough to handle a recurring problem and a follow-up; not longer</td>
1015
+ </tr>
1016
+ <tr>
1017
+ <td>Security, access and audit logs</td>
1018
+ <td><strong>12 months</strong></td>
1019
+ <td>Investigating unauthorised access, and evidencing that we did</td>
1020
+ </tr>
1021
+ <tr>
1022
+ <td>Application and error logs, crash reports, diagnostics</td>
1023
+ <td><strong>90 days</strong></td>
1024
+ <td>Fixing what broke; they lose value quickly</td>
1025
+ </tr>
1026
+ <tr>
1027
+ <td>Marketing contact records and the evidence of your consent</td>
1028
+ <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>
1029
+ <td>An unsubscribe that forgets you is not an unsubscribe</td>
1030
+ </tr>
1031
+ <tr>
1032
+ <td>Cookie and consent choices</td>
1033
+ <td>As stated in the <a href="https://async.ever.co/cookies">Cookie Policy</a>, which gives the lifetime of each entry</td>
1034
+ <td>It belongs with the technology it describes</td>
1035
+ </tr>
1036
+ <tr>
1037
+ <td>Backups</td>
1038
+ <td>Each backup ages out on its own rolling cycle, within <strong>30 days</strong></td>
1039
+ <td>Recovering from failure and ransomware, without becoming a second archive</td>
1040
+ </tr>
1041
+ <tr>
1042
+ <td>Anything we are required to preserve for a legal claim, investigation or regulatory request</td>
1043
+ <td>Until the claim, investigation or request ends, including any appeal period</td>
1044
+ <td>We are not allowed to delete evidence, and neither are you</td>
1045
+ </tr>
1046
+ </tbody>
1047
+ </table>
1048
+ <h3 id="data-that-belongs-to-one-of-our-customers" tabindex="-1">Data that belongs to one of our customers</h3>
1049
+ <p>For personal data held inside a customer's workspace — including anything the Service captures about that
1050
+ customer's own personnel — <strong>the customer sets the retention period, not us</strong>. We are their processor for
1051
+ it. The defaults and the limits of what they can configure are described in the product annex to this
1052
+ policy.</p>
1053
+ <p>We delete that data when the customer instructs us to, or at the end of the export window after their
1054
+ agreement ends, whichever comes first. If you are one of their people and you want their data about you
1055
+ deleted sooner, ask them — see the section on your rights, which explains how we route that.</p>
1056
+ <h3 id="what-delete-means-here" tabindex="-1">What &quot;delete&quot; means here</h3>
1057
+ <p>Deletion is applied to live systems straight away. Backup copies are not individually edited — doing so
1058
+ would defeat what a backup is for — so a deleted record persists in backups until that backup ages out on
1059
+ the cycle above, at most 30 days. During that window the data is not used for anything, and <strong>we do not
1060
+ restore a backup to bring back data someone asked us to delete</strong>; a backup is restored only to recover a
1061
+ whole system after a failure.</p>
1062
+ <p>Where we can keep something useful without keeping you identifiable, we anonymise instead of deleting —
1063
+ aggregate usage counts, for example. Once anonymised the data is no longer personal data, and it is not
1064
+ possible for us to re-identify you from it.</p>
1065
+ <h2 id="how-we-protect-personal-data" tabindex="-1">How we protect personal data</h2>
1066
+ <p>We take the measures Article 32 GDPR requires: technical and organisational safeguards appropriate to the
1067
+ risk, reviewed as the risk changes. In practice that means the following.</p>
1068
+ <ul>
1069
+ <li><strong>Encryption in transit.</strong> Traffic to and from the Service travels over TLS. HTTPS is enforced, and
1070
+ plain HTTP requests are redirected rather than served.</li>
1071
+ <li><strong>Encryption at rest.</strong> The storage holding customer content, databases and backups is encrypted at
1072
+ rest, and particularly sensitive values — credentials, tokens and keys — are additionally encrypted at
1073
+ the application layer rather than stored in readable form.</li>
1074
+ <li><strong>Access control and least privilege.</strong> Access to production systems is limited to the people whose job
1075
+ needs it, granted by named individual accounts rather than shared logins, protected by multi-factor
1076
+ authentication, scoped to the narrowest role that works, and reviewed and revoked when a role changes or
1077
+ someone leaves.</li>
1078
+ <li><strong>Network segmentation.</strong> Databases, storage and internal services sit on segmented internal networks
1079
+ and are not exposed to the public internet. Administrative interfaces are not publicly reachable.</li>
1080
+ <li><strong>Logging.</strong> Administrative and security-relevant events are logged, retained for the period in the
1081
+ retention section, and monitored so that unusual activity raises an alert rather than sitting unread.</li>
1082
+ <li><strong>Backups.</strong> Data is backed up regularly, held on separate infrastructure from the live systems, and
1083
+ restores are tested — an untested backup is a guess, not a control.</li>
1084
+ <li><strong>Vulnerability management.</strong> Dependencies are scanned, code is analysed automatically before it ships,
1085
+ security patches are applied on a defined schedule with a faster path for serious issues, and we operate
1086
+ a responsible disclosure route so that anyone who finds a problem can tell us.</li>
1087
+ <li><strong>Personnel.</strong> Everyone with access is bound by written confidentiality obligations that outlast their
1088
+ engagement, works on a need-to-know basis, and has access removed when it is no longer needed.</li>
1089
+ <li><strong>Providers.</strong> We assess a provider before we engage it, contract with it under Article 28 GDPR, and
1090
+ hold it to security obligations at least as strict as our own.</li>
1091
+ </ul>
1092
+ <p>Our <a href="https://async.ever.co/security">Security page</a> sets out the detail, including which measure applies to
1093
+ which part of the Service, our incident response process, and the shared responsibility split between what
1094
+ we secure and what you secure.</p>
1095
+ <h3 id="what-we-do-not-claim" tabindex="-1">What we do not claim</h3>
1096
+ <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>
1097
+ If anything you read or are told suggests otherwise, it is wrong, and we would like to know where it came
1098
+ from. Where we describe a practice on this page or on the Security page, we describe something we actually
1099
+ do; where we adopt a framework as a reference without being audited against it, we say so plainly rather
1100
+ than implying a certification.</p>
1101
+ <h3 id="no-system-is-perfectly-secure" tabindex="-1">No system is perfectly secure</h3>
1102
+ <p><strong>No service, ours included, can be made completely secure, and anyone who tells you otherwise is
1103
+ selling something.</strong> What we can honestly promise is that we take the measures above seriously, that we
1104
+ keep them under review, and that if a personal data breach affects you we will act on it: we notify the
1105
+ CPDP where the law requires it, within the deadline it sets, and we
1106
+ tell affected people directly without undue delay where the breach is likely to result in a high risk to
1107
+ them.</p>
1108
+ <p>Your part matters too. Use a strong and unique password, turn on multi-factor authentication where it is
1109
+ offered, keep your devices patched, and do not share credentials or access tokens. If you think an account
1110
+ has been compromised, tell us at privacy@ever.co immediately.</p>
1111
+ <h2 id="your-rights-over-your-personal-data" tabindex="-1">Your rights over your personal data</h2>
1112
+ <p>Where we are the controller, the GDPR gives you the rights below. They are yours to use, you do not have
1113
+ to explain why you are using them, and using one costs you nothing.</p>
1114
+ <ul>
1115
+ <li><strong>Access</strong> — ask whether we hold personal data about you and, if we do, get a copy of it together with
1116
+ the information in this policy about how it is used. (Article 15)</li>
1117
+ <li><strong>Rectification</strong> — have inaccurate data corrected and incomplete data completed. Much of this you can
1118
+ do yourself in your account settings, which is faster than asking us. (Article 16)</li>
1119
+ <li><strong>Erasure</strong> — have data deleted where we no longer need it for the purpose we collected it for, where
1120
+ you withdraw the consent it rested on, or where we have processed it unlawfully. (Article 17)</li>
1121
+ <li><strong>Restriction</strong> — have us pause processing while a dispute is sorted out: while we check an accuracy
1122
+ challenge, for example, or while we consider an objection. We keep the data but stop using it.
1123
+ (Article 18)</li>
1124
+ <li><strong>Portability</strong> — receive the data you gave us, in a structured, commonly used, machine-readable format,
1125
+ and have it sent to another provider where that is technically feasible. This applies to data processed
1126
+ by automated means on the basis of your consent or a contract with you. (Article 20)</li>
1127
+ <li><strong>Objection</strong> — object to processing we base on our legitimate interests. We then stop unless we can
1128
+ demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or unless
1129
+ we need the data for a legal claim. (Article 21(1))</li>
1130
+ <li><strong>Objection to direct marketing</strong> — <strong>absolute, and there is nothing to weigh.</strong> If you tell us to stop
1131
+ using your data for direct marketing, including any profiling connected to it, we stop. No balancing
1132
+ test, no grace period, no exceptions. (Article 21(2))</li>
1133
+ </ul>
1134
+ <p>You also have the right to withdraw consent where consent is what we rely on, which has its own section
1135
+ below, and the right to complain to a supervisory authority, which has the section after that.</p>
1136
+ <p>Some of these rights have limits written into the law itself. Erasure does not override an obligation to
1137
+ keep invoices for the statutory accounting period, and portability does not extend to data we inferred or
1138
+ generated rather than received from you. <strong>Where we cannot do all of what you ask, we will tell you which
1139
+ part we cannot do and why</strong>, rather than declining as a whole.</p>
1140
+ <h3 id="how-to-make-a-request" tabindex="-1">How to make a request</h3>
1141
+ <p>Write to privacy@ever.co. Tell us which right you are using and enough about yourself for us to find
1142
+ the right records — the email address on the account is usually enough. You can also write to us by post
1143
+ at the address at the end of this policy.</p>
1144
+ <ul>
1145
+ <li><strong>It is free.</strong> We charge nothing for a request. If a request is manifestly unfounded or excessive,
1146
+ particularly because it repeats one we have already answered, the law lets us charge a reasonable fee
1147
+ based on our administrative cost or refuse it. If we ever do either, we will explain why and tell you
1148
+ how to challenge that decision.</li>
1149
+ <li><strong>We answer within one month</strong> of receiving the request. Where a request is complex, or where you have
1150
+ made several, we may extend that by up to two further months — and if we do, <strong>we will tell you within
1151
+ the first month, and tell you why</strong>.</li>
1152
+ <li><strong>We check who you are</strong> before we hand over personal data, because the alternative is handing your data
1153
+ to someone who claims to be you. We ask for the least that makes us confident, usually a reply from the
1154
+ email address already on the account. We ask for an identity document only where nothing lighter works,
1155
+ and anything you send us for verification is used for that and nothing else, then deleted.</li>
1156
+ </ul>
1157
+ <h3 id="if-your-data-sits-in-a-customers-workspace" tabindex="-1">If your data sits in a customer's workspace</h3>
1158
+ <p><strong>This is the most important paragraph on this page for many of the people who read it.</strong></p>
1159
+ <p>A large part of the personal data in the Service was put there by one of our customers — your employer,
1160
+ the organisation whose workspace you belong to, or the operator of a site built on our platform. Where the
1161
+ Service captures data about how an organisation's own personnel work, that data belongs to that
1162
+ organisation's workspace.</p>
1163
+ <p><strong>For that data the customer is the controller and we are only their processor.</strong> We process it on their
1164
+ documented instructions and for no purpose of our own, so the law directs your request to them, not to us.
1165
+ Practically:</p>
1166
+ <ul>
1167
+ <li><strong>Send your request to that organisation.</strong> They decide it, and they are the ones who have to answer you
1168
+ within the deadline.</li>
1169
+ <li><strong>If you send it to us instead, we will not ignore it.</strong> We will forward it to the relevant customer
1170
+ promptly, tell you that we have done so, and assist them in answering it as our Data Processing Addendum
1171
+ requires.</li>
1172
+ <li><strong>We will not decide the request ourselves, and we will not delete, correct or hand over data from a
1173
+ customer's workspace without their instruction</strong> — unless a law that applies to us requires it. That is
1174
+ not us being unhelpful: acting on a workspace's data without the controller's instruction is precisely
1175
+ what a processor is not allowed to do.</li>
1176
+ </ul>
1177
+ <p>If you are not sure which of the two situations you are in, ask us at privacy@ever.co and we will tell
1178
+ you, and point you to the right organisation if it is not us.</p>
1179
+ <h2 id="withdrawing-your-consent" tabindex="-1">Withdrawing your consent</h2>
1180
+ <p>Where we rely on your consent for something, <strong>you can withdraw it at any time, and withdrawing is as easy
1181
+ as giving it</strong>. You do not have to give a reason, and we do not ask you to justify it.</p>
1182
+ <p>Withdrawing consent stops the processing from that point onwards. <strong>It does not make what we did before
1183
+ unlawful</strong> — processing carried out while your consent was in force stays lawful, and withdrawal does not
1184
+ undo it. What it does mean is that we stop, and that we do not start again unless you tell us to.</p>
1185
+ <h3 id="how-to-withdraw-purpose-by-purpose" tabindex="-1">How to withdraw, purpose by purpose</h3>
1186
+ <ul>
1187
+ <li><strong>Cookies and similar technologies</strong> — open the <strong>Cookie preferences</strong> link in the footer of any page on
1188
+ <a href="https://async.ever.co">async.ever.co</a>, turn off the categories you no longer want, and save. The change
1189
+ takes effect immediately. Details are in our <a href="https://async.ever.co/cookies">Cookie Policy</a>.</li>
1190
+ <li><strong>Marketing emails</strong> — use the unsubscribe link at the bottom of any message we send you, or write to
1191
+ privacy@ever.co and ask us to stop. Either route works, and the unsubscribe link does not require
1192
+ you to sign in or find your password first.</li>
1193
+ <li><strong>Optional features and integrations you switched on</strong> — turn the feature off, or disconnect the
1194
+ connected account, in your settings. If you cannot find the switch, ask us at privacy@ever.co and we
1195
+ will turn it off for you.</li>
1196
+ </ul>
1197
+ <p>If you have consented to something not listed here, write to privacy@ever.co naming it, and we will
1198
+ act on it the same way.</p>
1199
+ <h3 id="what-happens-next" tabindex="-1">What happens next</h3>
1200
+ <p>We stop the processing, and we remove you from the relevant list or turn the relevant feature off. We keep
1201
+ the minimum record needed to show that you consented and that you withdrew, because being able to evidence
1202
+ consent is itself a legal requirement — for how long, see the retention section.</p>
1203
+ <p><strong>We will not quietly move the same processing onto a different legal basis to keep it running.</strong> If some
1204
+ part of what you asked us to stop genuinely rests on another basis as well — an invoice we are required to
1205
+ keep, for example — we will tell you which part and why, rather than leaving you to discover it.</p>
1206
+ <p>Most of what we do is not based on consent at all. It rests on performing our contract with you, on legal
1207
+ obligations, or on legitimate interests. <strong>Withdrawing consent therefore does not close your account or
1208
+ switch off the Service</strong> — it affects only the things you consented to.</p>
1209
+ <h2 id="complaining-to-a-supervisory-authority" tabindex="-1">Complaining to a supervisory authority</h2>
1210
+ <p>If you think we have handled your personal data badly or unlawfully, <strong>you have the right to complain to a
1211
+ data protection supervisory authority</strong>. That right is yours regardless of anything else in this policy.</p>
1212
+ <p>We would like the chance to put it right first. Write to privacy@ever.co, tell us what went wrong, and
1213
+ we will look into it and come back to you. In most cases that is the quickest way to get the outcome you
1214
+ actually want. <strong>You are not required to do this, and it is not a condition of complaining</strong> — you can go
1215
+ straight to an authority, and you can do it at any point, including while we are still dealing with your
1216
+ complaint.</p>
1217
+ <h3 id="our-lead-supervisory-authority" tabindex="-1">Our lead supervisory authority</h3>
1218
+ <p>We are established in Bulgaria, so our lead authority is the
1219
+ <strong>Commission for Personal Data Protection (Комисия за защита на личните данни)</strong> — the CPDP. Its website,
1220
+ including its complaint form and current contact details, is at
1221
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>.</p>
1222
+ <h3 id="you-can-also-complain-closer-to-home" tabindex="-1">You can also complain closer to home</h3>
1223
+ <p>Under Article 77 GDPR you may lodge your complaint with the supervisory authority in the EU or EEA country:</p>
1224
+ <ul>
1225
+ <li>where you live;</li>
1226
+ <li>where you work; or</li>
1227
+ <li>where the thing you are complaining about took place.</li>
1228
+ </ul>
1229
+ <p>You do not have to use ours, and you do not need our agreement to use another one. If you complain to your
1230
+ local authority, it will co-operate with ours through the mechanism the GDPR sets up for exactly this
1231
+ situation, so nothing is lost by choosing whichever is easiest for you.</p>
1232
+ <p>You also have the right to an effective judicial remedy — against a supervisory authority's decision, and
1233
+ against us directly — in the courts of the country where you live or where we are established. Complaining
1234
+ to an authority does not use up that right.</p>
1235
+ <h2 id="automated-decision-making-and-profiling" tabindex="-1">Automated decision-making and profiling</h2>
1236
+ <p><strong>We do not make decisions about you that produce legal effects concerning you, or that similarly
1237
+ significantly affect you, based solely on automated processing.</strong> No algorithm of ours decides whether you
1238
+ are hired, paid, promoted, disciplined, dismissed, given credit, or charged a different price. Where a
1239
+ decision of that kind is made about you by an organisation using the Service, a person at that
1240
+ organisation makes it.</p>
1241
+ <p>We do use automated rules to detect fraud, spam, abuse and attacks against the Service — rate limits,
1242
+ anomaly detection, and similar. Those rules can block a request or temporarily restrict an account. If one
1243
+ of them affects you, write to privacy@ever.co and a person will review it.</p>
1244
+ <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>
1245
+ <p>This is the part worth reading carefully, because it is easy to misunderstand.</p>
1246
+ <p>Some of our products capture activity data on behalf of a customer — an employer, typically — and some of
1247
+ them offer optional AI features on top of it. <strong>Where a customer enables those features, the Service can
1248
+ generate automated assessments of the activity it captures.</strong> The clearest example: classifying whether
1249
+ the content of a captured screen appears to be work-related. Other examples include scoring or summarising
1250
+ captured activity and grouping it into categories.</p>
1251
+ <p>Four things follow, and we would rather state them plainly than let them be discovered later.</p>
1252
+ <ul>
1253
+ <li><strong>The output goes to the customer, not to us.</strong> It is presented to the organisation whose workspace the
1254
+ data belongs to. <strong>That organisation is the controller of it, and we are only its processor.</strong></li>
1255
+ <li><strong>The customer decides what, if anything, to do with it.</strong> We do not act on these assessments, we do not
1256
+ use them for any purpose of our own, and we do not share them with anyone else.</li>
1257
+ <li><strong>These outputs are not decisions, and must not be used as if they were.</strong> An automated assessment is an
1258
+ input to a human judgement. <strong>Our terms require the customer not to treat an output of the Service as an
1259
+ automated decision about a person, and to apply meaningful human review before acting on one.</strong> Whether
1260
+ any particular use is lawful where that customer operates — including the lawful basis for it, the
1261
+ notices it has to give, any impact assessment it has to carry out, and any consultation with employee
1262
+ representatives it has to run — is that customer's responsibility to determine, not ours.</li>
1263
+ <li><strong>They can be wrong.</strong> A classifier reading a screen has no idea what your job is. It can label genuine
1264
+ work as unrelated, and it can miss the opposite. Anyone relying on one of these outputs should treat it
1265
+ as a rough signal, and we say so to our customers as well as to you.</li>
1266
+ </ul>
1267
+ <h3 id="if-an-assessment-about-you-has-been-generated" tabindex="-1">If an assessment about you has been generated</h3>
1268
+ <p>Ask the organisation whose workspace holds the data — normally your employer. You can ask them for human
1269
+ involvement, for an explanation of how the assessment was reached, to express your point of view, and to
1270
+ contest the result. They are the controller, so they are the ones who have to answer.</p>
1271
+ <p>If you send that request to us, we will forward it to them promptly, tell you we have done so, and assist
1272
+ them in answering it. See the routing paragraph in the section on your rights, which explains why we
1273
+ cannot decide it ourselves.</p>
1274
+ <h2 id="children" tabindex="-1">Children</h2>
1275
+ <p><strong>The Service is not directed at children, and we do not knowingly collect personal data from them.</strong> It
1276
+ is a business product, bought by organisations and used by the people who work in them. We do not design
1277
+ it for children, we do not market it to them, and we do not offer accounts to them.</p>
1278
+ <p>Where consent is the basis for an online service offered directly to a child, the GDPR sets the age at
1279
+ which the child can consent alone. <strong>In Bulgaria that age is 14.</strong> Other EU and EEA countries set
1280
+ it anywhere between 13 and 16, and the age in the country where the child lives is the one that applies.
1281
+ Below that age, consent has to come from — or be authorised by — a holder of parental responsibility.
1282
+ Because we do not offer the Service to children, we do not operate a parental consent mechanism, and a
1283
+ child under the applicable age should not create an account or submit personal data to us.</p>
1284
+ <h3 id="if-a-childs-data-has-reached-us" tabindex="-1">If a child's data has reached us</h3>
1285
+ <p>Tell us. Write to privacy@ever.co with enough detail for us to find the record — an email address, an
1286
+ account name, or the page where the data was submitted. You do not need to prove anything first, and you
1287
+ do not need to be the child's parent to report it.</p>
1288
+ <p>We will check, and where we confirm that we hold personal data collected from a child without proper
1289
+ authorisation, <strong>we will delete it without undue delay</strong>, keeping only what a law that applies to us
1290
+ requires us to keep.</p>
1291
+ <p>If the data sits inside one of our customers' workspaces rather than in our own records, the customer is
1292
+ the controller of it. Tell them as well, and tell us — we will forward your report to them and press for
1293
+ it to be dealt with, as the routing paragraph in the section on your rights describes.</p>
1294
+ <h2 id="links-and-content-from-other-sites" tabindex="-1">Links and content from other sites</h2>
1295
+ <p>Our websites and the Service link to services we do not run, and some pages embed content that other
1296
+ people host — videos, maps, code repositories, documentation and similar.</p>
1297
+ <p>Following a link takes you somewhere this policy does not reach. Loading embedded content means the
1298
+ provider hosting it receives data directly from your browser, typically your IP address, your device and
1299
+ browser details, and the page you were on, and it may set its own cookies.</p>
1300
+ <p><strong>We do not control those services, and this policy does not apply to them.</strong> What they collect and what
1301
+ they do with it is governed by their own privacy notice, which is the one to read before you use them.
1302
+ Where embedded content is not strictly necessary to deliver a page, we load it only once you have agreed
1303
+ to the relevant cookie category — see our <a href="https://async.ever.co/cookies">Cookie Policy</a>.</p>
1304
+ <p>A link is not an endorsement. If a link from our site takes you somewhere that mishandles your data, we
1305
+ would like to know at privacy@ever.co so we can reconsider carrying it.</p>
1306
+ <h2 id="changes-to-this-policy" tabindex="-1">Changes to this policy</h2>
1307
+ <p>This policy changes when the Service changes, when we engage or replace a provider, or when the law moves.
1308
+ We would rather update it than let it drift out of date and quietly stop being true.</p>
1309
+ <p>Every version carries a version number and the date it takes effect, shown at the top of the page. <strong>This
1310
+ is version 1.0.2, in force from 2026-08-02.</strong></p>
1311
+ <h3 id="how-we-tell-you" tabindex="-1">How we tell you</h3>
1312
+ <ul>
1313
+ <li><strong>Minor changes</strong> — clarifying wording, correcting a mistake, adding a provider of a kind already
1314
+ described — are published with a new version number and a new effective date. We do not send a separate
1315
+ notice for these.</li>
1316
+ <li><strong>Material changes</strong> — a new purpose, a new category of personal data, a new category of recipient, a
1317
+ longer retention period, a change to how you exercise your rights, or a change to the legal basis we
1318
+ rely on — are notified <strong>at least 30 days before they take effect</strong>, by email to account holders and by
1319
+ a notice on the site. That gives you time to read them and to act before they apply.</li>
1320
+ <li><strong>Changes that need your consent</strong> are not made by publishing a new version. We ask you, and we treat
1321
+ silence as a no.</li>
1322
+ </ul>
1323
+ <p>This policy is a notice, not a contract. <strong>We do not ask you to accept it</strong>, and continuing to use the
1324
+ Service is not us collecting your agreement to it. Where we genuinely need your agreement to something, we
1325
+ ask for it separately and record it.</p>
1326
+ <h3 id="previous-versions-stay-available" tabindex="-1">Previous versions stay available</h3>
1327
+ <p>We do not overwrite the past. <strong>Every version of this policy that we have published remains available</strong>,
1328
+ with the dates it was in force, from the version history linked at the foot of
1329
+ <a href="https://async.ever.co/privacy">https://async.ever.co/privacy</a>. If you want to know what we said about your data on a
1330
+ particular date, that is where to look — and if you cannot find it, ask us at privacy@ever.co and we
1331
+ will send it to you.</p>
1332
+ <h2 id="how-to-contact-us" tabindex="-1">How to contact us</h2>
1333
+ <p>The controller for the personal data described in this policy is <strong>Ever Technologies LTD</strong>, registered in
1334
+ Bulgaria under company number 204599535, with its registered office at
1335
+ Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.</p>
1336
+ <ul>
1337
+ <li><strong>Privacy questions, and any request about your personal data</strong> — privacy@ever.co</li>
1338
+ <li><strong>Data protection correspondence</strong> — dpo@ever.co</li>
1339
+ </ul>
1340
+ <p>Both addresses are monitored by the same people, and either will reach us. By post, write to the registered
1341
+ office above and mark the letter for the attention of the privacy team. We correspond in English.</p>
1342
+ <p><strong>We have not designated a Data Protection Officer under Article 37 GDPR.</strong> The dpo@ever.co address is
1343
+ a contact channel, not a designation, and we will not describe it as one. If that position changes, this
1344
+ policy will say so and will give the designated office's contact details.</p>
1345
+ <p>If your question is about personal data held inside one of our customers' workspaces, that customer is the
1346
+ controller and the request goes to them — see the routing paragraph in the section on your rights. Write to
1347
+ us anyway if you are unsure, and we will tell you who to ask.</p>
1348
+ <p>This document is version 1.0.2 of the Privacy Policy for
1349
+ <a href="https://async.ever.co">async.ever.co</a>, in force from 2026-08-02. Earlier versions, with the
1350
+ dates they applied, are at <a href="https://async.ever.co/privacy">https://async.ever.co/privacy</a>.</p>