@ever-co/legal 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/content/aup/ever-corporate/en.html +667 -0
- package/dist/content/aup/ever-corporate/en.json +302 -0
- package/dist/content/aup/ever-demand/en.html +802 -0
- package/dist/content/aup/ever-demand/en.json +339 -0
- package/dist/content/aup/ever-rec/en.html +667 -0
- package/dist/content/aup/ever-rec/en.json +302 -0
- package/dist/content/aup/ever-teams/en.html +667 -0
- package/dist/content/aup/ever-teams/en.json +302 -0
- package/dist/content/aup/ever-works/en.html +667 -0
- package/dist/content/aup/ever-works/en.json +302 -0
- package/dist/content/aup/everiq/en.html +726 -0
- package/dist/content/aup/everiq/en.json +319 -0
- package/dist/content/aup/gauzy/en.html +715 -0
- package/dist/content/aup/gauzy/en.json +327 -0
- package/dist/content/aup/githands/en.html +864 -0
- package/dist/content/aup/githands/en.json +363 -0
- package/dist/content/aup/hust/en.html +781 -0
- package/dist/content/aup/hust/en.json +347 -0
- package/dist/content/aup/traduora/en.html +667 -0
- package/dist/content/aup/traduora/en.json +302 -0
- package/dist/content/cookies/ever-corporate/en.html +493 -0
- package/dist/content/cookies/ever-corporate/en.json +193 -0
- package/dist/content/cookies/ever-demand/en.html +633 -0
- package/dist/content/cookies/ever-demand/en.json +226 -0
- package/dist/content/cookies/ever-rec/en.html +564 -0
- package/dist/content/cookies/ever-rec/en.json +206 -0
- package/dist/content/cookies/ever-teams/en.html +549 -0
- package/dist/content/cookies/ever-teams/en.json +222 -0
- package/dist/content/cookies/ever-tech/en.html +469 -0
- package/dist/content/cookies/ever-tech/en.json +177 -0
- package/dist/content/cookies/ever-works/en.html +618 -0
- package/dist/content/cookies/ever-works/en.json +202 -0
- package/dist/content/cookies/everiq/en.html +437 -0
- package/dist/content/cookies/everiq/en.json +185 -0
- package/dist/content/cookies/gauzy/en.html +490 -0
- package/dist/content/cookies/gauzy/en.json +206 -0
- package/dist/content/cookies/githands/en.html +618 -0
- package/dist/content/cookies/githands/en.json +210 -0
- package/dist/content/cookies/hust/en.html +622 -0
- package/dist/content/cookies/hust/en.json +210 -0
- package/dist/content/cookies/traduora/en.html +580 -0
- package/dist/content/cookies/traduora/en.json +193 -0
- package/dist/content/dpa/ever-demand/en.html +1804 -0
- package/dist/content/dpa/ever-demand/en.json +628 -0
- package/dist/content/dpa/ever-rec/en.html +1963 -0
- package/dist/content/dpa/ever-rec/en.json +652 -0
- package/dist/content/dpa/ever-teams/en.html +1918 -0
- package/dist/content/dpa/ever-teams/en.json +648 -0
- package/dist/content/dpa/ever-works/en.html +1801 -0
- package/dist/content/dpa/ever-works/en.json +624 -0
- package/dist/content/dpa/gauzy/en.html +1836 -0
- package/dist/content/dpa/gauzy/en.json +632 -0
- package/dist/content/dpa/githands/en.html +1808 -0
- package/dist/content/dpa/githands/en.json +624 -0
- package/dist/content/dpa/hust/en.html +1804 -0
- package/dist/content/dpa/hust/en.json +632 -0
- package/dist/content/privacy/ever-corporate/en.html +1184 -0
- package/dist/content/privacy/ever-corporate/en.json +352 -0
- package/dist/content/privacy/ever-demand/en.html +1234 -0
- package/dist/content/privacy/ever-demand/en.json +364 -0
- package/dist/content/privacy/ever-rec/en.html +1250 -0
- package/dist/content/privacy/ever-rec/en.json +360 -0
- package/dist/content/privacy/ever-teams/en.html +1238 -0
- package/dist/content/privacy/ever-teams/en.json +368 -0
- package/dist/content/privacy/ever-tech/en.html +1127 -0
- package/dist/content/privacy/ever-tech/en.json +352 -0
- package/dist/content/privacy/ever-works/en.html +1284 -0
- package/dist/content/privacy/ever-works/en.json +364 -0
- package/dist/content/privacy/everiq/en.html +1172 -0
- package/dist/content/privacy/everiq/en.json +328 -0
- package/dist/content/privacy/gauzy/en.html +1281 -0
- package/dist/content/privacy/gauzy/en.json +356 -0
- package/dist/content/privacy/githands/en.html +1393 -0
- package/dist/content/privacy/githands/en.json +380 -0
- package/dist/content/privacy/hust/en.html +1359 -0
- package/dist/content/privacy/hust/en.json +368 -0
- package/dist/content/privacy/traduora/en.html +1146 -0
- package/dist/content/privacy/traduora/en.json +336 -0
- package/dist/content/refund/ever-works/en.html +595 -0
- package/dist/content/refund/ever-works/en.json +336 -0
- package/dist/content/refund/gauzy/en.html +595 -0
- package/dist/content/refund/gauzy/en.json +336 -0
- package/dist/content/refund/githands/en.html +647 -0
- package/dist/content/refund/githands/en.json +361 -0
- package/dist/content/refund/hust/en.html +595 -0
- package/dist/content/refund/hust/en.json +336 -0
- package/dist/content/security/ever-demand/en.html +900 -0
- package/dist/content/security/ever-demand/en.json +425 -0
- package/dist/content/security/ever-rec/en.html +768 -0
- package/dist/content/security/ever-rec/en.json +380 -0
- package/dist/content/security/ever-teams/en.html +768 -0
- package/dist/content/security/ever-teams/en.json +380 -0
- package/dist/content/security/ever-works/en.html +768 -0
- package/dist/content/security/ever-works/en.json +380 -0
- package/dist/content/security/gauzy/en.html +768 -0
- package/dist/content/security/gauzy/en.json +380 -0
- package/dist/content/security/githands/en.html +876 -0
- package/dist/content/security/githands/en.json +421 -0
- package/dist/content/security/hust/en.html +768 -0
- package/dist/content/security/hust/en.json +380 -0
- package/dist/content/subprocessors/ever-corporate/en.html +382 -0
- package/dist/content/subprocessors/ever-corporate/en.json +158 -0
- package/dist/content/subprocessors/ever-demand/en.html +452 -0
- package/dist/content/subprocessors/ever-demand/en.json +154 -0
- package/dist/content/subprocessors/ever-rec/en.html +439 -0
- package/dist/content/subprocessors/ever-rec/en.json +154 -0
- package/dist/content/subprocessors/ever-teams/en.html +477 -0
- package/dist/content/subprocessors/ever-teams/en.json +154 -0
- package/dist/content/subprocessors/ever-tech/en.html +335 -0
- package/dist/content/subprocessors/ever-tech/en.json +141 -0
- package/dist/content/subprocessors/ever-works/en.html +551 -0
- package/dist/content/subprocessors/ever-works/en.json +154 -0
- package/dist/content/subprocessors/everiq/en.html +296 -0
- package/dist/content/subprocessors/everiq/en.json +149 -0
- package/dist/content/subprocessors/gauzy/en.html +603 -0
- package/dist/content/subprocessors/gauzy/en.json +154 -0
- package/dist/content/subprocessors/githands/en.html +465 -0
- package/dist/content/subprocessors/githands/en.json +154 -0
- package/dist/content/subprocessors/hust/en.html +482 -0
- package/dist/content/subprocessors/hust/en.json +154 -0
- package/dist/content/subprocessors/traduora/en.html +362 -0
- package/dist/content/subprocessors/traduora/en.json +154 -0
- package/dist/content/tos/ever-corporate/en.html +973 -0
- package/dist/content/tos/ever-corporate/en.json +517 -0
- package/dist/content/tos/ever-demand/en.html +1598 -0
- package/dist/content/tos/ever-demand/en.json +783 -0
- package/dist/content/tos/ever-rec/en.html +1524 -0
- package/dist/content/tos/ever-rec/en.json +771 -0
- package/dist/content/tos/ever-teams/en.html +1551 -0
- package/dist/content/tos/ever-teams/en.json +779 -0
- package/dist/content/tos/ever-tech/en.html +762 -0
- package/dist/content/tos/ever-tech/en.json +421 -0
- package/dist/content/tos/ever-works/en.html +1552 -0
- package/dist/content/tos/ever-works/en.json +787 -0
- package/dist/content/tos/everiq/en.html +781 -0
- package/dist/content/tos/everiq/en.json +429 -0
- package/dist/content/tos/gauzy/en.html +1440 -0
- package/dist/content/tos/gauzy/en.json +755 -0
- package/dist/content/tos/githands/en.html +1542 -0
- package/dist/content/tos/githands/en.json +779 -0
- package/dist/content/tos/hust/en.html +1566 -0
- package/dist/content/tos/hust/en.json +787 -0
- package/dist/content/tos/traduora/en.html +1238 -0
- package/dist/content/tos/traduora/en.json +646 -0
- package/dist/index.json +26991 -0
- package/package.json +52 -0
|
@@ -0,0 +1,154 @@
|
|
|
1
|
+
{
|
|
2
|
+
"document": "subprocessors",
|
|
3
|
+
"product": "ever-teams",
|
|
4
|
+
"productName": "Ever Teams",
|
|
5
|
+
"domain": "ever.team",
|
|
6
|
+
"entity": "Ever Technologies LTD",
|
|
7
|
+
"entityId": "ever-technologies-bg",
|
|
8
|
+
"locale": "en",
|
|
9
|
+
"version": "1.0.0",
|
|
10
|
+
"effectiveDate": "2026-08-02",
|
|
11
|
+
"sha256": "ec9f12b283f55e36dd6ea3f3a725f9fa764c9d9cb04cc3ef4334dcc83246e456",
|
|
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": "What is deliberately not in the tables"
|
|
58
|
+
},
|
|
59
|
+
{
|
|
60
|
+
"level": 2,
|
|
61
|
+
"text": "Annex: Ever Teams"
|
|
62
|
+
},
|
|
63
|
+
{
|
|
64
|
+
"level": 3,
|
|
65
|
+
"text": "Tier 1 — always engaged"
|
|
66
|
+
},
|
|
67
|
+
{
|
|
68
|
+
"level": 3,
|
|
69
|
+
"text": "Tier 2 — engaged only when a feature, integration or consent brings them in"
|
|
70
|
+
},
|
|
71
|
+
{
|
|
72
|
+
"level": 3,
|
|
73
|
+
"text": "Tier 3 — self-hosted deployments only"
|
|
74
|
+
},
|
|
75
|
+
{
|
|
76
|
+
"level": 3,
|
|
77
|
+
"text": "Where Ever Teams data actually lives"
|
|
78
|
+
},
|
|
79
|
+
{
|
|
80
|
+
"level": 2,
|
|
81
|
+
"text": "Hosting and infrastructure"
|
|
82
|
+
},
|
|
83
|
+
{
|
|
84
|
+
"level": 3,
|
|
85
|
+
"text": "Where processing actually happens"
|
|
86
|
+
},
|
|
87
|
+
{
|
|
88
|
+
"level": 3,
|
|
89
|
+
"text": "Where a product does something different"
|
|
90
|
+
},
|
|
91
|
+
{
|
|
92
|
+
"level": 3,
|
|
93
|
+
"text": "The regions you should design around"
|
|
94
|
+
},
|
|
95
|
+
{
|
|
96
|
+
"level": 2,
|
|
97
|
+
"text": "When this list changes"
|
|
98
|
+
},
|
|
99
|
+
{
|
|
100
|
+
"level": 3,
|
|
101
|
+
"text": "The notice period"
|
|
102
|
+
},
|
|
103
|
+
{
|
|
104
|
+
"level": 3,
|
|
105
|
+
"text": "How you find out"
|
|
106
|
+
},
|
|
107
|
+
{
|
|
108
|
+
"level": 3,
|
|
109
|
+
"text": "What the notice tells you"
|
|
110
|
+
},
|
|
111
|
+
{
|
|
112
|
+
"level": 3,
|
|
113
|
+
"text": "Urgent replacements"
|
|
114
|
+
},
|
|
115
|
+
{
|
|
116
|
+
"level": 3,
|
|
117
|
+
"text": "Changes that do not need notice"
|
|
118
|
+
},
|
|
119
|
+
{
|
|
120
|
+
"level": 3,
|
|
121
|
+
"text": "The record"
|
|
122
|
+
},
|
|
123
|
+
{
|
|
124
|
+
"level": 2,
|
|
125
|
+
"text": "Objecting to a sub-processor"
|
|
126
|
+
},
|
|
127
|
+
{
|
|
128
|
+
"level": 3,
|
|
129
|
+
"text": "Who can object"
|
|
130
|
+
},
|
|
131
|
+
{
|
|
132
|
+
"level": 3,
|
|
133
|
+
"text": "How to object"
|
|
134
|
+
},
|
|
135
|
+
{
|
|
136
|
+
"level": 3,
|
|
137
|
+
"text": "What we do next"
|
|
138
|
+
},
|
|
139
|
+
{
|
|
140
|
+
"level": 3,
|
|
141
|
+
"text": "If we cannot resolve it"
|
|
142
|
+
},
|
|
143
|
+
{
|
|
144
|
+
"level": 3,
|
|
145
|
+
"text": "Objecting to a provider already on the list"
|
|
146
|
+
},
|
|
147
|
+
{
|
|
148
|
+
"level": 2,
|
|
149
|
+
"text": "How to reach us about this list"
|
|
150
|
+
}
|
|
151
|
+
],
|
|
152
|
+
"path": "content/subprocessors/ever-teams/en.html",
|
|
153
|
+
"markdown": "## Why this page exists\n\nWhen you use Ever Teams Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://ever.team/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [ever.team](https://ever.team), for Ever Teams\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\nbetween them — do not read this one as covering a product it does not name.\n\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\nexists to make that distinction visible rather than to blur it.\n\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\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://ever.team/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where that is outside the European Economic Area, the transfer mechanism we\n rely on for it is described in the international transfers section of our\n [Privacy Policy](https://ever.team/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### What is deliberately not in the tables\n\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\n container platform are not sub-processors, because there is no third party involved. The next section\n describes what we run and what really does sit in front of it.\n- **Recipients that are not processors** — payment providers acting under their own regulatory\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\n are covered in the [Privacy Policy](https://ever.team/privacy).\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\n site, their notice applies.\n\n## Annex: Ever Teams\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination, content delivery and web application firewall in front of every ever.team hostname — the application, the API, the boards, the meeting server, the documentation and the websites. All traffic to Ever Teams passes through it. Cloudflare Turnstile is also one of the bot-protection providers the sign-up form can be configured to use. | United States, with processing at edge locations worldwide including inside the EEA | IP address, request URL and headers, user agent, cookies in transit, bot-protection signals |\n| Google Ireland Limited (reCAPTCHA) | Bot protection on sign-up, sign-in and newsletter forms. The widget loads from Google in your browser and our server verifies the resulting token with Google. This is the bot-protection provider configured today. Strictly necessary — it loads without asking you, for the reasons given in the cookie categories section. | Ireland and the United States | IP address, user agent, mouse, touch and timing signals, reCAPTCHA cookies |\n| Functional Software, Inc. d/b/a Sentry | Error and crash reporting and performance tracing for the web application, the mobile and desktop applications, the boards application and the websites. This is Sentry's hosted service with ingest in the United States, not a Sentry instance we run. It also records session replay — a masked reconstruction of the interface — for a sample of sessions and for sessions that produced an error; replay is consent-gated. | United States | IP address, user id and email address attached to an error, browser, operating system, device model and application version, the page or route in use, stack traces and request breadcrumbs, masked session replay recordings |\n| Jitsu Labs, Inc. | Product analytics for the signed-in application. On each page you open it receives an identify event carrying your user id, email address and full name together with your organisation's tenant name and id, plus the page you navigated to. Its cookie is set on the ever.team domain, so it looks first-party to a scanner although the recipient is not us. Consent-gated as analytics. | United States | user id, email address, full name, tenant and organisation name and id, page URL and navigation history, IP address |\n| ActiveCampaign, LLC (Postmark) | Transactional email delivery for the application — team invitations, email verification, sign-in codes and email-change confirmations. Every message the product sends you leaves through it. | United States | recipient email address, recipient and inviter name, message subject and body, including invitation links and sign-in codes, delivery, bounce and open metadata |\n| Chatwoot Inc. | The in-application support chat widget, loaded from Chatwoot's hosted service at app.chatwoot.com — not the Chatwoot instance we run for other purposes. Consent-gated as a functional widget. | United States | support conversation content, name and email address if you supply them in the widget, IP address, browser, operating system and current page URL |\n| Wasabi Technologies, Inc. | Object storage behind the platform's file-asset service. This is where avatars, task attachments and time-tracker SCREENSHOTS are written when the platform's file provider is set to Wasabi. Which provider is in the path is our configuration, not a setting you control — so we list both. | United States | screen captures of a monitored person's screen, profile photographs, task and message attachments |\n| Cloudinary Ltd. | The alternative image store and delivery network behind the same platform file-asset service, holding the same categories of file as Wasabi. Listed for the same reason: which of the two is in the path is our configuration, not yours. | United States | screen captures of a monitored person's screen, profile photographs, task and message attachments, IP address of anyone fetching an image |\n| Google LLC (Google Fonts) | Webfont delivery to the Ever Teams desktop application, the browser extension and the server-side PDF report renderer. The signed-in web application serves its fonts from our own infrastructure and does not contact this provider. | United States | IP address of the device fetching the font, user agent |\n| 650 Industries, Inc. (Expo) | Build service and over-the-air update delivery for the Ever Teams mobile application, which checks for a new JavaScript bundle each time it launches. Mobile application only — it is not involved if you use the web application. | United States | device IP address, platform, operating system version, application and runtime version, update channel, Expo installation identifier |\n| iubenda s.r.l. | Cookie-consent banner and storage of your consent choice on the ever.team and apps.ever.team websites. It is not used inside the signed-in application. | Italy | IP address, consent choices, user agent, page URL |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Google LLC (Firebase Cloud Storage) | Storage for images pasted or uploaded into an Ever Teams whiteboard. The board document itself stays on our own infrastructure; the images inside it do not. Engaged only when someone puts an image on a board. | United States | the image file itself, and whatever personal data is visible in it, IP address of the uploading device, Firebase installation identifier |\n| GitHub, Inc. | Two separate things, each engaged by a choice somebody makes. First, the Ever Teams GitHub App, which an administrator installs to sync a customer's repositories and issues into tasks — this imports data about contributors and issue authors who are not our users. Second, distribution of the desktop application's automatic updates. | United States | GitHub account login, user id and, where exposed, email address, repository, issue and commit metadata belonging to the customer, installation identifier, IP address of a device downloading a desktop update |\n| Google Ireland Limited and Meta Platforms Ireland Limited (social sign-in) | Signing in with an existing account instead of an emailed code. These are the two identity providers enabled today. Engaged only if you choose that route; nothing reaches them if you sign in by email. | Ireland and the United States | provider account identifier, email address, display name, profile picture URL, IP address at the provider's consent screen |\n| Google Ireland Limited (Google Analytics and Google Tag Manager) | Web analytics on the ever.team and apps.ever.team websites. Consent-gated, and not loaded in the signed-in application. | Ireland and the United States | IP address, Google Analytics client identifier, page URLs and referrer, device and browser data |\n| PostHog, Inc. | Product analytics wired into the ever.team and apps.ever.team websites. Engaged only where a project key is configured for that surface and you have consented to analytics; no key is configured for the signed-in application. | United States | person profile for identified users, IP address, page URLs, referrer and campaign parameters, clicks and interaction events |\n| The Rocket Science Group LLC d/b/a Mailchimp | Newsletter and marketing list. Engaged only when you submit the subscribe form, which posts your email address and a source tag to the list. | United States | email address, subscription tags and source |\n| DigitalOcean, LLC (Spaces) | A second distribution point for Ever Teams desktop application installers and the automatic update feed. Engaged only if you install or update the desktop application. | United States | IP address of a device downloading an installer or update manifest |\n| Algolia SAS | Documentation search on docs.ever.team. Engaged only where search credentials are configured for that site; the documentation falls back to local search when they are not. | France and the United States | search query text, IP address, user agent |\n| Better Stack (Logtail) | Log shipping from the ChatGPT connector service, engaged only where a log token is configured for it. It is not in the path for the web, desktop or mobile applications. | United States | application log lines, which can include user identifiers, request paths and IP addresses |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Teams on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Amazon Web Services, Inc., Wasabi Technologies, Inc., Cloudinary Ltd. and DigitalOcean, LLC | Object and image storage options the software can be pointed at in a deployment you run — for avatars, attachments and, where you enable capture, screenshots. You pick one, you hold the credentials, you contract with them. | Chosen by whoever runs the deployment | Whatever that deployment stores there. We have no access to it and no visibility of it. |\n| Google LLC (Firebase Cloud Storage) | Whiteboard image storage in a deployment you run, under your own Firebase project and your own credentials. | Chosen by whoever runs the deployment | Whatever that deployment stores there. |\n| Functional Software, Inc. d/b/a Sentry, Jitsu Labs, Inc., PostHog, Inc. and Google (Analytics) | Error tracking and analytics endpoints a self-hosted deployment can be configured to send to, using its own keys. Leave them unset and the software sends nothing. | Chosen by whoever runs the deployment | Whatever that deployment sends them. |\n| Any SMTP relay or email provider you configure | Delivery of invitations, verification and sign-in codes from a deployment you run. The software takes an SMTP host and credentials; whose they are is your decision. | Chosen by whoever runs the deployment | Recipient addresses and message contents from that deployment. |\n| Google (reCAPTCHA), Intuition Machines, Inc. (hCaptcha) and Cloudflare, Inc. (Turnstile) | Bot protection on the sign-up form of a deployment you run. The software supports all three and reads your own site and secret keys. | Chosen by whoever runs the deployment | Connection and interaction signals from that deployment's visitors. |\n| OpenAI, L.L.C., Groq, Inc., Together Computer, Inc. or any OpenAI-compatible endpoint | Model providers for the in-product assistant. This is also how the assistant works on our hosted service: the key and the endpoint are supplied by the person using it, so the provider is their counterparty rather than our sub-processor. | Chosen by whoever supplies the key | Prompts and responses sent by that person. |\n| LiveKit, Inc. | An alternative real-time audio and video backend the software can be pointed at instead of a Jitsi server. Not enabled on our hosted service, where meetings run on a Jitsi server we operate. | Chosen by whoever runs the deployment | Audio and video streams, display identity and IP address in that deployment. |\n| Identity providers for social sign-in | Apple, Discord, GitHub, Google, LinkedIn, Meta, Microsoft, Slack and X can each be enabled in a deployment you run, using OAuth applications you register in your own name. | Chosen by whoever runs the deployment | Account identifiers and profile fields returned to that deployment. |\n| 650 Industries, Inc. (Expo) | Building and distributing your own copy of the mobile application, under your own Expo project. | Chosen by whoever runs the deployment | Device and application metadata from that deployment's builds. |\n\n### Where Ever Teams data actually lives\n\nEver Teams runs against the same platform API as our business management product, on our own\ninfrastructure. **That is not a third-party sub-processor** — it is us, under the same contract and the\nsame controller. It is named here only because \"which system holds my data\" is a fair question and the\nanswer is not obvious from the product name.\n\nWhere your organisation has enabled the monitoring features, captured media is stored through that same\nplatform's file provider on our own object storage.\n\n## Hosting and infrastructure\n\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\noperate ourselves.\n\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\n[Security page](https://ever.team/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://ever.team/privacy).\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\n third party and it is disclosed as one.\n\n### Where a product does something different\n\nA small number of products use a third-party managed database, managed storage or hosted platform for a\nspecific function instead of our own infrastructure. **Where that is the case for Ever Teams, the\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\n\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\ntable says so.\n\n### The regions you should design around\n\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\nsmall number of named providers established outside the European Economic Area, each with its own transfer\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\ninternational transfers section of the [Privacy Policy](https://ever.team/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://ever.team/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://ever.team/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.0 of the sub-processor list for\n[ever.team](https://ever.team), in force from 2026-08-02. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://ever.team/subprocessors](https://ever.team/subprocessors)."
|
|
154
|
+
}
|
|
@@ -0,0 +1,335 @@
|
|
|
1
|
+
<h2 id="how-to-read-this-list" tabindex="-1">How to read this list</h2>
|
|
2
|
+
<p>The three tables that follow mean genuinely different things, and reading them as one flat list will give
|
|
3
|
+
you the wrong answer.</p>
|
|
4
|
+
<p>Here is why the split exists. Our products are open-source at their core and built to be connected to other
|
|
5
|
+
things, so <strong>more than 160 distinct third-party providers appear somewhere in our source code across our
|
|
6
|
+
whole range of products.</strong> The overwhelming majority of them are never engaged by us for anything. Some are
|
|
7
|
+
optional integrations that do nothing until somebody switches them on. Many are reachable only in a
|
|
8
|
+
deployment that somebody else runs, with their own account and their own credentials.</p>
|
|
9
|
+
<p>Publishing all of them as "our sub-processors" would be inaccurate, and inaccurate in the worst direction:
|
|
10
|
+
it would tell you your data reaches companies it never touches, while burying the handful that it actually
|
|
11
|
+
does. <strong>A list that is technically exhaustive and practically misleading is not a disclosure.</strong> So there are
|
|
12
|
+
three tiers.</p>
|
|
13
|
+
<h3 id="tier-1-always-engaged" tabindex="-1">Tier 1 — always engaged</h3>
|
|
14
|
+
<p><strong>If you use the hosted Service, these providers are in the path.</strong> There is no setting that removes them,
|
|
15
|
+
because they are part of how the Service is delivered to everyone.</p>
|
|
16
|
+
<p>This is the real Article 28 sub-processor list. It is the tier to use when you are completing a data
|
|
17
|
+
protection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.
|
|
18
|
+
It is short, and it is short because we run our own infrastructure rather than renting someone else's.</p>
|
|
19
|
+
<h3 id="tier-2-engaged-only-if-you-turn-something-on" tabindex="-1">Tier 2 — engaged only if you turn something on</h3>
|
|
20
|
+
<p><strong>A provider in this tier is engaged only when a specific feature, connector or integration is enabled.</strong>
|
|
21
|
+
Enable nothing and it is never involved, and no data of yours ever reaches it.</p>
|
|
22
|
+
<p>Who does the enabling depends on the feature:</p>
|
|
23
|
+
<ul>
|
|
24
|
+
<li><strong>You or your workspace administrator</strong>, by switching on a feature or connecting an account in the
|
|
25
|
+
product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository
|
|
26
|
+
connector.</li>
|
|
27
|
+
<li><strong>An individual user</strong>, by making a personal choice — signing in with a social account, for example, or
|
|
28
|
+
connecting their own third-party tool.</li>
|
|
29
|
+
</ul>
|
|
30
|
+
<p>The table names the feature or setting that activates each provider, so you can check your own
|
|
31
|
+
configuration against it rather than take our word for the current state. If you want to know precisely
|
|
32
|
+
which of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.</p>
|
|
33
|
+
<p><strong>Enabling one of these is a decision to send your data somewhere else</strong>, and it is yours to make. The
|
|
34
|
+
provider's own terms and privacy notice then apply to what it does, alongside our contract with it.</p>
|
|
35
|
+
<h3 id="tier-3-self-hosted-deployments-only" tabindex="-1">Tier 3 — self-hosted deployments only</h3>
|
|
36
|
+
<p>Several of our products are published as open source and can be run on your own infrastructure. When you do
|
|
37
|
+
that, <strong>you</strong> choose the database, the object storage, the email relay, the AI provider and everything else,
|
|
38
|
+
using your own accounts and your own credentials.</p>
|
|
39
|
+
<p>The providers in this tier are listed <strong>only so that you can see what the software can be pointed at</strong>.
|
|
40
|
+
They are not our sub-processors, and they never become ours by appearing here.</p>
|
|
41
|
+
<p><strong>In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,
|
|
42
|
+
and nothing on this page or in our Data Processing Addendum describes it.</strong> You choose those providers, you
|
|
43
|
+
contract with them, you hold the credentials, and the obligations to your own users are yours alone. The
|
|
44
|
+
open-source section of our <a href="https://ever.tech/tos">Terms of Service</a> sets out the same split.</p>
|
|
45
|
+
<p>If you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a
|
|
46
|
+
useful starting inventory. It is not your list — only you know which of these you actually configured.</p>
|
|
47
|
+
<h3 id="what-the-columns-mean" tabindex="-1">What the columns mean</h3>
|
|
48
|
+
<ul>
|
|
49
|
+
<li><strong>Sub-processor</strong> — the contracting legal entity, not the brand on the website. Where a provider has a
|
|
50
|
+
separate European establishment that contracts with us, that is the one named.</li>
|
|
51
|
+
<li><strong>Purpose</strong> — what it does for the Service, specifically enough to be checked. Not "business operations".</li>
|
|
52
|
+
<li><strong>Location</strong> — where the processing takes place, or the provider's place of establishment where
|
|
53
|
+
processing is distributed. Where that is outside the European Economic Area, the transfer mechanism we
|
|
54
|
+
rely on for it is described in the international transfers section of our
|
|
55
|
+
<a href="https://ever.tech/privacy">Privacy Policy</a>, and we will give you a copy of the safeguards for a named
|
|
56
|
+
provider on request.</li>
|
|
57
|
+
<li><strong>Personal data</strong> — the categories that reach that provider. Categories, not a promise about volume: a
|
|
58
|
+
provider that receives email addresses receives them for the people who trigger the feature, not for
|
|
59
|
+
everyone.</li>
|
|
60
|
+
</ul>
|
|
61
|
+
<h3 id="what-is-deliberately-not-in-the-tables" tabindex="-1">What is deliberately not in the tables</h3>
|
|
62
|
+
<ul>
|
|
63
|
+
<li><strong>Infrastructure we operate ourselves.</strong> Our databases, object storage, cache, secrets manager and
|
|
64
|
+
container platform are not sub-processors, because there is no third party involved. The next section
|
|
65
|
+
describes what we run and what really does sit in front of it.</li>
|
|
66
|
+
<li><strong>Recipients that are not processors</strong> — payment providers acting under their own regulatory
|
|
67
|
+
obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those
|
|
68
|
+
are covered in the <a href="https://ever.tech/privacy">Privacy Policy</a>.</li>
|
|
69
|
+
<li><strong>Sites you choose to visit</strong> by following a link out of the Service. Once you are on someone else's
|
|
70
|
+
site, their notice applies.</li>
|
|
71
|
+
</ul>
|
|
72
|
+
<h2 id="annex-ever-tech" tabindex="-1">Annex: Ever Tech</h2>
|
|
73
|
+
<p>the Ever Tech website has no account, no subscription and no customer data, so this list is short and it
|
|
74
|
+
is a list of <strong>our</strong> providers rather than yours. Read the tier, not just the name.</p>
|
|
75
|
+
<h3 id="tier-1-always-engaged-1" tabindex="-1">Tier 1 — always engaged</h3>
|
|
76
|
+
<p>These are in the path for everyone who reads the site, or for everyone who submits a form. There is no
|
|
77
|
+
setting that removes them.</p>
|
|
78
|
+
<table>
|
|
79
|
+
<thead>
|
|
80
|
+
<tr>
|
|
81
|
+
<th>Sub-processor</th>
|
|
82
|
+
<th>Purpose</th>
|
|
83
|
+
<th>Location</th>
|
|
84
|
+
<th>Personal data</th>
|
|
85
|
+
</tr>
|
|
86
|
+
</thead>
|
|
87
|
+
<tbody>
|
|
88
|
+
<tr>
|
|
89
|
+
<td>Cloudflare, Inc.</td>
|
|
90
|
+
<td>Authoritative DNS, content delivery, TLS termination, bot and abuse protection, and the tunnel that carries traffic from the edge to our own infrastructure for ever.tech and the content management host behind it. Every request to the site passes through it.</td>
|
|
91
|
+
<td>United States, with edge termination worldwide</td>
|
|
92
|
+
<td>IP address, user agent and device characteristics, requested URLs and request headers, TLS and connection metadata, cookies in transit</td>
|
|
93
|
+
</tr>
|
|
94
|
+
<tr>
|
|
95
|
+
<td>ActiveCampaign, LLC (Postmark)</td>
|
|
96
|
+
<td>Delivery of every message the site generates — enquiries from the contact and hire-us forms, job applications from the careers pages, and talent applications from the join-us form, each sent to an internal mailbox with any attached file. It is also the mail provider configured in the content management system behind the site.</td>
|
|
97
|
+
<td>United States</td>
|
|
98
|
+
<td>name, email address, telephone number and company, free-text enquiry and application content, the CV or resume file attached to an application, anyone else named inside that free text or that file, delivery and bounce metadata</td>
|
|
99
|
+
</tr>
|
|
100
|
+
<tr>
|
|
101
|
+
<td>Google LLC (reCAPTCHA)</td>
|
|
102
|
+
<td>Bot protection on the public forms, with server-side verification of the resulting token. Treated as strictly necessary for the reasons given in our Cookie Policy, and loaded only on pages carrying a form.</td>
|
|
103
|
+
<td>United States</td>
|
|
104
|
+
<td>IP address, user agent and device characteristics, mouse, touch and timing signals from the form page</td>
|
|
105
|
+
</tr>
|
|
106
|
+
<tr>
|
|
107
|
+
<td>iubenda s.r.l.</td>
|
|
108
|
+
<td>Consent management — presenting the banner and the preference centre, recording what you chose and when, and making that choice available to the scripts that wait on it.</td>
|
|
109
|
+
<td>Italy, European Union</td>
|
|
110
|
+
<td>IP address, user agent, consent preferences and the timestamp of the choice</td>
|
|
111
|
+
</tr>
|
|
112
|
+
<tr>
|
|
113
|
+
<td>Functional Software, Inc. (Sentry)</td>
|
|
114
|
+
<td>Error and performance reporting. The server-side half runs for the site's own routes and for the content management system behind it whatever you choose in the banner, because a failed request has to be reportable. The browser-side half, including session replay, is in the analytics category and waits for your consent.</td>
|
|
115
|
+
<td>United States</td>
|
|
116
|
+
<td>IP address and device or operating-system details, URLs, route parameters and stack traces, which can carry fragments of the failing request, a masked replay of the visit in which an error occurred</td>
|
|
117
|
+
</tr>
|
|
118
|
+
<tr>
|
|
119
|
+
<td>GitHub, Inc.</td>
|
|
120
|
+
<td>Source hosting, continuous integration and the container registry the site is built and deployed from. It is also queried by our own server, once per page that shows the open-source contributor list, to read public repository and profile data from the GitHub search API.</td>
|
|
121
|
+
<td>United States</td>
|
|
122
|
+
<td>build, release and deployment metadata, developer and automation account identifiers, public GitHub usernames, avatars and profile links returned by the search API, no visitor data, because the call is made by our server and not by your browser</td>
|
|
123
|
+
</tr>
|
|
124
|
+
</tbody>
|
|
125
|
+
</table>
|
|
126
|
+
<h3 id="tier-2-engaged-only-when-your-consent-or-your-submission-brings-them-in" tabindex="-1">Tier 2 — engaged only when your consent or your submission brings them in</h3>
|
|
127
|
+
<p>Nothing here runs by default. Each provider arrives because somebody did something: consented to a cookie
|
|
128
|
+
category, opened the chat widget, or asked to join the mailing list. Refuse the banner and use no form,
|
|
129
|
+
and none of them is ever involved.</p>
|
|
130
|
+
<table>
|
|
131
|
+
<thead>
|
|
132
|
+
<tr>
|
|
133
|
+
<th>Sub-processor</th>
|
|
134
|
+
<th>Purpose</th>
|
|
135
|
+
<th>Location</th>
|
|
136
|
+
<th>Personal data</th>
|
|
137
|
+
</tr>
|
|
138
|
+
</thead>
|
|
139
|
+
<tbody>
|
|
140
|
+
<tr>
|
|
141
|
+
<td>Google Ireland Limited (Google Tag Manager and Google Analytics 4)</td>
|
|
142
|
+
<td>Tag management and website traffic measurement. Tag Manager is a container, so further tags can be loaded through it without a change to the site. Runs only after you consent to the analytics category.</td>
|
|
143
|
+
<td>Ireland, European Union, with processing by Google LLC in the United States</td>
|
|
144
|
+
<td>IP address, analytics client identifier, pages viewed, referrer, device and browser details</td>
|
|
145
|
+
</tr>
|
|
146
|
+
<tr>
|
|
147
|
+
<td>PostHog, Inc.</td>
|
|
148
|
+
<td>Product analytics for the website — page views, page-leave events and navigation paths. The integration is pinned to this provider's United States cloud. Runs only after you consent to the analytics category.</td>
|
|
149
|
+
<td>United States</td>
|
|
150
|
+
<td>IP address, an analytics identifier stored in your browser, page view and page-leave events, referrer and URL, device, browser, operating system and screen size</td>
|
|
151
|
+
</tr>
|
|
152
|
+
<tr>
|
|
153
|
+
<td>Dealfront Group GmbH (Leadfeeder)</td>
|
|
154
|
+
<td>Business-audience identification — resolving a visitor's IP address to the organisation it belongs to and reporting the pages that visitor read, so that we know which companies have looked at our services. Runs only after you consent to the marketing category.</td>
|
|
155
|
+
<td>Germany, European Union</td>
|
|
156
|
+
<td>IP address, inferred employer or organisation, pages viewed, navigation path and referrer</td>
|
|
157
|
+
</tr>
|
|
158
|
+
<tr>
|
|
159
|
+
<td>Chatwoot Inc.</td>
|
|
160
|
+
<td>The live support chat widget, which loads from this provider's own cloud service rather than an instance we run. Runs only after you consent to the functional category.</td>
|
|
161
|
+
<td>United States</td>
|
|
162
|
+
<td>name and email address you give the widget, the content of the chat, IP address and session identifiers, the page you were on when you opened it</td>
|
|
163
|
+
</tr>
|
|
164
|
+
<tr>
|
|
165
|
+
<td>Intuit Inc. (Mailchimp)</td>
|
|
166
|
+
<td>Mailing-list management for people who subscribe on the newsletter form. Engaged only for the address of someone who asked to be on the list.</td>
|
|
167
|
+
<td>United States</td>
|
|
168
|
+
<td>email address, subscription status, tags and timestamp, IP address at the time of subscription, campaign engagement</td>
|
|
169
|
+
</tr>
|
|
170
|
+
<tr>
|
|
171
|
+
<td>Vercel Inc.</td>
|
|
172
|
+
<td>A web analytics component that is still compiled into the site. Its beacon endpoint exists only on that provider's own hosting platform, and the site runs on our infrastructure instead, so nothing reaches it today. It is listed rather than omitted so that removing it stays a decision somebody makes rather than a detail nobody noticed.</td>
|
|
173
|
+
<td>United States</td>
|
|
174
|
+
<td>nothing, while the site is served from our own infrastructure, page view, referrer, device class and IP-derived country if it were ever served from that platform</td>
|
|
175
|
+
</tr>
|
|
176
|
+
</tbody>
|
|
177
|
+
</table>
|
|
178
|
+
<h3 id="tier-3-self-hosted-deployments-only-1" tabindex="-1">Tier 3 — self-hosted deployments only</h3>
|
|
179
|
+
<p><strong>Empty, and it should be.</strong> The code behind this website is not published under an open-source licence,
|
|
180
|
+
so there is no copy of it that anyone else runs and no configuration of yours to describe.</p>
|
|
181
|
+
<p><em>None in this category.</em></p>
|
|
182
|
+
<h3 id="where-the-candidate-records-actually-live" tabindex="-1">Where the candidate records actually live</h3>
|
|
183
|
+
<p>The candidate and application records created by the talent application form — including the CV file
|
|
184
|
+
itself — are held in <strong>our own content database, on our own hardware in the European Union</strong>. There is no
|
|
185
|
+
third-party applicant tracking system, no recruitment platform and no hosted database behind that form,
|
|
186
|
+
which is why none appears above.</p>
|
|
187
|
+
<p><strong>One copy does leave.</strong> Every application is also emailed to an internal mailbox, so the message and its
|
|
188
|
+
attachment pass through our mail provider in tier 1. That is the only route by which a CV reaches anyone
|
|
189
|
+
outside our own infrastructure.</p>
|
|
190
|
+
<h2 id="hosting-and-infrastructure" tabindex="-1">Hosting and infrastructure</h2>
|
|
191
|
+
<p>The tables above are short for a reason, and the reason is worth stating plainly: <strong>we run our own
|
|
192
|
+
infrastructure.</strong> The Service is not a tenancy in a public cloud account. It runs on physical servers we
|
|
193
|
+
own, in facilities we control, <strong>inside the European Union</strong>, on a virtualisation and container platform we
|
|
194
|
+
operate ourselves.</p>
|
|
195
|
+
<p>The database, the object storage that holds your files, the cache and queue layers, the secrets manager and
|
|
196
|
+
the deployment system are all components we run. <strong>None of them is a third party, so none of them appears
|
|
197
|
+
as a sub-processor</strong> — there is nobody else to disclose. What we do with them is described on our
|
|
198
|
+
<a href="https://ever.tech/security">Security page</a>.</p>
|
|
199
|
+
<h3 id="where-processing-actually-happens" tabindex="-1">Where processing actually happens</h3>
|
|
200
|
+
<ul>
|
|
201
|
+
<li><strong>Your data at rest, and the applications that process it, sit on our own hardware in the European
|
|
202
|
+
Union.</strong> That is the primary location for accounts, content, files and the databases behind them.</li>
|
|
203
|
+
<li><strong>Requests reach us through a global content delivery and security network.</strong> Traffic is terminated at
|
|
204
|
+
the edge location nearest to whoever is making the request, which can be anywhere in the world, before
|
|
205
|
+
being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the
|
|
206
|
+
transfer mechanism for it is described in our <a href="https://ever.tech/privacy">Privacy Policy</a>.</li>
|
|
207
|
+
<li><strong>Off-site backup copies are held with an external object storage provider</strong>, encrypted by us before they
|
|
208
|
+
leave our network. That provider holds ciphertext and no key, and cannot read what it stores.</li>
|
|
209
|
+
<li><strong>Our source code, build pipeline and container images are hosted with a third-party provider.</strong> That is
|
|
210
|
+
how the Service is built and deployed rather than where your data lives day to day, but it is a genuine
|
|
211
|
+
third party and it is disclosed as one.</li>
|
|
212
|
+
</ul>
|
|
213
|
+
<h3 id="where-a-product-does-something-different" tabindex="-1">Where a product does something different</h3>
|
|
214
|
+
<p>A small number of products use a third-party managed database, managed storage or hosted platform for a
|
|
215
|
+
specific function instead of our own infrastructure. <strong>Where that is the case for Ever Tech, the
|
|
216
|
+
provider appears in the always-engaged tier above and the product annex says which data goes there.</strong></p>
|
|
217
|
+
<p>We are explicit about this because "self-hosted" is exactly the sort of claim that gets made once and then
|
|
218
|
+
stops being true for one product in the range. If your data for a given feature sits with someone else, the
|
|
219
|
+
table says so.</p>
|
|
220
|
+
<h3 id="the-regions-you-should-design-around" tabindex="-1">The regions you should design around</h3>
|
|
221
|
+
<p>If you are completing a transfer mapping or a data protection impact assessment, the honest summary is:
|
|
222
|
+
<strong>primary processing in the European Union on infrastructure we operate; edge termination worldwide; a
|
|
223
|
+
small number of named providers established outside the European Economic Area, each with its own transfer
|
|
224
|
+
mechanism.</strong> Every one of those providers is in the tables above, and the mechanism for each is in the
|
|
225
|
+
international transfers section of the <a href="https://ever.tech/privacy">Privacy Policy</a>.</p>
|
|
226
|
+
<p>If you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which
|
|
227
|
+
modules apply — write to privacy@ever.co and we will send them.</p>
|
|
228
|
+
<h2 id="when-this-list-changes" tabindex="-1">When this list changes</h2>
|
|
229
|
+
<h3 id="the-notice-period" tabindex="-1">The notice period</h3>
|
|
230
|
+
<p><strong>We give at least 30 days' notice before a new or replacement sub-processor starts processing personal
|
|
231
|
+
data for the hosted Service.</strong> The 30 days run from the date the notice is published or sent, whichever
|
|
232
|
+
comes first, and they exist so that your objection right is a real one rather than a formality you learn
|
|
233
|
+
about afterwards.</p>
|
|
234
|
+
<h3 id="how-you-find-out" tabindex="-1">How you find out</h3>
|
|
235
|
+
<ul>
|
|
236
|
+
<li><strong>This page changes first.</strong> It carries the date it took effect and a dated record of what changed, so
|
|
237
|
+
the page itself is the notice.</li>
|
|
238
|
+
<li><strong>By email, if you ask for it.</strong> Write to privacy@ever.co and we will add your address to the
|
|
239
|
+
notification list. We then email you before each change, at the same time the page is updated. <strong>We
|
|
240
|
+
recommend a role address rather than an individual's</strong> — a notice sent to someone who has left your
|
|
241
|
+
organisation has been sent and not received.</li>
|
|
242
|
+
<li><strong>In the product</strong>, for changes that affect a feature you are using, through a notice to workspace
|
|
243
|
+
administrators.</li>
|
|
244
|
+
</ul>
|
|
245
|
+
<h3 id="what-the-notice-tells-you" tabindex="-1">What the notice tells you</h3>
|
|
246
|
+
<p>The provider's legal name, what it will do, where it is established, the categories of personal data it
|
|
247
|
+
will receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,
|
|
248
|
+
and whether it is a new provider or replaces one already on the list. If it replaces one, we say which.</p>
|
|
249
|
+
<h3 id="urgent-replacements" tabindex="-1">Urgent replacements</h3>
|
|
250
|
+
<p>Sometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its
|
|
251
|
+
service, loses the legal basis it relied on, or fails in a way that makes staying with it worse than
|
|
252
|
+
leaving.</p>
|
|
253
|
+
<p><strong>Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with
|
|
254
|
+
the reason we could not wait.</strong> Your right to object is not affected: it simply runs from the notice
|
|
255
|
+
instead of before the change. We do not use this route as a convenience, and a notice sent under it says
|
|
256
|
+
plainly why the normal period was not followed.</p>
|
|
257
|
+
<h3 id="changes-that-do-not-need-notice" tabindex="-1">Changes that do not need notice</h3>
|
|
258
|
+
<p>Removing a provider does not need a notice period — it reduces the number of people handling your data. A
|
|
259
|
+
provider changing its own name, or the group entity that contracts with us changing without a change in
|
|
260
|
+
where or how the processing happens, is recorded here as an administrative update rather than announced as
|
|
261
|
+
a new engagement. <strong>A provider moving its processing to a different country is not administrative, and gets
|
|
262
|
+
the full notice.</strong></p>
|
|
263
|
+
<h3 id="the-record" tabindex="-1">The record</h3>
|
|
264
|
+
<p>We keep the change history for this page so that you can reconstruct who was engaged during a given period.
|
|
265
|
+
That matters if you are updating your own records of processing, refreshing an impact assessment, or
|
|
266
|
+
answering a question about a period in the past. Ask privacy@ever.co if you need the state of the list
|
|
267
|
+
as it stood on a particular date.</p>
|
|
268
|
+
<h2 id="objecting-to-a-sub-processor" tabindex="-1">Objecting to a sub-processor</h2>
|
|
269
|
+
<h3 id="who-can-object" tabindex="-1">Who can object</h3>
|
|
270
|
+
<p>The customer — the organisation or person who contracts with us and acts as controller for the data in the
|
|
271
|
+
workspace. If you are an individual whose data we hold, this is not your route: your rights are in the
|
|
272
|
+
<a href="https://ever.tech/privacy">Privacy Policy</a>, and if your data sits in an employer's workspace, your employer
|
|
273
|
+
is the controller and the request goes to them.</p>
|
|
274
|
+
<h3 id="how-to-object" tabindex="-1">How to object</h3>
|
|
275
|
+
<p>Write to <strong>privacy@ever.co</strong> within <strong>30 days</strong> of the notice, and tell us:</p>
|
|
276
|
+
<ul>
|
|
277
|
+
<li>which provider you are objecting to;</li>
|
|
278
|
+
<li><strong>your reasons, on data protection grounds</strong> — a transfer you cannot justify, a conflict with a
|
|
279
|
+
commitment you have given your own users, a regulator's position that applies to you, a documented
|
|
280
|
+
security concern;</li>
|
|
281
|
+
<li>which of your workspaces or environments the objection covers.</li>
|
|
282
|
+
</ul>
|
|
283
|
+
<p><strong>The reasons matter.</strong> This is a right to object on data protection grounds, not a veto over our choice of
|
|
284
|
+
suppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem
|
|
285
|
+
is and we can usually solve it.</p>
|
|
286
|
+
<h3 id="what-we-do-next" tabindex="-1">What we do next</h3>
|
|
287
|
+
<p>We acknowledge your objection within five business days and <strong>respond substantively within 30 days.</strong> In
|
|
288
|
+
between we look for a way to make the objection unnecessary:</p>
|
|
289
|
+
<ul>
|
|
290
|
+
<li><strong>A different provider</strong> for your workspace, where one exists that does the job.</li>
|
|
291
|
+
<li><strong>A different configuration</strong> — narrowing what is sent, changing a region, or turning off the feature
|
|
292
|
+
that needs the provider at all, if you can live without it.</li>
|
|
293
|
+
<li><strong>Excluding your workspace</strong> from the provider, where that is technically possible.</li>
|
|
294
|
+
<li><strong>Additional safeguards or contractual terms</strong> where your concern is about a specific risk rather than
|
|
295
|
+
the provider as a whole.</li>
|
|
296
|
+
</ul>
|
|
297
|
+
<p>Where it is technically possible to hold off, <strong>we will not start using the provider you have objected to
|
|
298
|
+
for your data while the objection is open.</strong> Where it is not possible — because the provider is part of how
|
|
299
|
+
the Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the
|
|
300
|
+
clock run out on you.</p>
|
|
301
|
+
<h3 id="if-we-cannot-resolve-it" tabindex="-1">If we cannot resolve it</h3>
|
|
302
|
+
<p>If we cannot offer you a solution you can accept, <strong>you may terminate the affected subscription by written
|
|
303
|
+
notice, without penalty, and we will refund the fees you have prepaid for the period after termination.</strong>
|
|
304
|
+
That is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.</p>
|
|
305
|
+
<p>Give us notice within 30 days of our final response, and we will keep your data available for export for
|
|
306
|
+
the usual 30-day window described in the <a href="https://ever.tech/tos">Terms of Service</a> so that leaving does not
|
|
307
|
+
cost you the data.</p>
|
|
308
|
+
<p>If you are on a free tier there is nothing to refund, and the same route is simply to stop using the
|
|
309
|
+
Service and export your data.</p>
|
|
310
|
+
<h3 id="objecting-to-a-provider-already-on-the-list" tabindex="-1">Objecting to a provider already on the list</h3>
|
|
311
|
+
<p>You do not have to wait for a change. <strong>You can raise a concern about a provider already listed at any
|
|
312
|
+
time</strong>, using the same address and the same process, without the 30-day deadline. The realistic outcome
|
|
313
|
+
differs by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,
|
|
314
|
+
because it is part of how the Service works — and if the answer is going to be no, you will get it as a
|
|
315
|
+
straight no with the reason.</p>
|
|
316
|
+
<h2 id="how-to-reach-us-about-this-list" tabindex="-1">How to reach us about this list</h2>
|
|
317
|
+
<ul>
|
|
318
|
+
<li><strong>Questions about a provider, a request for the safeguards behind a transfer, or a request to join the
|
|
319
|
+
change notification list</strong> — privacy@ever.co.</li>
|
|
320
|
+
<li><strong>An objection to a sub-processor</strong> — privacy@ever.co, as set out above.</li>
|
|
321
|
+
<li><strong>The Data Processing Addendum, a due diligence request, or a security questionnaire</strong> —
|
|
322
|
+
legal@ever.co.</li>
|
|
323
|
+
</ul>
|
|
324
|
+
<p>We are <strong>Ever Technologies LTD</strong>, registered in Bulgaria under company number
|
|
325
|
+
204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our
|
|
326
|
+
own processing and your processor for the data in your workspace. By post, write to the registered office
|
|
327
|
+
and mark the letter for the attention of the privacy team. We correspond in English.</p>
|
|
328
|
+
<p>You may also complain to a data protection supervisory authority. Ours is the
|
|
329
|
+
Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
|
|
330
|
+
<a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
|
|
331
|
+
to the authority for the country where you live or work.</p>
|
|
332
|
+
<p>This document is version 1.0.0 of the sub-processor list for
|
|
333
|
+
<a href="https://ever.tech">ever.tech</a>, in force from 2026-08-02. It lists the providers engaged
|
|
334
|
+
as at that date. Earlier versions, with the dates they applied, are at
|
|
335
|
+
<a href="https://ever.tech/subprocessors">https://ever.tech/subprocessors</a>.</p>
|