@ever-co/legal 0.1.2 → 0.2.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.
- package/dist/content/aup/ever-async/en.html +778 -0
- package/dist/content/aup/ever-async/en.json +343 -0
- package/dist/content/aup/hust/en.html +9 -0
- package/dist/content/aup/hust/en.json +2 -2
- package/dist/content/cookies/ever-async/en.html +457 -0
- package/dist/content/cookies/ever-async/en.json +185 -0
- package/dist/content/cookies/ever-demand/en.html +5 -2
- package/dist/content/cookies/ever-demand/en.json +2 -2
- package/dist/content/cookies/ever-rec/en.html +5 -2
- package/dist/content/cookies/ever-rec/en.json +2 -2
- package/dist/content/cookies/ever-teams/en.html +5 -2
- package/dist/content/cookies/ever-teams/en.json +2 -2
- package/dist/content/cookies/ever-works/en.html +5 -2
- package/dist/content/cookies/ever-works/en.json +2 -2
- package/dist/content/cookies/gauzy/en.html +5 -2
- package/dist/content/cookies/gauzy/en.json +2 -2
- package/dist/content/cookies/githands/en.html +5 -2
- package/dist/content/cookies/githands/en.json +2 -2
- package/dist/content/cookies/hust/en.html +5 -2
- package/dist/content/cookies/hust/en.json +2 -2
- package/dist/content/dpa/ever-async/en.html +1848 -0
- package/dist/content/dpa/ever-async/en.json +640 -0
- package/dist/content/privacy/ever-async/en.html +1350 -0
- package/dist/content/privacy/ever-async/en.json +364 -0
- package/dist/content/privacy/ever-corporate/en.html +86 -3
- package/dist/content/privacy/ever-corporate/en.json +2 -2
- package/dist/content/privacy/ever-demand/en.html +99 -2
- package/dist/content/privacy/ever-demand/en.json +2 -2
- package/dist/content/privacy/ever-rec/en.html +110 -3
- package/dist/content/privacy/ever-rec/en.json +2 -2
- package/dist/content/privacy/ever-teams/en.html +97 -1
- package/dist/content/privacy/ever-teams/en.json +2 -2
- package/dist/content/privacy/ever-tech/en.html +86 -3
- package/dist/content/privacy/ever-tech/en.json +2 -2
- package/dist/content/privacy/ever-works/en.html +74 -5
- package/dist/content/privacy/ever-works/en.json +2 -2
- package/dist/content/privacy/everiq/en.html +107 -0
- package/dist/content/privacy/everiq/en.json +2 -2
- package/dist/content/privacy/gauzy/en.html +88 -3
- package/dist/content/privacy/gauzy/en.json +2 -2
- package/dist/content/privacy/githands/en.html +83 -2
- package/dist/content/privacy/githands/en.json +2 -2
- package/dist/content/privacy/hust/en.html +186 -37
- package/dist/content/privacy/hust/en.json +3 -3
- package/dist/content/privacy/traduora/en.html +93 -0
- package/dist/content/privacy/traduora/en.json +2 -2
- package/dist/content/refund/ever-rec/en.html +595 -0
- package/dist/content/refund/ever-rec/en.json +336 -0
- package/dist/content/security/ever-async/en.html +853 -0
- package/dist/content/security/ever-async/en.json +417 -0
- package/dist/content/subprocessors/ever-async/en.html +852 -0
- package/dist/content/subprocessors/ever-async/en.json +166 -0
- package/dist/content/subprocessors/ever-corporate/en.html +403 -9
- package/dist/content/subprocessors/ever-corporate/en.json +6 -2
- package/dist/content/subprocessors/ever-demand/en.html +443 -13
- package/dist/content/subprocessors/ever-demand/en.json +6 -2
- package/dist/content/subprocessors/ever-rec/en.html +493 -10
- package/dist/content/subprocessors/ever-rec/en.json +6 -2
- package/dist/content/subprocessors/ever-teams/en.html +435 -8
- package/dist/content/subprocessors/ever-teams/en.json +6 -2
- package/dist/content/subprocessors/ever-tech/en.html +443 -9
- package/dist/content/subprocessors/ever-tech/en.json +6 -2
- package/dist/content/subprocessors/ever-works/en.html +354 -13
- package/dist/content/subprocessors/ever-works/en.json +6 -2
- package/dist/content/subprocessors/everiq/en.html +484 -3
- package/dist/content/subprocessors/everiq/en.json +6 -2
- package/dist/content/subprocessors/gauzy/en.html +353 -20
- package/dist/content/subprocessors/gauzy/en.json +6 -2
- package/dist/content/subprocessors/githands/en.html +451 -13
- package/dist/content/subprocessors/githands/en.json +6 -2
- package/dist/content/subprocessors/hust/en.html +502 -12
- package/dist/content/subprocessors/hust/en.json +14 -2
- package/dist/content/subprocessors/traduora/en.html +461 -4
- package/dist/content/subprocessors/traduora/en.json +6 -2
- package/dist/content/tos/ever-async/en.html +1350 -0
- package/dist/content/tos/ever-async/en.json +687 -0
- package/dist/content/tos/ever-rec/en.html +40 -11
- package/dist/content/tos/ever-rec/en.json +5 -5
- package/dist/content/tos/hust/en.html +32 -8
- package/dist/content/tos/hust/en.json +10 -2
- package/dist/index.json +5338 -2148
- package/package.json +1 -1
|
@@ -0,0 +1,852 @@
|
|
|
1
|
+
<h2 id="why-this-page-exists" tabindex="-1">Why this page exists</h2>
|
|
2
|
+
<p>When you use the Ever Async hosted service 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 "who else can see this" 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://async.ever.co/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://async.ever.co">async.ever.co</a>, for Ever Async
|
|
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 "our sub-processors" 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://async.ever.co/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 "business operations".</li>
|
|
88
|
+
<li><strong>Location</strong> — where the processing takes place, or the provider's place of establishment where
|
|
89
|
+
processing is distributed. Where a provider contracts through a European establishment but processes
|
|
90
|
+
elsewhere, this column says both, because the two are different facts and only naming the first would
|
|
91
|
+
flatter us.</li>
|
|
92
|
+
<li><strong>Transfer mechanism</strong> — for a provider outside the European Economic Area, the Chapter V instrument we
|
|
93
|
+
actually rely on for that specific provider: an adequacy decision, the Standard Contractual Clauses, or
|
|
94
|
+
nothing yet. <strong>Where it reads "To be confirmed", we have not yet evidenced an instrument for that
|
|
95
|
+
provider, and we would rather say so here than print one we cannot produce.</strong> That is a live piece of
|
|
96
|
+
work, not a formula. Providers established inside the EEA need no mechanism and say so. For the third
|
|
97
|
+
tier the transfer is not ours at all — you choose the provider and hold the contract.
|
|
98
|
+
The general rules behind this column are in the international transfers section of our
|
|
99
|
+
<a href="https://async.ever.co/privacy">Privacy Policy</a>, and we will give you a copy of the safeguards for a named
|
|
100
|
+
provider on request.</li>
|
|
101
|
+
<li><strong>Personal data</strong> — the categories that reach that provider. Categories, not a promise about volume: a
|
|
102
|
+
provider that receives email addresses receives them for the people who trigger the feature, not for
|
|
103
|
+
everyone.</li>
|
|
104
|
+
</ul>
|
|
105
|
+
<h3 id="why-this-list-is-deliberately-longer-than-it-needs-to-be" tabindex="-1">Why this list is deliberately longer than it needs to be</h3>
|
|
106
|
+
<p><strong>We list providers we may engage, not only the ones engaged today.</strong> Where we have configured a
|
|
107
|
+
provider, kept one available behind a feature flag, used one recently, or expect to use one for a
|
|
108
|
+
purpose already described here, it appears in the tables below — even if no data has reached it this
|
|
109
|
+
month, and even where we currently run the equivalent ourselves.</p>
|
|
110
|
+
<p>We do this on purpose, and you should read the tables with it in mind:</p>
|
|
111
|
+
<ul>
|
|
112
|
+
<li><strong>A provider appearing here is not proof that your data has reached it.</strong> It means the provider is
|
|
113
|
+
within the scope of what we have told you we may do, at the tier shown. The tier is the part that
|
|
114
|
+
tells you when it is engaged.</li>
|
|
115
|
+
<li><strong>Where we self-host something today</strong> — our analytics, our job runner, our databases, our object
|
|
116
|
+
storage — we say so, and we also name the hosted service we would move to, so that a later change is
|
|
117
|
+
covered by a disclosure you have already seen rather than by a fresh surprise.</li>
|
|
118
|
+
<li><strong>The alternative is worse.</strong> A list that names only today's exact set has to be re-issued, and
|
|
119
|
+
re-consented, every time an engineer changes a setting. A list drawn slightly wide stays true through
|
|
120
|
+
ordinary operational change, which is what makes it dependable.</li>
|
|
121
|
+
</ul>
|
|
122
|
+
<p><strong>What we will not do is use this as cover.</strong> Breadth here does not license a purpose we have not
|
|
123
|
+
described, a category of data we have not listed, or a transfer without a mechanism. If we start
|
|
124
|
+
sending a new <em>kind</em> of personal data, or sending it for a new <em>reason</em>, that is a change to this page
|
|
125
|
+
and to the notice period below — not something the width of a table quietly absorbs.</p>
|
|
126
|
+
<p>If you need to know precisely which providers are live for your workspace today, rather than which ones
|
|
127
|
+
may be, ask us at privacy@ever.co and we will tell you.</p>
|
|
128
|
+
<h3 id="what-is-deliberately-not-in-the-tables" tabindex="-1">What is deliberately not in the tables</h3>
|
|
129
|
+
<ul>
|
|
130
|
+
<li><strong>Infrastructure we operate ourselves.</strong> Our databases, object storage, cache, secrets manager and
|
|
131
|
+
container platform are not sub-processors, because there is no third party involved. The next section
|
|
132
|
+
describes what we run and what really does sit in front of it.</li>
|
|
133
|
+
<li><strong>Recipients that are not processors</strong> — payment providers acting under their own regulatory
|
|
134
|
+
obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those
|
|
135
|
+
are covered in the <a href="https://async.ever.co/privacy">Privacy Policy</a>.</li>
|
|
136
|
+
<li><strong>Sites you choose to visit</strong> by following a link out of the Service. Once you are on someone else's
|
|
137
|
+
site, their notice applies.</li>
|
|
138
|
+
</ul>
|
|
139
|
+
<h2 id="annex-ever-async" tabindex="-1">Annex: Ever Async</h2>
|
|
140
|
+
<h3 id="tier-1-always-engaged-1" tabindex="-1">Tier 1 — always engaged</h3>
|
|
141
|
+
<table>
|
|
142
|
+
<thead>
|
|
143
|
+
<tr>
|
|
144
|
+
<th>Sub-processor</th>
|
|
145
|
+
<th>Purpose</th>
|
|
146
|
+
<th>Location</th>
|
|
147
|
+
<th>Transfer mechanism</th>
|
|
148
|
+
<th>Personal data</th>
|
|
149
|
+
</tr>
|
|
150
|
+
</thead>
|
|
151
|
+
<tbody>
|
|
152
|
+
<tr>
|
|
153
|
+
<td>Cloudflare, Inc.</td>
|
|
154
|
+
<td>Authoritative DNS, reverse proxy and TLS termination for every Ever Async hostname — the marketing site, the dashboard, the API and the webhook ingress. TLS is terminated at the edge and there is no certificate in our own pods, so every request to the Service passes through it and no setting removes it.</td>
|
|
155
|
+
<td>United States, with your connection terminated at the edge location nearest to you</td>
|
|
156
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
157
|
+
<td>IP address, TLS and connection metadata, request URLs and headers, user agent, cookies in transit</td>
|
|
158
|
+
</tr>
|
|
159
|
+
<tr>
|
|
160
|
+
<td>GitHub, Inc. (a Microsoft Corporation company)</td>
|
|
161
|
+
<td>Holds the source, runs the build, and is the container registry the running images are pulled from (ghcr.io/ever-co/everasync and ghcr.io/ever-co/everasync-docs). This is how the Service is built and shipped rather than where message data lives — but it is a genuine third party and it is disclosed as one.</td>
|
|
162
|
+
<td>United States, with global edge delivery for registry and release downloads</td>
|
|
163
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
164
|
+
<td>source, build, release and deployment metadata, developer and automation account identifiers, IP address and user agent of anyone pulling an image or a release</td>
|
|
165
|
+
</tr>
|
|
166
|
+
<tr>
|
|
167
|
+
<td>Cloudflare, Inc. (R2 object storage)</td>
|
|
168
|
+
<td>Third tier of our backup chain, holding the off-site copy of the volumes this product's database sits on. Everything bound for it is encrypted by us before it leaves our network, so the provider holds ciphertext and no key and cannot read what it stores.</td>
|
|
169
|
+
<td>Cloudflare R2 buckets</td>
|
|
170
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
171
|
+
<td>client-side encrypted backup archives only, which no third party can read, the archives derive from every category of data the Service holds</td>
|
|
172
|
+
</tr>
|
|
173
|
+
<tr>
|
|
174
|
+
<td>Cloudflare, Inc. (Turnstile)</td>
|
|
175
|
+
<td>Checks that the person completing registration, onboarding or an anonymous flow is not a bot; on ever-works the API refuses the anonymous flow when no CAPTCHA provider is configured, which is why it is unconditional there.</td>
|
|
176
|
+
<td>United States</td>
|
|
177
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
178
|
+
<td>IP address, user agent and device signals, mouse, touch and timing interaction signals, Turnstile challenge cookie</td>
|
|
179
|
+
</tr>
|
|
180
|
+
<tr>
|
|
181
|
+
<td>Clerk, Inc.</td>
|
|
182
|
+
<td>Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name.</td>
|
|
183
|
+
<td>United States</td>
|
|
184
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
185
|
+
<td>name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored</td>
|
|
186
|
+
</tr>
|
|
187
|
+
<tr>
|
|
188
|
+
<td>Tavily</td>
|
|
189
|
+
<td>The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain.</td>
|
|
190
|
+
<td>United States</td>
|
|
191
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
192
|
+
<td>search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata</td>
|
|
193
|
+
</tr>
|
|
194
|
+
<tr>
|
|
195
|
+
<td>ui-avatars.com</td>
|
|
196
|
+
<td>Generates placeholder avatars where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser.</td>
|
|
197
|
+
<td>UNKNOWN - not published by the provider</td>
|
|
198
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
199
|
+
<td>the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent</td>
|
|
200
|
+
</tr>
|
|
201
|
+
<tr>
|
|
202
|
+
<td>Prospect One sp. z o.o. (jsDelivr)</td>
|
|
203
|
+
<td>Serves the Lottie animation runtime hard-coded into the ever-works login and register pages, so every person who opens the login page hands their IP to it before authenticating.</td>
|
|
204
|
+
<td>Poland (operator); delivery worldwide</td>
|
|
205
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
206
|
+
<td>IP address, user agent, referring page URL</td>
|
|
207
|
+
</tr>
|
|
208
|
+
<tr>
|
|
209
|
+
<td>UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified</td>
|
|
210
|
+
<td>Second permitted origin for the Lottie animation runtime on the ever-works login and register pages.</td>
|
|
211
|
+
<td>United States (unverified)</td>
|
|
212
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
213
|
+
<td>IP address, user agent, referring page URL</td>
|
|
214
|
+
</tr>
|
|
215
|
+
<tr>
|
|
216
|
+
<td>ActiveCampaign, LLC (Postmark)</td>
|
|
217
|
+
<td>Relays every transactional email a product sends - account invitations, verification and sign-in codes, invoices, approvals - and on ever.co also carries contact-form enquiries with PDF attachments, so CVs and the third parties named inside them reach a US processor.</td>
|
|
218
|
+
<td>United States</td>
|
|
219
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
220
|
+
<td>recipient name and email address, full message subject and body - invitations, verification and sign-in codes, invoices, timesheets, HR and approval content, free-text enquiry content and attached CVs from website contact forms, anyone NAMED inside that free text or attachment, delivery, bounce and open metadata</td>
|
|
221
|
+
</tr>
|
|
222
|
+
<tr>
|
|
223
|
+
<td>Resend, Inc.</td>
|
|
224
|
+
<td>Sends transactional mail for the products and domains configured against it, relaying onward through Amazon SES.</td>
|
|
225
|
+
<td>United States</td>
|
|
226
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
227
|
+
<td>recipient name and email address, message subject and body, delivery and bounce metadata</td>
|
|
228
|
+
</tr>
|
|
229
|
+
<tr>
|
|
230
|
+
<td>Google Ireland Limited (Google Workspace)</td>
|
|
231
|
+
<td>Hosts the corporate mailboxes that receive every support, privacy and rights request our own documents tell data subjects to write to, plus the recruitment mailbox that holds candidate CVs.</td>
|
|
232
|
+
<td>Ireland (contracting) / United States and global (Google LLC)</td>
|
|
233
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
234
|
+
<td>all inbound and outbound company email, support, DSAR and privacy correspondence with data subjects, candidate CVs and application correspondence (ever-tech careers), customer and supplier correspondence and attachments</td>
|
|
235
|
+
</tr>
|
|
236
|
+
<tr>
|
|
237
|
+
<td>Functional Software, Inc. d/b/a Sentry</td>
|
|
238
|
+
<td>Captures application errors, performance traces and - on the tenant site template - masked session replays, attaching the reporting user's identity and IP to each event.</td>
|
|
239
|
+
<td>United States</td>
|
|
240
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
241
|
+
<td>IP address, device and OS details, user id and email attached to an error event or set on the scope, URLs, route params, query strings and stack traces, which can carry request fragments and local variables, masked session replay recordings (maskAllText, blockAllMedia), desktop and mobile crash dumps</td>
|
|
242
|
+
</tr>
|
|
243
|
+
<tr>
|
|
244
|
+
<td>Langfuse GmbH</td>
|
|
245
|
+
<td>Stores the full prompts and completions of AI features together with model, latency and cost metadata, so that agent behaviour can be traced and scored.</td>
|
|
246
|
+
<td>Germany</td>
|
|
247
|
+
<td>None needed — established in the EEA</td>
|
|
248
|
+
<td>full prompt and completion text, which can contain user-authored content and personal data, user and session identifiers, model, latency, token and cost metadata, developer scoring outputs</td>
|
|
249
|
+
</tr>
|
|
250
|
+
<tr>
|
|
251
|
+
<td>Google Ireland Limited (reCAPTCHA)</td>
|
|
252
|
+
<td>Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made.</td>
|
|
253
|
+
<td>Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC)</td>
|
|
254
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
255
|
+
<td>IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com</td>
|
|
256
|
+
</tr>
|
|
257
|
+
</tbody>
|
|
258
|
+
</table>
|
|
259
|
+
<p><strong>Three rows is not an omission, and it is worth a paragraph rather than a footnote.</strong> Tier 1 means "no
|
|
260
|
+
setting removes this". In Ever Async the chat channels, the connectors, the model providers and the
|
|
261
|
+
notification provider are each switched on by a customer or an administrator, and in the environments we
|
|
262
|
+
operate today <strong>not one of them is configured</strong>: no chat platform is connected, no connector is set up, no
|
|
263
|
+
model provider has a key and no notification provider is enabled. What is left that a reader genuinely
|
|
264
|
+
cannot avoid is the edge in front of every request, the build-and-registry path the images come from, and
|
|
265
|
+
the encrypted off-site copy of our backups. <strong>Putting a chat platform or a model provider in this tier
|
|
266
|
+
would assert a transfer you cannot escape, which would not be true</strong> — so they are in the tier that says
|
|
267
|
+
when they are engaged.</p>
|
|
268
|
+
<h3 id="tier-2-engaged-only-when-a-feature-connector-or-integration-brings-them-in" tabindex="-1">Tier 2 — engaged only when a feature, connector or integration brings them in</h3>
|
|
269
|
+
<table>
|
|
270
|
+
<thead>
|
|
271
|
+
<tr>
|
|
272
|
+
<th>Sub-processor</th>
|
|
273
|
+
<th>Purpose</th>
|
|
274
|
+
<th>Location</th>
|
|
275
|
+
<th>Transfer mechanism</th>
|
|
276
|
+
<th>Personal data</th>
|
|
277
|
+
</tr>
|
|
278
|
+
</thead>
|
|
279
|
+
<tbody>
|
|
280
|
+
<tr>
|
|
281
|
+
<td>Slack Technologies, LLC (a Salesforce, Inc. company)</td>
|
|
282
|
+
<td>The chat platform Ever Async is built for, engaged when a workspace administrator installs the bot. Slack then delivers message events to our ingress, and we call back to post the public context card, to post the private ephemeral nudge to the author alone, and to open a direct message. Slack is also one of the optional sign-in providers for the dashboard.</td>
|
|
283
|
+
<td>United States, with optional EU data residency on some Slack plans</td>
|
|
284
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
285
|
+
<td>workspace, channel, conversation and message identifiers, message text we receive and the message text we post back, chat user identifiers, display names and the bot flag, sign-in identity where Slack is used to sign in — provider user id, verified email address, name</td>
|
|
286
|
+
</tr>
|
|
287
|
+
<tr>
|
|
288
|
+
<td>Discord, Inc.</td>
|
|
289
|
+
<td>Second chat channel, engaged when the bot is added to a guild. It receives Ed25519-signed interactions, the /async slash command and button presses, and we take full REST egress back to it. It ships without a Gateway client, so ordinary Discord messages are never read or classified — only what a person deliberately sends to the bot reaches us. Also an optional sign-in provider.</td>
|
|
290
|
+
<td>United States. Discord Netherlands B.V. (Amsterdam) is Discord's EEA entity, and we have not yet established which entity would contract with us</td>
|
|
291
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
292
|
+
<td>guild, channel and interaction identifiers, the command or button payload a person sends to the bot, and what we post back, chat user identifiers and display names, sign-in identity where Discord is used to sign in — provider user id, email address, name</td>
|
|
293
|
+
</tr>
|
|
294
|
+
<tr>
|
|
295
|
+
<td>GitHub, Inc. (a Microsoft Corporation company)</td>
|
|
296
|
+
<td>Context connector, separate from the build path in tier 1 and engaged only when an administrator configures it with a token. When a message names a pull request or an issue we query GitHub with that token and read the item back. 🛑 If the token can read a private repository, so can the connector. Also one of the optional sign-in providers.</td>
|
|
297
|
+
<td>United States</td>
|
|
298
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
299
|
+
<td>pull request and issue titles, states and URLs, including from private repositories the token reaches, the names of their authors, assignees and reviewers, the access token the administrator supplied, sign-in identity where GitHub is used to sign in — provider user id, email address, name</td>
|
|
300
|
+
</tr>
|
|
301
|
+
<tr>
|
|
302
|
+
<td>Atlassian Pty Ltd (Jira, Trello)</td>
|
|
303
|
+
<td>Context connector. When a message names a ticket, we query the customer's own Jira site with the site address, account email and API token that customer supplies, and return the issue title and status. Engaged only when the customer configures it.</td>
|
|
304
|
+
<td>Depends on the customer's own Atlassian site region — EU data residency is available and commonly used, and the default is the United States</td>
|
|
305
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
306
|
+
<td>issue keys, titles, states and URLs, reporter and assignee identity, the account email address and API token the customer supplied</td>
|
|
307
|
+
</tr>
|
|
308
|
+
<tr>
|
|
309
|
+
<td>Google Ireland Limited (Sign in with Google)</td>
|
|
310
|
+
<td>Optional browser single sign-on for the dashboard. It returns the person's Google account identifier, verified email address and profile name, and an allowed-domains list can restrict logins to one company. Engaged only where an administrator configures it and a person uses it.</td>
|
|
311
|
+
<td>Ireland for contracting, with processing on global Google infrastructure including the United States</td>
|
|
312
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
313
|
+
<td>email address, name and profile picture, Google account identifier, OAuth tokens</td>
|
|
314
|
+
</tr>
|
|
315
|
+
<tr>
|
|
316
|
+
<td>OpenRouter, Inc.</td>
|
|
317
|
+
<td>Model router for the optional classification and rewrite calls. It receives the full plain-text body of an ambiguous chat message together with the workspace's own charter, and forwards each request to whichever upstream provider the selected model id resolves to. Engaged only where an [llm] provider is configured AND per-conversation sensitivity is set to balanced or high.</td>
|
|
318
|
+
<td>United States, and onward to whichever upstream model provider the selected model routes to</td>
|
|
319
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
320
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter sent with every call, resolved context items — titles, URLs and statuses, generated output</td>
|
|
321
|
+
</tr>
|
|
322
|
+
<tr>
|
|
323
|
+
<td>OpenAI, L.L.C.</td>
|
|
324
|
+
<td>Model provider for the optional classification and rewrite calls, receiving the message text and the charter. Engaged only where [llm.providers.openai] is configured with a key.</td>
|
|
325
|
+
<td>United States</td>
|
|
326
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
327
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter, generated output</td>
|
|
328
|
+
</tr>
|
|
329
|
+
<tr>
|
|
330
|
+
<td>Anthropic, PBC</td>
|
|
331
|
+
<td>Model provider for the optional classification and rewrite calls, receiving the message text and the charter. It is the example primary in the commented [llm] block of our own configuration, so it is the provider most likely to be selected first.</td>
|
|
332
|
+
<td>United States</td>
|
|
333
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
334
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter, generated output</td>
|
|
335
|
+
</tr>
|
|
336
|
+
<tr>
|
|
337
|
+
<td>Google Ireland Limited (Gemini API)</td>
|
|
338
|
+
<td>Model provider for the optional classification and rewrite calls, reached over the Generative Language endpoint and receiving the message text and the charter. Our own documentation warns that the free tier's terms differ from a paid Google Cloud project.</td>
|
|
339
|
+
<td>United States unless the integration is moved to a Vertex AI EU region</td>
|
|
340
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
341
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter, generated output</td>
|
|
342
|
+
</tr>
|
|
343
|
+
<tr>
|
|
344
|
+
<td>X.AI LLC</td>
|
|
345
|
+
<td>Model provider (Grok) for the optional classification and rewrite calls, reached over the OpenAI-compatible chat-completions shape and receiving the message text and the charter.</td>
|
|
346
|
+
<td>United States</td>
|
|
347
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
348
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter, generated output</td>
|
|
349
|
+
</tr>
|
|
350
|
+
<tr>
|
|
351
|
+
<td>Groq, Inc.</td>
|
|
352
|
+
<td>Reachable as an OpenAI-compatible endpoint through the generic compat provider, receiving the message text and the charter. It is the worked example in the shipped configuration because it is fast and cheap for a classifier.</td>
|
|
353
|
+
<td>United States</td>
|
|
354
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
355
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter, generated output</td>
|
|
356
|
+
</tr>
|
|
357
|
+
<tr>
|
|
358
|
+
<td>Together Computer, Inc. (trading as Together AI)</td>
|
|
359
|
+
<td>May be engaged as an OpenAI-compatible endpoint through the generic compat provider, or as an OpenRouter upstream, receiving the message text and the charter. Listed because the configuration permits it, not because it is wired today — there is no Together-specific code or key in the product.</td>
|
|
360
|
+
<td>United States</td>
|
|
361
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
362
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter, generated output</td>
|
|
363
|
+
</tr>
|
|
364
|
+
<tr>
|
|
365
|
+
<td>Mistral AI SAS</td>
|
|
366
|
+
<td>May be engaged as an OpenAI-compatible endpoint through the generic compat provider, or as an OpenRouter upstream, receiving the message text and the charter. It is the only EEA-established model provider on this path, which is worth knowing if a transfer out of the EEA is the thing you are trying to avoid.</td>
|
|
367
|
+
<td>European Union</td>
|
|
368
|
+
<td>None needed — established in the EEA</td>
|
|
369
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter, generated output</td>
|
|
370
|
+
</tr>
|
|
371
|
+
<tr>
|
|
372
|
+
<td>Vercel Inc.</td>
|
|
373
|
+
<td>May be engaged as an AI gateway in front of the generic compat provider, in which case it receives the message text and the charter before forwarding upstream. Listed for completeness of the routing paths the configuration permits; there is no Vercel-specific code or key in the product.</td>
|
|
374
|
+
<td>United States, with edge delivery worldwide</td>
|
|
375
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
376
|
+
<td>the full text of the chat message being classified or rewritten, the workspace charter, generated output</td>
|
|
377
|
+
</tr>
|
|
378
|
+
<tr>
|
|
379
|
+
<td>Noti-Fire Apps Ltd. (Novu)</td>
|
|
380
|
+
<td>Out-of-band delivery of the weekly digest, and of a nudge that could not be delivered in the channel. It receives a subscriber identifier — which is the chat user id — and the notification body, then fans it out to whatever channels the workspace configured in Novu. Engaged only where [notify.novu] is configured, which it is not in any environment we run today.</td>
|
|
381
|
+
<td>Israel for the contracting entity; Novu Cloud publishes both a United States and an EU endpoint and the region we would configure is not yet recorded, so we do not claim one</td>
|
|
382
|
+
<td>Adequacy decision — Israel</td>
|
|
383
|
+
<td>chat user identifier used as the subscriber id, the notification body, including digest contents and nudge text, whatever contact route the workspace configured in its own Novu account</td>
|
|
384
|
+
</tr>
|
|
385
|
+
<tr>
|
|
386
|
+
<td>DigitalOcean, LLC</td>
|
|
387
|
+
<td>Serves desktop installer downloads from the gauzy.co download page, holds media in Spaces where a deployment selects it as the file provider, still carries legacy container images and gated deploy workflows, and for cloc provisions servers on a customer's behalf.</td>
|
|
388
|
+
<td>United States</td>
|
|
389
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
390
|
+
<td>uploaded files, screenshots and captured media held in Spaces, IP address and user agent of anyone downloading an asset or a desktop installer, container images and build metadata (no personal data), for cloc: server handles, sizes and lifecycle state of infrastructure provisioned on a customer's behalf</td>
|
|
391
|
+
</tr>
|
|
392
|
+
<tr>
|
|
393
|
+
<td>Amazon Web Services, Inc.</td>
|
|
394
|
+
<td>S3 is the object-storage backend an operator or tenant can select for uploads and monitoring media; CloudFront serves maintenance.ever.co and security.ever.co on our flagship domain; SES sits underneath our email relay as that relay's own sub-processor.</td>
|
|
395
|
+
<td>United States (Luxembourg for the EEA contracting entity)</td>
|
|
396
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
397
|
+
<td>uploaded files, avatars and document images in S3, employee-monitoring screenshots, webcam stills, audio and screen recordings where S3 is the file provider, static assets served from CloudFront, exposing visitor IP and user agent, outbound email envelope and content where SES is in the path, certificate validation records (no personal data)</td>
|
|
398
|
+
</tr>
|
|
399
|
+
<tr>
|
|
400
|
+
<td>Uptime Robot Service Provider Ltd - UNVERIFIED. The commonly cited registration is Cyprus (Nicosia); confirm from the current Terms or Imprint before publishing any location claim.</td>
|
|
401
|
+
<td>Hosts the public status page at status.<our-domain>, so anyone who opens it hands their IP and user agent to the vendor.</td>
|
|
402
|
+
<td>Cyprus (unverified)</td>
|
|
403
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
404
|
+
<td>IP address and user agent of every visitor to a status page, cookies set by the status page, monitored endpoint URLs and response metadata</td>
|
|
405
|
+
</tr>
|
|
406
|
+
<tr>
|
|
407
|
+
<td>Wasabi Technologies, Inc.</td>
|
|
408
|
+
<td>Holds avatars, task attachments and time-tracker screenshots wherever the platform's or a tenant's file provider is set to Wasabi.</td>
|
|
409
|
+
<td>United States</td>
|
|
410
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
411
|
+
<td>uploaded files and document attachments, avatars, employee time-tracker screenshots and captured monitoring media</td>
|
|
412
|
+
</tr>
|
|
413
|
+
<tr>
|
|
414
|
+
<td>Cloudinary Ltd.</td>
|
|
415
|
+
<td>Stores and transforms images and video where a deployment's or the platform's media provider is set to Cloudinary, and serves them to viewers directly from its own CDN.</td>
|
|
416
|
+
<td>Israel</td>
|
|
417
|
+
<td>Adequacy decision — Israel</td>
|
|
418
|
+
<td>uploaded images and video, screenshots and captured media, IP address and user agent of every viewer fetching an asset</td>
|
|
419
|
+
</tr>
|
|
420
|
+
<tr>
|
|
421
|
+
<td>UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty</td>
|
|
422
|
+
<td>Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser.</td>
|
|
423
|
+
<td>United States (unverified)</td>
|
|
424
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
425
|
+
<td>IP address, user agent, referring page URL</td>
|
|
426
|
+
</tr>
|
|
427
|
+
<tr>
|
|
428
|
+
<td>Twilio Inc. (SendGrid)</td>
|
|
429
|
+
<td>Sends and tracks marketing or transactional email for gauzy.co through dedicated sending, reply and link-tracking subdomains, and stands as an alternative sender for githands.</td>
|
|
430
|
+
<td>United States</td>
|
|
431
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
432
|
+
<td>recipient email address and name, message content, open and click tracking events (links.gauzy.co), recipient IP and user agent via tracking pixels</td>
|
|
433
|
+
</tr>
|
|
434
|
+
<tr>
|
|
435
|
+
<td>The Rocket Science Group LLC d/b/a Mailchimp</td>
|
|
436
|
+
<td>Receives newsletter signups from the marketing sites, where a visitor submits the form, and holds the resulting subscriber list and consent state.</td>
|
|
437
|
+
<td>United States</td>
|
|
438
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
439
|
+
<td>email address, first and last name, company, phone, free-text notes submitted with the signup, signup IP address and timestamp, subscription status, tags and marketing consent state</td>
|
|
440
|
+
</tr>
|
|
441
|
+
<tr>
|
|
442
|
+
<td>Twilio Inc. (Programmable Messaging)</td>
|
|
443
|
+
<td>Sends SMS where a tenant configures Twilio as its SMS gateway using its own account SID and token.</td>
|
|
444
|
+
<td>United States</td>
|
|
445
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
446
|
+
<td>recipient telephone number, message body, which can contain a capture link or workspace content, delivery and status metadata</td>
|
|
447
|
+
</tr>
|
|
448
|
+
<tr>
|
|
449
|
+
<td>PostHog, Inc.</td>
|
|
450
|
+
<td>Records product and website usage events, and where enabled session recordings, against a persistent analytics identifier, on PostHog's US cluster.</td>
|
|
451
|
+
<td>United States</td>
|
|
452
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
453
|
+
<td>IP address (the server-side Node integration uses it to identify a visitor), browser-stored analytics identifier, user and workspace identifiers, pageview, pageleave and feature-usage events, referrer and URL, device, browser, OS and screen size, session recordings where enabled</td>
|
|
454
|
+
</tr>
|
|
455
|
+
<tr>
|
|
456
|
+
<td>Google Ireland Limited (Google Analytics 4 and Google Tag Manager)</td>
|
|
457
|
+
<td>Measures marketing-site and, on some properties, in-application usage through the GA4 tag loaded via Tag Manager, keyed to a persistent client-id cookie.</td>
|
|
458
|
+
<td>Ireland (contracting) / United States (processing)</td>
|
|
459
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
460
|
+
<td>IP address (anonymize_ip is set on some sites, not all), _ga / _gid / _gat cookies (GA client identifier), page URLs, referrer and UTM parameters, device, browser and approximate location, conversion events, tied to a user id on gauzy.co</td>
|
|
461
|
+
</tr>
|
|
462
|
+
<tr>
|
|
463
|
+
<td>Jitsu Labs, Inc.</td>
|
|
464
|
+
<td>Collects product events into an event pipeline where a write key is configured, on Jitsu's US cloud.</td>
|
|
465
|
+
<td>United States</td>
|
|
466
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
467
|
+
<td>IP address, user and workspace identifiers, page and feature events, device and browser characteristics</td>
|
|
468
|
+
</tr>
|
|
469
|
+
<tr>
|
|
470
|
+
<td>Hound Technology, Inc. (d/b/a Honeycomb.io)</td>
|
|
471
|
+
<td>Receives OpenTelemetry traces from the API where Honeycomb is selected as the OTEL provider, including request URLs and database statements that routinely carry identifiers.</td>
|
|
472
|
+
<td>United States</td>
|
|
473
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
474
|
+
<td>trace and span data including request URLs, route parameters and DB statements, service and host identifiers, anything a span attribute carries, which can include user and tenant ids</td>
|
|
475
|
+
</tr>
|
|
476
|
+
<tr>
|
|
477
|
+
<td>SigNoz Inc. (Delaware, USA) for SigNoz Cloud; SigNoz itself is Apache-2.0 and self-hostable.</td>
|
|
478
|
+
<td>Receives OpenTelemetry traces, metrics and logs from the API wherever the OTLP endpoint is configured, including route parameters and SQL text.</td>
|
|
479
|
+
<td>United States</td>
|
|
480
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
481
|
+
<td>distributed traces including HTTP routes, query strings and SQL statements, service and host metadata, metrics and logs, anything attached as a span attribute</td>
|
|
482
|
+
</tr>
|
|
483
|
+
<tr>
|
|
484
|
+
<td>Better Stack, s.r.o.</td>
|
|
485
|
+
<td>Receives shipped application logs where a log token is configured, including the ChatGPT connector service in ever-teams and the cloc platform's observability pipeline.</td>
|
|
486
|
+
<td>Czech Republic</td>
|
|
487
|
+
<td>None needed — established in the EEA</td>
|
|
488
|
+
<td>application log lines, which may embed user ids, request paths and IP addresses, uptime probe results</td>
|
|
489
|
+
</tr>
|
|
490
|
+
<tr>
|
|
491
|
+
<td>Intuition Machines, Inc. (hCaptcha)</td>
|
|
492
|
+
<td>Scores signup and login attempts wherever the CAPTCHA provider is set to hCaptcha.</td>
|
|
493
|
+
<td>United States</td>
|
|
494
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
495
|
+
<td>IP address, user agent and browser/device fingerprint signals, mouse, touch and timing interaction signals, challenge solution and token</td>
|
|
496
|
+
</tr>
|
|
497
|
+
<tr>
|
|
498
|
+
<td>Meta Platforms Ireland Limited (Facebook Login)</td>
|
|
499
|
+
<td>Authenticates a user who chooses to sign in with Facebook, returning their email, name and profile picture.</td>
|
|
500
|
+
<td>Ireland (contracting entity); processing in Ireland (contracting for EEA users) / United States (Meta Platforms, Inc.)</td>
|
|
501
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
502
|
+
<td>email address and name, Facebook user identifier, profile picture URL, OAuth tokens</td>
|
|
503
|
+
</tr>
|
|
504
|
+
<tr>
|
|
505
|
+
<td>LinkedIn Ireland Unlimited Company</td>
|
|
506
|
+
<td>Authenticates a user who chooses to sign in with LinkedIn, returning their email, name and the profile fields in the granted scope.</td>
|
|
507
|
+
<td>Ireland (contracting entity); processing in Ireland (EEA contracting) / United States (processing)</td>
|
|
508
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
509
|
+
<td>email address and name, LinkedIn member identifier, OAuth tokens, profile fields returned within the granted scope</td>
|
|
510
|
+
</tr>
|
|
511
|
+
<tr>
|
|
512
|
+
<td>X Corp. (Twitter)</td>
|
|
513
|
+
<td>Authenticates a user who chooses to sign in with X, where that provider is enabled for the deployment.</td>
|
|
514
|
+
<td>United States</td>
|
|
515
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
516
|
+
<td>handle and public profile, X user identifier, OAuth tokens</td>
|
|
517
|
+
</tr>
|
|
518
|
+
<tr>
|
|
519
|
+
<td>Microsoft Corporation (Microsoft Entra ID)</td>
|
|
520
|
+
<td>Authenticates a user or administrator who chooses a Microsoft work or personal account, reading profile details from Microsoft Graph, where FEATURE_MICROSOFT_LOGIN is enabled.</td>
|
|
521
|
+
<td>United States</td>
|
|
522
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
523
|
+
<td>email address and display name, Microsoft tenant identifier and user object id, OAuth access and refresh tokens, directory profile fields returned by Graph within the granted scope</td>
|
|
524
|
+
</tr>
|
|
525
|
+
<tr>
|
|
526
|
+
<td>Okta, Inc. (Auth0)</td>
|
|
527
|
+
<td>Authenticates an organisation's people where that organisation chooses to route sign-in through its own hosted Auth0 tenant.</td>
|
|
528
|
+
<td>United States</td>
|
|
529
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
530
|
+
<td>email address and profile, OAuth/OIDC tokens, login IP address, device and user agent, authentication and MFA event logs</td>
|
|
531
|
+
</tr>
|
|
532
|
+
<tr>
|
|
533
|
+
<td>Zapier, Inc.</td>
|
|
534
|
+
<td>Forwards workspace records into whatever third-party apps a customer wires into a Zap, so the onward destinations are the customer's choice and outside our contract.</td>
|
|
535
|
+
<td>United States</td>
|
|
536
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
537
|
+
<td>records pushed through a Zap (tasks, timesheets, contacts), OAuth tokens and authorization codes, arbitrary event payloads forwarded to whatever apps the customer wires up</td>
|
|
538
|
+
</tr>
|
|
539
|
+
<tr>
|
|
540
|
+
<td>Activepieces Inc.</td>
|
|
541
|
+
<td>Runs automation flows that read and receive whatever workspace records a customer wires in, on Activepieces' US cloud unless repointed at a self-hosted instance.</td>
|
|
542
|
+
<td>United States / Canada</td>
|
|
543
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
544
|
+
<td>records pushed through a flow, which can be any workspace data, API keys, webhook payloads</td>
|
|
545
|
+
</tr>
|
|
546
|
+
<tr>
|
|
547
|
+
<td>Celonis SE (Make.com)</td>
|
|
548
|
+
<td>Runs automation scenarios that read and receive whatever workspace records the customer wires in, from EU infrastructure.</td>
|
|
549
|
+
<td>Germany / Czech Republic</td>
|
|
550
|
+
<td>None needed — established in the EEA</td>
|
|
551
|
+
<td>records pushed through a scenario, webhook payloads, OAuth tokens</td>
|
|
552
|
+
</tr>
|
|
553
|
+
<tr>
|
|
554
|
+
<td>Plausible Insights OÜ</td>
|
|
555
|
+
<td>Cookieless site analytics on a Work site, where the Work Owner enables it.</td>
|
|
556
|
+
<td>Estonia</td>
|
|
557
|
+
<td>None needed — established in the EEA</td>
|
|
558
|
+
<td>page views and referrer, coarse device and country, derived and not stored as an IP address</td>
|
|
559
|
+
</tr>
|
|
560
|
+
<tr>
|
|
561
|
+
<td>HubSpot, Inc.</td>
|
|
562
|
+
<td>Two-way contact synchronisation, engaged only when a customer connects its own HubSpot account. Data moves in both directions once connected.</td>
|
|
563
|
+
<td>United States (HubSpot, Inc.) / Ireland (HubSpot Ireland Limited, for HubSpot's own EEA customers)</td>
|
|
564
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
565
|
+
<td>contact and company records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection</td>
|
|
566
|
+
</tr>
|
|
567
|
+
<tr>
|
|
568
|
+
<td>Chatwoot Inc.</td>
|
|
569
|
+
<td>Runs the support chat widget that visitors and signed-in users type into, receiving the whole conversation plus the page context.</td>
|
|
570
|
+
<td>United States</td>
|
|
571
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
572
|
+
<td>visitor or user name and email when supplied, full chat message content, IP address, page URL and browser details</td>
|
|
573
|
+
</tr>
|
|
574
|
+
<tr>
|
|
575
|
+
<td>iubenda s.r.l.</td>
|
|
576
|
+
<td>Delivers hosted legal documents to visitors who open the /legal route in the Gauzy application, which still fetches the policy from iubenda in the visitor's browser.</td>
|
|
577
|
+
<td>Italy</td>
|
|
578
|
+
<td>None needed — established in the EEA</td>
|
|
579
|
+
<td>IP address, user agent, consent preferences and the timestamp of the choice</td>
|
|
580
|
+
</tr>
|
|
581
|
+
<tr>
|
|
582
|
+
<td>Algolia SAS</td>
|
|
583
|
+
<td>Answers the search box on the documentation sites, receiving each reader's query and IP where Algolia credentials are configured.</td>
|
|
584
|
+
<td>France (EEA) or United States, depending on the contracting entity and the index region</td>
|
|
585
|
+
<td>To be confirmed — we do not yet evidence a mechanism</td>
|
|
586
|
+
<td>search queries typed by the reader, IP address, user agent, indexed page content</td>
|
|
587
|
+
</tr>
|
|
588
|
+
<tr>
|
|
589
|
+
<td>Google Ireland Limited (Google Fonts)</td>
|
|
590
|
+
<td>Delivers typefaces to the visitor's browser at page load on the properties that hot-link them, disclosing the visitor's IP to Google before any consent choice.</td>
|
|
591
|
+
<td>Ireland (contracting entity); processing in Ireland (contracting) / United States (operating)</td>
|
|
592
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
593
|
+
<td>IP address, user agent, referring page URL</td>
|
|
594
|
+
</tr>
|
|
595
|
+
<tr>
|
|
596
|
+
<td>Google Ireland Limited (Google Maps Platform)</td>
|
|
597
|
+
<td>Renders maps and completes typed addresses for contacts, clients and organisations where the Maps and Places features are enabled with an API key.</td>
|
|
598
|
+
<td>Ireland (contracting entity); processing in Ireland (contracting) / United States (processing)</td>
|
|
599
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
600
|
+
<td>IP address, typed address fragments and place queries, latitude and longitude of contacts, clients and organisations, session tokens for autocomplete billing</td>
|
|
601
|
+
</tr>
|
|
602
|
+
</tbody>
|
|
603
|
+
</table>
|
|
604
|
+
<p>Two entries here read <strong>"To be confirmed"</strong> in the transfer-mechanism column, and one names an entity
|
|
605
|
+
question we have not settled. That is deliberate. <strong>We would rather print the gap than print a mechanism
|
|
606
|
+
we could not produce if you asked for it</strong>, and if you are mapping transfers for a DPIA, treat those rows
|
|
607
|
+
as unresolved rather than as covered.</p>
|
|
608
|
+
<h3 id="tier-3-self-hosted-deployments-only-1" tabindex="-1">Tier 3 — self-hosted deployments only</h3>
|
|
609
|
+
<p>If you run Ever Async on your own infrastructure, you choose these providers and hold the
|
|
610
|
+
credentials. <strong>We are not a processor for anything in a deployment you run</strong>: we do not receive that data,
|
|
611
|
+
we cannot reach it, and we have no relationship with the providers you configure.</p>
|
|
612
|
+
<table>
|
|
613
|
+
<thead>
|
|
614
|
+
<tr>
|
|
615
|
+
<th>Sub-processor</th>
|
|
616
|
+
<th>Purpose</th>
|
|
617
|
+
<th>Location</th>
|
|
618
|
+
<th>Transfer mechanism</th>
|
|
619
|
+
<th>Personal data</th>
|
|
620
|
+
</tr>
|
|
621
|
+
</thead>
|
|
622
|
+
<tbody>
|
|
623
|
+
<tr>
|
|
624
|
+
<td>Ollama, run by whoever runs the deployment</td>
|
|
625
|
+
<td>Local model runtime. Where it is the provider, the message text and the charter never leave the deployment — this is the documented privacy and offline option and the recommended last-resort fallback. Ollama Inc. publishes the software and receives nothing.</td>
|
|
626
|
+
<td>Inside the deployment — localhost or an in-cluster service</td>
|
|
627
|
+
<td>Not our transfer — you choose the provider</td>
|
|
628
|
+
<td>prompts and completions that never leave that deployment</td>
|
|
629
|
+
</tr>
|
|
630
|
+
<tr>
|
|
631
|
+
<td>Any OpenAI-compatible endpoint the operator points the compat provider at</td>
|
|
632
|
+
<td>The generic compat provider takes an arbitrary base URL and an arbitrary key variable name. It will send the message text and the charter to whatever endpoint the operator configures. We cannot name that vendor, we have no contract with it, and the operator chooses it.</td>
|
|
633
|
+
<td>Chosen by whoever runs the deployment</td>
|
|
634
|
+
<td>Not our transfer — you choose the provider</td>
|
|
635
|
+
<td>whatever prompts that deployment sends there</td>
|
|
636
|
+
</tr>
|
|
637
|
+
<tr>
|
|
638
|
+
<td>PostgreSQL, MySQL or SQLite, and whoever operates the server</td>
|
|
639
|
+
<td>The state store in a deployment you run. SQLite is the default and needs no server; the postgres and orm drivers point at a database you operate, and the orm driver adds MySQL as a build feature. Whose hardware that database sits on is your decision, not ours.</td>
|
|
640
|
+
<td>Chosen by whoever runs the deployment</td>
|
|
641
|
+
<td>Not our transfer — you choose the provider</td>
|
|
642
|
+
<td>everything that deployment stores, including any pending nudge text held during its grace window</td>
|
|
643
|
+
</tr>
|
|
644
|
+
<tr>
|
|
645
|
+
<td>Slack, Discord, GitHub, Jira, Ever Gauzy and Google under your own credentials</td>
|
|
646
|
+
<td>In a deployment you run, every channel, connector and identity provider is reached with a token you mint in your own account — SLACK_BOT_TOKEN, DISCORD_BOT_TOKEN, GITHUB_TOKEN, JIRA_API_TOKEN, GAUZY_API_TOKEN and the OAuth client secrets. We never see that traffic and we have no relationship with those providers on your behalf.</td>
|
|
647
|
+
<td>Chosen by whoever runs the deployment</td>
|
|
648
|
+
<td>Not our transfer — you choose the provider</td>
|
|
649
|
+
<td>whatever that deployment sends and receives under those credentials</td>
|
|
650
|
+
</tr>
|
|
651
|
+
<tr>
|
|
652
|
+
<td>Any notification provider you configure, including Novu under your own account</td>
|
|
653
|
+
<td>Out-of-band delivery of digests and undeliverable nudges from a deployment you run, using your own API key. Leave [notify] unset and the software sends nothing out of band.</td>
|
|
654
|
+
<td>Chosen by whoever runs the deployment</td>
|
|
655
|
+
<td>Not our transfer — you choose the provider</td>
|
|
656
|
+
<td>subscriber identifiers and notification bodies from that deployment</td>
|
|
657
|
+
</tr>
|
|
658
|
+
<tr>
|
|
659
|
+
<td>Red Hat, Inc. (Keycloak)</td>
|
|
660
|
+
<td>Authenticates users through a Keycloak realm that the organisation running the deployment operates itself.</td>
|
|
661
|
+
<td>United States (Red Hat, Inc.) / wherever the reader runs the realm</td>
|
|
662
|
+
<td>Not our transfer — you choose the provider</td>
|
|
663
|
+
<td>email address and profile, OIDC tokens</td>
|
|
664
|
+
</tr>
|
|
665
|
+
<tr>
|
|
666
|
+
<td>Mixpanel, Inc.</td>
|
|
667
|
+
<td>Records in-app screens and named events - 'Order Delivered' from the courier application, 'Order Failed' from the merchant tablet and similar - against a device identifier, where the operator configures a Mixpanel token and publishes a build containing it.</td>
|
|
668
|
+
<td>United States</td>
|
|
669
|
+
<td>Not our transfer — you choose the provider</td>
|
|
670
|
+
<td>device identifier, screens viewed and in-app events, IP address, user identifier once the person has signed in, the Mixpanel project token, which is compiled into the distributed binary</td>
|
|
671
|
+
</tr>
|
|
672
|
+
<tr>
|
|
673
|
+
<td>Intercom, Inc.</td>
|
|
674
|
+
<td>Runs the in-application support conversation in the shopping, merchant and courier mobile applications through cordova-plugin-intercom / @ionic-native/intercom, where the operator supplies Intercom credentials.</td>
|
|
675
|
+
<td>United States (Intercom, Inc.) / Ireland (Intercom R&D Unlimited Company)</td>
|
|
676
|
+
<td>Not our transfer — you choose the provider</td>
|
|
677
|
+
<td>user identifier and email address, full support conversation content, device and application context, the operator's Intercom app id and API key</td>
|
|
678
|
+
</tr>
|
|
679
|
+
</tbody>
|
|
680
|
+
</table>
|
|
681
|
+
<p><strong>One caveat on this tier that we would rather state than let you discover.</strong> The licence is Apache-2.0
|
|
682
|
+
and we intend to publish the source, but <strong>the repository is private today</strong>, so the self-hosting route
|
|
683
|
+
these rows describe is not open to the public yet. They are listed now so that the disclosure is already
|
|
684
|
+
in front of you when it opens, rather than arriving as a change later.</p>
|
|
685
|
+
<h3 id="ever-gauzy-is-not-on-this-list-and-here-is-why" tabindex="-1">Ever Gauzy is not on this list, and here is why</h3>
|
|
686
|
+
<p>The Gauzy connector reaches <code>api.gauzy.co</code>, which is <strong>our own service under the same controller</strong>. There
|
|
687
|
+
is no third party in that hop, so there is no sub-processing relationship to disclose and no row to print.</p>
|
|
688
|
+
<p>That is not the same as saying nothing happens. <strong>Ever Gauzy is a separate service with its own terms and
|
|
689
|
+
its own privacy notice</strong>, and once a request crosses into it, those govern what happens there. If you want
|
|
690
|
+
to know what Ever Gauzy does with a task lookup, its notice is the document to read — not this one.</p>
|
|
691
|
+
<h3 id="what-the-model-path-really-looks-like" tabindex="-1">What the model path really looks like</h3>
|
|
692
|
+
<p>The tables above name each model provider individually rather than bundling them, because an Article 28
|
|
693
|
+
list has to be searchable by vendor name and a transfer question has to be answerable per vendor. Two
|
|
694
|
+
things they cannot show in a cell:</p>
|
|
695
|
+
<ul>
|
|
696
|
+
<li><strong>A router forwards onward.</strong> Where the configured provider is a model router, it selects an upstream
|
|
697
|
+
provider per request. The upstream ones we can name are named; the set is not fixed by us.</li>
|
|
698
|
+
<li><strong>The generic compatible-endpoint adapter has no vendor.</strong> It takes an arbitrary base URL and an
|
|
699
|
+
arbitrary key variable name, so it will send to whatever an operator points it at. <strong>We cannot name that
|
|
700
|
+
company, and where an operator configures it, the contract is theirs.</strong> That is why it sits in tier 3
|
|
701
|
+
under a description rather than a name.</li>
|
|
702
|
+
</ul>
|
|
703
|
+
<h3 id="if-you-want-to-know-what-is-live-for-you" tabindex="-1">If you want to know what is live for you</h3>
|
|
704
|
+
<p>The tier is the part that tells you when a provider is engaged, and your own configuration is the part
|
|
705
|
+
that tells you whether it is. Ask us at privacy@ever.co and we will tell you exactly which providers
|
|
706
|
+
are engaged for your workspace today, rather than which ones could be.</p>
|
|
707
|
+
<h2 id="hosting-and-infrastructure" tabindex="-1">Hosting and infrastructure</h2>
|
|
708
|
+
<p>The tables above are short for a reason, and the reason is worth stating plainly: <strong>we run our own
|
|
709
|
+
infrastructure.</strong> The Service is not a tenancy in a public cloud account. It runs on physical servers we
|
|
710
|
+
own, in facilities we control, <strong>inside the European Union</strong>, on a virtualisation and container platform we
|
|
711
|
+
operate ourselves.</p>
|
|
712
|
+
<p>The database, the object storage that holds your files, the cache and queue layers, the secrets manager and
|
|
713
|
+
the deployment system are all components we run. <strong>None of them is a third party, so none of them appears
|
|
714
|
+
as a sub-processor</strong> — there is nobody else to disclose. What we do with them is described on our
|
|
715
|
+
<a href="https://async.ever.co/security">Security page</a>.</p>
|
|
716
|
+
<h3 id="where-processing-actually-happens" tabindex="-1">Where processing actually happens</h3>
|
|
717
|
+
<ul>
|
|
718
|
+
<li><strong>Your data at rest, and the applications that process it, sit on our own hardware in the European
|
|
719
|
+
Union.</strong> That is the primary location for accounts, content, files and the databases behind them.</li>
|
|
720
|
+
<li><strong>Requests reach us through a global content delivery and security network.</strong> Traffic is terminated at
|
|
721
|
+
the edge location nearest to whoever is making the request, which can be anywhere in the world, before
|
|
722
|
+
being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the
|
|
723
|
+
transfer mechanism for it is described in our <a href="https://async.ever.co/privacy">Privacy Policy</a>.</li>
|
|
724
|
+
<li><strong>Off-site backup copies are held with an external object storage provider</strong>, encrypted by us before they
|
|
725
|
+
leave our network. That provider holds ciphertext and no key, and cannot read what it stores.</li>
|
|
726
|
+
<li><strong>Our source code, build pipeline and container images are hosted with a third-party provider.</strong> That is
|
|
727
|
+
how the Service is built and deployed rather than where your data lives day to day, but it is a genuine
|
|
728
|
+
third party and it is disclosed as one.</li>
|
|
729
|
+
</ul>
|
|
730
|
+
<h3 id="where-a-product-does-something-different" tabindex="-1">Where a product does something different</h3>
|
|
731
|
+
<p>A small number of products use a third-party managed database, managed storage or hosted platform for a
|
|
732
|
+
specific function instead of our own infrastructure. <strong>Where that is the case for Ever Async, the
|
|
733
|
+
provider appears in the always-engaged tier above and the product annex says which data goes there.</strong></p>
|
|
734
|
+
<p>We are explicit about this because "self-hosted" is exactly the sort of claim that gets made once and then
|
|
735
|
+
stops being true for one product in the range. If your data for a given feature sits with someone else, the
|
|
736
|
+
table says so.</p>
|
|
737
|
+
<h3 id="the-regions-you-should-design-around" tabindex="-1">The regions you should design around</h3>
|
|
738
|
+
<p>If you are completing a transfer mapping or a data protection impact assessment, the honest summary is:
|
|
739
|
+
<strong>primary processing in the European Union on infrastructure we operate; edge termination worldwide; a
|
|
740
|
+
small number of named providers established outside the European Economic Area, each with its own transfer
|
|
741
|
+
mechanism.</strong> Every one of those providers is in the tables above, and the mechanism for each is in the
|
|
742
|
+
international transfers section of the <a href="https://async.ever.co/privacy">Privacy Policy</a>.</p>
|
|
743
|
+
<p>If you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which
|
|
744
|
+
modules apply — write to privacy@ever.co and we will send them.</p>
|
|
745
|
+
<h2 id="when-this-list-changes" tabindex="-1">When this list changes</h2>
|
|
746
|
+
<h3 id="the-notice-period" tabindex="-1">The notice period</h3>
|
|
747
|
+
<p><strong>We give at least 30 days' notice before a new or replacement sub-processor starts processing personal
|
|
748
|
+
data for the hosted Service.</strong> The 30 days run from the date the notice is published or sent, whichever
|
|
749
|
+
comes first, and they exist so that your objection right is a real one rather than a formality you learn
|
|
750
|
+
about afterwards.</p>
|
|
751
|
+
<h3 id="how-you-find-out" tabindex="-1">How you find out</h3>
|
|
752
|
+
<ul>
|
|
753
|
+
<li><strong>This page changes first.</strong> It carries the date it took effect and a dated record of what changed, so
|
|
754
|
+
the page itself is the notice.</li>
|
|
755
|
+
<li><strong>By email, if you ask for it.</strong> Write to privacy@ever.co and we will add your address to the
|
|
756
|
+
notification list. We then email you before each change, at the same time the page is updated. <strong>We
|
|
757
|
+
recommend a role address rather than an individual's</strong> — a notice sent to someone who has left your
|
|
758
|
+
organisation has been sent and not received.</li>
|
|
759
|
+
<li><strong>In the product</strong>, for changes that affect a feature you are using, through a notice to workspace
|
|
760
|
+
administrators.</li>
|
|
761
|
+
</ul>
|
|
762
|
+
<h3 id="what-the-notice-tells-you" tabindex="-1">What the notice tells you</h3>
|
|
763
|
+
<p>The provider's legal name, what it will do, where it is established, the categories of personal data it
|
|
764
|
+
will receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,
|
|
765
|
+
and whether it is a new provider or replaces one already on the list. If it replaces one, we say which.</p>
|
|
766
|
+
<h3 id="urgent-replacements" tabindex="-1">Urgent replacements</h3>
|
|
767
|
+
<p>Sometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its
|
|
768
|
+
service, loses the legal basis it relied on, or fails in a way that makes staying with it worse than
|
|
769
|
+
leaving.</p>
|
|
770
|
+
<p><strong>Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with
|
|
771
|
+
the reason we could not wait.</strong> Your right to object is not affected: it simply runs from the notice
|
|
772
|
+
instead of before the change. We do not use this route as a convenience, and a notice sent under it says
|
|
773
|
+
plainly why the normal period was not followed.</p>
|
|
774
|
+
<h3 id="changes-that-do-not-need-notice" tabindex="-1">Changes that do not need notice</h3>
|
|
775
|
+
<p>Removing a provider does not need a notice period — it reduces the number of people handling your data. A
|
|
776
|
+
provider changing its own name, or the group entity that contracts with us changing without a change in
|
|
777
|
+
where or how the processing happens, is recorded here as an administrative update rather than announced as
|
|
778
|
+
a new engagement. <strong>A provider moving its processing to a different country is not administrative, and gets
|
|
779
|
+
the full notice.</strong></p>
|
|
780
|
+
<h3 id="the-record" tabindex="-1">The record</h3>
|
|
781
|
+
<p>We keep the change history for this page so that you can reconstruct who was engaged during a given period.
|
|
782
|
+
That matters if you are updating your own records of processing, refreshing an impact assessment, or
|
|
783
|
+
answering a question about a period in the past. Ask privacy@ever.co if you need the state of the list
|
|
784
|
+
as it stood on a particular date.</p>
|
|
785
|
+
<h2 id="objecting-to-a-sub-processor" tabindex="-1">Objecting to a sub-processor</h2>
|
|
786
|
+
<h3 id="who-can-object" tabindex="-1">Who can object</h3>
|
|
787
|
+
<p>The customer — the organisation or person who contracts with us and acts as controller for the data in the
|
|
788
|
+
workspace. If you are an individual whose data we hold, this is not your route: your rights are in the
|
|
789
|
+
<a href="https://async.ever.co/privacy">Privacy Policy</a>, and if your data sits in an employer's workspace, your employer
|
|
790
|
+
is the controller and the request goes to them.</p>
|
|
791
|
+
<h3 id="how-to-object" tabindex="-1">How to object</h3>
|
|
792
|
+
<p>Write to <strong>privacy@ever.co</strong> within <strong>30 days</strong> of the notice, and tell us:</p>
|
|
793
|
+
<ul>
|
|
794
|
+
<li>which provider you are objecting to;</li>
|
|
795
|
+
<li><strong>your reasons, on data protection grounds</strong> — a transfer you cannot justify, a conflict with a
|
|
796
|
+
commitment you have given your own users, a regulator's position that applies to you, a documented
|
|
797
|
+
security concern;</li>
|
|
798
|
+
<li>which of your workspaces or environments the objection covers.</li>
|
|
799
|
+
</ul>
|
|
800
|
+
<p><strong>The reasons matter.</strong> This is a right to object on data protection grounds, not a veto over our choice of
|
|
801
|
+
suppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem
|
|
802
|
+
is and we can usually solve it.</p>
|
|
803
|
+
<h3 id="what-we-do-next" tabindex="-1">What we do next</h3>
|
|
804
|
+
<p>We acknowledge your objection within five business days and <strong>respond substantively within 30 days.</strong> In
|
|
805
|
+
between we look for a way to make the objection unnecessary:</p>
|
|
806
|
+
<ul>
|
|
807
|
+
<li><strong>A different provider</strong> for your workspace, where one exists that does the job.</li>
|
|
808
|
+
<li><strong>A different configuration</strong> — narrowing what is sent, changing a region, or turning off the feature
|
|
809
|
+
that needs the provider at all, if you can live without it.</li>
|
|
810
|
+
<li><strong>Excluding your workspace</strong> from the provider, where that is technically possible.</li>
|
|
811
|
+
<li><strong>Additional safeguards or contractual terms</strong> where your concern is about a specific risk rather than
|
|
812
|
+
the provider as a whole.</li>
|
|
813
|
+
</ul>
|
|
814
|
+
<p>Where it is technically possible to hold off, <strong>we will not start using the provider you have objected to
|
|
815
|
+
for your data while the objection is open.</strong> Where it is not possible — because the provider is part of how
|
|
816
|
+
the Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the
|
|
817
|
+
clock run out on you.</p>
|
|
818
|
+
<h3 id="if-we-cannot-resolve-it" tabindex="-1">If we cannot resolve it</h3>
|
|
819
|
+
<p>If we cannot offer you a solution you can accept, <strong>you may terminate the affected subscription by written
|
|
820
|
+
notice, without penalty, and we will refund the fees you have prepaid for the period after termination.</strong>
|
|
821
|
+
That is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.</p>
|
|
822
|
+
<p>Give us notice within 30 days of our final response, and we will keep your data available for export for
|
|
823
|
+
the usual 30-day window described in the <a href="https://async.ever.co/tos">Terms of Service</a> so that leaving does not
|
|
824
|
+
cost you the data.</p>
|
|
825
|
+
<p>If you are on a free tier there is nothing to refund, and the same route is simply to stop using the
|
|
826
|
+
Service and export your data.</p>
|
|
827
|
+
<h3 id="objecting-to-a-provider-already-on-the-list" tabindex="-1">Objecting to a provider already on the list</h3>
|
|
828
|
+
<p>You do not have to wait for a change. <strong>You can raise a concern about a provider already listed at any
|
|
829
|
+
time</strong>, using the same address and the same process, without the 30-day deadline. The realistic outcome
|
|
830
|
+
differs by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,
|
|
831
|
+
because it is part of how the Service works — and if the answer is going to be no, you will get it as a
|
|
832
|
+
straight no with the reason.</p>
|
|
833
|
+
<h2 id="how-to-reach-us-about-this-list" tabindex="-1">How to reach us about this list</h2>
|
|
834
|
+
<ul>
|
|
835
|
+
<li><strong>Questions about a provider, a request for the safeguards behind a transfer, or a request to join the
|
|
836
|
+
change notification list</strong> — privacy@ever.co.</li>
|
|
837
|
+
<li><strong>An objection to a sub-processor</strong> — privacy@ever.co, as set out above.</li>
|
|
838
|
+
<li><strong>The Data Processing Addendum, a due diligence request, or a security questionnaire</strong> —
|
|
839
|
+
legal@ever.co.</li>
|
|
840
|
+
</ul>
|
|
841
|
+
<p>We are <strong>Ever Technologies LTD</strong>, registered in Bulgaria under company number
|
|
842
|
+
204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our
|
|
843
|
+
own processing and your processor for the data in your workspace. By post, write to the registered office
|
|
844
|
+
and mark the letter for the attention of the privacy team. We correspond in English.</p>
|
|
845
|
+
<p>You may also complain to a data protection supervisory authority. Ours is the
|
|
846
|
+
Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
|
|
847
|
+
<a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
|
|
848
|
+
to the authority for the country where you live or work.</p>
|
|
849
|
+
<p>This document is version 1.0.2 of the sub-processor list for
|
|
850
|
+
<a href="https://async.ever.co">async.ever.co</a>, in force from 2026-08-02. It lists the providers engaged
|
|
851
|
+
as at that date. Earlier versions, with the dates they applied, are at
|
|
852
|
+
<a href="https://async.ever.co/subprocessors">https://async.ever.co/subprocessors</a>.</p>
|