@ever-co/legal 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (146) hide show
  1. package/dist/content/aup/ever-corporate/en.html +667 -0
  2. package/dist/content/aup/ever-corporate/en.json +302 -0
  3. package/dist/content/aup/ever-demand/en.html +802 -0
  4. package/dist/content/aup/ever-demand/en.json +339 -0
  5. package/dist/content/aup/ever-rec/en.html +667 -0
  6. package/dist/content/aup/ever-rec/en.json +302 -0
  7. package/dist/content/aup/ever-teams/en.html +667 -0
  8. package/dist/content/aup/ever-teams/en.json +302 -0
  9. package/dist/content/aup/ever-works/en.html +667 -0
  10. package/dist/content/aup/ever-works/en.json +302 -0
  11. package/dist/content/aup/everiq/en.html +726 -0
  12. package/dist/content/aup/everiq/en.json +319 -0
  13. package/dist/content/aup/gauzy/en.html +715 -0
  14. package/dist/content/aup/gauzy/en.json +327 -0
  15. package/dist/content/aup/githands/en.html +864 -0
  16. package/dist/content/aup/githands/en.json +363 -0
  17. package/dist/content/aup/hust/en.html +781 -0
  18. package/dist/content/aup/hust/en.json +347 -0
  19. package/dist/content/aup/traduora/en.html +667 -0
  20. package/dist/content/aup/traduora/en.json +302 -0
  21. package/dist/content/cookies/ever-corporate/en.html +493 -0
  22. package/dist/content/cookies/ever-corporate/en.json +193 -0
  23. package/dist/content/cookies/ever-demand/en.html +633 -0
  24. package/dist/content/cookies/ever-demand/en.json +226 -0
  25. package/dist/content/cookies/ever-rec/en.html +564 -0
  26. package/dist/content/cookies/ever-rec/en.json +206 -0
  27. package/dist/content/cookies/ever-teams/en.html +549 -0
  28. package/dist/content/cookies/ever-teams/en.json +222 -0
  29. package/dist/content/cookies/ever-tech/en.html +469 -0
  30. package/dist/content/cookies/ever-tech/en.json +177 -0
  31. package/dist/content/cookies/ever-works/en.html +618 -0
  32. package/dist/content/cookies/ever-works/en.json +202 -0
  33. package/dist/content/cookies/everiq/en.html +437 -0
  34. package/dist/content/cookies/everiq/en.json +185 -0
  35. package/dist/content/cookies/gauzy/en.html +490 -0
  36. package/dist/content/cookies/gauzy/en.json +206 -0
  37. package/dist/content/cookies/githands/en.html +618 -0
  38. package/dist/content/cookies/githands/en.json +210 -0
  39. package/dist/content/cookies/hust/en.html +622 -0
  40. package/dist/content/cookies/hust/en.json +210 -0
  41. package/dist/content/cookies/traduora/en.html +580 -0
  42. package/dist/content/cookies/traduora/en.json +193 -0
  43. package/dist/content/dpa/ever-demand/en.html +1804 -0
  44. package/dist/content/dpa/ever-demand/en.json +628 -0
  45. package/dist/content/dpa/ever-rec/en.html +1963 -0
  46. package/dist/content/dpa/ever-rec/en.json +652 -0
  47. package/dist/content/dpa/ever-teams/en.html +1918 -0
  48. package/dist/content/dpa/ever-teams/en.json +648 -0
  49. package/dist/content/dpa/ever-works/en.html +1801 -0
  50. package/dist/content/dpa/ever-works/en.json +624 -0
  51. package/dist/content/dpa/gauzy/en.html +1836 -0
  52. package/dist/content/dpa/gauzy/en.json +632 -0
  53. package/dist/content/dpa/githands/en.html +1808 -0
  54. package/dist/content/dpa/githands/en.json +624 -0
  55. package/dist/content/dpa/hust/en.html +1804 -0
  56. package/dist/content/dpa/hust/en.json +632 -0
  57. package/dist/content/privacy/ever-corporate/en.html +1184 -0
  58. package/dist/content/privacy/ever-corporate/en.json +352 -0
  59. package/dist/content/privacy/ever-demand/en.html +1234 -0
  60. package/dist/content/privacy/ever-demand/en.json +364 -0
  61. package/dist/content/privacy/ever-rec/en.html +1250 -0
  62. package/dist/content/privacy/ever-rec/en.json +360 -0
  63. package/dist/content/privacy/ever-teams/en.html +1238 -0
  64. package/dist/content/privacy/ever-teams/en.json +368 -0
  65. package/dist/content/privacy/ever-tech/en.html +1127 -0
  66. package/dist/content/privacy/ever-tech/en.json +352 -0
  67. package/dist/content/privacy/ever-works/en.html +1284 -0
  68. package/dist/content/privacy/ever-works/en.json +364 -0
  69. package/dist/content/privacy/everiq/en.html +1172 -0
  70. package/dist/content/privacy/everiq/en.json +328 -0
  71. package/dist/content/privacy/gauzy/en.html +1281 -0
  72. package/dist/content/privacy/gauzy/en.json +356 -0
  73. package/dist/content/privacy/githands/en.html +1393 -0
  74. package/dist/content/privacy/githands/en.json +380 -0
  75. package/dist/content/privacy/hust/en.html +1359 -0
  76. package/dist/content/privacy/hust/en.json +368 -0
  77. package/dist/content/privacy/traduora/en.html +1146 -0
  78. package/dist/content/privacy/traduora/en.json +336 -0
  79. package/dist/content/refund/ever-works/en.html +595 -0
  80. package/dist/content/refund/ever-works/en.json +336 -0
  81. package/dist/content/refund/gauzy/en.html +595 -0
  82. package/dist/content/refund/gauzy/en.json +336 -0
  83. package/dist/content/refund/githands/en.html +647 -0
  84. package/dist/content/refund/githands/en.json +361 -0
  85. package/dist/content/refund/hust/en.html +595 -0
  86. package/dist/content/refund/hust/en.json +336 -0
  87. package/dist/content/security/ever-demand/en.html +900 -0
  88. package/dist/content/security/ever-demand/en.json +425 -0
  89. package/dist/content/security/ever-rec/en.html +768 -0
  90. package/dist/content/security/ever-rec/en.json +380 -0
  91. package/dist/content/security/ever-teams/en.html +768 -0
  92. package/dist/content/security/ever-teams/en.json +380 -0
  93. package/dist/content/security/ever-works/en.html +768 -0
  94. package/dist/content/security/ever-works/en.json +380 -0
  95. package/dist/content/security/gauzy/en.html +768 -0
  96. package/dist/content/security/gauzy/en.json +380 -0
  97. package/dist/content/security/githands/en.html +876 -0
  98. package/dist/content/security/githands/en.json +421 -0
  99. package/dist/content/security/hust/en.html +768 -0
  100. package/dist/content/security/hust/en.json +380 -0
  101. package/dist/content/subprocessors/ever-corporate/en.html +382 -0
  102. package/dist/content/subprocessors/ever-corporate/en.json +158 -0
  103. package/dist/content/subprocessors/ever-demand/en.html +452 -0
  104. package/dist/content/subprocessors/ever-demand/en.json +154 -0
  105. package/dist/content/subprocessors/ever-rec/en.html +439 -0
  106. package/dist/content/subprocessors/ever-rec/en.json +154 -0
  107. package/dist/content/subprocessors/ever-teams/en.html +477 -0
  108. package/dist/content/subprocessors/ever-teams/en.json +154 -0
  109. package/dist/content/subprocessors/ever-tech/en.html +335 -0
  110. package/dist/content/subprocessors/ever-tech/en.json +141 -0
  111. package/dist/content/subprocessors/ever-works/en.html +551 -0
  112. package/dist/content/subprocessors/ever-works/en.json +154 -0
  113. package/dist/content/subprocessors/everiq/en.html +296 -0
  114. package/dist/content/subprocessors/everiq/en.json +149 -0
  115. package/dist/content/subprocessors/gauzy/en.html +603 -0
  116. package/dist/content/subprocessors/gauzy/en.json +154 -0
  117. package/dist/content/subprocessors/githands/en.html +465 -0
  118. package/dist/content/subprocessors/githands/en.json +154 -0
  119. package/dist/content/subprocessors/hust/en.html +482 -0
  120. package/dist/content/subprocessors/hust/en.json +154 -0
  121. package/dist/content/subprocessors/traduora/en.html +362 -0
  122. package/dist/content/subprocessors/traduora/en.json +154 -0
  123. package/dist/content/tos/ever-corporate/en.html +973 -0
  124. package/dist/content/tos/ever-corporate/en.json +517 -0
  125. package/dist/content/tos/ever-demand/en.html +1598 -0
  126. package/dist/content/tos/ever-demand/en.json +783 -0
  127. package/dist/content/tos/ever-rec/en.html +1524 -0
  128. package/dist/content/tos/ever-rec/en.json +771 -0
  129. package/dist/content/tos/ever-teams/en.html +1551 -0
  130. package/dist/content/tos/ever-teams/en.json +779 -0
  131. package/dist/content/tos/ever-tech/en.html +762 -0
  132. package/dist/content/tos/ever-tech/en.json +421 -0
  133. package/dist/content/tos/ever-works/en.html +1552 -0
  134. package/dist/content/tos/ever-works/en.json +787 -0
  135. package/dist/content/tos/everiq/en.html +781 -0
  136. package/dist/content/tos/everiq/en.json +429 -0
  137. package/dist/content/tos/gauzy/en.html +1440 -0
  138. package/dist/content/tos/gauzy/en.json +755 -0
  139. package/dist/content/tos/githands/en.html +1542 -0
  140. package/dist/content/tos/githands/en.json +779 -0
  141. package/dist/content/tos/hust/en.html +1566 -0
  142. package/dist/content/tos/hust/en.json +787 -0
  143. package/dist/content/tos/traduora/en.html +1238 -0
  144. package/dist/content/tos/traduora/en.json +646 -0
  145. package/dist/index.json +26991 -0
  146. package/package.json +52 -0
