@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,141 @@
|
|
|
1
|
+
{
|
|
2
|
+
"document": "subprocessors",
|
|
3
|
+
"product": "ever-tech",
|
|
4
|
+
"productName": "Ever Tech",
|
|
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-08-02",
|
|
11
|
+
"sha256": "f160ad0cb2919560173fb32aa4090b3107346ec3bbbad4d2bc0ab0e8683337f1",
|
|
12
|
+
"publishable": true,
|
|
13
|
+
"sections": [
|
|
14
|
+
"core/subprocessors/020-how-to-read-this-list",
|
|
15
|
+
"@annex/subprocessors",
|
|
16
|
+
"core/subprocessors/100-hosting-and-infrastructure",
|
|
17
|
+
"core/subprocessors/110-change-notification",
|
|
18
|
+
"core/subprocessors/120-objection-procedure",
|
|
19
|
+
"core/subprocessors/900-contact"
|
|
20
|
+
],
|
|
21
|
+
"headings": [
|
|
22
|
+
{
|
|
23
|
+
"level": 2,
|
|
24
|
+
"text": "How to read this list"
|
|
25
|
+
},
|
|
26
|
+
{
|
|
27
|
+
"level": 3,
|
|
28
|
+
"text": "Tier 1 — always engaged"
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"level": 3,
|
|
32
|
+
"text": "Tier 2 — engaged only if you turn something on"
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"level": 3,
|
|
36
|
+
"text": "Tier 3 — self-hosted deployments only"
|
|
37
|
+
},
|
|
38
|
+
{
|
|
39
|
+
"level": 3,
|
|
40
|
+
"text": "What the columns mean"
|
|
41
|
+
},
|
|
42
|
+
{
|
|
43
|
+
"level": 3,
|
|
44
|
+
"text": "What is deliberately not in the tables"
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"level": 2,
|
|
48
|
+
"text": "Annex: Ever Tech"
|
|
49
|
+
},
|
|
50
|
+
{
|
|
51
|
+
"level": 3,
|
|
52
|
+
"text": "Tier 1 — always engaged"
|
|
53
|
+
},
|
|
54
|
+
{
|
|
55
|
+
"level": 3,
|
|
56
|
+
"text": "Tier 2 — engaged only when your consent or your submission brings them in"
|
|
57
|
+
},
|
|
58
|
+
{
|
|
59
|
+
"level": 3,
|
|
60
|
+
"text": "Tier 3 — self-hosted deployments only"
|
|
61
|
+
},
|
|
62
|
+
{
|
|
63
|
+
"level": 3,
|
|
64
|
+
"text": "Where the candidate records actually live"
|
|
65
|
+
},
|
|
66
|
+
{
|
|
67
|
+
"level": 2,
|
|
68
|
+
"text": "Hosting and infrastructure"
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"level": 3,
|
|
72
|
+
"text": "Where processing actually happens"
|
|
73
|
+
},
|
|
74
|
+
{
|
|
75
|
+
"level": 3,
|
|
76
|
+
"text": "Where a product does something different"
|
|
77
|
+
},
|
|
78
|
+
{
|
|
79
|
+
"level": 3,
|
|
80
|
+
"text": "The regions you should design around"
|
|
81
|
+
},
|
|
82
|
+
{
|
|
83
|
+
"level": 2,
|
|
84
|
+
"text": "When this list changes"
|
|
85
|
+
},
|
|
86
|
+
{
|
|
87
|
+
"level": 3,
|
|
88
|
+
"text": "The notice period"
|
|
89
|
+
},
|
|
90
|
+
{
|
|
91
|
+
"level": 3,
|
|
92
|
+
"text": "How you find out"
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"level": 3,
|
|
96
|
+
"text": "What the notice tells you"
|
|
97
|
+
},
|
|
98
|
+
{
|
|
99
|
+
"level": 3,
|
|
100
|
+
"text": "Urgent replacements"
|
|
101
|
+
},
|
|
102
|
+
{
|
|
103
|
+
"level": 3,
|
|
104
|
+
"text": "Changes that do not need notice"
|
|
105
|
+
},
|
|
106
|
+
{
|
|
107
|
+
"level": 3,
|
|
108
|
+
"text": "The record"
|
|
109
|
+
},
|
|
110
|
+
{
|
|
111
|
+
"level": 2,
|
|
112
|
+
"text": "Objecting to a sub-processor"
|
|
113
|
+
},
|
|
114
|
+
{
|
|
115
|
+
"level": 3,
|
|
116
|
+
"text": "Who can object"
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"level": 3,
|
|
120
|
+
"text": "How to object"
|
|
121
|
+
},
|
|
122
|
+
{
|
|
123
|
+
"level": 3,
|
|
124
|
+
"text": "What we do next"
|
|
125
|
+
},
|
|
126
|
+
{
|
|
127
|
+
"level": 3,
|
|
128
|
+
"text": "If we cannot resolve it"
|
|
129
|
+
},
|
|
130
|
+
{
|
|
131
|
+
"level": 3,
|
|
132
|
+
"text": "Objecting to a provider already on the list"
|
|
133
|
+
},
|
|
134
|
+
{
|
|
135
|
+
"level": 2,
|
|
136
|
+
"text": "How to reach us about this list"
|
|
137
|
+
}
|
|
138
|
+
],
|
|
139
|
+
"path": "content/subprocessors/ever-tech/en.html",
|
|
140
|
+
"markdown": "## 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.tech/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.tech/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.tech/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 Tech\n\nthe Ever Tech website has no account, no subscription and no customer data, so this list is short and it\nis a list of **our** providers rather than yours. Read the tier, not just the name.\n\n### Tier 1 — always engaged\n\nThese are in the path for everyone who reads the site, or for everyone who submits a form. There is no\nsetting that removes them.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | 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. | United States, with edge termination worldwide | IP address, user agent and device characteristics, requested URLs and request headers, TLS and connection metadata, cookies in transit |\n| ActiveCampaign, LLC (Postmark) | 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. | United States | 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 |\n| Google LLC (reCAPTCHA) | 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. | United States | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page |\n| iubenda s.r.l. | 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. | Italy, European Union | IP address, user agent, consent preferences and the timestamp of the choice |\n| Functional Software, Inc. (Sentry) | 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. | United States | 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 |\n| GitHub, Inc. | 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. | United States | 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 |\n\n### Tier 2 — engaged only when your consent or your submission brings them in\n\nNothing here runs by default. Each provider arrives because somebody did something: consented to a cookie\ncategory, opened the chat widget, or asked to join the mailing list. Refuse the banner and use no form,\nand none of them is ever involved.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Google Ireland Limited (Google Tag Manager and Google Analytics 4) | 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. | Ireland, European Union, with processing by Google LLC in the United States | IP address, analytics client identifier, pages viewed, referrer, device and browser details |\n| PostHog, Inc. | 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. | United States | 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 |\n| Dealfront Group GmbH (Leadfeeder) | 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. | Germany, European Union | IP address, inferred employer or organisation, pages viewed, navigation path and referrer |\n| Chatwoot Inc. | 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. | United States | 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 |\n| Intuit Inc. (Mailchimp) | 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. | United States | email address, subscription status, tags and timestamp, IP address at the time of subscription, campaign engagement |\n| Vercel Inc. | 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. | United States | 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 |\n\n### Tier 3 — self-hosted deployments only\n\n**Empty, and it should be.** The code behind this website is not published under an open-source licence,\nso there is no copy of it that anyone else runs and no configuration of yours to describe.\n\n_None in this category._\n\n### Where the candidate records actually live\n\nThe candidate and application records created by the talent application form — including the CV file\nitself — are held in **our own content database, on our own hardware in the European Union**. There is no\nthird-party applicant tracking system, no recruitment platform and no hosted database behind that form,\nwhich is why none appears above.\n\n**One copy does leave.** Every application is also emailed to an internal mailbox, so the message and its\nattachment pass through our mail provider in tier 1. That is the only route by which a CV reaches anyone\noutside our own infrastructure.\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.tech/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.tech/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 Tech, 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.tech/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.tech/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.tech/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.tech](https://ever.tech), 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.tech/subprocessors](https://ever.tech/subprocessors)."
|
|
141
|
+
}
|