@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,551 @@
1
+ <h2 id="why-this-page-exists" tabindex="-1">Why this page exists</h2>
2
+ <p>When you use Ever Works 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://ever.works/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://ever.works">ever.works</a>, for Ever Works
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://ever.works/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://ever.works/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://ever.works/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-works" tabindex="-1">Annex: Ever Works</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>DNS, reverse proxy, TLS termination and content delivery for ever.works, for the platform, and for every site we provision, which reaches the internet through a Cloudflare tunnel. Also Turnstile, the anti-bot check on registration and onboarding.</td>
123
+ <td>United States, with traffic terminated at the edge location nearest the visitor</td>
124
+ <td>IP address, user agent and device signals, request metadata such as URL, referrer and cookies, anti-bot challenge signals</td>
125
+ </tr>
126
+ <tr>
127
+ <td>PostHog, Inc.</td>
128
+ <td>Product analytics for the platform and the marketing site — page views, interaction capture, feature flags, and session recording with form inputs masked. Signed-in users are identified to it. Our server-side application logs are forwarded to the same account.</td>
129
+ <td>United States (PostHog US Cloud)</td>
130
+ <td>account identifier, email address, name, IP address, page views and interface interactions, masked session recordings, server log lines and error messages</td>
131
+ </tr>
132
+ <tr>
133
+ <td>GitHub, Inc. (Microsoft Corporation)</td>
134
+ <td>Sign-in with GitHub and the platform GitHub App; the repositories that hold a Work's website and its content, which for a platform-managed Work are private repositories in an organisation we own; the container registry that holds the image of the platform and of each provisioned site; and our build pipeline.</td>
135
+ <td>United States</td>
136
+ <td>GitHub account identity and access token, avatar URL, commit author name and email address, repository contents, including whatever a Work's content contains, pull request and issue text</td>
137
+ </tr>
138
+ <tr>
139
+ <td>OpenRouter, Inc.</td>
140
+ <td>The model gateway every agent run and generation pipeline goes through by default, including the automated research that runs when an account is created. It selects an upstream model provider to serve each request.</td>
141
+ <td>United States</td>
142
+ <td>prompts and completions, which routinely contain account identity and user-generated content, name, email address, sign-in provider, avatar URL and social profile URLs at registration, search results about a named person</td>
143
+ </tr>
144
+ <tr>
145
+ <td>Tavily</td>
146
+ <td>The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created — where the search queries are built from the new account holder's name and email domain.</td>
147
+ <td>United States</td>
148
+ <td>search queries, including a person's name and their employer's domain, the addresses of pages retrieved</td>
149
+ </tr>
150
+ <tr>
151
+ <td>Google LLC (Google Analytics 4 and Google Tag Manager)</td>
152
+ <td>Web analytics and tag delivery on the ever.works marketing site. Not used in the signed-in platform.</td>
153
+ <td>United States</td>
154
+ <td>IP address, analytics identifier, page views and events, device, browser and approximate location</td>
155
+ </tr>
156
+ <tr>
157
+ <td>Google LLC (reCAPTCHA)</td>
158
+ <td>Bot protection on the forms on the ever.works marketing site.</td>
159
+ <td>United States</td>
160
+ <td>IP address, browser and interaction signals</td>
161
+ </tr>
162
+ <tr>
163
+ <td>Google LLC (Google Fonts)</td>
164
+ <td>The documentation sites fetch a webfont from Google at the moment a page loads, so a visitor's browser contacts Google directly. The application and the site template do not — they build the font in and serve it themselves.</td>
165
+ <td>United States</td>
166
+ <td>IP address, user agent, the page being read</td>
167
+ </tr>
168
+ <tr>
169
+ <td>Intuit Inc. (Mailchimp)</td>
170
+ <td>Holds the newsletter list for the marketing site, and receives an address when someone subscribes.</td>
171
+ <td>United States</td>
172
+ <td>email address, subscription status and date, IP address</td>
173
+ </tr>
174
+ <tr>
175
+ <td>ActiveCampaign, LLC (Postmark)</td>
176
+ <td>Delivers the message when someone writes to us through the contact form on the marketing site.</td>
177
+ <td>United States</td>
178
+ <td>name, email address, the content of the message</td>
179
+ </tr>
180
+ <tr>
181
+ <td>jsDelivr</td>
182
+ <td>A public content delivery network that serves the WebAssembly file behind the animation on the sign-in and registration pages. The fetch happens before anyone has signed in or made a cookie choice, so it is listed rather than left implied.</td>
183
+ <td>Global anycast network</td>
184
+ <td>IP address, user agent, referring page</td>
185
+ </tr>
186
+ <tr>
187
+ <td>unpkg</td>
188
+ <td>The fallback for the same file, used when the primary content delivery network does not answer.</td>
189
+ <td>Global anycast network</td>
190
+ <td>IP address, user agent, referring page</td>
191
+ </tr>
192
+ </tbody>
193
+ </table>
194
+ <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>
195
+ <table>
196
+ <thead>
197
+ <tr>
198
+ <th>Sub-processor</th>
199
+ <th>Purpose</th>
200
+ <th>Location</th>
201
+ <th>Personal data</th>
202
+ </tr>
203
+ </thead>
204
+ <tbody>
205
+ <tr>
206
+ <td>Functional Software, Inc. (Sentry)</td>
207
+ <td>Error tracking and performance traces, where an account is configured with a Sentry project. On a provisioned site the template can additionally run Sentry in the visitor's browser, including its own session replay, if the Work Owner enables it.</td>
208
+ <td>United States</td>
209
+ <td>IP address, account identifier attached to an error, stack traces and request metadata, which can contain fragments of content, browser session replay on a Work site, where enabled</td>
210
+ </tr>
211
+ <tr>
212
+ <td>Resend, Inc.</td>
213
+ <td>Sends transactional email — verification, password reset, notifications — where it is selected as the mail provider, and outbound agent mail where it is selected as the agent mail provider.</td>
214
+ <td>United States</td>
215
+ <td>recipient name and email address, subject and body of the message</td>
216
+ </tr>
217
+ <tr>
218
+ <td>Stripe, Inc.</td>
219
+ <td>Checkout, subscriptions and invoicing for paid plans and credit packs, where billing is enabled on the account. Separately, a Work Owner can connect their own Stripe account to take payments from their own site's visitors.</td>
220
+ <td>United States</td>
221
+ <td>name and email address, billing address entered at checkout, customer and payment method references, purchase and invoice history, IP address collected by Stripe on its own pages</td>
222
+ </tr>
223
+ <tr>
224
+ <td>Google LLC (Google Identity)</td>
225
+ <td>Sign in with Google, where you choose it — on the platform, or on a Work site where the site owner has enabled it.</td>
226
+ <td>United States</td>
227
+ <td>Google account identifier, email address, name, profile photo URL</td>
228
+ </tr>
229
+ <tr>
230
+ <td>Meta Platforms, Inc.</td>
231
+ <td>Sign in with Facebook, where you choose it and where the site owner has enabled it.</td>
232
+ <td>United States</td>
233
+ <td>Facebook account identifier, email address, name, profile photo URL</td>
234
+ </tr>
235
+ <tr>
236
+ <td>LinkedIn Corporation (Microsoft Corporation)</td>
237
+ <td>Sign in with LinkedIn, where you choose it and where the site owner has enabled it.</td>
238
+ <td>United States</td>
239
+ <td>LinkedIn account identifier, email address, name, profile photo URL</td>
240
+ </tr>
241
+ <tr>
242
+ <td>Composio Inc.</td>
243
+ <td>Brokers an agent's access to third-party tools using accounts you have connected yourself, and receives the events those tools send back.</td>
244
+ <td>United States</td>
245
+ <td>access tokens for the accounts you connect, whatever those accounts return into an agent run</td>
246
+ </tr>
247
+ <tr>
248
+ <td>Novu Inc.</td>
249
+ <td>The in-application notification inbox and a delivery channel for notifications, where it is configured against Novu's hosted service rather than an instance you run.</td>
250
+ <td>United States</td>
251
+ <td>a hashed subscriber identifier, notification content, email address where used as a delivery channel</td>
252
+ </tr>
253
+ <tr>
254
+ <td>Twenty S.A.S.</td>
255
+ <td>Two-way sync of companies and people with a Twenty workspace, where you supply the workspace and an API key. Also available on a provisioned Work site.</td>
256
+ <td>France, unless you point it at a Twenty instance you run</td>
257
+ <td>contact name and email address, company and role, notes and activity records</td>
258
+ </tr>
259
+ <tr>
260
+ <td>Langfuse GmbH</td>
261
+ <td>Prompt versioning and model observability, where keys for it are supplied.</td>
262
+ <td>European Union, unless you point it at a Langfuse instance you run</td>
263
+ <td>prompt and completion text, which can contain account identity and user-generated content</td>
264
+ </tr>
265
+ <tr>
266
+ <td>Jitsu Labs, Inc.</td>
267
+ <td>Forwards activity-log events — who did what, to which Work, and whether it succeeded — to an analytics pipeline, where one is configured. Also available on a provisioned Work site.</td>
268
+ <td>United States, unless you point it at a Jitsu instance you run</td>
269
+ <td>account identifier and Work identifier, action, status and summary of an event, IP address, for the browser-side variant on a Work site</td>
270
+ </tr>
271
+ <tr>
272
+ <td>Trigger.dev Inc.</td>
273
+ <td>Runs background jobs for agent work, where an account is pointed at Trigger.dev's hosted service rather than the instance we run ourselves.</td>
274
+ <td>United States</td>
275
+ <td>job payloads, which can contain identifiers, email addresses and user-generated content</td>
276
+ </tr>
277
+ <tr>
278
+ <td>Vercel Inc.</td>
279
+ <td>An alternative place to deploy a Work site, chosen by the Work Owner and connected with their own account and token. The site template can also run Vercel's analytics and performance measurement if the Work Owner switches them on.</td>
280
+ <td>United States</td>
281
+ <td>deployment metadata, the account token the Work Owner supplies, site visitor IP address and page views, where its analytics are enabled</td>
282
+ </tr>
283
+ <tr>
284
+ <td>ScreenshotOne</td>
285
+ <td>Captures a screenshot of a website so that a directory entry has a thumbnail.</td>
286
+ <td>European Union</td>
287
+ <td>the address of the page to be captured, whatever that page displays</td>
288
+ </tr>
289
+ <tr>
290
+ <td>Algolia SAS</td>
291
+ <td>Search on the documentation sites, where search keys are configured.</td>
292
+ <td>European Union and United States</td>
293
+ <td>search queries, IP address</td>
294
+ </tr>
295
+ <tr>
296
+ <td>OpenAI, L.L.C.</td>
297
+ <td>An upstream model provider. Our default pipelines are routed to an OpenAI model through the gateway above. Where you instead supply your own OpenAI key, OpenAI is your provider under your own agreement with it and not our sub-processor.</td>
298
+ <td>United States</td>
299
+ <td>prompt and completion text, which can contain account identity and user-generated content</td>
300
+ </tr>
301
+ <tr>
302
+ <td>Anthropic, PBC</td>
303
+ <td>A model provider for the Claude-based agent pipelines, engaged where those are enabled or where you supply your own key.</td>
304
+ <td>United States</td>
305
+ <td>prompt and completion text, which can contain account identity and user-generated content</td>
306
+ </tr>
307
+ <tr>
308
+ <td>Google LLC (Gemini)</td>
309
+ <td>A model provider, engaged only where you select it and supply your own key.</td>
310
+ <td>United States</td>
311
+ <td>prompt and completion text</td>
312
+ </tr>
313
+ <tr>
314
+ <td>Amazon Web Services, Inc.</td>
315
+ <td>Object storage for uploads, where you point storage at an S3 bucket of your own instead of ours.</td>
316
+ <td>The region of the bucket you choose</td>
317
+ <td>uploads and attachments</td>
318
+ </tr>
319
+ <tr>
320
+ <td>Plausible Insights OÜ</td>
321
+ <td>Cookieless site analytics on a Work site, where the Work Owner enables it.</td>
322
+ <td>European Union</td>
323
+ <td>page views and referrer, coarse device and country</td>
324
+ </tr>
325
+ <tr>
326
+ <td>Twilio Inc. (Segment)</td>
327
+ <td>Event collection and routing on a Work site, where the Work Owner enables it.</td>
328
+ <td>United States</td>
329
+ <td>IP address, visitor identifier and traits where the visitor is identified, events and page views</td>
330
+ </tr>
331
+ <tr>
332
+ <td>DataFast</td>
333
+ <td>Product and marketing analytics on a Work site, where the Work Owner enables it.</td>
334
+ <td>United States</td>
335
+ <td>IP address, page views and events, campaign attribution</td>
336
+ </tr>
337
+ <tr>
338
+ <td>Google LLC (Google Maps Platform)</td>
339
+ <td>Renders maps and clusters markers for location-based listings on a Work site, where the Work Owner enables it.</td>
340
+ <td>United States</td>
341
+ <td>IP address, the area of the map being viewed and locations searched</td>
342
+ </tr>
343
+ <tr>
344
+ <td>Mapbox, Inc.</td>
345
+ <td>The alternative map renderer for the same purpose on a Work site.</td>
346
+ <td>United States</td>
347
+ <td>IP address, the area of the map being viewed and locations searched</td>
348
+ </tr>
349
+ <tr>
350
+ <td>Lemon Squeezy, LLC</td>
351
+ <td>Takes payments from a Work site's own visitors as merchant of record, where the Work Owner connects it. The Work Owner contracts with it directly.</td>
352
+ <td>United States</td>
353
+ <td>name and email address, billing address and tax location, payment identifiers and purchase history</td>
354
+ </tr>
355
+ <tr>
356
+ <td>Polar Software Inc.</td>
357
+ <td>An alternative payment and subscription provider for a Work site's own visitors.</td>
358
+ <td>United States</td>
359
+ <td>name and email address, billing and tax location, payment identifiers and subscription history</td>
360
+ </tr>
361
+ <tr>
362
+ <td>SolidGate</td>
363
+ <td>A further card payment option for a Work site's own visitors.</td>
364
+ <td>European Union</td>
365
+ <td>cardholder name, email address, billing address, payment identifiers</td>
366
+ </tr>
367
+ </tbody>
368
+ </table>
369
+ <h3 id="tier-3-self-hosted-deployments-only-1" tabindex="-1">Tier 3 — self-hosted deployments only</h3>
370
+ <p>If you run Ever Works on your own infrastructure, you choose these providers and hold the
371
+ credentials. <strong>We are not a processor for anything in a deployment you run</strong>: we do not receive that data,
372
+ we cannot reach it, and we have no relationship with the providers you configure.</p>
373
+ <table>
374
+ <thead>
375
+ <tr>
376
+ <th>Sub-processor</th>
377
+ <th>Purpose</th>
378
+ <th>Location</th>
379
+ <th>Personal data</th>
380
+ </tr>
381
+ </thead>
382
+ <tbody>
383
+ <tr>
384
+ <td>Supabase, Inc.</td>
385
+ <td>An authentication and database adapter that ships in the directory site template and can be used instead of a PostgreSQL server. <strong>No site we host uses it</strong> — every site we provision runs on the PostgreSQL cluster we operate. It is here so that a self-hoster can see the option exists.</td>
386
+ <td>The region you choose when you create the project</td>
387
+ <td>site visitor account records, if you configure it</td>
388
+ </tr>
389
+ <tr>
390
+ <td>Ollama, LM Studio or a vLLM server you run yourself</td>
391
+ <td>Local model runtimes the software can be pointed at instead of a hosted model provider. Listed because it is the one configuration in which no third party sees a prompt at all.</td>
392
+ <td>Your own infrastructure</td>
393
+ <td>nothing leaves your deployment</td>
394
+ </tr>
395
+ </tbody>
396
+ </table>
397
+ <h3 id="sites-we-provision-for-you" tabindex="-1">Sites we provision for you</h3>
398
+ <p>Where we provision and host a directory site for you, <strong>that site's visitors are your data subjects, not
399
+ ours.</strong> You are the controller for what the site collects from them; we are your processor for hosting it.</p>
400
+ <p>The providers above are the ones in the path for the platform. A site you have us provision may bring in
401
+ further providers because <strong>you</strong> configured them — an analytics tool, a form handler, a payment provider,
402
+ a comment system. Those are yours: you choose them, you contract with them, and they belong in the privacy
403
+ notice you publish on that site, not in ours.</p>
404
+ <p>If you are unsure which of your site's providers we engage and which you do, ask at privacy@ever.co
405
+ and we will tell you exactly what the platform touches.</p>
406
+ <h2 id="hosting-and-infrastructure" tabindex="-1">Hosting and infrastructure</h2>
407
+ <p>The tables above are short for a reason, and the reason is worth stating plainly: <strong>we run our own
408
+ infrastructure.</strong> The Service is not a tenancy in a public cloud account. It runs on physical servers we
409
+ own, in facilities we control, <strong>inside the European Union</strong>, on a virtualisation and container platform we
410
+ operate ourselves.</p>
411
+ <p>The database, the object storage that holds your files, the cache and queue layers, the secrets manager and
412
+ the deployment system are all components we run. <strong>None of them is a third party, so none of them appears
413
+ as a sub-processor</strong> — there is nobody else to disclose. What we do with them is described on our
414
+ <a href="https://ever.works/security">Security page</a>.</p>
415
+ <h3 id="where-processing-actually-happens" tabindex="-1">Where processing actually happens</h3>
416
+ <ul>
417
+ <li><strong>Your data at rest, and the applications that process it, sit on our own hardware in the European
418
+ Union.</strong> That is the primary location for accounts, content, files and the databases behind them.</li>
419
+ <li><strong>Requests reach us through a global content delivery and security network.</strong> Traffic is terminated at
420
+ the edge location nearest to whoever is making the request, which can be anywhere in the world, before
421
+ being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the
422
+ transfer mechanism for it is described in our <a href="https://ever.works/privacy">Privacy Policy</a>.</li>
423
+ <li><strong>Off-site backup copies are held with an external object storage provider</strong>, encrypted by us before they
424
+ leave our network. That provider holds ciphertext and no key, and cannot read what it stores.</li>
425
+ <li><strong>Our source code, build pipeline and container images are hosted with a third-party provider.</strong> That is
426
+ how the Service is built and deployed rather than where your data lives day to day, but it is a genuine
427
+ third party and it is disclosed as one.</li>
428
+ </ul>
429
+ <h3 id="where-a-product-does-something-different" tabindex="-1">Where a product does something different</h3>
430
+ <p>A small number of products use a third-party managed database, managed storage or hosted platform for a
431
+ specific function instead of our own infrastructure. <strong>Where that is the case for Ever Works, the
432
+ provider appears in the always-engaged tier above and the product annex says which data goes there.</strong></p>
433
+ <p>We are explicit about this because &quot;self-hosted&quot; is exactly the sort of claim that gets made once and then
434
+ stops being true for one product in the range. If your data for a given feature sits with someone else, the
435
+ table says so.</p>
436
+ <h3 id="the-regions-you-should-design-around" tabindex="-1">The regions you should design around</h3>
437
+ <p>If you are completing a transfer mapping or a data protection impact assessment, the honest summary is:
438
+ <strong>primary processing in the European Union on infrastructure we operate; edge termination worldwide; a
439
+ small number of named providers established outside the European Economic Area, each with its own transfer
440
+ mechanism.</strong> Every one of those providers is in the tables above, and the mechanism for each is in the
441
+ international transfers section of the <a href="https://ever.works/privacy">Privacy Policy</a>.</p>
442
+ <p>If you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which
443
+ modules apply — write to privacy@ever.co and we will send them.</p>
444
+ <h2 id="when-this-list-changes" tabindex="-1">When this list changes</h2>
445
+ <h3 id="the-notice-period" tabindex="-1">The notice period</h3>
446
+ <p><strong>We give at least 30 days' notice before a new or replacement sub-processor starts processing personal
447
+ data for the hosted Service.</strong> The 30 days run from the date the notice is published or sent, whichever
448
+ comes first, and they exist so that your objection right is a real one rather than a formality you learn
449
+ about afterwards.</p>
450
+ <h3 id="how-you-find-out" tabindex="-1">How you find out</h3>
451
+ <ul>
452
+ <li><strong>This page changes first.</strong> It carries the date it took effect and a dated record of what changed, so
453
+ the page itself is the notice.</li>
454
+ <li><strong>By email, if you ask for it.</strong> Write to privacy@ever.co and we will add your address to the
455
+ notification list. We then email you before each change, at the same time the page is updated. <strong>We
456
+ recommend a role address rather than an individual's</strong> — a notice sent to someone who has left your
457
+ organisation has been sent and not received.</li>
458
+ <li><strong>In the product</strong>, for changes that affect a feature you are using, through a notice to workspace
459
+ administrators.</li>
460
+ </ul>
461
+ <h3 id="what-the-notice-tells-you" tabindex="-1">What the notice tells you</h3>
462
+ <p>The provider's legal name, what it will do, where it is established, the categories of personal data it
463
+ will receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,
464
+ and whether it is a new provider or replaces one already on the list. If it replaces one, we say which.</p>
465
+ <h3 id="urgent-replacements" tabindex="-1">Urgent replacements</h3>
466
+ <p>Sometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its
467
+ service, loses the legal basis it relied on, or fails in a way that makes staying with it worse than
468
+ leaving.</p>
469
+ <p><strong>Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with
470
+ the reason we could not wait.</strong> Your right to object is not affected: it simply runs from the notice
471
+ instead of before the change. We do not use this route as a convenience, and a notice sent under it says
472
+ plainly why the normal period was not followed.</p>
473
+ <h3 id="changes-that-do-not-need-notice" tabindex="-1">Changes that do not need notice</h3>
474
+ <p>Removing a provider does not need a notice period — it reduces the number of people handling your data. A
475
+ provider changing its own name, or the group entity that contracts with us changing without a change in
476
+ where or how the processing happens, is recorded here as an administrative update rather than announced as
477
+ a new engagement. <strong>A provider moving its processing to a different country is not administrative, and gets
478
+ the full notice.</strong></p>
479
+ <h3 id="the-record" tabindex="-1">The record</h3>
480
+ <p>We keep the change history for this page so that you can reconstruct who was engaged during a given period.
481
+ That matters if you are updating your own records of processing, refreshing an impact assessment, or
482
+ answering a question about a period in the past. Ask privacy@ever.co if you need the state of the list
483
+ as it stood on a particular date.</p>
484
+ <h2 id="objecting-to-a-sub-processor" tabindex="-1">Objecting to a sub-processor</h2>
485
+ <h3 id="who-can-object" tabindex="-1">Who can object</h3>
486
+ <p>The customer — the organisation or person who contracts with us and acts as controller for the data in the
487
+ workspace. If you are an individual whose data we hold, this is not your route: your rights are in the
488
+ <a href="https://ever.works/privacy">Privacy Policy</a>, and if your data sits in an employer's workspace, your employer
489
+ is the controller and the request goes to them.</p>
490
+ <h3 id="how-to-object" tabindex="-1">How to object</h3>
491
+ <p>Write to <strong>privacy@ever.co</strong> within <strong>30 days</strong> of the notice, and tell us:</p>
492
+ <ul>
493
+ <li>which provider you are objecting to;</li>
494
+ <li><strong>your reasons, on data protection grounds</strong> — a transfer you cannot justify, a conflict with a
495
+ commitment you have given your own users, a regulator's position that applies to you, a documented
496
+ security concern;</li>
497
+ <li>which of your workspaces or environments the objection covers.</li>
498
+ </ul>
499
+ <p><strong>The reasons matter.</strong> This is a right to object on data protection grounds, not a veto over our choice of
500
+ suppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem
501
+ is and we can usually solve it.</p>
502
+ <h3 id="what-we-do-next" tabindex="-1">What we do next</h3>
503
+ <p>We acknowledge your objection within five business days and <strong>respond substantively within 30 days.</strong> In
504
+ between we look for a way to make the objection unnecessary:</p>
505
+ <ul>
506
+ <li><strong>A different provider</strong> for your workspace, where one exists that does the job.</li>
507
+ <li><strong>A different configuration</strong> — narrowing what is sent, changing a region, or turning off the feature
508
+ that needs the provider at all, if you can live without it.</li>
509
+ <li><strong>Excluding your workspace</strong> from the provider, where that is technically possible.</li>
510
+ <li><strong>Additional safeguards or contractual terms</strong> where your concern is about a specific risk rather than
511
+ the provider as a whole.</li>
512
+ </ul>
513
+ <p>Where it is technically possible to hold off, <strong>we will not start using the provider you have objected to
514
+ for your data while the objection is open.</strong> Where it is not possible — because the provider is part of how
515
+ the Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the
516
+ clock run out on you.</p>
517
+ <h3 id="if-we-cannot-resolve-it" tabindex="-1">If we cannot resolve it</h3>
518
+ <p>If we cannot offer you a solution you can accept, <strong>you may terminate the affected subscription by written
519
+ notice, without penalty, and we will refund the fees you have prepaid for the period after termination.</strong>
520
+ That is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.</p>
521
+ <p>Give us notice within 30 days of our final response, and we will keep your data available for export for
522
+ the usual 30-day window described in the <a href="https://ever.works/tos">Terms of Service</a> so that leaving does not
523
+ cost you the data.</p>
524
+ <p>If you are on a free tier there is nothing to refund, and the same route is simply to stop using the
525
+ Service and export your data.</p>
526
+ <h3 id="objecting-to-a-provider-already-on-the-list" tabindex="-1">Objecting to a provider already on the list</h3>
527
+ <p>You do not have to wait for a change. <strong>You can raise a concern about a provider already listed at any
528
+ time</strong>, using the same address and the same process, without the 30-day deadline. The realistic outcome
529
+ differs by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,
530
+ because it is part of how the Service works — and if the answer is going to be no, you will get it as a
531
+ straight no with the reason.</p>
532
+ <h2 id="how-to-reach-us-about-this-list" tabindex="-1">How to reach us about this list</h2>
533
+ <ul>
534
+ <li><strong>Questions about a provider, a request for the safeguards behind a transfer, or a request to join the
535
+ change notification list</strong> — privacy@ever.co.</li>
536
+ <li><strong>An objection to a sub-processor</strong> — privacy@ever.co, as set out above.</li>
537
+ <li><strong>The Data Processing Addendum, a due diligence request, or a security questionnaire</strong> —
538
+ legal@ever.co.</li>
539
+ </ul>
540
+ <p>We are <strong>Ever Technologies LTD</strong>, registered in Bulgaria under company number
541
+ 204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our
542
+ own processing and your processor for the data in your workspace. By post, write to the registered office
543
+ and mark the letter for the attention of the privacy team. We correspond in English.</p>
544
+ <p>You may also complain to a data protection supervisory authority. Ours is the
545
+ Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
546
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
547
+ to the authority for the country where you live or work.</p>
548
+ <p>This document is version 1.0.0 of the sub-processor list for
549
+ <a href="https://ever.works">ever.works</a>, in force from 2026-08-02. It lists the providers engaged
550
+ as at that date. Earlier versions, with the dates they applied, are at
551
+ <a href="https://ever.works/subprocessors">https://ever.works/subprocessors</a>.</p>