@@ -0,0 +1,1250 @@
1
+ <h1 id="privacy-policy" tabindex="-1">Privacy Policy</h1>
2
+ <p><strong>Ever Rec</strong> — <a href="https://rec.so">rec.so</a></p>
3
+ <p>Version 1.0.0 · In force from 2026-08-02</p>
4
+ <p>This notice explains what we do with personal data when you use Ever Rec Cloud and the websites,
5
+ applications and application programming interfaces we make available at <a href="https://rec.so">rec.so</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://rec.so">rec.so</a> and the pages served from it.</li>
14
+ <li>The Ever Rec Cloud web application, together with any desktop application, mobile application or
15
+ browser extension we publish for it.</li>
16
+ <li>The application programming interfaces and integrations we operate for it.</li>
17
+ <li>The emails, notifications and support conversations that go with it.</li>
18
+ </ul>
19
+ <p>A product-specific annex appears later in this notice. It adds detail for Ever Rec — 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 Rec, the annex governs.</p>
22
+ <h2 id="what-this-notice-does-not-cover" tabindex="-1">What this notice does not cover</h2>
23
+ <p><strong>Other companies' products.</strong> Other companies operate their own websites, products and services, and
24
+ publish their own privacy notices. This notice covers only what is listed above. If a service is not on
25
+ that list, this notice does not apply to it — whatever it looks like, and whoever links to it.</p>
26
+ <p><strong>Software you run yourself.</strong> Some of our software is published as open source and can be installed on
27
+ your own infrastructure. <strong>If you run your own deployment, you are the controller of the personal data in
28
+ it — not us.</strong> You choose its hosting, its storage, its email provider and every other component. We have
29
+ no access to that data, we do not process it, we are not your processor for it, and nothing in this notice
30
+ describes it. Telling your own users what happens in your deployment is your job, not ours.</p>
31
+ <p><strong>Sites we link to.</strong> The Service links out to third-party websites and services. Once you follow a link
32
+ away from us, the operator of that site decides what happens to your data. We do not control those sites,
33
+ we do not receive what you do on them, and we are not responsible for them. Read their notices, not this
34
+ one.</p>
35
+ <p><strong>Your organisation's own systems.</strong> Where your employer or another organisation uses the Service, it also
36
+ runs systems of its own. This notice covers our part. Its notice covers its part.</p>
37
+ <h2 id="who-we-are" tabindex="-1">Who we are</h2>
38
+ <p>The controller of the personal data described in this notice is <strong>Ever Technologies LTD</strong>, a company
39
+ registered in Bulgaria under company number 204599535, with its registered office
40
+ at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.</p>
41
+ <p>&quot;Controller&quot; is the legal term for the organisation that decides why personal data is used and how.
42
+ Wherever this notice says we make that decision, <strong>Ever Technologies LTD is the organisation accountable to
43
+ you</strong> — and to the Commission for Personal Data Protection (Комисия за защита на личните данни) (CPDP), which
44
+ is our lead supervisory authority.</p>
45
+ <p>Ever Technologies LTD operates Ever Rec Cloud and is the company you contract with for it. There
46
+ is no other operator behind us and no second company you have to chase to get an answer.</p>
47
+ <p>You can reach us about anything in this notice at privacy@ever.co, or by post at the registered office
48
+ above.</p>
49
+ <p>There are parts of this notice where we are deliberately <strong>not</strong> the controller: where a customer puts
50
+ personal data about its own people into the Service, that customer decides, and we act on its instructions.
51
+ That split matters, so it has its own section below.</p>
52
+ <h2 id="other-companies-in-our-group" tabindex="-1">Other companies in our group</h2>
53
+ <p>There is one other company in our group, and its role is narrow enough to state in a sentence.</p>
54
+ <p><strong>Ever Co. LTD</strong>, a company registered in Israel under company number
55
+ 515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, owns the intellectual
56
+ property in the software. Ever Technologies LTD operates the Service under licence from it.</p>
57
+ <p>That is the entire relationship. Its consequences are worth stating positively rather than leaving you to
58
+ work them out:</p>
59
+ <ul>
60
+ <li><strong>Ever Co. LTD does not access personal data held in the Service.</strong> No administration console,
61
+ no production database, no support tooling, no backups, no error reports.</li>
62
+ <li>It is <strong>not a controller</strong> of that data, <strong>not a processor</strong> of it, and <strong>not a sub-processor</strong>. It does
63
+ not appear on our sub-processor list, because there is nothing for it to appear against.</li>
64
+ <li><strong>No personal data is transferred to it.</strong> No international transfer to Israel arises out of
65
+ your use of the Service, because none happens.</li>
66
+ </ul>
67
+ <p>Owning software is not the same as having access to the data that software holds, and we have kept the two
68
+ apart on purpose.</p>
69
+ <p>If that ever changes — if Ever Co. LTD were to take on any role involving personal data from the
70
+ Service — we would update this notice before it happened, name the role, disclose the transfer and the
71
+ safeguard we relied on, and add it to our sub-processor list. <strong>Until you read that here, none of it is
72
+ happening.</strong></p>
73
+ <h2 id="data-protection-contact" tabindex="-1">Data protection contact</h2>
74
+ <p><strong>We have not designated a Data Protection Officer.</strong> Article 13(1)(b) of the GDPR asks a controller to
75
+ publish a Data Protection Officer's contact details where one has been designated. None has been designated
76
+ at Ever Technologies LTD, so there are none to publish. We would rather tell you that outright than let a
77
+ mailbox name imply otherwise. We keep the question under review, and if it changes we will publish the
78
+ details here.</p>
79
+ <p>What we do publish is a contact route that is monitored and acted on. <strong>Privacy questions and requests to
80
+ exercise your rights are handled through these addresses:</strong></p>
81
+ <ul>
82
+ <li><strong>privacy@ever.co</strong> — use this for anything about this notice, about the personal data we hold, or to
83
+ make a request under any of your rights.</li>
84
+ <li><strong>dpo@ever.co</strong> — an alias that reaches the same people. It exists because procurement forms,
85
+ security questionnaires and privacy tooling routinely expect an address in that form. <strong>It is a routing
86
+ alias, not an office. Nothing about it means a Data Protection Officer has been designated.</strong></li>
87
+ </ul>
88
+ <p>You can also write to us by post at the registered office given above.</p>
89
+ <p>We will acknowledge your message, and we will answer a request to exercise your rights within one month —
90
+ the deadline the GDPR sets. Where a request is genuinely complex, or where you have made several, we may
91
+ extend that by up to two further months. If we do, we will tell you inside the first month and explain
92
+ why.</p>
93
+ <h2 id="who-decides-what-controller-and-processor" tabindex="-1">Who decides what: controller and processor</h2>
94
+ <p>Data protection law splits responsibility in two. The <strong>controller</strong> decides why personal data is used and
95
+ how. The <strong>processor</strong> only acts on the controller's instructions. Which of the two we are is not a
96
+ formality — it decides who you go to, who has to answer you, and who is accountable when something goes
97
+ wrong.</p>
98
+ <p>Our position depends on whose data it is. There are three cases. We set them out here, in the privacy
99
+ notice, rather than leaving them to a data processing agreement, because the person most affected by the
100
+ second case is usually the person least likely to read a contract.</p>
101
+ <h3 id="1-our-own-relationship-with-you-we-are-the-controller" tabindex="-1">1. Our own relationship with you — we are the controller</h3>
102
+ <p>Where we decide, we are accountable. <strong>We are the controller</strong> for:</p>
103
+ <ul>
104
+ <li>registration and account identity — the name, email address and credentials used to create and hold an
105
+ account;</li>
106
+ <li>billing, payments, invoices, tax records and collections;</li>
107
+ <li>support conversations, including the tickets, emails, chats and attachments themselves;</li>
108
+ <li>security, fraud prevention, abuse handling and audit logging;</li>
109
+ <li>our own websites and their analytics, our newsletters, and our marketing to prospective customers; and</li>
110
+ <li>running our business — accounting, insurance, professional advice, and defending claims.</li>
111
+ </ul>
112
+ <p>Everything in this notice about purposes, legal bases, retention, transfers and your rights applies to this
113
+ first case directly, and you exercise those rights against us.</p>
114
+ <h3 id="2-personal-data-a-customer-puts-into-the-service-about-its-own-people-the-customer-is-the-controller" tabindex="-1">2. Personal data a customer puts into the Service about its own people — the customer is the controller</h3>
115
+ <p>When an organisation subscribes to the Service and uses it to run its business, the personal data it puts
116
+ in is <strong>its</strong> data. It decides what to collect, which features to switch on, why, and for how long to keep
117
+ it. <strong>We process that data only on that organisation's instructions.</strong> For it, the organisation is the
118
+ controller and we are the processor.</p>
119
+ <p>This covers the ordinary contents of a workspace — employee and contractor records, contact details,
120
+ projects, tasks, documents and messages. It also covers the parts that matter most, where a product
121
+ provides them and the customer has enabled them:</p>
122
+ <ul>
123
+ <li><strong>time-tracking data</strong> — timers, timesheets, time entries and the records behind them;</li>
124
+ <li><strong>activity data</strong> — how much keyboard and mouse activity occurred in a period, idle time, and which
125
+ applications and websites were in use;</li>
126
+ <li><strong>screen and media capture</strong> — periodic screenshots and, where separately switched on, webcam stills,
127
+ audio recordings and screen recordings.</li>
128
+ </ul>
129
+ <p><strong>We do not decide to collect any of this. The customer does.</strong> We build the features, we document what
130
+ each one captures and what each control does, and we run them exactly as the customer configures them. We
131
+ do not use that data for our own purposes, we do not use it to train models, and we do not look at it
132
+ except where we must in order to run, secure or support the Service.</p>
133
+ <p>What Ever Rec 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 Rec 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://rec.so/cookies">Cookie Policy</a>.</li>
215
+ </ul>
216
+ <h3 id="what-we-receive-from-other-people" tabindex="-1">What we receive from other people</h3>
217
+ <ul>
218
+ <li><strong>Identity providers</strong> — if you sign in with a third-party account, we receive that account's identifier,
219
+ your email address, your display name and usually your profile picture, plus confirmation that the
220
+ sign-in succeeded. <strong>We never receive your password for it.</strong></li>
221
+ <li><strong>Payment processors</strong> — whether a payment succeeded or failed, the payment method type, the last four
222
+ digits and expiry of a card, the billing country, and any dispute or chargeback.</li>
223
+ <li><strong>Integrations you or your administrator connect</strong> — whatever the connected service returns within the
224
+ permissions granted. That varies by integration and is shown to you when you authorise it.</li>
225
+ <li><strong>Your organisation</strong> — where an administrator creates your account, invites you, sets your role or
226
+ imports records about you.</li>
227
+ <li><strong>Other sources</strong>, where a particular product uses them. Those are set out in the next section and in the
228
+ annex.</li>
229
+ </ul>
230
+ <h3 id="what-you-have-to-give-us" tabindex="-1">What you have to give us</h3>
231
+ <p>Some of it is unavoidable. Without account identity we cannot create an account for you; without billing
232
+ details we cannot take payment for a paid plan; without certain records we cannot meet our own legal
233
+ obligations. Where data is necessary in that sense, <strong>not providing it means we cannot provide that part of
234
+ the Service</strong> — but nothing worse follows.</p>
235
+ <p>Everything else — an optional profile field, a newsletter subscription, an integration you could simply not
236
+ connect — is genuinely optional, and declining it costs you nothing.</p>
237
+ <h2 id="data-we-do-not-collect" tabindex="-1">Data we do not collect</h2>
238
+ <p>Shorter than the previous section, and just as binding. These are commitments about how the Service is
239
+ built, not aspirations.</p>
240
+ <ul>
241
+ <li><strong>We do not sell personal data.</strong> Not to data brokers, not to advertisers, not to anyone — and not under
242
+ the broader definitions of &quot;sell&quot; or &quot;share&quot; used outside the European Union.</li>
243
+ <li><strong>We do not buy marketing lists.</strong> If we contact you about our products it is because you gave us your
244
+ details, or because you are already a customer. We do not purchase your name from someone else in order
245
+ to email you.</li>
246
+ <li><strong>We do not use your content to train machine-learning models</strong> — not for our own purposes, and not for
247
+ the benefit of other customers. Where a product has an AI feature, it processes your content to produce
248
+ your result, and that is the end of it. If we ever want that to change, it will be an opt-in you actively
249
+ choose, described before you choose it.</li>
250
+ <li><strong>We do not run advertising inside the Service.</strong> No third-party advertising, no behavioural ad
251
+ targeting, no cross-site advertising identifiers in the product.</li>
252
+ <li><strong>We do not record what you type.</strong> Where a product measures keyboard and mouse activity, it counts
253
+ events over a period. <strong>There is no keylogger in our software. The content of your keystrokes is never
254
+ captured, stored or transmitted.</strong></li>
255
+ <li><strong>We do not ask for special-category data</strong> — health, racial or ethnic origin, religious or philosophical
256
+ beliefs, political opinions, trade union membership, sex life or sexual orientation, genetic or biometric
257
+ data. There are no fields for it, we do not infer it, and we do not want it. The one honest caveat is
258
+ about what can end up inside a screenshot, and it has its own section below.</li>
259
+ <li><strong>We do not store full card numbers or card security codes.</strong> Those are entered on our payment
260
+ processor's systems and never reach ours.</li>
261
+ <li><strong>We do not collect precise location by default.</strong> Where a product uses location at all, it is because a
262
+ specific feature needs it, and that feature says so.</li>
263
+ </ul>
264
+ <p>If you find any of this to be untrue of something we ship, tell us at privacy@ever.co. We will treat it
265
+ as a defect in the product, not as a disagreement about wording.</p>
266
+ <h2 id="where-data-comes-from-when-it-does-not-come-from-you" tabindex="-1">Where data comes from when it does not come from you</h2>
267
+ <p>Not all of the personal data we hold came from you. Article 14 of the GDPR requires us to tell you where it
268
+ came from, and this section does that.</p>
269
+ <ul>
270
+ <li><strong>Your employer, or the administrator of your workspace.</strong> Where an organisation subscribes to the
271
+ Service, an administrator creates accounts, invites people, sets roles and imports records. That supplies
272
+ your name, work email address, job title, team, role and permissions, and whatever else the organisation
273
+ chooses to hold about you in its workspace. <strong>For that data the organisation is the controller</strong>, as set
274
+ out above.</li>
275
+ <li><strong>Identity providers.</strong> If you sign in with a third-party account, that provider supplies the account
276
+ identifier, your email address, your display name and usually a profile picture, and confirms the sign-in
277
+ succeeded. It supplies nothing else, and never a password.</li>
278
+ <li><strong>Integrations you or your administrator connect.</strong> A connected service supplies whatever the permissions
279
+ you granted allow — for example issues and repositories from a code host, messages and channel names from
280
+ a chat tool, calendar entries, contacts, or records from another business system. The scope is shown when
281
+ the connection is authorised, and it can be revoked in the same place.</li>
282
+ <li><strong>Payment processors and resellers.</strong> They supply the outcome of a payment, the payment method type, the
283
+ last four digits and expiry of a card, the billing country, and any dispute or chargeback. They do not
284
+ pass us the card itself.</li>
285
+ <li><strong>Publicly available sources, where a product builds profiles from them.</strong> Some products work with
286
+ information people have published themselves — a public code-hosting profile, a public company page, a
287
+ public professional listing. Where a product does this, the annex names the categories taken and the
288
+ sources they came from, explains the basis we rely on, and says how to object. <strong>If we hold a profile
289
+ about you that you never gave us, you can object to it and we will act on that.</strong></li>
290
+ <li><strong>Service providers acting for us.</strong> Fraud and abuse signals, delivery and bounce information from the
291
+ systems that send our email, and security intelligence about addresses and networks.</li>
292
+ </ul>
293
+ <p>Where we are the controller of personal data that did not come from you, we will tell you within a
294
+ reasonable period and at the latest within one month of obtaining it — or, if we use it to contact you, at
295
+ that first contact. Where informing every individual separately would take disproportionate effort, this
296
+ notice and its annex are the public information we provide instead, which is what Article 14(5)(b) allows.</p>
297
+ <h2 id="why-we-use-personal-data-and-on-what-legal-basis" tabindex="-1">Why we use personal data, and on what legal basis</h2>
298
+ <p>Article 6 of the GDPR requires a lawful basis for each purpose. So this is one row per purpose, rather than
299
+ a general list of all six bases — you can check us against each line.</p>
300
+ <table>
301
+ <thead>
302
+ <tr>
303
+ <th>Purpose</th>
304
+ <th>Personal data used</th>
305
+ <th>Lawful basis</th>
306
+ </tr>
307
+ </thead>
308
+ <tbody>
309
+ <tr>
310
+ <td>Providing Ever Rec Cloud: creating and running your account, signing you in, delivering the features you use, and keeping your data available to you</td>
311
+ <td>Account identity, organisation and role, credentials, content you submit, device and connection data</td>
312
+ <td><strong>Contract</strong> — Art 6(1)(b). Necessary to perform our agreement with you</td>
313
+ </tr>
314
+ <tr>
315
+ <td>Taking payment: invoicing, collecting fees, applying refunds, chasing non-payment</td>
316
+ <td>Billing details, plan and subscription data, invoices, payment outcomes</td>
317
+ <td><strong>Contract</strong> — Art 6(1)(b)</td>
318
+ </tr>
319
+ <tr>
320
+ <td>Keeping accounting, tax and invoicing records</td>
321
+ <td>Invoices, payment records, billing identity</td>
322
+ <td><strong>Legal obligation</strong> — Art 6(1)(c), under tax and accounting law</td>
323
+ </tr>
324
+ <tr>
325
+ <td>Support: answering your questions, investigating faults and reproducing problems you report</td>
326
+ <td>Support correspondence, account identity, logs and diagnostics, and whatever you point us at</td>
327
+ <td><strong>Contract</strong> — Art 6(1)(b) where you are a customer. <strong>Legitimate interests</strong> — Art 6(1)(f) where you are not, so that we can answer anyone who writes to us</td>
328
+ </tr>
329
+ <tr>
330
+ <td>Security and abuse prevention: authentication, rate limiting, bot and fraud detection, investigating misuse, protecting accounts and infrastructure</td>
331
+ <td>Account identity, IP address, device data, request logs, sign-in and failed sign-in records</td>
332
+ <td><strong>Legitimate interests</strong> — Art 6(1)(f) in keeping the Service and the people who use it safe</td>
333
+ </tr>
334
+ <tr>
335
+ <td>Keeping the Service running: monitoring, error tracking, debugging, capacity planning and backups</td>
336
+ <td>Logs, diagnostics, usage data, account identifiers</td>
337
+ <td><strong>Legitimate interests</strong> — Art 6(1)(f) in operating a reliable service</td>
338
+ </tr>
339
+ <tr>
340
+ <td>Understanding how the Service is used, so we can improve it</td>
341
+ <td>Usage events, feature interactions, device and browser data, aggregated statistics</td>
342
+ <td><strong>Legitimate interests</strong> — Art 6(1)(f). <strong>Consent</strong> — Art 6(1)(a) wherever cookies or similar device storage are involved, as set out in our <a href="https://rec.so/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 Rec provides, and what its defaults are, is set out in the annex later
489
+ in this notice.</p>
490
+ <h2 id="ever-rec-what-it-captures-and-the-people-who-never-signed-up" tabindex="-1">Ever Rec: what it captures, and the people who never signed up</h2>
491
+ <p>Everything above describes how we handle personal data generally. This annex describes Ever Rec
492
+ specifically, and it exists because this product does something unusual: <strong>most of the people whose personal
493
+ data it processes have no account, gave us nothing, and have never heard of us.</strong> They are in a recording
494
+ somebody else made, or they clicked a link somebody else sent them. We would rather write for them than
495
+ about them.</p>
496
+ <h3 id="three-ways-a-capture-is-made" tabindex="-1">Three ways a capture is made</h3>
497
+ <ul>
498
+ <li><strong>The browser extension.</strong> It records a full screen, a single application window, or a single browser tab
499
+ — <strong>and where you record a tab, it records that tab's audio.</strong> It can record your webcam, on its own or
500
+ alongside the screen, and your microphone.</li>
501
+ <li><strong>The web application</strong> at <a href="https://rec.so">https://rec.so</a>. Your library, the image and video editor,
502
+ whiteboards, folders, comments, likes, workspaces and teams.</li>
503
+ <li><strong>The desktop application.</strong> It takes screenshots on a cadence you set, can record the audio your computer
504
+ is playing, and records the activity data described further down. It is a materially different thing from
505
+ the other two and it has its own section below.</li>
506
+ </ul>
507
+ <p><strong>Nothing captures until a person starts a capture.</strong> There is no organisation-wide setting that switches
508
+ recording on for somebody else, and no configuration in which the Service records without a person having
509
+ begun it on that device.</p>
510
+ <h3 id="your-captures-are-content-and-we-do-not-go-looking-inside-them" tabindex="-1">Your captures are content, and we do not go looking inside them</h3>
511
+ <p>A capture is unstructured. <strong>It contains whatever was on the screen and whatever the microphone could hear</strong>
512
+ — other people's names and email addresses, a chat thread, an open document, a customer record, a medical
513
+ portal, a bank balance, a face, a voice in the background of the room.</p>
514
+ <p>We cannot classify that, and we do not try. We store it, we serve it back to you, we serve it to whoever you
515
+ share it with, and that is the extent of our involvement. We do not review captures for our own purposes, we
516
+ do not index their contents, and we do not use them to train models.</p>
517
+ <p><strong>Where a workspace belongs to an organisation, that organisation is the controller of what its people
518
+ capture into it and we are its processor.</strong> Where you use Ever Rec on a personal account, you decide
519
+ what to capture and we hold it for you.</p>
520
+ <p>Practical advice, offered because it is the only real protection: <strong>close what should not be in the frame
521
+ before you press record.</strong> Ever Rec has no blur, no masking and no excluded-application list. Once a
522
+ capture exists, editing it out or deleting it is the only remedy.</p>
523
+ <h3 id="faces-and-voices" tabindex="-1">Faces and voices</h3>
524
+ <p>The webcam, the microphone, a recorded browser tab during a video call and the desktop application's system
525
+ audio all mean the same thing: <strong>we routinely hold recordings of identifiable faces and voices</strong>, including
526
+ of people who are not our users.</p>
527
+ <p>So that there is no ambiguity about what we do with them:</p>
528
+ <ul>
529
+ <li><strong>We do not extract biometric templates</strong>, faceprints or voiceprints from anything you capture.</li>
530
+ <li><strong>We do not run facial recognition, voice recognition, matching or identification</strong> on captures, and we do
531
+ not attempt to identify anyone appearing in one.</li>
532
+ <li><strong>We do not transcribe captures, and we do not summarise them with a model.</strong></li>
533
+ </ul>
534
+ <p>If we ever build a feature that does any of that, <strong>we will publish a separate notice describing it and ask
535
+ for consent before it runs on anything</strong> — we will not switch it on across an existing library and announce
536
+ it afterwards.</p>
537
+ <h3 id="the-controls-that-exist-and-the-ones-that-do-not" tabindex="-1">The controls that exist, and the ones that do not</h3>
538
+ <p>The privacy notice above lists the controls a capture product can offer. Being accurate about
539
+ Ever Rec means saying which of them we actually have.</p>
540
+ <p><strong>What you can do:</strong></p>
541
+ <ul>
542
+ <li>choose the source of every recording — a screen, a window, a single tab, the camera, the microphone — and
543
+ see that choice before you start;</li>
544
+ <li>stop a recording, discard it, or delete an item afterwards;</li>
545
+ <li>end sharing for an item, subject to the important caveat in the retention section below;</li>
546
+ <li>edit a capture, including cropping or drawing over part of it, before you share it; and</li>
547
+ <li>for the desktop application, choose the capture interval and choose the storage it uploads to.</li>
548
+ </ul>
549
+ <p><strong>What Ever Rec does not currently provide, stated plainly:</strong></p>
550
+ <ul>
551
+ <li><strong>no recording indicator or notice to the people being captured.</strong> Nothing in the product tells a person
552
+ on the other end of a call that a recording has started. Telling them is entirely on the person recording;</li>
553
+ <li>no blur, masking or redaction applied automatically, and no way to exclude a named application or window
554
+ from capture;</li>
555
+ <li>no retention setting, no expiry and no automatic deletion; and</li>
556
+ <li>no administrator control that limits what an individual member may capture.</li>
557
+ </ul>
558
+ <p>We are not presenting the absence of those controls as a design decision. They are gaps, and this notice is
559
+ where you should be able to find that out.</p>
560
+ <h3 id="people-we-hold-data-about-who-never-dealt-with-us" tabindex="-1">People we hold data about who never dealt with us</h3>
561
+ <p>Article 14 of the GDPR is about exactly this: personal data we hold that the person did not give us. There
562
+ are four groups, and this section is for them.</p>
563
+ <p><strong>1. People inside a capture.</strong> If you appear in, are heard in, or are identifiable from a recording or
564
+ screenshot somebody else made, we hold that recording. <strong>We got it from that person, not from you.</strong> We had
565
+ no relationship with you, no way to reach you before it happened, and no way to tell that you were in it.
566
+ For the content itself we act for the account that made it. <strong>You can still write to abuse@ever.co</strong>
567
+ with the link — the Terms of Service describe what we will do, including disabling access to the item while
568
+ we look at it. If the capture was made through an employer's workspace, that employer is the controller and
569
+ you also have rights directly against them.</p>
570
+ <p><strong>2. Anonymous viewers of a share link.</strong> When you open a share link without signing in, we record <strong>your IP
571
+ address and the time</strong> against that item, so that the person who shared it can see it has been viewed and so
572
+ that we can detect abuse of our open share endpoints. <strong>Our lawful basis is our legitimate interest</strong> in
573
+ counting views and protecting the Service from automated scraping. That record lives with the item it
574
+ belongs to.</p>
575
+ <p><strong>3. Signed-in viewers.</strong> If you open a share link while signed in to Ever Rec, we record your
576
+ account identifier, <strong>your display name, your profile picture and your email address</strong>, and the time — and
577
+ <strong>we show all of that to the person who owns the item.</strong> That is deliberate: it is how a sharer knows who
578
+ watched. We are telling you here because almost nobody expects a video link to hand their work email address
579
+ to the sender. <strong>If you do not want that, open the link signed out</strong> — your IP address is still recorded, but
580
+ your identity is not disclosed. If it has already happened and you want the record removed, ask us at
581
+ privacy@ever.co.</p>
582
+ <p><strong>4. Recipients of a shared item.</strong> When someone sends you a capture by email or by WhatsApp, they give us
583
+ <strong>your email address or your telephone number</strong> so that we can deliver it, together with any message they
584
+ wrote. We pass those to our email and messaging providers for that delivery and keep the record of the send.
585
+ We do not add you to any marketing list, and you can ask us at privacy@ever.co to stop sending you items
586
+ from a particular account.</p>
587
+ <p>None of these four groups needs an account to exercise any right in the rights section below, and none of
588
+ them needs to explain why they are asking.</p>
589
+ <h3 id="the-browser-extension" tabindex="-1">The browser extension</h3>
590
+ <p>The extension asks your browser for <strong>access to all sites, a script that runs on every page, and access to
591
+ cookies.</strong> That is a wide permission set, and it is wide because a capture can be started from any page you
592
+ happen to be on and the extension has to be able to run there.</p>
593
+ <p><strong>What we commit to, and what you should hold us to:</strong> we do not use that access to read, collect, store or
594
+ transmit the contents of the pages you visit, what you type into them, or your cookies — other than as part
595
+ of a capture you have started, where by definition what is on the page is what you are recording. <strong>If you
596
+ find that untrue of something we ship, tell us at privacy@ever.co and we will treat it as a defect in
597
+ the product, not as a difference of opinion about wording.</strong></p>
598
+ <p><strong>When the extension is removed from your browser, we record an IP address and the time</strong>, so that we can
599
+ count removals. That is our legitimate interest in knowing how the product is doing. It is not linked to
600
+ your account, and you can ask us to delete it at privacy@ever.co.</p>
601
+ <h3 id="the-desktop-application-which-is-not-simply-a-screenshot-tool" tabindex="-1">The desktop application, which is not simply a screenshot tool</h3>
602
+ <p>The desktop application does more than the marketing describes, and this is the honest inventory.</p>
603
+ <p><strong>With every capture it takes, it records:</strong></p>
604
+ <ul>
605
+ <li>the name of the application that was in the foreground;</li>
606
+ <li><strong>the title of the active window</strong>;</li>
607
+ <li><strong>the address of the page open in the active browser</strong>; and</li>
608
+ <li>the application's icon.</li>
609
+ </ul>
610
+ <p><strong>Separately from captures, it records:</strong></p>
611
+ <ul>
612
+ <li>whether the machine is active, idle or locked, and for how long;</li>
613
+ <li>time logs — when a tracked period started and ended, and how long it ran; and</li>
614
+ <li>figures derived from those: <strong>a productivity score</strong>, and an hour-by-hour distribution of active, idle and
615
+ locked time.</li>
616
+ </ul>
617
+ <p>Window titles and browser addresses are personal data about the person at the keyboard, and they are far
618
+ more revealing than a count of keystrokes: a window title routinely names a document, a client, a colleague
619
+ or a medical appointment.</p>
620
+ <p><strong>Where that data goes, and why it mostly does not come to us:</strong></p>
621
+ <ul>
622
+ <li>it is written to <strong>a database on your own computer</strong>; and</li>
623
+ <li>it is uploaded to <strong>an S3-compatible storage bucket you supply</strong>. You enter the endpoint, the region, the
624
+ bucket, the access key and the secret, and those credentials are held in your own operating system's
625
+ keychain, on your machine.</li>
626
+ </ul>
627
+ <p><strong>We never receive those captures and we never see those credentials.</strong> We are not the controller or the
628
+ processor for the contents of your bucket, our security commitments do not describe it, and our
629
+ sub-processor list does not cover it. Data reaches us from the desktop application only if you separately
630
+ sign in and upload something to Ever Rec Cloud.</p>
631
+ <p><strong>If an organisation deploys the desktop application to its workforce</strong>, that organisation is the controller
632
+ of everything above. It needs its own lawful basis, it must tell each person what is being recorded before
633
+ it starts, it must complete a data protection impact assessment where one is required — and for this kind of
634
+ systematic monitoring one usually is — and it must complete any works council or employee-representative
635
+ process its country requires. Our Data Processing Addendum puts that in binding terms, and our
636
+ <a href="https://rec.so/aup">Acceptable Use Policy</a> prohibits deploying it covertly.</p>
637
+ <p><strong>If you are being monitored this way and want to know what is held about you, ask your employer</strong> — it
638
+ holds the bucket and it holds the answers. If you write to us instead we will help you reach them, as the
639
+ controller-and-processor section above describes.</p>
640
+ <h3 id="what-is-not-private-about-your-account" tabindex="-1">What is not private about your account</h3>
641
+ <ul>
642
+ <li><strong>Your display name and your profile picture are not private.</strong> They are shown to everyone who opens an
643
+ item you shared, and the profile record that holds them can be read without an account.</li>
644
+ <li><strong>An item you have shared is reachable by anyone holding the link</strong>, and its record is visible to other
645
+ signed-in users of the Service. Sharing is closer to publishing than to sending.</li>
646
+ <li><strong>A workspace administrator can open every item in that workspace</strong>, including items you never shared.</li>
647
+ </ul>
648
+ <h3 id="where-your-captures-actually-live" tabindex="-1">Where your captures actually live</h3>
649
+ <p>Elsewhere in this notice we say that we run our own infrastructure. <strong>Ever Rec is the exception, and
650
+ it is a large one:</strong></p>
651
+ <ul>
652
+ <li><strong>Account identity, sign-in, item metadata, folder and workspace structure, sharing records, comments,
653
+ likes and the view records described above are held in Google Firebase</strong> — Firebase Authentication and the
654
+ Firebase Realtime Database.</li>
655
+ <li><strong>The captures themselves — screenshots, recordings, edited images and whiteboards — are stored in
656
+ Firebase Cloud Storage.</strong></li>
657
+ <li><strong>Screen recordings are additionally handed to a video provider</strong> for transcoding, thumbnailing and
658
+ streaming. <strong>That is the recording content itself, not just a reference to it.</strong></li>
659
+ </ul>
660
+ <p>Both are named, with what reaches them and where they are, in our
661
+ <a href="https://rec.so/subprocessors">Sub-processor List</a>, and the transfer mechanisms are in the international
662
+ transfers section below.</p>
663
+ <h3 id="how-long-we-keep-captures-and-what-delete-does-here" tabindex="-1">How long we keep captures, and what &quot;delete&quot; does here</h3>
664
+ <p>The retention table below gives our periods for accounts, logs, billing records and support. For captures
665
+ themselves, the honest answer for Ever Rec today is different and you should have it plainly:</p>
666
+ <ul>
667
+ <li><strong>We do not delete captures automatically.</strong> There is no expiry, no time-to-live and no inactivity rule.
668
+ A capture stays until you delete it, or until the end of the export window after an account closes.</li>
669
+ <li><strong>Moving an item to trash hides it from your library. It does not by itself erase the stored file.</strong> Use
670
+ delete when you mean delete.</li>
671
+ <li><strong>Deleting an item is not guaranteed to invalidate a direct storage address that was already issued for
672
+ it</strong>, and ending sharing is not the same as deleting. If something must genuinely stop being reachable,
673
+ delete it and tell us at privacy@ever.co so that we can confirm the underlying file is gone.</li>
674
+ <li>View records live with the item they belong to, and go when it goes.</li>
675
+ <li><strong>Deleting your account</strong> removes your account record and the items held under it. It does not reach
676
+ copies you exported to Google Drive, Dropbox, Slack, Jira, Trello, an inbox or a WhatsApp thread, and it
677
+ does not reach a capture somebody else made of you.</li>
678
+ </ul>
679
+ <p><strong>We will not introduce automatic deletion of existing libraries without publishing the schedule first and
680
+ giving notice</strong>, because a retention rule applied retrospectively and silently would destroy people's work.
681
+ If you want a shorter period than &quot;until you delete it&quot;, ask privacy@ever.co and we will carry out a
682
+ bulk deletion for you.</p>
683
+ <h3 id="analytics-and-telemetry-inside-the-product" tabindex="-1">Analytics and telemetry inside the product</h3>
684
+ <ul>
685
+ <li><strong>Product events</strong> — registration, sign-in and connecting an integration — are sent to our analytics
686
+ provider, keyed to your account identifier.</li>
687
+ <li><strong>Error telemetry</strong> from the portal, the API and the extension goes to our error-tracking provider. Error
688
+ reports carry your IP address, the page or endpoint that failed, and fragments of the failing request,
689
+ which can incidentally contain other data.</li>
690
+ <li><strong>The signed-in application does not run third-party website analytics.</strong> What runs on the marketing site
691
+ at <a href="https://rec.so">rec.so</a> is different, and our
692
+ <a href="https://rec.so/cookies">Cookie Policy</a> lists it surface by surface.</li>
693
+ </ul>
694
+ <h2 id="cookies-and-similar-technologies" tabindex="-1">Cookies and similar technologies</h2>
695
+ <p>Cookies, local storage, pixels, software development kits and similar technologies get their own document,
696
+ because they need more detail than a summary can carry. What each one is, what it does, how long it lasts,
697
+ who operates it and how to refuse it is set out in our <a href="https://rec.so/cookies">Cookie Policy</a>.</p>
698
+ <p>In short, we sort them into four categories:</p>
699
+ <ul>
700
+ <li><strong>Strictly necessary</strong> — needed to deliver what you asked for: signing you in, holding your session,
701
+ routing traffic, remembering your cookie choice itself, and protecting forms and sign-in against
702
+ automated abuse. These are not optional, and we do not ask for consent to them.</li>
703
+ <li><strong>Preferences</strong> — remember choices you have made, such as language, region and interface settings.</li>
704
+ <li><strong>Analytics</strong> — help us understand how the Service is used so we can improve it.</li>
705
+ <li><strong>Marketing</strong> — measure our campaigns and help us understand which organisations take an interest in us.</li>
706
+ </ul>
707
+ <p><strong>Nothing in the preferences, analytics or marketing categories is placed or read on your device until you
708
+ agree to it.</strong> You can accept everything, refuse everything, or choose category by category, and refusing
709
+ takes exactly as few clicks as accepting.</p>
710
+ <h3 id="changing-your-mind" tabindex="-1">Changing your mind</h3>
711
+ <p>Your choices are not permanent. A <strong>Cookie preferences</strong> link sits in the footer of every page on
712
+ <a href="https://rec.so">rec.so</a> and reopens the same panel you saw the first time. Change a category
713
+ there and it takes effect immediately, for the future. Withdrawing is as easy as agreeing, and nothing
714
+ about the Service is withheld from you for refusing.</p>
715
+ <p>One analytics tool runs without consent, because it is configured so that it stores and reads nothing on
716
+ your device and never builds a persistent identifier for you. That is a conditional position, not a
717
+ permanent one: the <a href="https://rec.so/cookies">Cookie Policy</a> names the tool, describes the exact
718
+ configuration we rely on, and says what happens if any part of that configuration ever changes.</p>
719
+ <h2 id="who-receives-your-personal-data" tabindex="-1">Who receives your personal data</h2>
720
+ <p>We disclose personal data only to the categories of recipient below, and only as much as each one needs to
721
+ do the job it is there for.</p>
722
+ <ul>
723
+ <li><strong>Service providers acting as our processors</strong> — hosting and infrastructure, storage, content delivery,
724
+ email delivery, error monitoring, product analytics, customer support tooling and similar. They act on
725
+ our documented instructions under a written contract that meets Article 28 GDPR, they are bound to
726
+ confidentiality and appropriate security, and <strong>they may not use your data for their own purposes</strong>.</li>
727
+ <li><strong>Payment processors</strong> — to take payment, issue invoices and handle refunds and disputes. For their own
728
+ regulated obligations — fraud prevention, anti-money-laundering, card-scheme rules — they act as
729
+ controllers in their own right, and their own privacy notice governs that part.</li>
730
+ <li><strong>Professional advisers</strong> — lawyers, accountants, auditors and insurers, bound by professional
731
+ confidentiality, where we need advice or have to evidence that we have complied with something.</li>
732
+ <li><strong>Public authorities, courts and regulators</strong> — where the law requires us to disclose, or where we need
733
+ to establish, exercise or defend a legal claim. We check that a request has a proper legal basis and is
734
+ no wider than it needs to be, we push back where it is not, and we tell you about it unless we are
735
+ legally prohibited from doing so.</li>
736
+ <li><strong>An acquirer or successor</strong> — if we are reorganised, merged or sold, or if part of the business changes
737
+ hands, personal data may pass to the acquirer as part of that transaction. The acquirer is bound by this
738
+ policy or by a notice at least as protective, and we will tell you before anything about the handling of
739
+ your data changes.</li>
740
+ </ul>
741
+ <h3 id="the-sub-processors-we-engage-for-the-hosted-service" tabindex="-1">The sub-processors we engage for the hosted Service</h3>
742
+ <p>These providers are engaged for the hosted Service as it is delivered to everyone. They are the ones your
743
+ data is most likely to reach.</p>
744
+ <table>
745
+ <thead>
746
+ <tr>
747
+ <th>Sub-processor</th>
748
+ <th>Purpose</th>
749
+ <th>Location</th>
750
+ <th>Personal data</th>
751
+ </tr>
752
+ </thead>
753
+ <tbody>
754
+ <tr>
755
+ <td>Cloudflare, Inc.</td>
756
+ <td>Authoritative DNS, reverse proxy, TLS termination, content delivery and bot/DDoS filtering in front of rec.so, app.rec.so and api.rec.so, and the tunnel that reaches our origin. Every request to the Service passes through it.</td>
757
+ <td>United States, with connections terminated at the edge location nearest the visitor worldwide</td>
758
+ <td>IP address, request URL, headers and TLS metadata, cookies in transit</td>
759
+ </tr>
760
+ <tr>
761
+ <td>Google Ireland Limited (Firebase)</td>
762
+ <td>The core store for the hosted Service. Firebase Authentication holds account identity and sign-in; Firebase Realtime Database holds item metadata, folder and workspace structure, sharing records, comments, likes and the view records described in the Privacy Policy; Firebase Cloud Storage holds the screenshots, recordings, edited images and whiteboards themselves.</td>
763
+ <td>European Union and United States</td>
764
+ <td>screenshots, screen recordings, webcam and audio recordings, edited images and whiteboards, item titles, descriptions, chapters, folder and workspace structure, account identifier, email address, display name, profile picture and authentication tokens, sharing records, comments, likes, and viewer IP addresses and identities</td>
765
+ </tr>
766
+ <tr>
767
+ <td>Mux, Inc.</td>
768
+ <td>Transcoding, thumbnailing and adaptive streaming of screen recordings, and playback quality telemetry in the player. Mux and Api Video SAS are the two selectable video backends; the hosted Service uses one of them for every screen recording, and we will tell you which is in use for your account on request. Recording CONTENT reaches this provider, not only metadata.</td>
769
+ <td>United States</td>
770
+ <td>screen recording video content, which can contain anything that was on the capturer's screen, video thumbnails and asset identifiers, viewer IP address and playback telemetry</td>
771
+ </tr>
772
+ <tr>
773
+ <td>Api Video SAS</td>
774
+ <td>The alternative video backend to Mux, on the same basis — transcoding, hosting and streaming of screen recordings, with direct upload from the browser extension. Recording CONTENT reaches this provider.</td>
775
+ <td>France, with delivery from servers worldwide</td>
776
+ <td>screen recording video content, video thumbnails and asset identifiers, viewer IP address on playback</td>
777
+ </tr>
778
+ <tr>
779
+ <td>Functional Software, Inc. d/b/a Sentry</td>
780
+ <td>Error and performance telemetry from the web portal, the API and the browser extension, so that we can see what is failing and fix it.</td>
781
+ <td>United States</td>
782
+ <td>IP address, browser and device, the page or endpoint that failed, stack traces and breadcrumbs, account identifier where the error occurred while signed in, fragments of the failing request, which can incidentally contain other data</td>
783
+ </tr>
784
+ <tr>
785
+ <td>ActiveCampaign, LLC (Postmark)</td>
786
+ <td>Delivery of the transactional email the Service sends — account welcome, password reset, workspace invitation, and the notification that someone has shared an image or a recording with you.</td>
787
+ <td>United States</td>
788
+ <td>recipient email address, sender display name, the free-text message a sharer chooses to include, the link to the shared item</td>
789
+ </tr>
790
+ <tr>
791
+ <td>Twilio Inc. (Twilio Segment)</td>
792
+ <td>Product analytics for the hosted application. Events are emitted when an account registers, signs in and connects an integration, keyed to the account identifier.</td>
793
+ <td>United States</td>
794
+ <td>account identifier and account traits, product events and their timestamps, IP address</td>
795
+ </tr>
796
+ <tr>
797
+ <td>iubenda s.r.l.</td>
798
+ <td>The consent banner and preference centre on the rec.so website, and the record that proves what you chose and when.</td>
799
+ <td>Italy</td>
800
+ <td>IP address, consent choices and the proof record, timestamp and user agent</td>
801
+ </tr>
802
+ <tr>
803
+ <td>GitHub, Inc.</td>
804
+ <td>Source hosting, continuous integration and the container registry the Service is built from and deployed out of. This is how the Service is made, not where your data lives.</td>
805
+ <td>United States</td>
806
+ <td>no capture content and no account content, contributor and developer identity in commits and build logs</td>
807
+ </tr>
808
+ </tbody>
809
+ </table>
810
+ <p>The full and current list, including everything below, is published at
811
+ <a href="https://rec.so/subprocessors">https://rec.so/subprocessors</a>, together with the notice period and
812
+ objection procedure that apply when we add or replace one.</p>
813
+ <h3 id="three-tiers-and-why-the-difference-matters" tabindex="-1">Three tiers, and why the difference matters</h3>
814
+ <p>A single flat list of every vendor that appears anywhere in our software would be both inaccurate and
815
+ misleading, so the sub-processor page is split into three tiers. They mean genuinely different things.</p>
816
+ <ul>
817
+ <li><strong>Always engaged.</strong> The providers above. If you use the hosted Service, these are in the path.</li>
818
+ <li><strong>Engaged only if you turn something on.</strong> Optional integrations, connectors and features. A provider in
819
+ this tier is engaged only when you or your workspace administrator enables the specific feature or
820
+ connects the specific account it belongs to. Enable nothing and it is never involved. The list says which
821
+ feature or setting activates each one.</li>
822
+ <li><strong>Self-hosted deployments only.</strong> Several of our products are published as open source and can be run on
823
+ your own infrastructure. In that case <strong>you</strong> choose the database, object storage, email relay, AI
824
+ provider and everything else, using your own credentials. Those providers appear in the list so you can
825
+ see what the software can be pointed at — but they are <strong>your</strong> providers, not ours. <strong>We process nothing
826
+ in a deployment you run, we are not your processor for it, and the commitments in this policy do not
827
+ describe it.</strong></li>
828
+ </ul>
829
+ <h3 id="we-do-not-sell-your-personal-data" tabindex="-1">We do not sell your personal data</h3>
830
+ <p>We do not sell personal data, and we do not share it for cross-context behavioural advertising. We do not
831
+ supply it to data brokers, we do not trade it for services, and we do not permit any provider we engage to
832
+ use it to build advertising or interest profiles, on our sites or anywhere else.</p>
833
+ <h2 id="sending-personal-data-outside-the-eea" tabindex="-1">Sending personal data outside the EEA</h2>
834
+ <p>Most of the personal data we hold stays inside the European Economic Area, on infrastructure we operate
835
+ ourselves. Some of it does not: a number of the providers we engage are established outside the EEA —
836
+ principally in the United States — and some of them route, cache or store data on servers outside it.</p>
837
+ <p>Where that happens, the transfer needs a lawful mechanism under Chapter V GDPR. We use one of the
838
+ following for every transfer, and the sub-processor page names the destination country and the mechanism
839
+ provider by provider.</p>
840
+ <h3 id="adequacy" tabindex="-1">Adequacy</h3>
841
+ <p>Where the European Commission has decided that a country provides an adequate level of protection, the
842
+ transfer relies on that decision and needs nothing further. Adequacy decisions are kept under review by
843
+ the Commission and can be amended, suspended or repealed, so we monitor them rather than treat them as
844
+ permanent.</p>
845
+ <h3 id="providers-in-the-united-states" tabindex="-1">Providers in the United States</h3>
846
+ <p>For a US provider we rely on one of two things.</p>
847
+ <ul>
848
+ <li><strong>The EU–US Data Privacy Framework</strong>, but only where that provider is <em>actively self-certified</em> under it
849
+ for the type of data concerned. We check the official Data Privacy Framework list when we engage a
850
+ provider and re-check it periodically. <strong>We do not claim the Framework for a provider that has not
851
+ certified, or whose certification has lapsed.</strong></li>
852
+ <li><strong>Standard Contractual Clauses</strong> — the clauses approved by the European Commission in Implementing
853
+ Decision (EU) 2021/914, with the modules that match the relationship, together with a transfer impact
854
+ assessment and supplementary measures: encryption in transit and at rest, minimising what is sent in the
855
+ first place, contractual limits on onward disclosure, and a commitment from the provider to notify and
856
+ where possible challenge a government access request.</li>
857
+ </ul>
858
+ <p><strong>We keep Standard Contractual Clauses in place as the standing mechanism</strong>, including for providers that
859
+ are also certified under the Framework. That is deliberate, and here is the honest reason.</p>
860
+ <p>The Commission's adequacy decision for the Framework, adopted on 10 July 2023, is currently valid. It was
861
+ challenged, and on 3 September 2025 the General Court of the European Union dismissed that challenge in
862
+ <em>Latombe</em> (Case T-553/23). <strong>That is not the end of it</strong> — an appeal is pending before the Court of
863
+ Justice as Case C-703/25 P, and the two arrangements that preceded this one were each struck down by the
864
+ same court. So we treat the Framework as a mechanism under review rather than a settled answer, and we
865
+ keep a second mechanism standing behind it so that a change in the law is a paperwork event for us and not
866
+ an interruption for you.</p>
867
+ <h3 id="other-countries" tabindex="-1">Other countries</h3>
868
+ <p>For a transfer to any other country without an adequacy decision, we use Standard Contractual Clauses with
869
+ the same assessment and supplementary measures. Where a transfer is to the United Kingdom or Switzerland,
870
+ the corresponding UK and Swiss additions are applied to those clauses.</p>
871
+ <p>We rely on an Article 49 derogation — for example, a transfer that is strictly necessary to perform a
872
+ contract you have asked us to perform — only in a specific, occasional case where no other mechanism fits.
873
+ It is not a routine mechanism for us, and we do not use it to run a regular data flow.</p>
874
+ <h3 id="getting-a-copy-of-the-safeguards" tabindex="-1">Getting a copy of the safeguards</h3>
875
+ <p>You are entitled to see the safeguards we rely on. Write to privacy@ever.co naming the provider or the
876
+ transfer you are asking about, and we will send you a copy of the relevant clauses and tell you which
877
+ modules apply. We may redact commercial terms such as pricing and service levels; we do not redact the
878
+ data protection terms, which are the part that concerns you.</p>
879
+ <h2 id="how-long-we-keep-personal-data" tabindex="-1">How long we keep personal data</h2>
880
+ <p>&quot;As long as necessary&quot; is not an answer, so here are the actual periods. Each one runs from the event in
881
+ the middle column, and at the end of it we delete the data or irreversibly anonymise it.</p>
882
+ <table>
883
+ <thead>
884
+ <tr>
885
+ <th>What we hold</th>
886
+ <th>How long we keep it</th>
887
+ <th>Why that period</th>
888
+ </tr>
889
+ </thead>
890
+ <tbody>
891
+ <tr>
892
+ <td>Account and profile data — name, email address, workspace membership, settings</td>
893
+ <td>For as long as the account is open, then deleted within <strong>30 days</strong> of closure</td>
894
+ <td>We need it to give you the account; after that we do not</td>
895
+ </tr>
896
+ <tr>
897
+ <td>Content and files you put into the Service</td>
898
+ <td>For as long as the account is open; after it ends, available for export for <strong>30 days</strong>, then deleted</td>
899
+ <td>You decide what is in it — see below</td>
900
+ </tr>
901
+ <tr>
902
+ <td>Invoices, payment records and the tax data attached to them</td>
903
+ <td><strong>10 years</strong> from the end of the accounting year in which the transaction fell</td>
904
+ <td>Accounting and tax law in Bulgaria requires it, and we cannot shorten it at your request</td>
905
+ </tr>
906
+ <tr>
907
+ <td>Record that you accepted our terms — version, date, method</td>
908
+ <td><strong>5 years</strong> after the agreement ends</td>
909
+ <td>The general limitation period for a claim under the contract</td>
910
+ </tr>
911
+ <tr>
912
+ <td>Support correspondence and tickets</td>
913
+ <td><strong>24 months</strong> from the last message in the thread</td>
914
+ <td>Long enough to handle a recurring problem and a follow-up; not longer</td>
915
+ </tr>
916
+ <tr>
917
+ <td>Security, access and audit logs</td>
918
+ <td><strong>12 months</strong></td>
919
+ <td>Investigating unauthorised access, and evidencing that we did</td>
920
+ </tr>
921
+ <tr>
922
+ <td>Application and error logs, crash reports, diagnostics</td>
923
+ <td><strong>90 days</strong></td>
924
+ <td>Fixing what broke; they lose value quickly</td>
925
+ </tr>
926
+ <tr>
927
+ <td>Marketing contact records and the evidence of your consent</td>
928
+ <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>
929
+ <td>An unsubscribe that forgets you is not an unsubscribe</td>
930
+ </tr>
931
+ <tr>
932
+ <td>Cookie and consent choices</td>
933
+ <td>As stated in the <a href="https://rec.so/cookies">Cookie Policy</a>, which gives the lifetime of each entry</td>
934
+ <td>It belongs with the technology it describes</td>
935
+ </tr>
936
+ <tr>
937
+ <td>Backups</td>
938
+ <td>Each backup ages out on its own rolling cycle, within <strong>30 days</strong></td>
939
+ <td>Recovering from failure and ransomware, without becoming a second archive</td>
940
+ </tr>
941
+ <tr>
942
+ <td>Anything we are required to preserve for a legal claim, investigation or regulatory request</td>
943
+ <td>Until the claim, investigation or request ends, including any appeal period</td>
944
+ <td>We are not allowed to delete evidence, and neither are you</td>
945
+ </tr>
946
+ </tbody>
947
+ </table>
948
+ <h3 id="data-that-belongs-to-one-of-our-customers" tabindex="-1">Data that belongs to one of our customers</h3>
949
+ <p>For personal data held inside a customer's workspace — including anything the Service captures about that
950
+ customer's own personnel — <strong>the customer sets the retention period, not us</strong>. We are their processor for
951
+ it. The defaults and the limits of what they can configure are described in the product annex to this
952
+ policy.</p>
953
+ <p>We delete that data when the customer instructs us to, or at the end of the export window after their
954
+ agreement ends, whichever comes first. If you are one of their people and you want their data about you
955
+ deleted sooner, ask them — see the section on your rights, which explains how we route that.</p>
956
+ <h3 id="what-delete-means-here" tabindex="-1">What &quot;delete&quot; means here</h3>
957
+ <p>Deletion is applied to live systems straight away. Backup copies are not individually edited — doing so
958
+ would defeat what a backup is for — so a deleted record persists in backups until that backup ages out on
959
+ the cycle above, at most 30 days. During that window the data is not used for anything, and <strong>we do not
960
+ restore a backup to bring back data someone asked us to delete</strong>; a backup is restored only to recover a
961
+ whole system after a failure.</p>
962
+ <p>Where we can keep something useful without keeping you identifiable, we anonymise instead of deleting —
963
+ aggregate usage counts, for example. Once anonymised the data is no longer personal data, and it is not
964
+ possible for us to re-identify you from it.</p>
965
+ <h2 id="how-we-protect-personal-data" tabindex="-1">How we protect personal data</h2>
966
+ <p>We take the measures Article 32 GDPR requires: technical and organisational safeguards appropriate to the
967
+ risk, reviewed as the risk changes. In practice that means the following.</p>
968
+ <ul>
969
+ <li><strong>Encryption in transit.</strong> Traffic to and from the Service travels over TLS. HTTPS is enforced, and
970
+ plain HTTP requests are redirected rather than served.</li>
971
+ <li><strong>Encryption at rest.</strong> The storage holding customer content, databases and backups is encrypted at
972
+ rest, and particularly sensitive values — credentials, tokens and keys — are additionally encrypted at
973
+ the application layer rather than stored in readable form.</li>
974
+ <li><strong>Access control and least privilege.</strong> Access to production systems is limited to the people whose job
975
+ needs it, granted by named individual accounts rather than shared logins, protected by multi-factor
976
+ authentication, scoped to the narrowest role that works, and reviewed and revoked when a role changes or
977
+ someone leaves.</li>
978
+ <li><strong>Network segmentation.</strong> Databases, storage and internal services sit on segmented internal networks
979
+ and are not exposed to the public internet. Administrative interfaces are not publicly reachable.</li>
980
+ <li><strong>Logging.</strong> Administrative and security-relevant events are logged, retained for the period in the
981
+ retention section, and monitored so that unusual activity raises an alert rather than sitting unread.</li>
982
+ <li><strong>Backups.</strong> Data is backed up regularly, held on separate infrastructure from the live systems, and
983
+ restores are tested — an untested backup is a guess, not a control.</li>
984
+ <li><strong>Vulnerability management.</strong> Dependencies are scanned, code is analysed automatically before it ships,
985
+ security patches are applied on a defined schedule with a faster path for serious issues, and we operate
986
+ a responsible disclosure route so that anyone who finds a problem can tell us.</li>
987
+ <li><strong>Personnel.</strong> Everyone with access is bound by written confidentiality obligations that outlast their
988
+ engagement, works on a need-to-know basis, and has access removed when it is no longer needed.</li>
989
+ <li><strong>Providers.</strong> We assess a provider before we engage it, contract with it under Article 28 GDPR, and
990
+ hold it to security obligations at least as strict as our own.</li>
991
+ </ul>
992
+ <p>Our <a href="https://rec.so/security">Security page</a> sets out the detail, including which measure applies to
993
+ which part of the Service, our incident response process, and the shared responsibility split between what
994
+ we secure and what you secure.</p>
995
+ <h3 id="what-we-do-not-claim" tabindex="-1">What we do not claim</h3>
996
+ <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>
997
+ If anything you read or are told suggests otherwise, it is wrong, and we would like to know where it came
998
+ from. Where we describe a practice on this page or on the Security page, we describe something we actually
999
+ do; where we adopt a framework as a reference without being audited against it, we say so plainly rather
1000
+ than implying a certification.</p>
1001
+ <h3 id="no-system-is-perfectly-secure" tabindex="-1">No system is perfectly secure</h3>
1002
+ <p><strong>No service, ours included, can be made completely secure, and anyone who tells you otherwise is
1003
+ selling something.</strong> What we can honestly promise is that we take the measures above seriously, that we
1004
+ keep them under review, and that if a personal data breach affects you we will act on it: we notify the
1005
+ CPDP where the law requires it, within the deadline it sets, and we
1006
+ tell affected people directly without undue delay where the breach is likely to result in a high risk to
1007
+ them.</p>
1008
+ <p>Your part matters too. Use a strong and unique password, turn on multi-factor authentication where it is
1009
+ offered, keep your devices patched, and do not share credentials or access tokens. If you think an account
1010
+ has been compromised, tell us at privacy@ever.co immediately.</p>
1011
+ <h2 id="your-rights-over-your-personal-data" tabindex="-1">Your rights over your personal data</h2>
1012
+ <p>Where we are the controller, the GDPR gives you the rights below. They are yours to use, you do not have
1013
+ to explain why you are using them, and using one costs you nothing.</p>
1014
+ <ul>
1015
+ <li><strong>Access</strong> — ask whether we hold personal data about you and, if we do, get a copy of it together with
1016
+ the information in this policy about how it is used. (Article 15)</li>
1017
+ <li><strong>Rectification</strong> — have inaccurate data corrected and incomplete data completed. Much of this you can
1018
+ do yourself in your account settings, which is faster than asking us. (Article 16)</li>
1019
+ <li><strong>Erasure</strong> — have data deleted where we no longer need it for the purpose we collected it for, where
1020
+ you withdraw the consent it rested on, or where we have processed it unlawfully. (Article 17)</li>
1021
+ <li><strong>Restriction</strong> — have us pause processing while a dispute is sorted out: while we check an accuracy
1022
+ challenge, for example, or while we consider an objection. We keep the data but stop using it.
1023
+ (Article 18)</li>
1024
+ <li><strong>Portability</strong> — receive the data you gave us, in a structured, commonly used, machine-readable format,
1025
+ and have it sent to another provider where that is technically feasible. This applies to data processed
1026
+ by automated means on the basis of your consent or a contract with you. (Article 20)</li>
1027
+ <li><strong>Objection</strong> — object to processing we base on our legitimate interests. We then stop unless we can
1028
+ demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or unless
1029
+ we need the data for a legal claim. (Article 21(1))</li>
1030
+ <li><strong>Objection to direct marketing</strong> — <strong>absolute, and there is nothing to weigh.</strong> If you tell us to stop
1031
+ using your data for direct marketing, including any profiling connected to it, we stop. No balancing
1032
+ test, no grace period, no exceptions. (Article 21(2))</li>
1033
+ </ul>
1034
+ <p>You also have the right to withdraw consent where consent is what we rely on, which has its own section
1035
+ below, and the right to complain to a supervisory authority, which has the section after that.</p>
1036
+ <p>Some of these rights have limits written into the law itself. Erasure does not override an obligation to
1037
+ keep invoices for the statutory accounting period, and portability does not extend to data we inferred or
1038
+ generated rather than received from you. <strong>Where we cannot do all of what you ask, we will tell you which
1039
+ part we cannot do and why</strong>, rather than declining as a whole.</p>
1040
+ <h3 id="how-to-make-a-request" tabindex="-1">How to make a request</h3>
1041
+ <p>Write to privacy@ever.co. Tell us which right you are using and enough about yourself for us to find
1042
+ the right records — the email address on the account is usually enough. You can also write to us by post
1043
+ at the address at the end of this policy.</p>
1044
+ <ul>
1045
+ <li><strong>It is free.</strong> We charge nothing for a request. If a request is manifestly unfounded or excessive,
1046
+ particularly because it repeats one we have already answered, the law lets us charge a reasonable fee
1047
+ based on our administrative cost or refuse it. If we ever do either, we will explain why and tell you
1048
+ how to challenge that decision.</li>
1049
+ <li><strong>We answer within one month</strong> of receiving the request. Where a request is complex, or where you have
1050
+ made several, we may extend that by up to two further months — and if we do, <strong>we will tell you within
1051
+ the first month, and tell you why</strong>.</li>
1052
+ <li><strong>We check who you are</strong> before we hand over personal data, because the alternative is handing your data
1053
+ to someone who claims to be you. We ask for the least that makes us confident, usually a reply from the
1054
+ email address already on the account. We ask for an identity document only where nothing lighter works,
1055
+ and anything you send us for verification is used for that and nothing else, then deleted.</li>
1056
+ </ul>
1057
+ <h3 id="if-your-data-sits-in-a-customers-workspace" tabindex="-1">If your data sits in a customer's workspace</h3>
1058
+ <p><strong>This is the most important paragraph on this page for many of the people who read it.</strong></p>
1059
+ <p>A large part of the personal data in the Service was put there by one of our customers — your employer,
1060
+ the organisation whose workspace you belong to, or the operator of a site built on our platform. Where the
1061
+ Service captures data about how an organisation's own personnel work, that data belongs to that
1062
+ organisation's workspace.</p>
1063
+ <p><strong>For that data the customer is the controller and we are only their processor.</strong> We process it on their
1064
+ documented instructions and for no purpose of our own, so the law directs your request to them, not to us.
1065
+ Practically:</p>
1066
+ <ul>
1067
+ <li><strong>Send your request to that organisation.</strong> They decide it, and they are the ones who have to answer you
1068
+ within the deadline.</li>
1069
+ <li><strong>If you send it to us instead, we will not ignore it.</strong> We will forward it to the relevant customer
1070
+ promptly, tell you that we have done so, and assist them in answering it as our Data Processing Addendum
1071
+ requires.</li>
1072
+ <li><strong>We will not decide the request ourselves, and we will not delete, correct or hand over data from a
1073
+ customer's workspace without their instruction</strong> — unless a law that applies to us requires it. That is
1074
+ not us being unhelpful: acting on a workspace's data without the controller's instruction is precisely
1075
+ what a processor is not allowed to do.</li>
1076
+ </ul>
1077
+ <p>If you are not sure which of the two situations you are in, ask us at privacy@ever.co and we will tell
1078
+ you, and point you to the right organisation if it is not us.</p>
1079
+ <h2 id="withdrawing-your-consent" tabindex="-1">Withdrawing your consent</h2>
1080
+ <p>Where we rely on your consent for something, <strong>you can withdraw it at any time, and withdrawing is as easy
1081
+ as giving it</strong>. You do not have to give a reason, and we do not ask you to justify it.</p>
1082
+ <p>Withdrawing consent stops the processing from that point onwards. <strong>It does not make what we did before
1083
+ unlawful</strong> — processing carried out while your consent was in force stays lawful, and withdrawal does not
1084
+ undo it. What it does mean is that we stop, and that we do not start again unless you tell us to.</p>
1085
+ <h3 id="how-to-withdraw-purpose-by-purpose" tabindex="-1">How to withdraw, purpose by purpose</h3>
1086
+ <ul>
1087
+ <li><strong>Cookies and similar technologies</strong> — open the <strong>Cookie preferences</strong> link in the footer of any page on
1088
+ <a href="https://rec.so">rec.so</a>, turn off the categories you no longer want, and save. The change
1089
+ takes effect immediately. Details are in our <a href="https://rec.so/cookies">Cookie Policy</a>.</li>
1090
+ <li><strong>Marketing emails</strong> — use the unsubscribe link at the bottom of any message we send you, or write to
1091
+ privacy@ever.co and ask us to stop. Either route works, and the unsubscribe link does not require
1092
+ you to sign in or find your password first.</li>
1093
+ <li><strong>Optional features and integrations you switched on</strong> — turn the feature off, or disconnect the
1094
+ connected account, in your settings. If you cannot find the switch, ask us at privacy@ever.co and we
1095
+ will turn it off for you.</li>
1096
+ </ul>
1097
+ <p>If you have consented to something not listed here, write to privacy@ever.co naming it, and we will
1098
+ act on it the same way.</p>
1099
+ <h3 id="what-happens-next" tabindex="-1">What happens next</h3>
1100
+ <p>We stop the processing, and we remove you from the relevant list or turn the relevant feature off. We keep
1101
+ the minimum record needed to show that you consented and that you withdrew, because being able to evidence
1102
+ consent is itself a legal requirement — for how long, see the retention section.</p>
1103
+ <p><strong>We will not quietly move the same processing onto a different legal basis to keep it running.</strong> If some
1104
+ part of what you asked us to stop genuinely rests on another basis as well — an invoice we are required to
1105
+ keep, for example — we will tell you which part and why, rather than leaving you to discover it.</p>
1106
+ <p>Most of what we do is not based on consent at all. It rests on performing our contract with you, on legal
1107
+ obligations, or on legitimate interests. <strong>Withdrawing consent therefore does not close your account or
1108
+ switch off the Service</strong> — it affects only the things you consented to.</p>
1109
+ <h2 id="complaining-to-a-supervisory-authority" tabindex="-1">Complaining to a supervisory authority</h2>
1110
+ <p>If you think we have handled your personal data badly or unlawfully, <strong>you have the right to complain to a
1111
+ data protection supervisory authority</strong>. That right is yours regardless of anything else in this policy.</p>
1112
+ <p>We would like the chance to put it right first. Write to privacy@ever.co, tell us what went wrong, and
1113
+ we will look into it and come back to you. In most cases that is the quickest way to get the outcome you
1114
+ actually want. <strong>You are not required to do this, and it is not a condition of complaining</strong> — you can go
1115
+ straight to an authority, and you can do it at any point, including while we are still dealing with your
1116
+ complaint.</p>
1117
+ <h3 id="our-lead-supervisory-authority" tabindex="-1">Our lead supervisory authority</h3>
1118
+ <p>We are established in Bulgaria, so our lead authority is the
1119
+ <strong>Commission for Personal Data Protection (Комисия за защита на личните данни)</strong> — the CPDP. Its website,
1120
+ including its complaint form and current contact details, is at
1121
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>.</p>
1122
+ <h3 id="you-can-also-complain-closer-to-home" tabindex="-1">You can also complain closer to home</h3>
1123
+ <p>Under Article 77 GDPR you may lodge your complaint with the supervisory authority in the EU or EEA country:</p>
1124
+ <ul>
1125
+ <li>where you live;</li>
1126
+ <li>where you work; or</li>
1127
+ <li>where the thing you are complaining about took place.</li>
1128
+ </ul>
1129
+ <p>You do not have to use ours, and you do not need our agreement to use another one. If you complain to your
1130
+ local authority, it will co-operate with ours through the mechanism the GDPR sets up for exactly this
1131
+ situation, so nothing is lost by choosing whichever is easiest for you.</p>
1132
+ <p>You also have the right to an effective judicial remedy — against a supervisory authority's decision, and
1133
+ against us directly — in the courts of the country where you live or where we are established. Complaining
1134
+ to an authority does not use up that right.</p>
1135
+ <h2 id="automated-decision-making-and-profiling" tabindex="-1">Automated decision-making and profiling</h2>
1136
+ <p><strong>We do not make decisions about you that produce legal effects concerning you, or that similarly
1137
+ significantly affect you, based solely on automated processing.</strong> No algorithm of ours decides whether you
1138
+ are hired, paid, promoted, disciplined, dismissed, given credit, or charged a different price. Where a
1139
+ decision of that kind is made about you by an organisation using the Service, a person at that
1140
+ organisation makes it.</p>
1141
+ <p>We do use automated rules to detect fraud, spam, abuse and attacks against the Service — rate limits,
1142
+ anomaly detection, and similar. Those rules can block a request or temporarily restrict an account. If one
1143
+ of them affects you, write to privacy@ever.co and a person will review it.</p>
1144
+ <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>
1145
+ <p>This is the part worth reading carefully, because it is easy to misunderstand.</p>
1146
+ <p>Some of our products capture activity data on behalf of a customer — an employer, typically — and some of
1147
+ them offer optional AI features on top of it. <strong>Where a customer enables those features, the Service can
1148
+ generate automated assessments of the activity it captures.</strong> The clearest example: classifying whether
1149
+ the content of a captured screen appears to be work-related. Other examples include scoring or summarising
1150
+ captured activity and grouping it into categories.</p>
1151
+ <p>Four things follow, and we would rather state them plainly than let them be discovered later.</p>
1152
+ <ul>
1153
+ <li><strong>The output goes to the customer, not to us.</strong> It is presented to the organisation whose workspace the
1154
+ data belongs to. <strong>That organisation is the controller of it, and we are only its processor.</strong></li>
1155
+ <li><strong>The customer decides what, if anything, to do with it.</strong> We do not act on these assessments, we do not
1156
+ use them for any purpose of our own, and we do not share them with anyone else.</li>
1157
+ <li><strong>These outputs are not decisions, and must not be used as if they were.</strong> An automated assessment is an
1158
+ input to a human judgement. <strong>Our terms require the customer not to treat an output of the Service as an
1159
+ automated decision about a person, and to apply meaningful human review before acting on one.</strong> Whether
1160
+ any particular use is lawful where that customer operates — including the lawful basis for it, the
1161
+ notices it has to give, any impact assessment it has to carry out, and any consultation with employee
1162
+ representatives it has to run — is that customer's responsibility to determine, not ours.</li>
1163
+ <li><strong>They can be wrong.</strong> A classifier reading a screen has no idea what your job is. It can label genuine
1164
+ work as unrelated, and it can miss the opposite. Anyone relying on one of these outputs should treat it
1165
+ as a rough signal, and we say so to our customers as well as to you.</li>
1166
+ </ul>
1167
+ <h3 id="if-an-assessment-about-you-has-been-generated" tabindex="-1">If an assessment about you has been generated</h3>
1168
+ <p>Ask the organisation whose workspace holds the data — normally your employer. You can ask them for human
1169
+ involvement, for an explanation of how the assessment was reached, to express your point of view, and to
1170
+ contest the result. They are the controller, so they are the ones who have to answer.</p>
1171
+ <p>If you send that request to us, we will forward it to them promptly, tell you we have done so, and assist
1172
+ them in answering it. See the routing paragraph in the section on your rights, which explains why we
1173
+ cannot decide it ourselves.</p>
1174
+ <h2 id="children" tabindex="-1">Children</h2>
1175
+ <p><strong>The Service is not directed at children, and we do not knowingly collect personal data from them.</strong> It
1176
+ is a business product, bought by organisations and used by the people who work in them. We do not design
1177
+ it for children, we do not market it to them, and we do not offer accounts to them.</p>
1178
+ <p>Where consent is the basis for an online service offered directly to a child, the GDPR sets the age at
1179
+ which the child can consent alone. <strong>In Bulgaria that age is 14.</strong> Other EU and EEA countries set
1180
+ it anywhere between 13 and 16, and the age in the country where the child lives is the one that applies.
1181
+ Below that age, consent has to come from — or be authorised by — a holder of parental responsibility.
1182
+ Because we do not offer the Service to children, we do not operate a parental consent mechanism, and a
1183
+ child under the applicable age should not create an account or submit personal data to us.</p>
1184
+ <h3 id="if-a-childs-data-has-reached-us" tabindex="-1">If a child's data has reached us</h3>
1185
+ <p>Tell us. Write to privacy@ever.co with enough detail for us to find the record — an email address, an
1186
+ account name, or the page where the data was submitted. You do not need to prove anything first, and you
1187
+ do not need to be the child's parent to report it.</p>
1188
+ <p>We will check, and where we confirm that we hold personal data collected from a child without proper
1189
+ authorisation, <strong>we will delete it without undue delay</strong>, keeping only what a law that applies to us
1190
+ requires us to keep.</p>
1191
+ <p>If the data sits inside one of our customers' workspaces rather than in our own records, the customer is
1192
+ the controller of it. Tell them as well, and tell us — we will forward your report to them and press for
1193
+ it to be dealt with, as the routing paragraph in the section on your rights describes.</p>
1194
+ <h2 id="links-and-content-from-other-sites" tabindex="-1">Links and content from other sites</h2>
1195
+ <p>Our websites and the Service link to services we do not run, and some pages embed content that other
1196
+ people host — videos, maps, code repositories, documentation and similar.</p>
1197
+ <p>Following a link takes you somewhere this policy does not reach. Loading embedded content means the
1198
+ provider hosting it receives data directly from your browser, typically your IP address, your device and
1199
+ browser details, and the page you were on, and it may set its own cookies.</p>
1200
+ <p><strong>We do not control those services, and this policy does not apply to them.</strong> What they collect and what
1201
+ they do with it is governed by their own privacy notice, which is the one to read before you use them.
1202
+ Where embedded content is not strictly necessary to deliver a page, we load it only once you have agreed
1203
+ to the relevant cookie category — see our <a href="https://rec.so/cookies">Cookie Policy</a>.</p>
1204
+ <p>A link is not an endorsement. If a link from our site takes you somewhere that mishandles your data, we
1205
+ would like to know at privacy@ever.co so we can reconsider carrying it.</p>
1206
+ <h2 id="changes-to-this-policy" tabindex="-1">Changes to this policy</h2>
1207
+ <p>This policy changes when the Service changes, when we engage or replace a provider, or when the law moves.
1208
+ We would rather update it than let it drift out of date and quietly stop being true.</p>
1209
+ <p>Every version carries a version number and the date it takes effect, shown at the top of the page. <strong>This
1210
+ is version 1.0.0, in force from 2026-08-02.</strong></p>
1211
+ <h3 id="how-we-tell-you" tabindex="-1">How we tell you</h3>
1212
+ <ul>
1213
+ <li><strong>Minor changes</strong> — clarifying wording, correcting a mistake, adding a provider of a kind already
1214
+ described — are published with a new version number and a new effective date. We do not send a separate
1215
+ notice for these.</li>
1216
+ <li><strong>Material changes</strong> — a new purpose, a new category of personal data, a new category of recipient, a
1217
+ longer retention period, a change to how you exercise your rights, or a change to the legal basis we
1218
+ rely on — are notified <strong>at least 30 days before they take effect</strong>, by email to account holders and by
1219
+ a notice on the site. That gives you time to read them and to act before they apply.</li>
1220
+ <li><strong>Changes that need your consent</strong> are not made by publishing a new version. We ask you, and we treat
1221
+ silence as a no.</li>
1222
+ </ul>
1223
+ <p>This policy is a notice, not a contract. <strong>We do not ask you to accept it</strong>, and continuing to use the
1224
+ Service is not us collecting your agreement to it. Where we genuinely need your agreement to something, we
1225
+ ask for it separately and record it.</p>
1226
+ <h3 id="previous-versions-stay-available" tabindex="-1">Previous versions stay available</h3>
1227
+ <p>We do not overwrite the past. <strong>Every version of this policy that we have published remains available</strong>,
1228
+ with the dates it was in force, from the version history linked at the foot of
1229
+ <a href="https://rec.so/privacy">https://rec.so/privacy</a>. If you want to know what we said about your data on a
1230
+ particular date, that is where to look — and if you cannot find it, ask us at privacy@ever.co and we
1231
+ will send it to you.</p>
1232
+ <h2 id="how-to-contact-us" tabindex="-1">How to contact us</h2>
1233
+ <p>The controller for the personal data described in this policy is <strong>Ever Technologies LTD</strong>, registered in
1234
+ Bulgaria under company number 204599535, with its registered office at
1235
+ Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.</p>
1236
+ <ul>
1237
+ <li><strong>Privacy questions, and any request about your personal data</strong> — privacy@ever.co</li>
1238
+ <li><strong>Data protection correspondence</strong> — dpo@ever.co</li>
1239
+ </ul>
1240
+ <p>Both addresses are monitored by the same people, and either will reach us. By post, write to the registered
1241
+ office above and mark the letter for the attention of the privacy team. We correspond in English.</p>
1242
+ <p><strong>We have not designated a Data Protection Officer under Article 37 GDPR.</strong> The dpo@ever.co address is
1243
+ a contact channel, not a designation, and we will not describe it as one. If that position changes, this
1244
+ policy will say so and will give the designated office's contact details.</p>
1245
+ <p>If your question is about personal data held inside one of our customers' workspaces, that customer is the
1246
+ controller and the request goes to them — see the routing paragraph in the section on your rights. Write to
1247
+ us anyway if you are unsure, and we will tell you who to ask.</p>
1248
+ <p>This document is version 1.0.0 of the Privacy Policy for
1249
+ <a href="https://rec.so">rec.so</a>, in force from 2026-08-02. Earlier versions, with the
1250
+ dates they applied, are at <a href="https://rec.so/privacy">https://rec.so/privacy</a>.</p>