@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,439 @@
1
+ <h2 id="why-this-page-exists" tabindex="-1">Why this page exists</h2>
2
+ <p>When you use Ever Rec Cloud to process personal data, we act as your processor and you are the
3
+ controller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that
4
+ you must be told in advance when we intend to add or replace one so that you have a real chance to object.</p>
5
+ <p><strong>This page is that disclosure.</strong> It names every provider we engage to process personal data for the hosted
6
+ Service, says what each one does, where it does it, and what categories of data reach it. Our Data
7
+ Processing Addendum refers to this page, and your general authorisation to the providers listed here is
8
+ given through it.</p>
9
+ <p>It is also written for people who are not our customers — someone whose employer uses the Service, or
10
+ whose data ends up here for some other reason — because &quot;who else can see this&quot; is a fair question and the
11
+ answer should not be available only to the person paying the invoice.</p>
12
+ <h3 id="what-counts-as-a-sub-processor" tabindex="-1">What counts as a sub-processor</h3>
13
+ <p>A <strong>sub-processor</strong> is a third party we engage that processes personal data <strong>on our behalf and on our
14
+ instructions</strong>, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,
15
+ delivers your email, catches our errors or answers your support chat is a sub-processor.</p>
16
+ <p>Three things are not sub-processors, and lumping them in would make this page less accurate rather than
17
+ more complete:</p>
18
+ <ul>
19
+ <li><strong>A provider that never touches personal data.</strong> A design tool or an accounting package we use internally
20
+ is not in the path of your data.</li>
21
+ <li><strong>A company that decides its own purposes.</strong> A payment processor acting on its own regulated obligations
22
+ — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that
23
+ part, not our processor. Those recipients are described in the
24
+ <a href="https://rec.so/privacy">Privacy Policy</a> instead.</li>
25
+ <li><strong>Something we run ourselves.</strong> Our databases, object storage, secrets manager and container platform are
26
+ ours. There is no third party to disclose. The infrastructure section below explains what we operate and
27
+ what genuinely sits in front of it.</li>
28
+ </ul>
29
+ <h3 id="what-this-page-covers" tabindex="-1">What this page covers</h3>
30
+ <p>The <strong>hosted Service we operate</strong> at <a href="https://rec.so">rec.so</a>, for Ever Rec
31
+ specifically. Other products in our range have their own list on their own domain, and the providers differ
32
+ between them — do not read this one as covering a product it does not name.</p>
33
+ <p><strong>It does not cover a deployment you run yourself.</strong> If you install our open-source software on your own
34
+ infrastructure, you choose your own providers with your own credentials and contracts. The third tier below
35
+ exists to make that distinction visible rather than to blur it.</p>
36
+ <p>This page is versioned and dated. The version in force, and the date it took effect, are at the end.</p>
37
+ <h2 id="how-to-read-this-list" tabindex="-1">How to read this list</h2>
38
+ <p>The three tables that follow mean genuinely different things, and reading them as one flat list will give
39
+ you the wrong answer.</p>
40
+ <p>Here is why the split exists. Our products are open-source at their core and built to be connected to other
41
+ things, so <strong>more than 160 distinct third-party providers appear somewhere in our source code across our
42
+ whole range of products.</strong> The overwhelming majority of them are never engaged by us for anything. Some are
43
+ optional integrations that do nothing until somebody switches them on. Many are reachable only in a
44
+ deployment that somebody else runs, with their own account and their own credentials.</p>
45
+ <p>Publishing all of them as &quot;our sub-processors&quot; would be inaccurate, and inaccurate in the worst direction:
46
+ it would tell you your data reaches companies it never touches, while burying the handful that it actually
47
+ does. <strong>A list that is technically exhaustive and practically misleading is not a disclosure.</strong> So there are
48
+ three tiers.</p>
49
+ <h3 id="tier-1-always-engaged" tabindex="-1">Tier 1 — always engaged</h3>
50
+ <p><strong>If you use the hosted Service, these providers are in the path.</strong> There is no setting that removes them,
51
+ because they are part of how the Service is delivered to everyone.</p>
52
+ <p>This is the real Article 28 sub-processor list. It is the tier to use when you are completing a data
53
+ protection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.
54
+ It is short, and it is short because we run our own infrastructure rather than renting someone else's.</p>
55
+ <h3 id="tier-2-engaged-only-if-you-turn-something-on" tabindex="-1">Tier 2 — engaged only if you turn something on</h3>
56
+ <p><strong>A provider in this tier is engaged only when a specific feature, connector or integration is enabled.</strong>
57
+ Enable nothing and it is never involved, and no data of yours ever reaches it.</p>
58
+ <p>Who does the enabling depends on the feature:</p>
59
+ <ul>
60
+ <li><strong>You or your workspace administrator</strong>, by switching on a feature or connecting an account in the
61
+ product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository
62
+ connector.</li>
63
+ <li><strong>An individual user</strong>, by making a personal choice — signing in with a social account, for example, or
64
+ connecting their own third-party tool.</li>
65
+ </ul>
66
+ <p>The table names the feature or setting that activates each provider, so you can check your own
67
+ configuration against it rather than take our word for the current state. If you want to know precisely
68
+ which of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.</p>
69
+ <p><strong>Enabling one of these is a decision to send your data somewhere else</strong>, and it is yours to make. The
70
+ provider's own terms and privacy notice then apply to what it does, alongside our contract with it.</p>
71
+ <h3 id="tier-3-self-hosted-deployments-only" tabindex="-1">Tier 3 — self-hosted deployments only</h3>
72
+ <p>Several of our products are published as open source and can be run on your own infrastructure. When you do
73
+ that, <strong>you</strong> choose the database, the object storage, the email relay, the AI provider and everything else,
74
+ using your own accounts and your own credentials.</p>
75
+ <p>The providers in this tier are listed <strong>only so that you can see what the software can be pointed at</strong>.
76
+ They are not our sub-processors, and they never become ours by appearing here.</p>
77
+ <p><strong>In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,
78
+ and nothing on this page or in our Data Processing Addendum describes it.</strong> You choose those providers, you
79
+ contract with them, you hold the credentials, and the obligations to your own users are yours alone. The
80
+ open-source section of our <a href="https://rec.so/tos">Terms of Service</a> sets out the same split.</p>
81
+ <p>If you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a
82
+ useful starting inventory. It is not your list — only you know which of these you actually configured.</p>
83
+ <h3 id="what-the-columns-mean" tabindex="-1">What the columns mean</h3>
84
+ <ul>
85
+ <li><strong>Sub-processor</strong> — the contracting legal entity, not the brand on the website. Where a provider has a
86
+ separate European establishment that contracts with us, that is the one named.</li>
87
+ <li><strong>Purpose</strong> — what it does for the Service, specifically enough to be checked. Not &quot;business operations&quot;.</li>
88
+ <li><strong>Location</strong> — where the processing takes place, or the provider's place of establishment where
89
+ processing is distributed. Where that is outside the European Economic Area, the transfer mechanism we
90
+ rely on for it is described in the international transfers section of our
91
+ <a href="https://rec.so/privacy">Privacy Policy</a>, and we will give you a copy of the safeguards for a named
92
+ provider on request.</li>
93
+ <li><strong>Personal data</strong> — the categories that reach that provider. Categories, not a promise about volume: a
94
+ provider that receives email addresses receives them for the people who trigger the feature, not for
95
+ everyone.</li>
96
+ </ul>
97
+ <h3 id="what-is-deliberately-not-in-the-tables" tabindex="-1">What is deliberately not in the tables</h3>
98
+ <ul>
99
+ <li><strong>Infrastructure we operate ourselves.</strong> Our databases, object storage, cache, secrets manager and
100
+ container platform are not sub-processors, because there is no third party involved. The next section
101
+ describes what we run and what really does sit in front of it.</li>
102
+ <li><strong>Recipients that are not processors</strong> — payment providers acting under their own regulatory
103
+ obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those
104
+ are covered in the <a href="https://rec.so/privacy">Privacy Policy</a>.</li>
105
+ <li><strong>Sites you choose to visit</strong> by following a link out of the Service. Once you are on someone else's
106
+ site, their notice applies.</li>
107
+ </ul>
108
+ <h2 id="annex-ever-rec" tabindex="-1">Annex: Ever Rec</h2>
109
+ <h3 id="tier-1-always-engaged-1" tabindex="-1">Tier 1 — always engaged</h3>
110
+ <table>
111
+ <thead>
112
+ <tr>
113
+ <th>Sub-processor</th>
114
+ <th>Purpose</th>
115
+ <th>Location</th>
116
+ <th>Personal data</th>
117
+ </tr>
118
+ </thead>
119
+ <tbody>
120
+ <tr>
121
+ <td>Cloudflare, Inc.</td>
122
+ <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>
123
+ <td>United States, with connections terminated at the edge location nearest the visitor worldwide</td>
124
+ <td>IP address, request URL, headers and TLS metadata, cookies in transit</td>
125
+ </tr>
126
+ <tr>
127
+ <td>Google Ireland Limited (Firebase)</td>
128
+ <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>
129
+ <td>European Union and United States</td>
130
+ <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>
131
+ </tr>
132
+ <tr>
133
+ <td>Mux, Inc.</td>
134
+ <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>
135
+ <td>United States</td>
136
+ <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>
137
+ </tr>
138
+ <tr>
139
+ <td>Api Video SAS</td>
140
+ <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>
141
+ <td>France, with delivery from servers worldwide</td>
142
+ <td>screen recording video content, video thumbnails and asset identifiers, viewer IP address on playback</td>
143
+ </tr>
144
+ <tr>
145
+ <td>Functional Software, Inc. d/b/a Sentry</td>
146
+ <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>
147
+ <td>United States</td>
148
+ <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>
149
+ </tr>
150
+ <tr>
151
+ <td>ActiveCampaign, LLC (Postmark)</td>
152
+ <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>
153
+ <td>United States</td>
154
+ <td>recipient email address, sender display name, the free-text message a sharer chooses to include, the link to the shared item</td>
155
+ </tr>
156
+ <tr>
157
+ <td>Twilio Inc. (Twilio Segment)</td>
158
+ <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>
159
+ <td>United States</td>
160
+ <td>account identifier and account traits, product events and their timestamps, IP address</td>
161
+ </tr>
162
+ <tr>
163
+ <td>iubenda s.r.l.</td>
164
+ <td>The consent banner and preference centre on the rec.so website, and the record that proves what you chose and when.</td>
165
+ <td>Italy</td>
166
+ <td>IP address, consent choices and the proof record, timestamp and user agent</td>
167
+ </tr>
168
+ <tr>
169
+ <td>GitHub, Inc.</td>
170
+ <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>
171
+ <td>United States</td>
172
+ <td>no capture content and no account content, contributor and developer identity in commits and build logs</td>
173
+ </tr>
174
+ </tbody>
175
+ </table>
176
+ <h3 id="tier-2-engaged-only-when-a-feature-integration-or-consent-brings-them-in" tabindex="-1">Tier 2 — engaged only when a feature, integration or consent brings them in</h3>
177
+ <table>
178
+ <thead>
179
+ <tr>
180
+ <th>Sub-processor</th>
181
+ <th>Purpose</th>
182
+ <th>Location</th>
183
+ <th>Personal data</th>
184
+ </tr>
185
+ </thead>
186
+ <tbody>
187
+ <tr>
188
+ <td>Twilio Inc.</td>
189
+ <td>Delivery of a capture to a WhatsApp or SMS recipient. Engaged only when a user chooses to send an item that way, and only for that send.</td>
190
+ <td>United States</td>
191
+ <td>recipient telephone number, message body, the link to the shared item</td>
192
+ </tr>
193
+ <tr>
194
+ <td>Rebrandly S.r.l.</td>
195
+ <td>Shortening a share link. Engaged only when a user chooses to shorten one. Rebrandly holds the destination address and sees every click on the short link.</td>
196
+ <td>Italy</td>
197
+ <td>the destination address of the shared item, IP address, user agent and referrer of anyone opening the short link</td>
198
+ </tr>
199
+ <tr>
200
+ <td>Google Ireland Limited (Sign in with Google, Google Drive)</td>
201
+ <td>Signing in with a Google account instead of a password, and saving a capture into your own Google Drive. Both are started by the individual user; neither runs unless you choose it.</td>
202
+ <td>European Union and United States</td>
203
+ <td>Google account identifier, email address, display name and profile picture, OAuth access and refresh tokens held so the connection keeps working, the capture you choose to copy into your own Drive</td>
204
+ </tr>
205
+ <tr>
206
+ <td>Dropbox International Unlimited Company</td>
207
+ <td>Saving a capture into your own Dropbox, when you connect a Dropbox account and choose to send one.</td>
208
+ <td>Ireland and United States</td>
209
+ <td>Dropbox account identifier and OAuth tokens, the capture you choose to copy into your own Dropbox</td>
210
+ </tr>
211
+ <tr>
212
+ <td>Salesforce, Inc. (Slack)</td>
213
+ <td>Posting a capture into a Slack channel, when a user connects a Slack workspace and chooses to send one there.</td>
214
+ <td>United States</td>
215
+ <td>Slack workspace and account identifiers, and OAuth tokens, the capture and the message posted with it</td>
216
+ </tr>
217
+ <tr>
218
+ <td>Atlassian Pty Ltd (Jira, Trello)</td>
219
+ <td>Attaching a capture to a Jira issue or a Trello card, when a user connects that account and chooses to attach one.</td>
220
+ <td>Australia, with hosting in the European Union and United States</td>
221
+ <td>Atlassian or Trello account identifier and OAuth tokens, the capture attached, and the issue or card it is attached to</td>
222
+ </tr>
223
+ <tr>
224
+ <td>Google Ireland Limited (Google Analytics 4, Google Tag Manager)</td>
225
+ <td>Website analytics on rec.so. Loads only after you accept analytics cookies in the consent banner, and never inside the signed-in application.</td>
226
+ <td>European Union and United States</td>
227
+ <td>IP address and a persistent analytics identifier, pages viewed, referrer, device, browser and operating system</td>
228
+ </tr>
229
+ <tr>
230
+ <td>PostHog, Inc.</td>
231
+ <td>Website product analytics on rec.so — which pages are viewed and where people leave. Loads only after you accept analytics cookies.</td>
232
+ <td>United States</td>
233
+ <td>IP address and a persistent visitor identifier, pageview and page-leave events, referrer, device and browser</td>
234
+ </tr>
235
+ <tr>
236
+ <td>Chatwoot Inc.</td>
237
+ <td>The support chat widget on the rec.so website, engaged when you open it and start a conversation.</td>
238
+ <td>United States</td>
239
+ <td>name and email address if you give them, the messages in the conversation, IP address and the page you were on</td>
240
+ </tr>
241
+ <tr>
242
+ <td>The Rocket Science Group LLC (Mailchimp, an Intuit company)</td>
243
+ <td>The rec.so newsletter. Engaged only if you subscribe, and you can unsubscribe from any message we send.</td>
244
+ <td>United States</td>
245
+ <td>email address, subscription status, tags and the date you subscribed, the IP address the subscription came from</td>
246
+ </tr>
247
+ </tbody>
248
+ </table>
249
+ <h3 id="tier-3-self-hosted-deployments-only-1" tabindex="-1">Tier 3 — self-hosted deployments only</h3>
250
+ <p>If you run Ever Rec on your own infrastructure, you choose these providers and hold the
251
+ credentials. <strong>We are not a processor for anything in a deployment you run</strong>: we do not receive that data,
252
+ we cannot reach it, and we have no relationship with the providers you configure.</p>
253
+ <table>
254
+ <thead>
255
+ <tr>
256
+ <th>Sub-processor</th>
257
+ <th>Purpose</th>
258
+ <th>Location</th>
259
+ <th>Personal data</th>
260
+ </tr>
261
+ </thead>
262
+ <tbody>
263
+ <tr>
264
+ <td>The S3-compatible object storage provider you configure in the desktop application</td>
265
+ <td>The Ever Rec desktop application uploads its captures to a bucket YOU nominate. You enter the endpoint, region, bucket name, access key and secret, and they are held in your own operating system's keychain on your own machine. We never receive those captures and we never see those credentials.</td>
266
+ <td>Wherever the provider you chose stores it — you decide, and you contract with it</td>
267
+ <td>screenshots and recordings taken by the desktop application, the metadata the desktop application records alongside them</td>
268
+ </tr>
269
+ <tr>
270
+ <td>Your own Google Firebase project</td>
271
+ <td>A self-hosted deployment of the open-source platform points at a Firebase project you create, with your own credentials, for authentication, metadata and capture storage.</td>
272
+ <td>The regions you select when you create the project</td>
273
+ <td>everything your deployment's users capture, and their account identities</td>
274
+ </tr>
275
+ <tr>
276
+ <td>Your own video streaming account (Mux, Inc. or Api Video SAS)</td>
277
+ <td>A self-hosted deployment transcodes and streams recordings through whichever of the two you configure.</td>
278
+ <td>Determined by the account you open</td>
279
+ <td>the recordings your deployment's users make</td>
280
+ </tr>
281
+ <tr>
282
+ <td>Your own email, messaging, analytics, error-tracking and link-shortening accounts (Postmark, Twilio, Twilio Segment, Sentry, Rebrandly)</td>
283
+ <td>A self-hosted deployment can be configured to send its mail, its WhatsApp messages, its product analytics, its error reports and its short links through accounts you open in your own name. Configure none of them and none of them is involved.</td>
284
+ <td>Determined by the accounts you open</td>
285
+ <td>whatever your deployment sends them, under your configuration and your contracts</td>
286
+ </tr>
287
+ </tbody>
288
+ </table>
289
+ <h3 id="where-recordings-are-stored" tabindex="-1">Where recordings are stored</h3>
290
+ <p>Recordings, screenshots and their thumbnails are held in our object storage on our own infrastructure.
291
+ <strong>No recording is sent to a third party for analysis, transcription or advertising.</strong></p>
292
+ <p>Where you share a recording by link, the recipient's access is served from that same storage. Sharing is
293
+ the act that exposes it — the link is the control, and the privacy annex explains how to withdraw it.</p>
294
+ <h2 id="hosting-and-infrastructure" tabindex="-1">Hosting and infrastructure</h2>
295
+ <p>The tables above are short for a reason, and the reason is worth stating plainly: <strong>we run our own
296
+ infrastructure.</strong> The Service is not a tenancy in a public cloud account. It runs on physical servers we
297
+ own, in facilities we control, <strong>inside the European Union</strong>, on a virtualisation and container platform we
298
+ operate ourselves.</p>
299
+ <p>The database, the object storage that holds your files, the cache and queue layers, the secrets manager and
300
+ the deployment system are all components we run. <strong>None of them is a third party, so none of them appears
301
+ as a sub-processor</strong> — there is nobody else to disclose. What we do with them is described on our
302
+ <a href="https://rec.so/security">Security page</a>.</p>
303
+ <h3 id="where-processing-actually-happens" tabindex="-1">Where processing actually happens</h3>
304
+ <ul>
305
+ <li><strong>Your data at rest, and the applications that process it, sit on our own hardware in the European
306
+ Union.</strong> That is the primary location for accounts, content, files and the databases behind them.</li>
307
+ <li><strong>Requests reach us through a global content delivery and security network.</strong> Traffic is terminated at
308
+ the edge location nearest to whoever is making the request, which can be anywhere in the world, before
309
+ being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the
310
+ transfer mechanism for it is described in our <a href="https://rec.so/privacy">Privacy Policy</a>.</li>
311
+ <li><strong>Off-site backup copies are held with an external object storage provider</strong>, encrypted by us before they
312
+ leave our network. That provider holds ciphertext and no key, and cannot read what it stores.</li>
313
+ <li><strong>Our source code, build pipeline and container images are hosted with a third-party provider.</strong> That is
314
+ how the Service is built and deployed rather than where your data lives day to day, but it is a genuine
315
+ third party and it is disclosed as one.</li>
316
+ </ul>
317
+ <h3 id="where-a-product-does-something-different" tabindex="-1">Where a product does something different</h3>
318
+ <p>A small number of products use a third-party managed database, managed storage or hosted platform for a
319
+ specific function instead of our own infrastructure. <strong>Where that is the case for Ever Rec, the
320
+ provider appears in the always-engaged tier above and the product annex says which data goes there.</strong></p>
321
+ <p>We are explicit about this because &quot;self-hosted&quot; is exactly the sort of claim that gets made once and then
322
+ stops being true for one product in the range. If your data for a given feature sits with someone else, the
323
+ table says so.</p>
324
+ <h3 id="the-regions-you-should-design-around" tabindex="-1">The regions you should design around</h3>
325
+ <p>If you are completing a transfer mapping or a data protection impact assessment, the honest summary is:
326
+ <strong>primary processing in the European Union on infrastructure we operate; edge termination worldwide; a
327
+ small number of named providers established outside the European Economic Area, each with its own transfer
328
+ mechanism.</strong> Every one of those providers is in the tables above, and the mechanism for each is in the
329
+ international transfers section of the <a href="https://rec.so/privacy">Privacy Policy</a>.</p>
330
+ <p>If you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which
331
+ modules apply — write to privacy@ever.co and we will send them.</p>
332
+ <h2 id="when-this-list-changes" tabindex="-1">When this list changes</h2>
333
+ <h3 id="the-notice-period" tabindex="-1">The notice period</h3>
334
+ <p><strong>We give at least 30 days' notice before a new or replacement sub-processor starts processing personal
335
+ data for the hosted Service.</strong> The 30 days run from the date the notice is published or sent, whichever
336
+ comes first, and they exist so that your objection right is a real one rather than a formality you learn
337
+ about afterwards.</p>
338
+ <h3 id="how-you-find-out" tabindex="-1">How you find out</h3>
339
+ <ul>
340
+ <li><strong>This page changes first.</strong> It carries the date it took effect and a dated record of what changed, so
341
+ the page itself is the notice.</li>
342
+ <li><strong>By email, if you ask for it.</strong> Write to privacy@ever.co and we will add your address to the
343
+ notification list. We then email you before each change, at the same time the page is updated. <strong>We
344
+ recommend a role address rather than an individual's</strong> — a notice sent to someone who has left your
345
+ organisation has been sent and not received.</li>
346
+ <li><strong>In the product</strong>, for changes that affect a feature you are using, through a notice to workspace
347
+ administrators.</li>
348
+ </ul>
349
+ <h3 id="what-the-notice-tells-you" tabindex="-1">What the notice tells you</h3>
350
+ <p>The provider's legal name, what it will do, where it is established, the categories of personal data it
351
+ will receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,
352
+ and whether it is a new provider or replaces one already on the list. If it replaces one, we say which.</p>
353
+ <h3 id="urgent-replacements" tabindex="-1">Urgent replacements</h3>
354
+ <p>Sometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its
355
+ service, loses the legal basis it relied on, or fails in a way that makes staying with it worse than
356
+ leaving.</p>
357
+ <p><strong>Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with
358
+ the reason we could not wait.</strong> Your right to object is not affected: it simply runs from the notice
359
+ instead of before the change. We do not use this route as a convenience, and a notice sent under it says
360
+ plainly why the normal period was not followed.</p>
361
+ <h3 id="changes-that-do-not-need-notice" tabindex="-1">Changes that do not need notice</h3>
362
+ <p>Removing a provider does not need a notice period — it reduces the number of people handling your data. A
363
+ provider changing its own name, or the group entity that contracts with us changing without a change in
364
+ where or how the processing happens, is recorded here as an administrative update rather than announced as
365
+ a new engagement. <strong>A provider moving its processing to a different country is not administrative, and gets
366
+ the full notice.</strong></p>
367
+ <h3 id="the-record" tabindex="-1">The record</h3>
368
+ <p>We keep the change history for this page so that you can reconstruct who was engaged during a given period.
369
+ That matters if you are updating your own records of processing, refreshing an impact assessment, or
370
+ answering a question about a period in the past. Ask privacy@ever.co if you need the state of the list
371
+ as it stood on a particular date.</p>
372
+ <h2 id="objecting-to-a-sub-processor" tabindex="-1">Objecting to a sub-processor</h2>
373
+ <h3 id="who-can-object" tabindex="-1">Who can object</h3>
374
+ <p>The customer — the organisation or person who contracts with us and acts as controller for the data in the
375
+ workspace. If you are an individual whose data we hold, this is not your route: your rights are in the
376
+ <a href="https://rec.so/privacy">Privacy Policy</a>, and if your data sits in an employer's workspace, your employer
377
+ is the controller and the request goes to them.</p>
378
+ <h3 id="how-to-object" tabindex="-1">How to object</h3>
379
+ <p>Write to <strong>privacy@ever.co</strong> within <strong>30 days</strong> of the notice, and tell us:</p>
380
+ <ul>
381
+ <li>which provider you are objecting to;</li>
382
+ <li><strong>your reasons, on data protection grounds</strong> — a transfer you cannot justify, a conflict with a
383
+ commitment you have given your own users, a regulator's position that applies to you, a documented
384
+ security concern;</li>
385
+ <li>which of your workspaces or environments the objection covers.</li>
386
+ </ul>
387
+ <p><strong>The reasons matter.</strong> This is a right to object on data protection grounds, not a veto over our choice of
388
+ suppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem
389
+ is and we can usually solve it.</p>
390
+ <h3 id="what-we-do-next" tabindex="-1">What we do next</h3>
391
+ <p>We acknowledge your objection within five business days and <strong>respond substantively within 30 days.</strong> In
392
+ between we look for a way to make the objection unnecessary:</p>
393
+ <ul>
394
+ <li><strong>A different provider</strong> for your workspace, where one exists that does the job.</li>
395
+ <li><strong>A different configuration</strong> — narrowing what is sent, changing a region, or turning off the feature
396
+ that needs the provider at all, if you can live without it.</li>
397
+ <li><strong>Excluding your workspace</strong> from the provider, where that is technically possible.</li>
398
+ <li><strong>Additional safeguards or contractual terms</strong> where your concern is about a specific risk rather than
399
+ the provider as a whole.</li>
400
+ </ul>
401
+ <p>Where it is technically possible to hold off, <strong>we will not start using the provider you have objected to
402
+ for your data while the objection is open.</strong> Where it is not possible — because the provider is part of how
403
+ the Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the
404
+ clock run out on you.</p>
405
+ <h3 id="if-we-cannot-resolve-it" tabindex="-1">If we cannot resolve it</h3>
406
+ <p>If we cannot offer you a solution you can accept, <strong>you may terminate the affected subscription by written
407
+ notice, without penalty, and we will refund the fees you have prepaid for the period after termination.</strong>
408
+ That is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.</p>
409
+ <p>Give us notice within 30 days of our final response, and we will keep your data available for export for
410
+ the usual 30-day window described in the <a href="https://rec.so/tos">Terms of Service</a> so that leaving does not
411
+ cost you the data.</p>
412
+ <p>If you are on a free tier there is nothing to refund, and the same route is simply to stop using the
413
+ Service and export your data.</p>
414
+ <h3 id="objecting-to-a-provider-already-on-the-list" tabindex="-1">Objecting to a provider already on the list</h3>
415
+ <p>You do not have to wait for a change. <strong>You can raise a concern about a provider already listed at any
416
+ time</strong>, using the same address and the same process, without the 30-day deadline. The realistic outcome
417
+ differs by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,
418
+ because it is part of how the Service works — and if the answer is going to be no, you will get it as a
419
+ straight no with the reason.</p>
420
+ <h2 id="how-to-reach-us-about-this-list" tabindex="-1">How to reach us about this list</h2>
421
+ <ul>
422
+ <li><strong>Questions about a provider, a request for the safeguards behind a transfer, or a request to join the
423
+ change notification list</strong> — privacy@ever.co.</li>
424
+ <li><strong>An objection to a sub-processor</strong> — privacy@ever.co, as set out above.</li>
425
+ <li><strong>The Data Processing Addendum, a due diligence request, or a security questionnaire</strong> —
426
+ legal@ever.co.</li>
427
+ </ul>
428
+ <p>We are <strong>Ever Technologies LTD</strong>, registered in Bulgaria under company number
429
+ 204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our
430
+ own processing and your processor for the data in your workspace. By post, write to the registered office
431
+ and mark the letter for the attention of the privacy team. We correspond in English.</p>
432
+ <p>You may also complain to a data protection supervisory authority. Ours is the
433
+ Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
434
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
435
+ to the authority for the country where you live or work.</p>
436
+ <p>This document is version 1.0.0 of the sub-processor list for
437
+ <a href="https://rec.so">rec.so</a>, in force from 2026-08-02. It lists the providers engaged
438
+ as at that date. Earlier versions, with the dates they applied, are at
439
+ <a href="https://rec.so/subprocessors">https://rec.so/subprocessors</a>.</p>