@ever-co/legal 0.5.0 → 0.6.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.json +2 -2
- package/dist/content/aup/ever-corporate/en.json +2 -2
- package/dist/content/aup/ever-demand/en.json +2 -2
- package/dist/content/aup/ever-rec/en.json +2 -2
- package/dist/content/aup/ever-teams/en.json +2 -2
- package/dist/content/aup/ever-works/en.json +2 -2
- package/dist/content/aup/everiq/en.json +2 -2
- package/dist/content/aup/gauzy/en.json +2 -2
- package/dist/content/aup/githands/en.json +2 -2
- package/dist/content/aup/hust/en.json +2 -2
- package/dist/content/aup/traduora/en.json +2 -2
- package/dist/content/cookies/ever-async/en.json +2 -2
- package/dist/content/cookies/ever-corporate/en.json +2 -2
- package/dist/content/cookies/ever-demand/en.json +2 -2
- package/dist/content/cookies/ever-rec/en.json +2 -2
- package/dist/content/cookies/ever-teams/en.json +2 -2
- package/dist/content/cookies/ever-tech/en.html +11 -3
- package/dist/content/cookies/ever-tech/en.json +4 -4
- package/dist/content/cookies/ever-works/en.json +2 -2
- package/dist/content/cookies/everiq/en.json +2 -2
- package/dist/content/cookies/gauzy/en.json +2 -2
- package/dist/content/cookies/githands/en.json +2 -2
- package/dist/content/cookies/hust/en.json +2 -2
- package/dist/content/cookies/traduora/en.json +2 -2
- package/dist/content/dpa/ever-async/en.json +2 -2
- package/dist/content/dpa/ever-demand/en.json +2 -2
- package/dist/content/dpa/ever-rec/en.json +2 -2
- package/dist/content/dpa/ever-teams/en.json +2 -2
- package/dist/content/dpa/ever-tech-services/en.html +1847 -0
- package/dist/content/dpa/ever-tech-services/en.json +624 -0
- package/dist/content/dpa/ever-works/en.json +2 -2
- package/dist/content/dpa/gauzy/en.html +5 -10
- package/dist/content/dpa/gauzy/en.json +3 -3
- package/dist/content/dpa/githands/en.json +2 -2
- package/dist/content/dpa/hust/en.json +2 -2
- package/dist/content/dpia/gauzy/en.json +2 -2
- package/dist/content/privacy/ever-async/en.json +2 -2
- package/dist/content/privacy/ever-corporate/en.json +2 -2
- package/dist/content/privacy/ever-demand/en.json +2 -2
- package/dist/content/privacy/ever-rec/en.json +2 -2
- package/dist/content/privacy/ever-teams/en.json +2 -2
- package/dist/content/privacy/ever-tech/en.html +55 -12
- package/dist/content/privacy/ever-tech/en.json +12 -4
- package/dist/content/privacy/ever-works/en.json +2 -2
- package/dist/content/privacy/everiq/en.json +2 -2
- package/dist/content/privacy/gauzy/en.json +2 -2
- package/dist/content/privacy/githands/en.json +2 -2
- package/dist/content/privacy/hust/en.json +2 -2
- package/dist/content/privacy/traduora/en.json +2 -2
- package/dist/content/refund/ever-corporate/en.json +2 -2
- package/dist/content/refund/ever-demand/en.json +2 -2
- package/dist/content/refund/ever-rec/en.json +2 -2
- package/dist/content/refund/ever-teams/en.json +2 -2
- package/dist/content/refund/ever-tech-services/en.html +270 -0
- package/dist/content/refund/ever-tech-services/en.json +178 -0
- package/dist/content/refund/ever-works/en.json +2 -2
- package/dist/content/refund/gauzy/en.json +2 -2
- package/dist/content/refund/githands/en.json +2 -2
- package/dist/content/refund/hust/en.json +2 -2
- package/dist/content/refund/traduora/en.json +2 -2
- package/dist/content/security/ever-async/en.json +2 -2
- package/dist/content/security/ever-corporate/en.json +2 -2
- package/dist/content/security/ever-demand/en.json +2 -2
- package/dist/content/security/ever-rec/en.json +2 -2
- package/dist/content/security/ever-teams/en.json +2 -2
- package/dist/content/security/ever-tech/en.json +2 -2
- package/dist/content/security/ever-works/en.json +2 -2
- package/dist/content/security/gauzy/en.json +2 -2
- package/dist/content/security/githands/en.json +2 -2
- package/dist/content/security/hust/en.json +2 -2
- package/dist/content/security/traduora/en.json +2 -2
- package/dist/content/subprocessors/ever-async/en.json +2 -2
- package/dist/content/subprocessors/ever-corporate/en.json +2 -2
- package/dist/content/subprocessors/ever-demand/en.json +2 -2
- package/dist/content/subprocessors/ever-rec/en.json +2 -2
- package/dist/content/subprocessors/ever-teams/en.json +2 -2
- package/dist/content/subprocessors/ever-tech/en.html +16 -2
- package/dist/content/subprocessors/ever-tech/en.json +4 -4
- package/dist/content/subprocessors/ever-tech-services/en.html +357 -0
- package/dist/content/subprocessors/ever-tech-services/en.json +158 -0
- package/dist/content/subprocessors/ever-works/en.json +2 -2
- package/dist/content/subprocessors/everiq/en.json +2 -2
- package/dist/content/subprocessors/gauzy/en.json +2 -2
- package/dist/content/subprocessors/githands/en.json +2 -2
- package/dist/content/subprocessors/hust/en.json +2 -2
- package/dist/content/subprocessors/traduora/en.json +2 -2
- package/dist/content/tos/ever-async/en.json +2 -2
- package/dist/content/tos/ever-corporate/en.json +2 -2
- package/dist/content/tos/ever-demand/en.json +2 -2
- package/dist/content/tos/ever-rec/en.json +2 -2
- package/dist/content/tos/ever-teams/en.json +2 -2
- package/dist/content/tos/ever-tech/en.html +46 -11
- package/dist/content/tos/ever-tech/en.json +12 -4
- package/dist/content/tos/ever-tech-services/en.html +937 -0
- package/dist/content/tos/ever-tech-services/en.json +473 -0
- package/dist/content/tos/ever-works/en.json +2 -2
- package/dist/content/tos/everiq/en.json +2 -2
- package/dist/content/tos/gauzy/en.json +2 -2
- package/dist/content/tos/githands/en.json +2 -2
- package/dist/content/tos/hust/en.json +2 -2
- package/dist/content/tos/traduora/en.json +2 -2
- package/dist/index.json +1788 -343
- package/package.json +52 -52
|
@@ -0,0 +1,357 @@
|
|
|
1
|
+
<h2 id="why-this-page-exists" tabindex="-1">Why this page exists</h2>
|
|
2
|
+
<p>When you use Ever Tech's engineering services 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://ever.tech/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.tech">ever.tech</a>, for Ever Tech Engineering Services
|
|
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://ever.tech/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://ever.tech/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://ever.tech/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-tech-engineering-services" tabindex="-1">Annex: Ever Tech Engineering Services</h2>
|
|
140
|
+
<p>This list covers personal data we process <strong>as your processor</strong> in engagements under the Terms for
|
|
141
|
+
Ever Tech's engineering services. Read the tier, not just the name.</p>
|
|
142
|
+
<p><strong>Agent engagements do not run on our own infrastructure.</strong> The general sections describe our hosted
|
|
143
|
+
products, which do. The machines that run our AI agents are provided through the platform listed below, by
|
|
144
|
+
providers it engages; the principal ones are listed here, and the platform publishes its full list. Where the general sections mention a <strong>subscription</strong>, read <em>a
|
|
145
|
+
signed order form</em>.</p>
|
|
146
|
+
<h3 id="tier-1-always-engaged-for-agent-engagements" tabindex="-1">Tier 1 — always engaged for agent engagements</h3>
|
|
147
|
+
<table>
|
|
148
|
+
<thead>
|
|
149
|
+
<tr>
|
|
150
|
+
<th>Sub-processor</th>
|
|
151
|
+
<th>Purpose</th>
|
|
152
|
+
<th>Location</th>
|
|
153
|
+
<th>Transfer mechanism</th>
|
|
154
|
+
<th>Personal data</th>
|
|
155
|
+
</tr>
|
|
156
|
+
</thead>
|
|
157
|
+
<tbody>
|
|
158
|
+
<tr>
|
|
159
|
+
<td>Cloc M operations platform — operated by a separate company outside our group (legal name, address and company number given in your order form)</td>
|
|
160
|
+
<td>Runs our AI agents for your engagement: dedicated machines, connections to your tools, approval gate and gate modes, metering, work diary and audit trail.</td>
|
|
161
|
+
<td>European Union (platform and machines); the operating company is established in the United States</td>
|
|
162
|
+
<td>Standard Contractual Clauses (EU 2021/914) for access from outside the EEA</td>
|
|
163
|
+
<td>all content of the engagement the Agents process, your users' names, work contact details and account handles</td>
|
|
164
|
+
</tr>
|
|
165
|
+
<tr>
|
|
166
|
+
<td>Hetzner Online GmbH (via the platform)</td>
|
|
167
|
+
<td>Machines and storage for agent Instances, where the platform uses Hetzner as the hosting target.</td>
|
|
168
|
+
<td>Germany and Finland</td>
|
|
169
|
+
<td>— (inside the EEA)</td>
|
|
170
|
+
<td>all content processed on an Instance, encrypted exports during the retention period</td>
|
|
171
|
+
</tr>
|
|
172
|
+
<tr>
|
|
173
|
+
<td>Anthropic, PBC (via the platform)</td>
|
|
174
|
+
<td>Model inference for the Agents, under commercial API terms that prohibit training on requests.</td>
|
|
175
|
+
<td>United States</td>
|
|
176
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
177
|
+
<td>the text of inference requests and responses, which may contain personal data from your content</td>
|
|
178
|
+
</tr>
|
|
179
|
+
</tbody>
|
|
180
|
+
</table>
|
|
181
|
+
<h3 id="tier-2-engaged-only-when-you-a-feature-or-an-order-form-brings-them-in" tabindex="-1">Tier 2 — engaged only when you, a feature or an order form brings them in</h3>
|
|
182
|
+
<table>
|
|
183
|
+
<thead>
|
|
184
|
+
<tr>
|
|
185
|
+
<th>Sub-processor</th>
|
|
186
|
+
<th>Purpose</th>
|
|
187
|
+
<th>Location</th>
|
|
188
|
+
<th>Transfer mechanism</th>
|
|
189
|
+
<th>Personal data</th>
|
|
190
|
+
</tr>
|
|
191
|
+
</thead>
|
|
192
|
+
<tbody>
|
|
193
|
+
<tr>
|
|
194
|
+
<td>OpenAI Ireland Ltd (via the platform)</td>
|
|
195
|
+
<td>Fallback model inference. You can exclude it in your order form.</td>
|
|
196
|
+
<td>United States (via Ireland)</td>
|
|
197
|
+
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
198
|
+
<td>the text of inference requests and responses</td>
|
|
199
|
+
</tr>
|
|
200
|
+
</tbody>
|
|
201
|
+
</table>
|
|
202
|
+
<h3 id="tier-3-deployments-you-run-yourself" tabindex="-1">Tier 3 — deployments you run yourself</h3>
|
|
203
|
+
<p><em>None in this category.</em></p>
|
|
204
|
+
<h3 id="not-on-this-list-and-why" tabindex="-1">Not on this list, and why</h3>
|
|
205
|
+
<ul>
|
|
206
|
+
<li><strong>Human engineering without agents</strong> uses no third-party processor of ours: our engineers work in your own
|
|
207
|
+
tools, under your own contracts with those tools' providers.</li>
|
|
208
|
+
<li><strong>Our time-tracking and project systems</strong> are self-hosted on our own infrastructure in the European Union.</li>
|
|
209
|
+
<li><strong>Upwork</strong> is a separate controller for engagements contracted there, and <strong>the Cloc Now marketplace</strong> is a
|
|
210
|
+
separate controller for purchases made there. Neither is our processor.</li>
|
|
211
|
+
</ul>
|
|
212
|
+
<h2 id="hosting-and-infrastructure" tabindex="-1">Hosting and infrastructure</h2>
|
|
213
|
+
<p>The tables above are short for a reason, and the reason is worth stating plainly: <strong>we run our own
|
|
214
|
+
infrastructure.</strong> The Service is not a tenancy in a public cloud account. It runs on physical servers we
|
|
215
|
+
own, in facilities we control, <strong>inside the European Union</strong>, on a virtualisation and container platform we
|
|
216
|
+
operate ourselves.</p>
|
|
217
|
+
<p>The database, the object storage that holds your files, the cache and queue layers, the secrets manager and
|
|
218
|
+
the deployment system are all components we run. <strong>None of them is a third party, so none of them appears
|
|
219
|
+
as a sub-processor</strong> — there is nobody else to disclose. What we do with them is described on our
|
|
220
|
+
<a href="https://ever.tech/security">Security page</a>.</p>
|
|
221
|
+
<h3 id="where-processing-actually-happens" tabindex="-1">Where processing actually happens</h3>
|
|
222
|
+
<ul>
|
|
223
|
+
<li><strong>Your data at rest, and the applications that process it, sit on our own hardware in the European
|
|
224
|
+
Union.</strong> That is the primary location for accounts, content, files and the databases behind them.</li>
|
|
225
|
+
<li><strong>Requests reach us through a global content delivery and security network.</strong> Traffic is terminated at
|
|
226
|
+
the edge location nearest to whoever is making the request, which can be anywhere in the world, before
|
|
227
|
+
being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the
|
|
228
|
+
transfer mechanism for it is described in our <a href="https://ever.tech/privacy">Privacy Policy</a>.</li>
|
|
229
|
+
<li><strong>Off-site backup copies are held with an external object storage provider</strong>, encrypted by us before they
|
|
230
|
+
leave our network. That provider holds ciphertext and no key, and cannot read what it stores.</li>
|
|
231
|
+
<li><strong>Our source code, build pipeline and container images are hosted with a third-party provider.</strong> That is
|
|
232
|
+
how the Service is built and deployed rather than where your data lives day to day, but it is a genuine
|
|
233
|
+
third party and it is disclosed as one.</li>
|
|
234
|
+
</ul>
|
|
235
|
+
<h3 id="where-a-product-does-something-different" tabindex="-1">Where a product does something different</h3>
|
|
236
|
+
<p>A small number of products use a third-party managed database, managed storage or hosted platform for a
|
|
237
|
+
specific function instead of our own infrastructure. <strong>Where that is the case for Ever Tech Engineering Services, the
|
|
238
|
+
provider appears in the always-engaged tier above and the product annex says which data goes there.</strong></p>
|
|
239
|
+
<p>We are explicit about this because "self-hosted" is exactly the sort of claim that gets made once and then
|
|
240
|
+
stops being true for one product in the range. If your data for a given feature sits with someone else, the
|
|
241
|
+
table says so.</p>
|
|
242
|
+
<h3 id="the-regions-you-should-design-around" tabindex="-1">The regions you should design around</h3>
|
|
243
|
+
<p>If you are completing a transfer mapping or a data protection impact assessment, the honest summary is:
|
|
244
|
+
<strong>primary processing in the European Union on infrastructure we operate; edge termination worldwide; a
|
|
245
|
+
small number of named providers established outside the European Economic Area, each with its own transfer
|
|
246
|
+
mechanism.</strong> Every one of those providers is in the tables above, and the mechanism for each is in the
|
|
247
|
+
international transfers section of the <a href="https://ever.tech/privacy">Privacy Policy</a>.</p>
|
|
248
|
+
<p>If you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which
|
|
249
|
+
modules apply — write to privacy@ever.co and we will send them.</p>
|
|
250
|
+
<h2 id="when-this-list-changes" tabindex="-1">When this list changes</h2>
|
|
251
|
+
<h3 id="the-notice-period" tabindex="-1">The notice period</h3>
|
|
252
|
+
<p><strong>We give at least 30 days' notice before a new or replacement sub-processor starts processing personal
|
|
253
|
+
data for the hosted Service.</strong> The 30 days run from the date the notice is published or sent, whichever
|
|
254
|
+
comes first, and they exist so that your objection right is a real one rather than a formality you learn
|
|
255
|
+
about afterwards.</p>
|
|
256
|
+
<h3 id="how-you-find-out" tabindex="-1">How you find out</h3>
|
|
257
|
+
<ul>
|
|
258
|
+
<li><strong>This page changes first.</strong> It carries the date it took effect and a dated record of what changed, so
|
|
259
|
+
the page itself is the notice.</li>
|
|
260
|
+
<li><strong>By email, if you ask for it.</strong> Write to privacy@ever.co and we will add your address to the
|
|
261
|
+
notification list. We then email you before each change, at the same time the page is updated. <strong>We
|
|
262
|
+
recommend a role address rather than an individual's</strong> — a notice sent to someone who has left your
|
|
263
|
+
organisation has been sent and not received.</li>
|
|
264
|
+
<li><strong>In the product</strong>, for changes that affect a feature you are using, through a notice to workspace
|
|
265
|
+
administrators.</li>
|
|
266
|
+
</ul>
|
|
267
|
+
<h3 id="what-the-notice-tells-you" tabindex="-1">What the notice tells you</h3>
|
|
268
|
+
<p>The provider's legal name, what it will do, where it is established, the categories of personal data it
|
|
269
|
+
will receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,
|
|
270
|
+
and whether it is a new provider or replaces one already on the list. If it replaces one, we say which.</p>
|
|
271
|
+
<h3 id="urgent-replacements" tabindex="-1">Urgent replacements</h3>
|
|
272
|
+
<p>Sometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its
|
|
273
|
+
service, loses the legal basis it relied on, or fails in a way that makes staying with it worse than
|
|
274
|
+
leaving.</p>
|
|
275
|
+
<p><strong>Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with
|
|
276
|
+
the reason we could not wait.</strong> Your right to object is not affected: it simply runs from the notice
|
|
277
|
+
instead of before the change. We do not use this route as a convenience, and a notice sent under it says
|
|
278
|
+
plainly why the normal period was not followed.</p>
|
|
279
|
+
<h3 id="changes-that-do-not-need-notice" tabindex="-1">Changes that do not need notice</h3>
|
|
280
|
+
<p>Removing a provider does not need a notice period — it reduces the number of people handling your data. A
|
|
281
|
+
provider changing its own name, or the group entity that contracts with us changing without a change in
|
|
282
|
+
where or how the processing happens, is recorded here as an administrative update rather than announced as
|
|
283
|
+
a new engagement. <strong>A provider moving its processing to a different country is not administrative, and gets
|
|
284
|
+
the full notice.</strong></p>
|
|
285
|
+
<h3 id="the-record" tabindex="-1">The record</h3>
|
|
286
|
+
<p>We keep the change history for this page so that you can reconstruct who was engaged during a given period.
|
|
287
|
+
That matters if you are updating your own records of processing, refreshing an impact assessment, or
|
|
288
|
+
answering a question about a period in the past. Ask privacy@ever.co if you need the state of the list
|
|
289
|
+
as it stood on a particular date.</p>
|
|
290
|
+
<h2 id="objecting-to-a-sub-processor" tabindex="-1">Objecting to a sub-processor</h2>
|
|
291
|
+
<h3 id="who-can-object" tabindex="-1">Who can object</h3>
|
|
292
|
+
<p>The customer — the organisation or person who contracts with us and acts as controller for the data in the
|
|
293
|
+
workspace. If you are an individual whose data we hold, this is not your route: your rights are in the
|
|
294
|
+
<a href="https://ever.tech/privacy">Privacy Policy</a>, and if your data sits in an employer's workspace, your employer
|
|
295
|
+
is the controller and the request goes to them.</p>
|
|
296
|
+
<h3 id="how-to-object" tabindex="-1">How to object</h3>
|
|
297
|
+
<p>Write to <strong>privacy@ever.co</strong> within <strong>30 days</strong> of the notice, and tell us:</p>
|
|
298
|
+
<ul>
|
|
299
|
+
<li>which provider you are objecting to;</li>
|
|
300
|
+
<li><strong>your reasons, on data protection grounds</strong> — a transfer you cannot justify, a conflict with a
|
|
301
|
+
commitment you have given your own users, a regulator's position that applies to you, a documented
|
|
302
|
+
security concern;</li>
|
|
303
|
+
<li>which of your workspaces or environments the objection covers.</li>
|
|
304
|
+
</ul>
|
|
305
|
+
<p><strong>The reasons matter.</strong> This is a right to object on data protection grounds, not a veto over our choice of
|
|
306
|
+
suppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem
|
|
307
|
+
is and we can usually solve it.</p>
|
|
308
|
+
<h3 id="what-we-do-next" tabindex="-1">What we do next</h3>
|
|
309
|
+
<p>We acknowledge your objection within five business days and <strong>respond substantively within 30 days.</strong> In
|
|
310
|
+
between we look for a way to make the objection unnecessary:</p>
|
|
311
|
+
<ul>
|
|
312
|
+
<li><strong>A different provider</strong> for your workspace, where one exists that does the job.</li>
|
|
313
|
+
<li><strong>A different configuration</strong> — narrowing what is sent, changing a region, or turning off the feature
|
|
314
|
+
that needs the provider at all, if you can live without it.</li>
|
|
315
|
+
<li><strong>Excluding your workspace</strong> from the provider, where that is technically possible.</li>
|
|
316
|
+
<li><strong>Additional safeguards or contractual terms</strong> where your concern is about a specific risk rather than
|
|
317
|
+
the provider as a whole.</li>
|
|
318
|
+
</ul>
|
|
319
|
+
<p>Where it is technically possible to hold off, <strong>we will not start using the provider you have objected to
|
|
320
|
+
for your data while the objection is open.</strong> Where it is not possible — because the provider is part of how
|
|
321
|
+
the Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the
|
|
322
|
+
clock run out on you.</p>
|
|
323
|
+
<h3 id="if-we-cannot-resolve-it" tabindex="-1">If we cannot resolve it</h3>
|
|
324
|
+
<p>If we cannot offer you a solution you can accept, <strong>you may terminate the affected subscription by written
|
|
325
|
+
notice, without penalty, and we will refund the fees you have prepaid for the period after termination.</strong>
|
|
326
|
+
That is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.</p>
|
|
327
|
+
<p>Give us notice within 30 days of our final response, and we will keep your data available for export for
|
|
328
|
+
the usual 30-day window described in the <a href="https://ever.tech/tos">Terms of Service</a> so that leaving does not
|
|
329
|
+
cost you the data.</p>
|
|
330
|
+
<p>If you are on a free tier there is nothing to refund, and the same route is simply to stop using the
|
|
331
|
+
Service and export your data.</p>
|
|
332
|
+
<h3 id="objecting-to-a-provider-already-on-the-list" tabindex="-1">Objecting to a provider already on the list</h3>
|
|
333
|
+
<p>You do not have to wait for a change. <strong>You can raise a concern about a provider already listed at any
|
|
334
|
+
time</strong>, using the same address and the same process, without the 30-day deadline. The realistic outcome
|
|
335
|
+
differs by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,
|
|
336
|
+
because it is part of how the Service works — and if the answer is going to be no, you will get it as a
|
|
337
|
+
straight no with the reason.</p>
|
|
338
|
+
<h2 id="how-to-reach-us-about-this-list" tabindex="-1">How to reach us about this list</h2>
|
|
339
|
+
<ul>
|
|
340
|
+
<li><strong>Questions about a provider, a request for the safeguards behind a transfer, or a request to join the
|
|
341
|
+
change notification list</strong> — privacy@ever.co.</li>
|
|
342
|
+
<li><strong>An objection to a sub-processor</strong> — privacy@ever.co, as set out above.</li>
|
|
343
|
+
<li><strong>The Data Processing Addendum, a due diligence request, or a security questionnaire</strong> —
|
|
344
|
+
legal@ever.co.</li>
|
|
345
|
+
</ul>
|
|
346
|
+
<p>We are <strong>Ever Technologies LTD</strong>, registered in Bulgaria under company number
|
|
347
|
+
204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our
|
|
348
|
+
own processing and your processor for the data in your workspace. By post, write to the registered office
|
|
349
|
+
and mark the letter for the attention of the privacy team. We correspond in English.</p>
|
|
350
|
+
<p>You may also complain to a data protection supervisory authority. Ours is the
|
|
351
|
+
Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
|
|
352
|
+
<a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
|
|
353
|
+
to the authority for the country where you live or work.</p>
|
|
354
|
+
<p>This document is version 1.0.0 of the sub-processor list for
|
|
355
|
+
<a href="https://ever.tech">ever.tech</a>, in force from 2026-10-25. It lists the providers engaged
|
|
356
|
+
as at that date. Earlier versions, with the dates they applied, are at
|
|
357
|
+
<a href="https://ever.tech/subprocessors">https://ever.tech/subprocessors</a>.</p>
|
|
@@ -0,0 +1,158 @@
|
|
|
1
|
+
{
|
|
2
|
+
"document": "subprocessors",
|
|
3
|
+
"product": "ever-tech-services",
|
|
4
|
+
"productName": "Ever Tech Engineering Services",
|
|
5
|
+
"domain": "ever.tech",
|
|
6
|
+
"entity": "Ever Technologies LTD",
|
|
7
|
+
"entityId": "ever-technologies-bg",
|
|
8
|
+
"locale": "en",
|
|
9
|
+
"version": "1.0.0",
|
|
10
|
+
"effectiveDate": "2026-10-25",
|
|
11
|
+
"sha256": "aa8fe793c5712404969e742b91ce5d8e18d148f2bd425a627b5bfda9b41a2d8a",
|
|
12
|
+
"publishable": true,
|
|
13
|
+
"sections": [
|
|
14
|
+
"core/subprocessors/010-purpose",
|
|
15
|
+
"core/subprocessors/020-how-to-read-this-list",
|
|
16
|
+
"@annex/subprocessors",
|
|
17
|
+
"core/subprocessors/100-hosting-and-infrastructure",
|
|
18
|
+
"core/subprocessors/110-change-notification",
|
|
19
|
+
"core/subprocessors/120-objection-procedure",
|
|
20
|
+
"core/subprocessors/900-contact"
|
|
21
|
+
],
|
|
22
|
+
"headings": [
|
|
23
|
+
{
|
|
24
|
+
"level": 2,
|
|
25
|
+
"text": "Why this page exists"
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"level": 3,
|
|
29
|
+
"text": "What counts as a sub-processor"
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"level": 3,
|
|
33
|
+
"text": "What this page covers"
|
|
34
|
+
},
|
|
35
|
+
{
|
|
36
|
+
"level": 2,
|
|
37
|
+
"text": "How to read this list"
|
|
38
|
+
},
|
|
39
|
+
{
|
|
40
|
+
"level": 3,
|
|
41
|
+
"text": "Tier 1 — always engaged"
|
|
42
|
+
},
|
|
43
|
+
{
|
|
44
|
+
"level": 3,
|
|
45
|
+
"text": "Tier 2 — engaged only if you turn something on"
|
|
46
|
+
},
|
|
47
|
+
{
|
|
48
|
+
"level": 3,
|
|
49
|
+
"text": "Tier 3 — self-hosted deployments only"
|
|
50
|
+
},
|
|
51
|
+
{
|
|
52
|
+
"level": 3,
|
|
53
|
+
"text": "What the columns mean"
|
|
54
|
+
},
|
|
55
|
+
{
|
|
56
|
+
"level": 3,
|
|
57
|
+
"text": "Why this list is deliberately longer than it needs to be"
|
|
58
|
+
},
|
|
59
|
+
{
|
|
60
|
+
"level": 3,
|
|
61
|
+
"text": "What is deliberately not in the tables"
|
|
62
|
+
},
|
|
63
|
+
{
|
|
64
|
+
"level": 2,
|
|
65
|
+
"text": "Annex: Ever Tech Engineering Services"
|
|
66
|
+
},
|
|
67
|
+
{
|
|
68
|
+
"level": 3,
|
|
69
|
+
"text": "Tier 1 — always engaged for agent engagements"
|
|
70
|
+
},
|
|
71
|
+
{
|
|
72
|
+
"level": 3,
|
|
73
|
+
"text": "Tier 2 — engaged only when you, a feature or an order form brings them in"
|
|
74
|
+
},
|
|
75
|
+
{
|
|
76
|
+
"level": 3,
|
|
77
|
+
"text": "Tier 3 — deployments you run yourself"
|
|
78
|
+
},
|
|
79
|
+
{
|
|
80
|
+
"level": 3,
|
|
81
|
+
"text": "Not on this list, and why"
|
|
82
|
+
},
|
|
83
|
+
{
|
|
84
|
+
"level": 2,
|
|
85
|
+
"text": "Hosting and infrastructure"
|
|
86
|
+
},
|
|
87
|
+
{
|
|
88
|
+
"level": 3,
|
|
89
|
+
"text": "Where processing actually happens"
|
|
90
|
+
},
|
|
91
|
+
{
|
|
92
|
+
"level": 3,
|
|
93
|
+
"text": "Where a product does something different"
|
|
94
|
+
},
|
|
95
|
+
{
|
|
96
|
+
"level": 3,
|
|
97
|
+
"text": "The regions you should design around"
|
|
98
|
+
},
|
|
99
|
+
{
|
|
100
|
+
"level": 2,
|
|
101
|
+
"text": "When this list changes"
|
|
102
|
+
},
|
|
103
|
+
{
|
|
104
|
+
"level": 3,
|
|
105
|
+
"text": "The notice period"
|
|
106
|
+
},
|
|
107
|
+
{
|
|
108
|
+
"level": 3,
|
|
109
|
+
"text": "How you find out"
|
|
110
|
+
},
|
|
111
|
+
{
|
|
112
|
+
"level": 3,
|
|
113
|
+
"text": "What the notice tells you"
|
|
114
|
+
},
|
|
115
|
+
{
|
|
116
|
+
"level": 3,
|
|
117
|
+
"text": "Urgent replacements"
|
|
118
|
+
},
|
|
119
|
+
{
|
|
120
|
+
"level": 3,
|
|
121
|
+
"text": "Changes that do not need notice"
|
|
122
|
+
},
|
|
123
|
+
{
|
|
124
|
+
"level": 3,
|
|
125
|
+
"text": "The record"
|
|
126
|
+
},
|
|
127
|
+
{
|
|
128
|
+
"level": 2,
|
|
129
|
+
"text": "Objecting to a sub-processor"
|
|
130
|
+
},
|
|
131
|
+
{
|
|
132
|
+
"level": 3,
|
|
133
|
+
"text": "Who can object"
|
|
134
|
+
},
|
|
135
|
+
{
|
|
136
|
+
"level": 3,
|
|
137
|
+
"text": "How to object"
|
|
138
|
+
},
|
|
139
|
+
{
|
|
140
|
+
"level": 3,
|
|
141
|
+
"text": "What we do next"
|
|
142
|
+
},
|
|
143
|
+
{
|
|
144
|
+
"level": 3,
|
|
145
|
+
"text": "If we cannot resolve it"
|
|
146
|
+
},
|
|
147
|
+
{
|
|
148
|
+
"level": 3,
|
|
149
|
+
"text": "Objecting to a provider already on the list"
|
|
150
|
+
},
|
|
151
|
+
{
|
|
152
|
+
"level": 2,
|
|
153
|
+
"text": "How to reach us about this list"
|
|
154
|
+
}
|
|
155
|
+
],
|
|
156
|
+
"path": "content/subprocessors/ever-tech-services/en.html",
|
|
157
|
+
"markdown": "## Why this page exists\r\n\r\nWhen you use Ever Tech's engineering services to process personal data, we act as your processor and you are the\r\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\r\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\r\n\r\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\r\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\r\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\r\ngiven through it.\r\n\r\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\r\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\r\nanswer should not be available only to the person paying the invoice.\r\n\r\n### What counts as a sub-processor\r\n\r\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\r\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\r\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\r\n\r\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\r\nmore complete:\r\n\r\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\r\n is not in the path of your data.\r\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\r\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\r\n part, not our processor. Those recipients are described in the\r\n [Privacy Policy](https://ever.tech/privacy) instead.\r\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\r\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\r\n what genuinely sits in front of it.\r\n\r\n### What this page covers\r\n\r\nThe **hosted Service we operate** at [ever.tech](https://ever.tech), for Ever Tech Engineering Services\r\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\r\nbetween them — do not read this one as covering a product it does not name.\r\n\r\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\r\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\r\nexists to make that distinction visible rather than to blur it.\r\n\r\nThis page is versioned and dated. The version in force, and the date it took effect, are at the end.\n\n## How to read this list\r\n\r\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\r\nyou the wrong answer.\r\n\r\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\r\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\r\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\r\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\r\ndeployment that somebody else runs, with their own account and their own credentials.\r\n\r\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\r\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\r\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\r\nthree tiers.\r\n\r\n### Tier 1 — always engaged\r\n\r\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\r\nbecause they are part of how the Service is delivered to everyone.\r\n\r\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\r\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\r\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\r\n\r\n### Tier 2 — engaged only if you turn something on\r\n\r\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\r\nEnable nothing and it is never involved, and no data of yours ever reaches it.\r\n\r\nWho does the enabling depends on the feature:\r\n\r\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\r\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\r\n connector.\r\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\r\n connecting their own third-party tool.\r\n\r\nThe table names the feature or setting that activates each provider, so you can check your own\r\nconfiguration against it rather than take our word for the current state. If you want to know precisely\r\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\r\n\r\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\r\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\r\n\r\n### Tier 3 — self-hosted deployments only\r\n\r\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\r\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\r\nusing your own accounts and your own credentials.\r\n\r\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\r\nThey are not our sub-processors, and they never become ours by appearing here.\r\n\r\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\r\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\r\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\r\nopen-source section of our [Terms of Service](https://ever.tech/tos) sets out the same split.\r\n\r\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\r\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\r\n\r\n### What the columns mean\r\n\r\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\r\n separate European establishment that contracts with us, that is the one named.\r\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\r\n- **Location** — where the processing takes place, or the provider's place of establishment where\r\n processing is distributed. Where a provider contracts through a European establishment but processes\r\n elsewhere, this column says both, because the two are different facts and only naming the first would\r\n flatter us.\r\n- **Transfer mechanism** — for a provider outside the European Economic Area, the Chapter V instrument we\r\n actually rely on for that specific provider: an adequacy decision, the Standard Contractual Clauses, or\r\n nothing yet. **Where it reads \"To be confirmed\", we have not yet evidenced an instrument for that\r\n provider, and we would rather say so here than print one we cannot produce.** That is a live piece of\r\n work, not a formula. Providers established inside the EEA need no mechanism and say so. For the third\r\n tier the transfer is not ours at all — you choose the provider and hold the contract.\r\n The general rules behind this column are in the international transfers section of our\r\n [Privacy Policy](https://ever.tech/privacy), and we will give you a copy of the safeguards for a named\r\n provider on request.\r\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\r\n provider that receives email addresses receives them for the people who trigger the feature, not for\r\n everyone.\r\n\r\n### Why this list is deliberately longer than it needs to be\r\n\r\n**We list providers we may engage, not only the ones engaged today.** Where we have configured a\r\nprovider, kept one available behind a feature flag, used one recently, or expect to use one for a\r\npurpose already described here, it appears in the tables below — even if no data has reached it this\r\nmonth, and even where we currently run the equivalent ourselves.\r\n\r\nWe do this on purpose, and you should read the tables with it in mind:\r\n\r\n- **A provider appearing here is not proof that your data has reached it.** It means the provider is\r\n within the scope of what we have told you we may do, at the tier shown. The tier is the part that\r\n tells you when it is engaged.\r\n- **Where we self-host something today** — our analytics, our job runner, our databases, our object\r\n storage — we say so, and we also name the hosted service we would move to, so that a later change is\r\n covered by a disclosure you have already seen rather than by a fresh surprise.\r\n- **The alternative is worse.** A list that names only today's exact set has to be re-issued, and\r\n re-consented, every time an engineer changes a setting. A list drawn slightly wide stays true through\r\n ordinary operational change, which is what makes it dependable.\r\n\r\n**What we will not do is use this as cover.** Breadth here does not license a purpose we have not\r\ndescribed, a category of data we have not listed, or a transfer without a mechanism. If we start\r\nsending a new *kind* of personal data, or sending it for a new *reason*, that is a change to this page\r\nand to the notice period below — not something the width of a table quietly absorbs.\r\n\r\nIf you need to know precisely which providers are live for your workspace today, rather than which ones\r\nmay be, ask us at privacy@ever.co and we will tell you.\r\n\r\n### What is deliberately not in the tables\r\n\r\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\r\n container platform are not sub-processors, because there is no third party involved. The next section\r\n describes what we run and what really does sit in front of it.\r\n- **Recipients that are not processors** — payment providers acting under their own regulatory\r\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\r\n are covered in the [Privacy Policy](https://ever.tech/privacy).\r\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\r\n site, their notice applies.\n\n## Annex: Ever Tech Engineering Services\r\n\r\nThis list covers personal data we process **as your processor** in engagements under the Terms for\r\nEver Tech's engineering services. Read the tier, not just the name.\r\n\r\n**Agent engagements do not run on our own infrastructure.** The general sections describe our hosted\r\nproducts, which do. The machines that run our AI agents are provided through the platform listed below, by\r\nproviders it engages; the principal ones are listed here, and the platform publishes its full list. Where the general sections mention a **subscription**, read *a\r\nsigned order form*.\r\n\r\n### Tier 1 — always engaged for agent engagements\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloc M operations platform — operated by a separate company outside our group (legal name, address and company number given in your order form) | Runs our AI agents for your engagement: dedicated machines, connections to your tools, approval gate and gate modes, metering, work diary and audit trail. | European Union (platform and machines); the operating company is established in the United States | Standard Contractual Clauses (EU 2021/914) for access from outside the EEA | all content of the engagement the Agents process, your users' names, work contact details and account handles |\n| Hetzner Online GmbH (via the platform) | Machines and storage for agent Instances, where the platform uses Hetzner as the hosting target. | Germany and Finland | — (inside the EEA) | all content processed on an Instance, encrypted exports during the retention period |\n| Anthropic, PBC (via the platform) | Model inference for the Agents, under commercial API terms that prohibit training on requests. | United States | Standard Contractual Clauses (EU 2021/914) | the text of inference requests and responses, which may contain personal data from your content |\r\n\r\n### Tier 2 — engaged only when you, a feature or an order form brings them in\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| OpenAI Ireland Ltd (via the platform) | Fallback model inference. You can exclude it in your order form. | United States (via Ireland) | Standard Contractual Clauses (EU 2021/914) | the text of inference requests and responses |\r\n\r\n### Tier 3 — deployments you run yourself\r\n\r\n_None in this category._\r\n\r\n### Not on this list, and why\r\n\r\n- **Human engineering without agents** uses no third-party processor of ours: our engineers work in your own\r\n tools, under your own contracts with those tools' providers.\r\n- **Our time-tracking and project systems** are self-hosted on our own infrastructure in the European Union.\r\n- **Upwork** is a separate controller for engagements contracted there, and **the Cloc Now marketplace** is a\r\n separate controller for purchases made there. Neither is our processor.\n\n## Hosting and infrastructure\r\n\r\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\r\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\r\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\r\noperate ourselves.\r\n\r\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\r\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\r\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\r\n[Security page](https://ever.tech/security).\r\n\r\n### Where processing actually happens\r\n\r\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\r\n Union.** That is the primary location for accounts, content, files and the databases behind them.\r\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\r\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\r\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\r\n transfer mechanism for it is described in our [Privacy Policy](https://ever.tech/privacy).\r\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\r\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\r\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\r\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\r\n third party and it is disclosed as one.\r\n\r\n### Where a product does something different\r\n\r\nA small number of products use a third-party managed database, managed storage or hosted platform for a\r\nspecific function instead of our own infrastructure. **Where that is the case for Ever Tech Engineering Services, the\r\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\r\n\r\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\r\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\r\ntable says so.\r\n\r\n### The regions you should design around\r\n\r\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\r\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\r\nsmall number of named providers established outside the European Economic Area, each with its own transfer\r\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\r\ninternational transfers section of the [Privacy Policy](https://ever.tech/privacy).\r\n\r\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\r\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\r\n\r\n### The notice period\r\n\r\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\r\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\r\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\r\nabout afterwards.\r\n\r\n### How you find out\r\n\r\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\r\n the page itself is the notice.\r\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\r\n notification list. We then email you before each change, at the same time the page is updated. **We\r\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\r\n organisation has been sent and not received.\r\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\r\n administrators.\r\n\r\n### What the notice tells you\r\n\r\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\r\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\r\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\r\n\r\n### Urgent replacements\r\n\r\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\r\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\r\nleaving.\r\n\r\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\r\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\r\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\r\nplainly why the normal period was not followed.\r\n\r\n### Changes that do not need notice\r\n\r\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\r\nprovider changing its own name, or the group entity that contracts with us changing without a change in\r\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\r\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\r\nthe full notice.**\r\n\r\n### The record\r\n\r\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\r\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\r\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\r\nas it stood on a particular date.\n\n## Objecting to a sub-processor\r\n\r\n### Who can object\r\n\r\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\r\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\r\n[Privacy Policy](https://ever.tech/privacy), and if your data sits in an employer's workspace, your employer\r\nis the controller and the request goes to them.\r\n\r\n### How to object\r\n\r\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\r\n\r\n- which provider you are objecting to;\r\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\r\n commitment you have given your own users, a regulator's position that applies to you, a documented\r\n security concern;\r\n- which of your workspaces or environments the objection covers.\r\n\r\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\r\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\r\nis and we can usually solve it.\r\n\r\n### What we do next\r\n\r\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\r\nbetween we look for a way to make the objection unnecessary:\r\n\r\n- **A different provider** for your workspace, where one exists that does the job.\r\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\r\n that needs the provider at all, if you can live without it.\r\n- **Excluding your workspace** from the provider, where that is technically possible.\r\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\r\n the provider as a whole.\r\n\r\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\r\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\r\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\r\nclock run out on you.\r\n\r\n### If we cannot resolve it\r\n\r\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\r\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\r\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\r\n\r\nGive us notice within 30 days of our final response, and we will keep your data available for export for\r\nthe usual 30-day window described in the [Terms of Service](https://ever.tech/tos) so that leaving does not\r\ncost you the data.\r\n\r\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\r\nService and export your data.\r\n\r\n### Objecting to a provider already on the list\r\n\r\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\r\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\r\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\r\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\r\nstraight no with the reason.\n\n## How to reach us about this list\r\n\r\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\r\n change notification list** — privacy@ever.co.\r\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\r\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\r\n legal@ever.co.\r\n\r\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\r\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\r\nown processing and your processor for the data in your workspace. By post, write to the registered office\r\nand mark the letter for the attention of the privacy team. We correspond in English.\r\n\r\nYou may also complain to a data protection supervisory authority. Ours is the\r\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\r\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\r\nto the authority for the country where you live or work.\r\n\r\nThis document is version 1.0.0 of the sub-processor list for\r\n[ever.tech](https://ever.tech), in force from 2026-10-25. It lists the providers engaged\r\nas at that date. Earlier versions, with the dates they applied, are at\r\n[https://ever.tech/subprocessors](https://ever.tech/subprocessors)."
|
|
158
|
+
}
|