@ever-co/legal 0.1.2 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/content/aup/ever-async/en.html +778 -0
- package/dist/content/aup/ever-async/en.json +343 -0
- package/dist/content/aup/hust/en.html +9 -0
- package/dist/content/aup/hust/en.json +2 -2
- package/dist/content/cookies/ever-async/en.html +457 -0
- package/dist/content/cookies/ever-async/en.json +185 -0
- package/dist/content/cookies/ever-demand/en.html +5 -2
- package/dist/content/cookies/ever-demand/en.json +2 -2
- package/dist/content/cookies/ever-rec/en.html +5 -2
- package/dist/content/cookies/ever-rec/en.json +2 -2
- package/dist/content/cookies/ever-teams/en.html +5 -2
- package/dist/content/cookies/ever-teams/en.json +2 -2
- package/dist/content/cookies/ever-works/en.html +5 -2
- package/dist/content/cookies/ever-works/en.json +2 -2
- package/dist/content/cookies/gauzy/en.html +5 -2
- package/dist/content/cookies/gauzy/en.json +2 -2
- package/dist/content/cookies/githands/en.html +5 -2
- package/dist/content/cookies/githands/en.json +2 -2
- package/dist/content/cookies/hust/en.html +5 -2
- package/dist/content/cookies/hust/en.json +2 -2
- package/dist/content/dpa/ever-async/en.html +1848 -0
- package/dist/content/dpa/ever-async/en.json +640 -0
- package/dist/content/privacy/ever-async/en.html +1350 -0
- package/dist/content/privacy/ever-async/en.json +364 -0
- package/dist/content/privacy/ever-corporate/en.html +86 -3
- package/dist/content/privacy/ever-corporate/en.json +2 -2
- package/dist/content/privacy/ever-demand/en.html +99 -2
- package/dist/content/privacy/ever-demand/en.json +2 -2
- package/dist/content/privacy/ever-rec/en.html +110 -3
- package/dist/content/privacy/ever-rec/en.json +2 -2
- package/dist/content/privacy/ever-teams/en.html +97 -1
- package/dist/content/privacy/ever-teams/en.json +2 -2
- package/dist/content/privacy/ever-tech/en.html +86 -3
- package/dist/content/privacy/ever-tech/en.json +2 -2
- package/dist/content/privacy/ever-works/en.html +74 -5
- package/dist/content/privacy/ever-works/en.json +2 -2
- package/dist/content/privacy/everiq/en.html +107 -0
- package/dist/content/privacy/everiq/en.json +2 -2
- package/dist/content/privacy/gauzy/en.html +88 -3
- package/dist/content/privacy/gauzy/en.json +2 -2
- package/dist/content/privacy/githands/en.html +83 -2
- package/dist/content/privacy/githands/en.json +2 -2
- package/dist/content/privacy/hust/en.html +186 -37
- package/dist/content/privacy/hust/en.json +3 -3
- package/dist/content/privacy/traduora/en.html +93 -0
- package/dist/content/privacy/traduora/en.json +2 -2
- package/dist/content/refund/ever-rec/en.html +595 -0
- package/dist/content/refund/ever-rec/en.json +336 -0
- package/dist/content/security/ever-async/en.html +853 -0
- package/dist/content/security/ever-async/en.json +417 -0
- package/dist/content/subprocessors/ever-async/en.html +852 -0
- package/dist/content/subprocessors/ever-async/en.json +166 -0
- package/dist/content/subprocessors/ever-corporate/en.html +403 -9
- package/dist/content/subprocessors/ever-corporate/en.json +6 -2
- package/dist/content/subprocessors/ever-demand/en.html +443 -13
- package/dist/content/subprocessors/ever-demand/en.json +6 -2
- package/dist/content/subprocessors/ever-rec/en.html +493 -10
- package/dist/content/subprocessors/ever-rec/en.json +6 -2
- package/dist/content/subprocessors/ever-teams/en.html +435 -8
- package/dist/content/subprocessors/ever-teams/en.json +6 -2
- package/dist/content/subprocessors/ever-tech/en.html +443 -9
- package/dist/content/subprocessors/ever-tech/en.json +6 -2
- package/dist/content/subprocessors/ever-works/en.html +354 -13
- package/dist/content/subprocessors/ever-works/en.json +6 -2
- package/dist/content/subprocessors/everiq/en.html +484 -3
- package/dist/content/subprocessors/everiq/en.json +6 -2
- package/dist/content/subprocessors/gauzy/en.html +353 -20
- package/dist/content/subprocessors/gauzy/en.json +6 -2
- package/dist/content/subprocessors/githands/en.html +451 -13
- package/dist/content/subprocessors/githands/en.json +6 -2
- package/dist/content/subprocessors/hust/en.html +502 -12
- package/dist/content/subprocessors/hust/en.json +14 -2
- package/dist/content/subprocessors/traduora/en.html +461 -4
- package/dist/content/subprocessors/traduora/en.json +6 -2
- package/dist/content/tos/ever-async/en.html +1350 -0
- package/dist/content/tos/ever-async/en.json +687 -0
- package/dist/content/tos/ever-rec/en.html +40 -11
- package/dist/content/tos/ever-rec/en.json +5 -5
- package/dist/content/tos/hust/en.html +32 -8
- package/dist/content/tos/hust/en.json +10 -2
- package/dist/index.json +5338 -2148
- package/package.json +1 -1
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
"locale": "en",
|
|
9
9
|
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "6ba38fee74f37ee122e9578fda49753059f2f4216ceac2de47a7d0a84b95a643",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/subprocessors/010-purpose",
|
|
@@ -52,6 +52,10 @@
|
|
|
52
52
|
"level": 3,
|
|
53
53
|
"text": "What the columns mean"
|
|
54
54
|
},
|
|
55
|
+
{
|
|
56
|
+
"level": 3,
|
|
57
|
+
"text": "Why this list is deliberately longer than it needs to be"
|
|
58
|
+
},
|
|
55
59
|
{
|
|
56
60
|
"level": 3,
|
|
57
61
|
"text": "What is deliberately not in the tables"
|
|
@@ -72,6 +76,14 @@
|
|
|
72
76
|
"level": 3,
|
|
73
77
|
"text": "Tier 3 — self-hosted deployments only"
|
|
74
78
|
},
|
|
79
|
+
{
|
|
80
|
+
"level": 3,
|
|
81
|
+
"text": "The 1,832 job sources, and why almost none of them is in a table above"
|
|
82
|
+
},
|
|
83
|
+
{
|
|
84
|
+
"level": 3,
|
|
85
|
+
"text": "The engine that does the collecting is ours, and it is open source"
|
|
86
|
+
},
|
|
75
87
|
{
|
|
76
88
|
"level": 3,
|
|
77
89
|
"text": "Your mailbox, and what does not happen to it"
|
|
@@ -150,5 +162,5 @@
|
|
|
150
162
|
}
|
|
151
163
|
],
|
|
152
164
|
"path": "content/subprocessors/hust/en.html",
|
|
153
|
-
"markdown": "## Why this page exists\n\nWhen you use the Ever Hust hosted service 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://hust.so/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 [hust.so](https://hust.so), for Ever Hust\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://hust.so/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://hust.so/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://hust.so/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 Hust\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination and the tunnel that is the only public route into our network. Every request to the website and to the application passes through it. | United States, with your connection terminated at the edge location nearest to you | IP address, TLS and connection metadata, request URLs and headers, cookies in transit |\n| Stripe Payments Europe, Limited | Subscription checkout, recurring billing, invoices, refunds and payment fraud checks. Engaged when you buy a plan. The free tier never reaches it, and we never receive your full card number. | Ireland, with processing on Stripe infrastructure including the United States | name, email address, billing address and country, card token and last four digits, tax identification number, subscription and invoice history, IP address at checkout |\n| OpenRouter, Inc. | Routes the assistant's model requests. It carries your chat messages, job description text, your CV text and the prompts behind evaluations, cover letters, tailored resumes, interview preparation and outreach drafts — then forwards each request to the upstream provider of the model in use. | United States, with onward processing by the upstream provider of the selected model | chat messages, CV and profile text, job description text, generated output, user and session identifiers |\n| Anthropic PBC | CV parsing. The full extracted text of a CV you upload is sent here on a direct call, outside the router above, to produce the structured profile. Also the default assistant model on paid plans. | United States | the full text of your CV, name, email address, telephone number, location, employment history, education, skills |\n| Langfuse GmbH | Tracing and observability for the assistant. It receives complete model prompts and completions, which means CV text, job text and chat content, with the identifiers that tie a trace to a user. | Germany (European Union) | model prompts and completions, CV, job and chat text contained in them, user and session identifiers |\n| Resend, Inc. | Delivery of the email we send you — address verification, sign-in, password reset, job alerts, application reminders and billing notices. It does not send anything from your connected mailbox. | United States | recipient email address and name, message subject and body, delivery, bounce and complaint events |\n| Functional Software, Inc. d/b/a Sentry | Error and performance monitoring. Error context carries your user identifier and email address, so this is not anonymous telemetry and we do not describe it as such. | United States | user identifier, email address, IP address, page or route, browser and device, stack traces and breadcrumbs |\n| GitHub, Inc. | Source code, build pipeline and container registry. This is how the Service is built and shipped rather than where your data lives, and it is disclosed because it is still a third party. | United States | none of your account or job-search data in the ordinary course, build and deployment metadata |\n| Automattic Inc. | Gravatar avatar fallback. Where you have not set a profile picture, your browser asks Gravatar for one using a hash of your email address. | United States | a hash of your email address, IP address, browser and device |\n| Prospect One (jsDelivr) | Public content delivery network serving the API reference viewer on the developer documentation pages. Your browser fetches those assets directly, so the request discloses your address to it. | Poland, with delivery from edge locations worldwide | IP address, browser and device, the page you were on |\n\n### Tier 2 — engaged only when a feature or integration brings them in\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| PostHog, Inc. | Product analytics — pageviews and in-app events. Engaged only after you accept analytics in the cookie banner, and stopped when you withdraw that. | United States | IP address, device and browser, pageviews and in-app events, user identifier, referrer |\n| Google Ireland Limited (Maps Platform) | Maps and geocoding for the map view of job results. The map loads directly in your browser, so the request goes to Google rather than through us. Engaged only when you open the map view. | Ireland, with processing on Google infrastructure including the United States | IP address, browser and device, the job location or search area you are viewing |\n| Google Ireland Limited (Gmail API) | One-click connection of a Google mailbox to the in-app inbox, which authorises us to read and send mail through your Google account. Engaged only if you connect a mailbox this way, and only where that option is offered to you. | Ireland, with processing on Google infrastructure including the United States | your Google account email address, OAuth access and refresh tokens, the contents of the mailbox you connect, including messages from and to other people |\n| Google Ireland Limited (sign-in) | Sign in with Google. Engaged only if you choose that provider, and only where it is offered on your sign-in screen. | Ireland, with processing on Google infrastructure including the United States | email address, name, profile picture, Google account identifier |\n| LinkedIn Ireland Unlimited Company | Sign in with LinkedIn, which returns your profile fields so we can pre-fill your Ever Hust profile. Engaged only if you choose that provider. | Ireland, with processing on LinkedIn infrastructure including the United States | email address, name, headline, profile picture, LinkedIn member identifier, the profile payload LinkedIn returns |\n| Meta Platforms Ireland Limited | Sign in with Facebook. Engaged only if you choose that provider, and only where it is offered on your sign-in screen. | Ireland, with processing on Meta infrastructure including the United States | email address, name, profile picture, Facebook account identifier |\n| X Corp. | Sign in with X. Engaged only if you choose that provider, and only where it is offered on your sign-in screen. | United States | email address, username, profile picture |\n| Google Ireland Limited (Analytics and Tag Manager) | Website measurement on the marketing site, in the environments where a measurement identifier is configured. Engaged only after you accept analytics. | Ireland, with processing on Google infrastructure including the United States | IP address, cookie identifier, pageviews and referrer, browser and device |\n| Google Ireland Limited, Mozilla Corporation or Apple Inc. | Delivery of web push notifications to the browser you allowed them in. Which of the three is involved is decided by your browser, not by us. Engaged only if you grant the notification permission, and the payload is encrypted before it leaves us. | Ireland or the United States, depending on the browser | the push endpoint identifier for that browser installation, an encrypted notification payload |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Hust yourself, you choose these providers and hold the credentials. **We are not a\nprocessor for anything in a deployment you run**, we do not receive that data, and we have no relationship\nwith the providers you configure.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Trigger.dev Ltd. | Managed background-job runtime. The hosted Service does not use it — our background jobs run on an instance we host ourselves — but a deployment you run can point at the Trigger.dev cloud. | as you configure it | job payloads, model prompts and logs from your own deployment |\n| Supabase, Inc. | Managed Postgres, realtime and storage. We run those components on our own infrastructure. A deployment you run can point at Supabase Cloud instead. | as you configure it | the whole application database of your own deployment |\n| Upstash, Inc. | Serverless Redis for distributed rate limiting. The software falls back to in-memory limiting when it is not configured, which is what we run. | as you configure it | the IP address or user identifier used as a rate-limit key |\n| Anthropic PBC, OpenAI, L.L.C., Google, OpenRouter, Inc. or another provider you configure | The models your deployment calls, under your own account and your own key. You choose which, and you agree that provider's terms. | as you configure it | prompts and completions from your deployment, including CV and job text |\n| Resend, Inc., ActiveCampaign (Postmark) or any SMTP relay you configure | Sending your deployment's transactional mail. | as you configure it | recipient email addresses and message contents |\n| MinIO you run, Amazon Web Services, Inc. (S3), Cloudflare, Inc. (R2) or another S3-compatible provider | Where your deployment stores uploaded files, including CVs. | as you configure it | uploaded files, including CVs |\n| Functional Software, Inc. d/b/a Sentry, PostHog, Inc. or another provider you configure | Error monitoring and analytics for your own deployment, under your own account. | as you configure it | diagnostics and usage events from your own deployment |\n| Stripe, Inc. or another payment provider you configure | Billing, if you charge for access to your own deployment. Your merchant account, not ours. | as you configure it | billing details of your own users |\n| The job boards, applicant tracking systems and company career endpoints you supply credentials for | Your deployment queries whichever sources you configure, using your own API keys and publisher identifiers, so those queries are attributable to you. | as you configure it | the search terms your users enter, your deployment's outbound IP address |\n\n### Your mailbox, and what does not happen to it\n\nEver Hust can connect to your mailbox. Because that is the most sensitive thing this product\ntouches, the sub-processor position around it is worth stating explicitly rather than leaving to be\ninferred from a table.\n\n- **Your mail provider is not our sub-processor.** You already have a relationship with whoever runs your\n mailbox. Connecting it authorises us to read from and send through it on your behalf; it does not put\n them in our supply chain, and their terms continue to govern their side.\n- **Message content is not sent to any third party for analysis by default.** Where you enable a feature\n that uses an AI provider, the provider is named in tier 2 and the feature description says what is sent.\n Nothing about your correspondence is passed to an analytics, advertising or enrichment provider — not in\n any tier, not under any setting.\n- **Your correspondents did not agree to any of this.** The privacy annex explains what that means and what\n we do about it. What matters here is that the list above is the complete set of parties who could\n receive it, and it is short on purpose.\n\nIf that ever changes, the change is announced under the notification process above before it takes effect,\nand you can object.\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://hust.so/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://hust.so/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 Hust, 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://hust.so/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://hust.so/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://hust.so/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.2 of the sub-processor list for\n[hust.so](https://hust.so), 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://hust.so/subprocessors](https://hust.so/subprocessors)."
|
|
165
|
+
"markdown": "## Why this page exists\n\nWhen you use the Ever Hust hosted service 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://hust.so/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 [hust.so](https://hust.so), for Ever Hust\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://hust.so/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 a provider contracts through a European establishment but processes\n elsewhere, this column says both, because the two are different facts and only naming the first would\n flatter us.\n- **Transfer mechanism** — for a provider outside the European Economic Area, the Chapter V instrument we\n actually rely on for that specific provider: an adequacy decision, the Standard Contractual Clauses, or\n nothing yet. **Where it reads \"To be confirmed\", we have not yet evidenced an instrument for that\n provider, and we would rather say so here than print one we cannot produce.** That is a live piece of\n work, not a formula. Providers established inside the EEA need no mechanism and say so. For the third\n tier the transfer is not ours at all — you choose the provider and hold the contract.\n The general rules behind this column are in the international transfers section of our\n [Privacy Policy](https://hust.so/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### Why this list is deliberately longer than it needs to be\n\n**We list providers we may engage, not only the ones engaged today.** Where we have configured a\nprovider, kept one available behind a feature flag, used one recently, or expect to use one for a\npurpose already described here, it appears in the tables below — even if no data has reached it this\nmonth, and even where we currently run the equivalent ourselves.\n\nWe do this on purpose, and you should read the tables with it in mind:\n\n- **A provider appearing here is not proof that your data has reached it.** It means the provider is\n within the scope of what we have told you we may do, at the tier shown. The tier is the part that\n tells you when it is engaged.\n- **Where we self-host something today** — our analytics, our job runner, our databases, our object\n storage — we say so, and we also name the hosted service we would move to, so that a later change is\n covered by a disclosure you have already seen rather than by a fresh surprise.\n- **The alternative is worse.** A list that names only today's exact set has to be re-issued, and\n re-consented, every time an engineer changes a setting. A list drawn slightly wide stays true through\n ordinary operational change, which is what makes it dependable.\n\n**What we will not do is use this as cover.** Breadth here does not license a purpose we have not\ndescribed, a category of data we have not listed, or a transfer without a mechanism. If we start\nsending a new *kind* of personal data, or sending it for a new *reason*, that is a change to this page\nand to the notice period below — not something the width of a table quietly absorbs.\n\nIf you need to know precisely which providers are live for your workspace today, rather than which ones\nmay be, ask us at privacy@ever.co and we will tell you.\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://hust.so/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 Hust\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination and the tunnel that is the only public route into our network. Every request to the website and to the application passes through it. | United States, with your connection terminated at the edge location nearest to you | Standard Contractual Clauses (EU 2021/914) | IP address, TLS and connection metadata, request URLs and headers, cookies in transit |\n| Stripe Payments Europe, Limited | Subscription checkout, recurring billing, invoices, refunds and payment fraud checks. Engaged when you buy a plan. The free tier never reaches it, and we never receive your full card number. | Ireland, with processing on Stripe infrastructure including the United States | Standard Contractual Clauses (EU 2021/914) | name, email address, billing address and country, card token and last four digits, tax identification number, subscription and invoice history, IP address at checkout |\n| OpenRouter, Inc. | Routes the assistant's model requests. It carries your chat messages, job description text, your CV text and the prompts behind evaluations, cover letters, tailored resumes, interview preparation and outreach drafts — then forwards each request to the upstream provider of the model in use. | United States, with onward processing by the upstream provider of the selected model | To be confirmed — we do not yet evidence a mechanism | chat messages, CV and profile text, job description text, generated output, user and session identifiers |\n| Anthropic, PBC | CV parsing. The full extracted text of a CV you upload is sent here on a direct call, outside the router above, to produce the structured profile. Also the default assistant model on paid plans. | United States | Standard Contractual Clauses (EU 2021/914) | the full text of your CV, name, email address, telephone number, location, employment history, education, skills |\n| Langfuse GmbH | Tracing and observability for the assistant. It receives complete model prompts and completions, which means CV text, job text and chat content, with the identifiers that tie a trace to a user. | Germany (European Union) | None needed — established in the EEA | model prompts and completions, CV, job and chat text contained in them, user and session identifiers |\n| Resend, Inc. | Delivery of the email we send you — address verification, sign-in, password reset, job alerts, application reminders and billing notices. It does not send anything from your connected mailbox. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message subject and body, delivery, bounce and complaint events |\n| Functional Software, Inc. d/b/a Sentry | Error and performance monitoring. Error context carries your user identifier and email address, so this is not anonymous telemetry and we do not describe it as such. | United States | Standard Contractual Clauses (EU 2021/914) | user identifier, email address, IP address, page or route, browser and device, stack traces and breadcrumbs |\n| GitHub, Inc. (a Microsoft Corporation company) | Source code, build pipeline and container registry. This is how the Service is built and shipped rather than where your data lives, and it is disclosed because it is still a third party. | United States | Standard Contractual Clauses (EU 2021/914) | none of your account or job-search data in the ordinary course, build and deployment metadata |\n| Automattic Inc. | Gravatar avatar fallback. Where you have not set a profile picture, your browser asks Gravatar for one using a hash of your email address. | United States | To be confirmed — we do not yet evidence a mechanism | a hash of your email address, IP address, browser and device |\n| Prospect One sp. z o.o. (jsDelivr) | Public content delivery network serving the API reference viewer on the developer documentation pages. Your browser fetches those assets directly, so the request discloses your address to it. | Poland, with delivery from edge locations worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, browser and device, the page you were on |\n| Cloudflare, Inc. (R2 object storage) | Holds the encrypted off-site copy of our backups - Postgres WAL and dumps, Velero, etcd, Proxmox configuration and MinIO mirrors - as the third tier of the backup chain (node8 NVMe, then Ceph RGW, then Cloudflare R2). Encrypted by us before it leaves our network. | United States | Standard Contractual Clauses (EU 2021/914) | client-side encrypted backup archives only - no plaintext is ever readable by the provider, the archives themselves derive from every category of data the products hold |\n| Google Ireland Limited (reCAPTCHA) | Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made. | Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com |\n| Clerk, Inc. | Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name. | United States | Standard Contractual Clauses (EU 2021/914) | name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored |\n| Tavily | The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain. | United States | To be confirmed — we do not yet evidence a mechanism | search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata |\n| ui-avatars.com | Generates placeholder avatars where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser. | UNKNOWN - not published by the provider | To be confirmed — we do not yet evidence a mechanism | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n| UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified | Second permitted origin for the Lottie animation runtime on the ever-works login and register pages. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Chargebee, Inc. - VERIFY; Chargebee Europe BV (Netherlands) is the EEA entity if it is the one contracting. | Handles subscription billing and invoicing for the hosted Gauzy service. | United States / Netherlands | To be confirmed — we do not yet evidence a mechanism | billing identity and address, plan, invoice and payment history |\n| Shopify International Limited | Runs the storefront and order pipeline for the shop product, holding customer, order and payment-status records. | Ireland (contracting) / Canada and United States (Shopify group) | Standard Contractual Clauses (EU 2021/914) | customer name, email address and shipping address, order and payment status, browsing and cart events on the storefront, cookies set by the storefront |\n| Upwork Global Inc. | The one posting source in the whole catalogue that we authenticate to. Freelance and gig postings are pulled from Upwork's API under an OAuth credential of ours, so those queries run as an identified account rather than anonymously, and they run on every scheduled ingestion because Upwork is in the default source list. It is a source we read from - nothing about you is sent to it. | United States | To be confirmed — we do not yet evidence a mechanism | our own OAuth account identity with Upwork, not yours, a generic job-title search term from our fixed rotation, our egress server IP address, none of your account, profile, CV, search or application data |\n| Google Ireland Limited (Google Maps Platform) | Server-side geocoding on the ingestion path. When a posting is newly collected, our own backend sends its city, state and country to the Geocoding API to turn that text into coordinates. This runs on a schedule with nobody present and there is no setting that removes it, which is why it sits here and not only in tier 2 with the browser-side map. | Ireland and the United States | Standard Contractual Clauses (EU 2021/914) | the city, state and country named in a job posting, our server's IP address and API key, none of your account, profile, CV or search data |\n\n### Tier 2 — engaged only when a feature or integration brings them in\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Lemon Squeezy, LLC | An AI-powered web search across a fixed list of job-board domains, wired in as one more posting source and present in the default source list. It is not engaged today because no API key is configured in any of our environments, so the plugin logs a warning and returns nothing - but that is one environment variable away from receiving our generic ingestion search terms, so we list it rather than wait. | United States (unverified) | Not our transfer — you choose the provider | generic job-title search terms from our fixed ingestion rotation, our egress server IP address and API key, none of your account, profile, CV or search data |\n| PostHog, Inc. | Product analytics — pageviews and in-app events. Engaged only after you accept analytics in the cookie banner, and stopped when you withdraw that. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, device and browser, pageviews and in-app events, user identifier, referrer |\n| Google Ireland Limited (Google Maps Platform) | The browser-side half of the same provider. The map on the job-results map view loads directly in your browser, so that request carries your address to Google rather than going through us, and it happens only when you open the map view. This row is about your browser only - the separate, unconditional server-side geocoding of every ingested posting is the tier 1 row above, and reading this row alone would leave you thinking Maps is engaged only by your own choice. | Ireland and the United States | Standard Contractual Clauses (EU 2021/914) | IP address, browser and device, the job location or search area you are viewing |\n| Google Ireland Limited (Google Workspace) | One-click connection of a Google mailbox to the in-app inbox, which authorises us to read and send mail through your Google account. Engaged only if you connect a mailbox this way, and only where that option is offered to you. | Ireland, with processing on Google infrastructure including the United States | Standard Contractual Clauses (EU 2021/914) | your Google account email address, OAuth access and refresh tokens, the contents of the mailbox you connect, including messages from and to other people |\n| Google Ireland Limited (sign-in) | Sign in with Google. Engaged only if you choose that provider, and only where it is offered on your sign-in screen. | Ireland, with processing on Google infrastructure including the United States | Standard Contractual Clauses (EU 2021/914) | email address, name, profile picture, Google account identifier |\n| LinkedIn Ireland Unlimited Company | Sign in with LinkedIn, which returns your profile fields so we can pre-fill your Ever Hust profile. Engaged only if you choose that provider. | Ireland, with processing on LinkedIn infrastructure including the United States | Standard Contractual Clauses (EU 2021/914) | email address, name, headline, profile picture, LinkedIn member identifier, the profile payload LinkedIn returns |\n| Meta Platforms Ireland Limited (Facebook Login) | Sign in with Facebook. Engaged only if you choose that provider, and only where it is offered on your sign-in screen. | Ireland, with processing on Meta infrastructure including the United States | Standard Contractual Clauses (EU 2021/914) | email address, name, profile picture, Facebook account identifier |\n| X Corp. (Twitter) | Sign in with X. Engaged only if you choose that provider, and only where it is offered on your sign-in screen. | United States | To be confirmed — we do not yet evidence a mechanism | email address, username, profile picture |\n| Google Ireland Limited (Analytics and Tag Manager) | Website measurement on the marketing site, in the environments where a measurement identifier is configured. Engaged only after you accept analytics. | Ireland, with processing on Google infrastructure including the United States | Standard Contractual Clauses (EU 2021/914) | IP address, cookie identifier, pageviews and referrer, browser and device |\n| Google Ireland Limited, Mozilla Corporation or Apple Inc. | Delivery of web push notifications to the browser you allowed them in. Which of the three is involved is decided by your browser, not by us. Engaged only if you grant the notification permission, and the payload is encrypted before it leaves us. | Ireland or the United States, depending on the browser | Standard Contractual Clauses (EU 2021/914) | the push endpoint identifier for that browser installation, an encrypted notification payload |\n| Google Ireland Limited (Sign in with Google) | Authenticates a user who chooses 'sign in with Google', returning their email, name and picture, and in ever-rec also exports recordings to the user's own Google Drive when they connect it. | Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | email address, name and profile picture, Google account identifier, OAuth access and refresh tokens, Google Drive file metadata and content the user chooses to export, where the Drive scope is granted (ever-rec) |\n| Algolia SAS | Answers the search box on the documentation sites, receiving each reader's query and IP where Algolia credentials are configured. | France (EEA) or United States, depending on the contracting entity and the index region | To be confirmed — we do not yet evidence a mechanism | search queries typed by the reader, IP address, user agent, indexed page content |\n| Google Ireland Limited (Google Fonts) | Delivers typefaces to the visitor's browser at page load on the properties that hot-link them, disclosing the visitor's IP to Google before any consent choice. | Ireland (contracting entity); processing in Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| Vercel Inc. | Hosts the cloc platform; routes AI prompts to downstream model providers for gauzy through the AI Gateway; and remains the deployment target of surviving workflows and DNS delegations for several frontends that have since moved to our own cluster. | United States | Standard Contractual Clauses (EU 2021/914) | for cloc: full application traffic and runtime data (the platform actually runs there), IP address and user agent of visitors where a site is served from Vercel, page-view and Web Vitals events, for gauzy: prompt content and model responses routed through the AI Gateway, plus routing and usage metadata, deployment metadata |\n| DigitalOcean, LLC | Serves desktop installer downloads from the gauzy.co download page, holds media in Spaces where a deployment selects it as the file provider, still carries legacy container images and gated deploy workflows, and for cloc provisions servers on a customer's behalf. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files, screenshots and captured media held in Spaces, IP address and user agent of anyone downloading an asset or a desktop installer, container images and build metadata (no personal data), for cloc: server handles, sizes and lifecycle state of infrastructure provisioned on a customer's behalf |\n| Uptime Robot Service Provider Ltd - UNVERIFIED. The commonly cited registration is Cyprus (Nicosia); confirm from the current Terms or Imprint before publishing any location claim. | Hosts the public status page at status.<our-domain>, so anyone who opens it hands their IP and user agent to the vendor. | Cyprus (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address and user agent of every visitor to a status page, cookies set by the status page, monitored endpoint URLs and response metadata |\n| Wasabi Technologies, Inc. | Holds avatars, task attachments and time-tracker screenshots wherever the platform's or a tenant's file provider is set to Wasabi. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files and document attachments, avatars, employee time-tracker screenshots and captured monitoring media |\n| Cloudinary Ltd. | Stores and transforms images and video where a deployment's or the platform's media provider is set to Cloudinary, and serves them to viewers directly from its own CDN. | Israel | Adequacy decision — Israel | uploaded images and video, screenshots and captured media, IP address and user agent of every viewer fetching an asset |\n| UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty | Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Twilio Inc. (SendGrid) | Sends and tracks marketing or transactional email for gauzy.co through dedicated sending, reply and link-tracking subdomains, and stands as an alternative sender for githands. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, open and click tracking events (links.gauzy.co), recipient IP and user agent via tracking pixels |\n| Twilio Inc. (Programmable Messaging) | Sends SMS where a tenant configures Twilio as its SMS gateway using its own account SID and token. | United States | Standard Contractual Clauses (EU 2021/914) | recipient telephone number, message body, which can contain a capture link or workspace content, delivery and status metadata |\n| Jitsu Labs, Inc. | Collects product events into an event pipeline where a write key is configured, on Jitsu's US cloud. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user and workspace identifiers, page and feature events, device and browser characteristics |\n| Hound Technology, Inc. (d/b/a Honeycomb.io) | Receives OpenTelemetry traces from the API where Honeycomb is selected as the OTEL provider, including request URLs and database statements that routinely carry identifiers. | United States | Standard Contractual Clauses (EU 2021/914) | trace and span data including request URLs, route parameters and DB statements, service and host identifiers, anything a span attribute carries, which can include user and tenant ids |\n| SigNoz Inc. (Delaware, USA) for SigNoz Cloud; SigNoz itself is Apache-2.0 and self-hostable. | Receives OpenTelemetry traces, metrics and logs from the API wherever the OTLP endpoint is configured, including route parameters and SQL text. | United States | To be confirmed — we do not yet evidence a mechanism | distributed traces including HTTP routes, query strings and SQL statements, service and host metadata, metrics and logs, anything attached as a span attribute |\n| Better Stack, s.r.o. | Receives shipped application logs where a log token is configured, including the ChatGPT connector service in ever-teams and the cloc platform's observability pipeline. | Czech Republic | None needed — established in the EEA | application log lines, which may embed user ids, request paths and IP addresses, uptime probe results |\n| Google Ireland Limited (Gemini API) | Generates completions for the in-application AI assistant where a customer connects a Gemini key, through the AI Studio endpoint rather than Vertex AI. | Ireland (contracting entity); processing in United States (AI Studio) / Ireland (Vertex AI) | Standard Contractual Clauses (EU 2021/914) | prompt content, which can carry workspace, HR and candidate data, model responses |\n| Mistral AI SAS | Generates completions where the Mistral plugin is enabled for a Work. | France | None needed — established in the EEA | prompt text, completions |\n| X.AI LLC | Generates completions where a customer selects Grok and supplies a key. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, model responses |\n| Groq, Inc. | Serves completions where a user supplies a Groq key and selects it as the provider. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, model responses |\n| Together Computer, Inc. (trading as Together AI) | Serves completions where a user selects Together as the provider and supplies a key, called from our own Next.js server route. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, including chat message text, model responses |\n| Vercel Inc. | Routes AI prompts from the Gauzy assistant to whichever downstream model provider the customer's selected model resolves to. | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, model responses, request routing and usage metadata |\n| Intuition Machines, Inc. (hCaptcha) | Scores signup and login attempts wherever the CAPTCHA provider is set to hCaptcha. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and browser/device fingerprint signals, mouse, touch and timing interaction signals, challenge solution and token |\n| Microsoft Corporation (Microsoft Entra ID) | Authenticates a user or administrator who chooses a Microsoft work or personal account, reading profile details from Microsoft Graph, where FEATURE_MICROSOFT_LOGIN is enabled. | United States | Standard Contractual Clauses (EU 2021/914) | email address and display name, Microsoft tenant identifier and user object id, OAuth access and refresh tokens, directory profile fields returned by Graph within the granted scope |\n| Okta, Inc. (Auth0) | Authenticates an organisation's people where that organisation chooses to route sign-in through its own hosted Auth0 tenant. | United States | Standard Contractual Clauses (EU 2021/914) | email address and profile, OAuth/OIDC tokens, login IP address, device and user agent, authentication and MFA event logs |\n| PayPal (Europe) S.à r.l. et Cie, S.C.A. | Takes payments for a commerce deployment, where the merchant running that deployment contracts with PayPal directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Luxembourg (EEA users) / United States (PayPal, Inc.) | None needed — established in the EEA | payer identity and email address, transaction amount and order reference, payment status and history |\n| Atlassian Pty Ltd (Jira, Trello) | Syncs tasks, issues and attachments with a Jira or Trello site the customer connects using its own account. | Australia (Atlassian Pty Ltd) / Netherlands (Atlassian B.V.) / United States (Atlassian, Inc.) | Standard Contractual Clauses (EU 2021/914) | issue, project, card and board records, reporter and assignee identity, attachments, screenshots and recordings pushed to an issue, API key and OAuth tokens |\n| Slack Technologies, LLC (a Salesforce, Inc. company) | Posts notifications into, and reads events from, a Slack workspace the customer connects by installing our app into its own workspace. | United States (group); Ireland (EEA contracting for Slack's own customers) | Standard Contractual Clauses (EU 2021/914) | channel and workspace identifiers, message content we post or receive, Slack user identity, including member email addresses, OAuth tokens and webhook payloads, shared recordings, screenshots and their links (ever-rec) |\n| Zapier, Inc. | Forwards workspace records into whatever third-party apps a customer wires into a Zap, so the onward destinations are the customer's choice and outside our contract. | United States | Standard Contractual Clauses (EU 2021/914) | records pushed through a Zap (tasks, timesheets, contacts), OAuth tokens and authorization codes, arbitrary event payloads forwarded to whatever apps the customer wires up |\n| Activepieces Inc. | Runs automation flows that read and receive whatever workspace records a customer wires in, on Activepieces' US cloud unless repointed at a self-hosted instance. | United States / Canada | Standard Contractual Clauses (EU 2021/914) | records pushed through a flow, which can be any workspace data, API keys, webhook payloads |\n| Celonis SE (Make.com) | Runs automation scenarios that read and receive whatever workspace records the customer wires in, from EU infrastructure. | Germany / Czech Republic | None needed — established in the EEA | records pushed through a scenario, webhook payloads, OAuth tokens |\n| Noti-Fire Apps Ltd. (Novu) | The in-application notification inbox and a delivery channel for notifications, where it is configured against Novu's hosted service rather than an instance you run. | Israel | Adequacy decision — Israel | a hashed subscriber identifier, computed server-side under NOVU_SECRET_KEY, notification content, email address where Novu is used as a delivery channel |\n| Plausible Insights OÜ | Cookieless site analytics on a Work site, where the Work Owner enables it. | Estonia | None needed — established in the EEA | page views and referrer, coarse device and country, derived and not stored as an IP address |\n| HubSpot, Inc. | Two-way contact synchronisation, engaged only when a customer connects its own HubSpot account. Data moves in both directions once connected. | United States (HubSpot, Inc.) / Ireland (HubSpot Ireland Limited, for HubSpot's own EEA customers) | Standard Contractual Clauses (EU 2021/914) | contact and company records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Chatwoot Inc. | Runs the support chat widget that visitors and signed-in users type into, receiving the whole conversation plus the page context. | United States | Standard Contractual Clauses (EU 2021/914) | visitor or user name and email when supplied, full chat message content, IP address, page URL and browser details |\n| iubenda s.r.l. | Delivers hosted legal documents to visitors who open the /legal route in the Gauzy application, which still fetches the policy from iubenda in the visitor's browser. | Italy | None needed — established in the EEA | IP address, user agent, consent preferences and the timestamp of the choice |\n| Lemon Squeezy, LLC | Takes payments from a Work site's own visitors as merchant of record where the Work Owner connects it, so the Work Owner contracts with it directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | United States (Delaware) | Not our transfer — you choose the provider | name and email address, billing address and tax location, payment identifiers and purchase history, card data entered on Lemon Squeezy's own hosted checkout and never reaching us |\n| Polar Software Inc. | An alternative payment and subscription provider for a Work site's own visitors, connected and contracted by the Work Owner. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | United States (Delaware) | Not our transfer — you choose the provider | name and email address, billing and tax location, payment identifiers and subscription history, card data entered on Polar's own hosted checkout and never reaching us |\n| SolidGate | A further card payment option for a Work site's own visitors, where the Work Owner enables it and contracts with the payment institution directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Cyprus (EEA) | None needed — established in the EEA | cardholder name, email address, billing address, payment identifiers |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Hust yourself, you choose these providers and hold the credentials. **We are not a\nprocessor for anything in a deployment you run**, we do not receive that data, and we have no relationship\nwith the providers you configure.\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Trigger.dev Ltd. | Managed background-job runtime. The hosted Service does not use it — our background jobs run on an instance we host ourselves — but a deployment you run can point at the Trigger.dev cloud. | as you configure it | Not our transfer — you choose the provider | job payloads, model prompts and logs from your own deployment |\n| Supabase, Inc. | Managed Postgres, realtime and storage. We run those components on our own infrastructure. A deployment you run can point at Supabase Cloud instead. | as you configure it | Not our transfer — you choose the provider | the whole application database of your own deployment |\n| Upstash, Inc. | Serverless Redis for distributed rate limiting. The software falls back to in-memory limiting when it is not configured, which is what we run. | as you configure it | Not our transfer — you choose the provider | the IP address or user identifier used as a rate-limit key |\n| Anthropic PBC, OpenAI, L.L.C., Google, OpenRouter, Inc. or another provider you configure | The models your deployment calls, under your own account and your own key. You choose which, and you agree that provider's terms. | as you configure it | Not our transfer — you choose the provider | prompts and completions from your deployment, including CV and job text |\n| Resend, Inc., ActiveCampaign (Postmark) or any SMTP relay you configure | Sending your deployment's transactional mail. | as you configure it | Not our transfer — you choose the provider | recipient email addresses and message contents |\n| MinIO you run, Amazon Web Services, Inc. (S3), Cloudflare, Inc. (R2) or another S3-compatible provider | Where your deployment stores uploaded files, including CVs. | as you configure it | Not our transfer — you choose the provider | uploaded files, including CVs |\n| Functional Software, Inc. d/b/a Sentry, PostHog, Inc. or another provider you configure | Error monitoring and analytics for your own deployment, under your own account. | as you configure it | Not our transfer — you choose the provider | diagnostics and usage events from your own deployment |\n| Stripe, Inc. or another payment provider you configure | Billing, if you charge for access to your own deployment. Your merchant account, not ours. | as you configure it | Not our transfer — you choose the provider | billing details of your own users |\n| The Rocket Science Group LLC d/b/a Mailchimp | Your deployment queries whichever sources you configure, using your own API keys and publisher identifiers, so those queries are attributable to you. | as you configure it | Not our transfer — you choose the provider | the search terms your users enter, your deployment's outbound IP address |\n| Cloudflare, Inc. (Turnstile) | Checks that the person completing registration, onboarding or an anonymous flow is not a bot; on ever-works the API refuses the anonymous flow when no CAPTCHA provider is configured, which is why it is unconditional there. | United States | Not our transfer — you choose the provider | IP address, user agent and device signals, mouse, touch and timing interaction signals, Turnstile challenge cookie |\n| OpenAI, L.L.C. | Generates completions and transcribes audio for in-application AI features, using either a platform-held key (cloc) or a key the customer supplies (gauzy, ever-works, ever-teams, hust). | United States | Not our transfer — you choose the provider | prompt content, including workspace records, job posts, candidate and employee profile text, issue and task text and chat messages, audio submitted for transcription, model responses, OAuth device-auth identity for the Codex CLI plugin |\n| none in a self-hosted deployment - the reader (or we) runs the runtime. Ollama Inc. (US) publishes the software and would become a processor only if a hosted Ollama service were adopted. | Runs open-weight models inside the deployment itself, so prompts reach no third party at all. | n/a (self-hosted); United States for Ollama Inc. | Not our transfer — you choose the provider | chat and prompt text, which never leaves the deployment |\n| Red Hat, Inc. (Keycloak) | Authenticates users through a Keycloak realm that the organisation running the deployment operates itself. | United States (Red Hat, Inc.) / wherever the reader runs the realm | Not our transfer — you choose the provider | email address and profile, OIDC tokens |\n| Mixpanel, Inc. | Records in-app screens and named events - 'Order Delivered' from the courier application, 'Order Failed' from the merchant tablet and similar - against a device identifier, where the operator configures a Mixpanel token and publishes a build containing it. | United States | Not our transfer — you choose the provider | device identifier, screens viewed and in-app events, IP address, user identifier once the person has signed in, the Mixpanel project token, which is compiled into the distributed binary |\n| Intercom, Inc. | Runs the in-application support conversation in the shopping, merchant and courier mobile applications through cordova-plugin-intercom / @ionic-native/intercom, where the operator supplies Intercom credentials. | United States (Intercom, Inc.) / Ireland (Intercom R&D Unlimited Company) | Not our transfer — you choose the provider | user identifier and email address, full support conversation content, device and application context, the operator's Intercom app id and API key |\n\n### The 1,832 job sources, and why almost none of them is in a table above\n\nEver Hust aggregates job postings from **1,832 sources** — **180 applicant tracking systems**,\n**1,540 named employers' own career endpoints**, and **112 job boards, feeds and public registries**. That\nis a large number of third parties for a page like this not to list, so here is the reasoning, because it\nturns entirely on one fact.\n\n**The flow is one-way. We read; we never send.** A sub-processor is a party that processes personal data\n**on our behalf and on our instructions**. These sources are given no personal data to process and no\ninstruction to carry out. On each scheduled request what leaves us is a generic job title from a fixed\nrotation of roughly thirty, a country and radius, our own server's IP address and a browser-like user\nagent — and nothing else. **No user's name, email address, account identifier, session, CV, profile,\napplication or typed search is ever part of that traffic.** They are recipients of a query about a job\ntitle. They are not processors, and calling them one would tell you your data reaches 1,832 companies that\nit never touches.\n\nThree consequences worth stating rather than leaving to be inferred:\n\n- **Your own search never leaves our network.** Searching in the product queries our own database of\n already-collected postings. It is not fanned out to the boards.\n- **The data flowing on this path is mostly other people's, and it flows inwards.** What comes back is a\n posting written by someone else, and it routinely names a recruiter or a hiring manager. What we do with\n that — including the fact that we extract email addresses out of the posting text into a field of their\n own — is set out in the [Privacy Policy](https://hust.so/privacy), together with the lawful basis and how\n a person named in a posting gets themselves removed.\n- **A source can have us stop.** Write to legal@ever.co. That route is open to boards, applicant\n tracking systems and employers whether or not they are customers.\n\n**One source is different, and it has a row.** With **Upwork** we hold an OAuth credential, so those queries\nrun as an identified account of ours rather than anonymously. It receives nothing about you either, but it\nreceives something about **us**, and that is enough to earn a place in tier 1 rather than a footnote.\n\n**One further provider is engaged by the collection itself**, and it is not a source: as each newly\ncollected posting is stored, our backend sends its city, state and country to **Google's Geocoding API** to\nturn that text into coordinates. That happens on the schedule, with nobody present, and no setting removes\nit — which is why Google Maps Platform now appears in tier 1 for that path, alongside its tier 2 row for\nthe map that loads in your own browser. Two different engagements of the same provider, listed separately\nbecause only one of them is your choice.\n\n### The engine that does the collecting is ours, and it is open source\n\nThe collection is done by **Ever Jobs**, a separate project of ours published under the **MIT licence** at\n[github.com/ever-jobs/ever-jobs](https://github.com/ever-jobs/ever-jobs). **We run it ourselves**, inside\nour own cluster, with no route in from the internet and no third party operating any part of it.\n\nThat is why it is absent from every table above: **there is no vendor to disclose.** It is not a data\nsupplier we buy a feed from, not a hosted aggregation service, and not somebody else's API we resell. It\nholds no account and no identity, keeps nothing between runs, and writes its output into our own database.\nIf you want to know precisely what it sends and what it stores, the source is published and you can read it\nrather than take our word for it.\n\n### Your mailbox, and what does not happen to it\n\nEver Hust can connect to your mailbox. Because that is the most sensitive thing this product\ntouches, the sub-processor position around it is worth stating explicitly rather than leaving to be\ninferred from a table.\n\n- **Your mail provider is not our sub-processor.** You already have a relationship with whoever runs your\n mailbox. Connecting it authorises us to read from and send through it on your behalf; it does not put\n them in our supply chain, and their terms continue to govern their side.\n- **Message content is not sent to any third party for analysis by default.** Where you enable a feature\n that uses an AI provider, the provider is named in tier 2 and the feature description says what is sent.\n Nothing about your correspondence is passed to an analytics, advertising or enrichment provider — not in\n any tier, not under any setting.\n- **Your correspondents did not agree to any of this.** The privacy annex explains what that means and what\n we do about it. What matters here is that the list above is the complete set of parties who could\n receive it, and it is short on purpose.\n\nIf that ever changes, the change is announced under the notification process above before it takes effect,\nand you can object.\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://hust.so/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://hust.so/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 Hust, 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://hust.so/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://hust.so/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://hust.so/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.2 of the sub-processor list for\n[hust.so](https://hust.so), 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://hust.so/subprocessors](https://hust.so/subprocessors)."
|
|
154
166
|
}
|