@ever-co/legal 0.1.0 → 0.1.1

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.
Files changed (146) hide show
  1. package/dist/content/aup/ever-corporate/en.html +2 -2
  2. package/dist/content/aup/ever-corporate/en.json +3 -3
  3. package/dist/content/aup/ever-demand/en.html +2 -2
  4. package/dist/content/aup/ever-demand/en.json +3 -3
  5. package/dist/content/aup/ever-rec/en.html +2 -2
  6. package/dist/content/aup/ever-rec/en.json +3 -3
  7. package/dist/content/aup/ever-teams/en.html +2 -2
  8. package/dist/content/aup/ever-teams/en.json +3 -3
  9. package/dist/content/aup/ever-works/en.html +2 -2
  10. package/dist/content/aup/ever-works/en.json +3 -3
  11. package/dist/content/aup/everiq/en.html +2 -2
  12. package/dist/content/aup/everiq/en.json +3 -3
  13. package/dist/content/aup/gauzy/en.html +2 -2
  14. package/dist/content/aup/gauzy/en.json +3 -3
  15. package/dist/content/aup/githands/en.html +2 -2
  16. package/dist/content/aup/githands/en.json +3 -3
  17. package/dist/content/aup/hust/en.html +2 -2
  18. package/dist/content/aup/hust/en.json +3 -3
  19. package/dist/content/aup/traduora/en.html +2 -2
  20. package/dist/content/aup/traduora/en.json +3 -3
  21. package/dist/content/cookies/ever-corporate/en.html +16 -1
  22. package/dist/content/cookies/ever-corporate/en.json +3 -3
  23. package/dist/content/cookies/ever-demand/en.html +16 -1
  24. package/dist/content/cookies/ever-demand/en.json +3 -3
  25. package/dist/content/cookies/ever-rec/en.html +16 -1
  26. package/dist/content/cookies/ever-rec/en.json +3 -3
  27. package/dist/content/cookies/ever-teams/en.html +16 -1
  28. package/dist/content/cookies/ever-teams/en.json +3 -3
  29. package/dist/content/cookies/ever-tech/en.html +16 -1
  30. package/dist/content/cookies/ever-tech/en.json +3 -3
  31. package/dist/content/cookies/ever-works/en.html +16 -1
  32. package/dist/content/cookies/ever-works/en.json +3 -3
  33. package/dist/content/cookies/everiq/en.html +16 -1
  34. package/dist/content/cookies/everiq/en.json +3 -3
  35. package/dist/content/cookies/gauzy/en.html +16 -1
  36. package/dist/content/cookies/gauzy/en.json +3 -3
  37. package/dist/content/cookies/githands/en.html +16 -1
  38. package/dist/content/cookies/githands/en.json +3 -3
  39. package/dist/content/cookies/hust/en.html +16 -1
  40. package/dist/content/cookies/hust/en.json +3 -3
  41. package/dist/content/cookies/traduora/en.html +16 -1
  42. package/dist/content/cookies/traduora/en.json +3 -3
  43. package/dist/content/dpa/ever-demand/en.html +2 -2
  44. package/dist/content/dpa/ever-demand/en.json +3 -3
  45. package/dist/content/dpa/ever-rec/en.html +2 -2
  46. package/dist/content/dpa/ever-rec/en.json +3 -3
  47. package/dist/content/dpa/ever-teams/en.html +2 -2
  48. package/dist/content/dpa/ever-teams/en.json +3 -3
  49. package/dist/content/dpa/ever-works/en.html +2 -2
  50. package/dist/content/dpa/ever-works/en.json +3 -3
  51. package/dist/content/dpa/gauzy/en.html +2 -2
  52. package/dist/content/dpa/gauzy/en.json +3 -3
  53. package/dist/content/dpa/githands/en.html +2 -2
  54. package/dist/content/dpa/githands/en.json +3 -3
  55. package/dist/content/dpa/hust/en.html +2 -2
  56. package/dist/content/dpa/hust/en.json +3 -3
  57. package/dist/content/privacy/ever-corporate/en.html +3 -9
  58. package/dist/content/privacy/ever-corporate/en.json +3 -3
  59. package/dist/content/privacy/ever-demand/en.html +3 -3
  60. package/dist/content/privacy/ever-demand/en.json +3 -3
  61. package/dist/content/privacy/ever-rec/en.html +3 -9
  62. package/dist/content/privacy/ever-rec/en.json +3 -3
  63. package/dist/content/privacy/ever-teams/en.html +3 -3
  64. package/dist/content/privacy/ever-teams/en.json +3 -3
  65. package/dist/content/privacy/ever-tech/en.html +3 -9
  66. package/dist/content/privacy/ever-tech/en.json +3 -3
  67. package/dist/content/privacy/ever-works/en.html +3 -3
  68. package/dist/content/privacy/ever-works/en.json +3 -3
  69. package/dist/content/privacy/everiq/en.html +3 -3
  70. package/dist/content/privacy/everiq/en.json +3 -3
  71. package/dist/content/privacy/gauzy/en.html +3 -3
  72. package/dist/content/privacy/gauzy/en.json +3 -3
  73. package/dist/content/privacy/githands/en.html +3 -3
  74. package/dist/content/privacy/githands/en.json +3 -3
  75. package/dist/content/privacy/hust/en.html +3 -3
  76. package/dist/content/privacy/hust/en.json +3 -3
  77. package/dist/content/privacy/traduora/en.html +3 -3
  78. package/dist/content/privacy/traduora/en.json +3 -3
  79. package/dist/content/refund/ever-works/en.html +2 -2
  80. package/dist/content/refund/ever-works/en.json +3 -3
  81. package/dist/content/refund/gauzy/en.html +2 -2
  82. package/dist/content/refund/gauzy/en.json +3 -3
  83. package/dist/content/refund/githands/en.html +2 -2
  84. package/dist/content/refund/githands/en.json +3 -3
  85. package/dist/content/refund/hust/en.html +2 -2
  86. package/dist/content/refund/hust/en.json +3 -3
  87. package/dist/content/security/ever-demand/en.html +1 -1
  88. package/dist/content/security/ever-demand/en.json +3 -3
  89. package/dist/content/security/ever-rec/en.html +1 -1
  90. package/dist/content/security/ever-rec/en.json +3 -3
  91. package/dist/content/security/ever-teams/en.html +1 -1
  92. package/dist/content/security/ever-teams/en.json +3 -3
  93. package/dist/content/security/ever-works/en.html +1 -1
  94. package/dist/content/security/ever-works/en.json +3 -3
  95. package/dist/content/security/gauzy/en.html +1 -1
  96. package/dist/content/security/gauzy/en.json +3 -3
  97. package/dist/content/security/githands/en.html +1 -1
  98. package/dist/content/security/githands/en.json +3 -3
  99. package/dist/content/security/hust/en.html +1 -1
  100. package/dist/content/security/hust/en.json +3 -3
  101. package/dist/content/subprocessors/ever-corporate/en.html +1 -7
  102. package/dist/content/subprocessors/ever-corporate/en.json +3 -3
  103. package/dist/content/subprocessors/ever-demand/en.html +1 -1
  104. package/dist/content/subprocessors/ever-demand/en.json +3 -3
  105. package/dist/content/subprocessors/ever-rec/en.html +1 -7
  106. package/dist/content/subprocessors/ever-rec/en.json +3 -3
  107. package/dist/content/subprocessors/ever-teams/en.html +1 -1
  108. package/dist/content/subprocessors/ever-teams/en.json +3 -3
  109. package/dist/content/subprocessors/ever-tech/en.html +1 -7
  110. package/dist/content/subprocessors/ever-tech/en.json +3 -3
  111. package/dist/content/subprocessors/ever-works/en.html +1 -1
  112. package/dist/content/subprocessors/ever-works/en.json +3 -3
  113. package/dist/content/subprocessors/everiq/en.html +1 -1
  114. package/dist/content/subprocessors/everiq/en.json +3 -3
  115. package/dist/content/subprocessors/gauzy/en.html +1 -1
  116. package/dist/content/subprocessors/gauzy/en.json +3 -3
  117. package/dist/content/subprocessors/githands/en.html +1 -1
  118. package/dist/content/subprocessors/githands/en.json +3 -3
  119. package/dist/content/subprocessors/hust/en.html +1 -1
  120. package/dist/content/subprocessors/hust/en.json +3 -3
  121. package/dist/content/subprocessors/traduora/en.html +1 -1
  122. package/dist/content/subprocessors/traduora/en.json +3 -3
  123. package/dist/content/tos/ever-corporate/en.html +3 -3
  124. package/dist/content/tos/ever-corporate/en.json +3 -3
  125. package/dist/content/tos/ever-demand/en.html +3 -3
  126. package/dist/content/tos/ever-demand/en.json +3 -3
  127. package/dist/content/tos/ever-rec/en.html +3 -3
  128. package/dist/content/tos/ever-rec/en.json +3 -3
  129. package/dist/content/tos/ever-teams/en.html +3 -3
  130. package/dist/content/tos/ever-teams/en.json +3 -3
  131. package/dist/content/tos/ever-tech/en.html +3 -3
  132. package/dist/content/tos/ever-tech/en.json +3 -3
  133. package/dist/content/tos/ever-works/en.html +3 -3
  134. package/dist/content/tos/ever-works/en.json +3 -3
  135. package/dist/content/tos/everiq/en.html +3 -3
  136. package/dist/content/tos/everiq/en.json +3 -3
  137. package/dist/content/tos/gauzy/en.html +3 -3
  138. package/dist/content/tos/gauzy/en.json +3 -3
  139. package/dist/content/tos/githands/en.html +3 -3
  140. package/dist/content/tos/githands/en.json +3 -3
  141. package/dist/content/tos/hust/en.html +3 -3
  142. package/dist/content/tos/hust/en.json +3 -3
  143. package/dist/content/tos/traduora/en.html +3 -3
  144. package/dist/content/tos/traduora/en.json +3 -3
  145. package/dist/index.json +144 -144
  146. package/package.json +50 -50
@@ -6,9 +6,9 @@
6
6
  "entity": "Ever Technologies LTD",
7
7
  "entityId": "ever-technologies-bg",
8
8
  "locale": "en",
9
- "version": "1.0.0",
9
+ "version": "1.0.1",
10
10
  "effectiveDate": "2026-08-02",
11
- "sha256": "83ef2a9c56348e4ef9a989335de507148c2ed7ad7af66bdd0b5559f531d2eefb",
11
+ "sha256": "6e6eb5852e828f4f9f51a2d117fbe6547980e01a89373c9123ef7b0a2512cfdf",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/subprocessors/010-purpose",
@@ -150,5 +150,5 @@
150
150
  }
151
151
  ],
152
152
  "path": "content/subprocessors/githands/en.html",
153
- "markdown": "## Why this page exists\n\nWhen you use GitHands Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://githands.com/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 [githands.com](https://githands.com), for GitHands\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://githands.com/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://githands.com/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://githands.com/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: GitHands\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 infrastructure. Every request to any GitHands hostname passes through it. | United States, with edge termination worldwide | IP address, connection and TLS metadata, full request URLs and headers, cookies in transit |\n| GitHub, Inc. | Three distinct roles. It hosts our source code, our container images and our build pipeline. It is the identity provider when a customer signs in with GitHub. And its public API is the primary source from which the developer database is built — profiles, stargazer and forker lists, contributor and participant lists, public commit metadata and public event streams. | United States | the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity |\n| Resend, Inc. | Delivery of outbound email — account and invitation mail, and the campaign messages a customer sends through the Service's default sending path — together with the delivery, open, click, bounce, complaint and reply events that come back. | United States | recipient email address and name, personalised subject line and message body, delivery, open, click, bounce and unsubscribe events, recipient IP address and user agent captured by open and click tracking, the content of a reply |\n| OpenRouter, Inc. | Routing of every AI request the Service makes to the model provider selected for it. This is the only AI provider configured in the hosted Service. OpenRouter forwards the prompt on to the upstream model provider it routes to, and that provider receives the same content. | United States, and onward to the selected model provider | developer names, usernames, email addresses, biographies and repository lists embedded in prompts, drafted outreach messages and the inbound replies being classified, customer chat messages with the in-product assistant |\n| Langfuse GmbH | Observability for AI requests — the full prompt and the full completion for each call are recorded as a trace so we can debug quality and cost. That means the same personal data that goes to the model provider is also stored here, in readable form. | Germany | complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace |\n| Functional Software, Inc. dba Sentry | Application error monitoring and performance tracing. Browser reports are sent to a path on our own domain and forwarded on, so that an extension blocking third-party requests does not silently hide our errors from us. Server-side logging is enabled, so console output can travel with a report. | United States | IP address and user agent, user identifier and email address attached as error context, URL and route, stack traces and breadcrumbs, console output, which can carry fragments of whatever request failed |\n| PostHog, Inc. | Product analytics — which pages and features are used, where people abandon a flow, and what fails. Captured both in the browser and on our servers. Consent-gated in the browser. | United States | IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer |\n| Jitsu Labs, Inc. | A second product-analytics event pipeline. Events are collected through an endpoint on the githands.com domain rather than a vendor hostname, which is worth saying plainly: an endpoint on our own domain that forwards to somebody else should never be a surprise. Consent-gated. | United States | IP address and user agent, in-product events and their properties, user identifier |\n| Trigger.dev Ltd. | The managed runtime that executes background work — extraction runs, enrichment, scoring, sequence steps and scheduled jobs. Job payloads and run logs are held there, and the runtime holds the credentials it needs to reach our database. | United Kingdom | job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data |\n| ui-avatars.com | Generated placeholder avatars, used 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. | Not published by the provider | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Google LLC | Sign in with Google. Engaged only where an individual chooses that sign-in method. | United States | email address, name, profile picture URL, Google account identifier |\n| LinkedIn Corporation | Sign in with LinkedIn, and the delivery of LinkedIn-hosted profile images where a signed-in user has one. Engaged only where an individual chooses that sign-in method. | United States | email address, name and profile fields, profile picture URL, LinkedIn member identifier |\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 | 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| Salesforce, Inc. | Two-way contact synchronisation, engaged only when a customer connects its own Salesforce organisation. | United States | contact and account records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Slack Technologies, LLC | Workspace notifications and in-Slack actions, engaged only when a customer installs the Slack application into its own workspace. | United States | workspace, channel and user identifiers, the notification content we send |\n| Stripe, Inc. | Payments and subscription billing. **Not engaged today** — the hosted Service is free, no payment method is collected and nothing is charged. Stripe becomes a sub-processor only if and when paid plans are switched on, and we will give notice before that happens. | United States | billing name and address, country and tax identification number, payment method token and card last four digits, invoice and subscription history |\n| Twilio SendGrid | An alternative outbound sending provider. The Service can be configured to send through it instead of the default. Not configured in the hosted Service. | United States | recipient email address and name, message content, delivery and engagement events |\n| Sinch Mailgun | An alternative outbound sending provider. Not configured in the hosted Service. | United States, with an optional European region | recipient email address and name, message content, delivery events |\n| Amazon Web Services, Inc. | Amazon SES as an alternative outbound sending provider, with Amazon SNS carrying bounce and complaint notifications back. Not configured in the hosted Service. | United States | recipient email address and name, message content, bounce and complaint events |\n| ActiveCampaign (Postmark) | An alternative outbound sending provider. Not configured in the hosted Service. | United States | recipient email address and name, message content, delivery events |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run GitHands on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| The email sending provider you choose | A self-hosted installation has no sending path of ours to fall back on — we removed the shared sending address deliberately. You bring your own sending account and your own verified sending domain. The software supports Resend, Twilio SendGrid, Sinch Mailgun, Amazon SES, Postmark and a plain SMTP relay. | Wherever the provider you choose processes | recipient email addresses and names, message content, delivery and engagement events |\n| The model provider you choose | Every AI feature in a self-hosted installation runs against a key you supply, to a provider you pick. Nothing routes through us and we see none of it. | Wherever the provider you choose processes | prompts and completions, including any personal data your installation puts in them |\n| The GitHub or GitLab account you connect | A self-hosted installation reads the source platforms under your own credentials and in your own name. The rate limits, the platform's acceptable use rules and the consequences of breaching them attach to your account, not ours. | The platform's own infrastructure | the queries your installation makes, your own account identity and access token |\n| The database, object storage and job runtime you choose | You select and operate the PostgreSQL database, the object storage and the background-job runtime. Trigger.dev can be pointed at its hosted service or at an instance you run yourself. | Wherever you deploy them | all application data in your installation |\n| The error-monitoring and analytics projects you choose | Sentry, PostHog and Jitsu wiring ships in the software but is inert until you supply your own project keys. Supply them and the data goes to your projects, under your account. | Wherever the provider you choose processes | error reports, console output, product analytics events and the identifiers attached to them |\n| Mem0 AI, Inc. | Long-term memory for the command-line client and the MCP server. Disabled in the hosted Service and available only to a self-hoster who switches it on with a key of their own. | United States | stored agent conversation memory, which can contain customer and developer details |\n\n### Data about developers who are not our users\n\nMost of the personal data in GitHands is about people who never signed up. The sub-processors\nabove process that data on our instructions in the same way as any other — but two points follow that a\nplain table does not convey.\n\n- **The source platforms are not our sub-processors.** GitHub, GitLab and similar platforms are where the\n data comes from, not parties we send it to. Their terms govern what may be collected from them and what\n may be done with it afterwards.\n- **We do not sell this data, and no provider above receives it for their own purposes.** Every one of them\n acts on our instructions under a written contract.\n\nIf you are a developer whose data is here and you want it removed, you do not need to work out which\nprovider holds what. Use the objection route in the privacy annex and it is handled across all of them.\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://githands.com/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://githands.com/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 GitHands, 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://githands.com/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://githands.com/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://githands.com/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.0 of the sub-processor list for\n[githands.com](https://githands.com), 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://githands.com/subprocessors](https://githands.com/subprocessors)."
153
+ "markdown": "## Why this page exists\n\nWhen you use GitHands Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://githands.com/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 [githands.com](https://githands.com), for GitHands\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://githands.com/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://githands.com/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://githands.com/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: GitHands\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 infrastructure. Every request to any GitHands hostname passes through it. | United States, with edge termination worldwide | IP address, connection and TLS metadata, full request URLs and headers, cookies in transit |\n| GitHub, Inc. | Three distinct roles. It hosts our source code, our container images and our build pipeline. It is the identity provider when a customer signs in with GitHub. And its public API is the primary source from which the developer database is built — profiles, stargazer and forker lists, contributor and participant lists, public commit metadata and public event streams. | United States | the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity |\n| Resend, Inc. | Delivery of outbound email — account and invitation mail, and the campaign messages a customer sends through the Service's default sending path — together with the delivery, open, click, bounce, complaint and reply events that come back. | United States | recipient email address and name, personalised subject line and message body, delivery, open, click, bounce and unsubscribe events, recipient IP address and user agent captured by open and click tracking, the content of a reply |\n| OpenRouter, Inc. | Routing of every AI request the Service makes to the model provider selected for it. This is the only AI provider configured in the hosted Service. OpenRouter forwards the prompt on to the upstream model provider it routes to, and that provider receives the same content. | United States, and onward to the selected model provider | developer names, usernames, email addresses, biographies and repository lists embedded in prompts, drafted outreach messages and the inbound replies being classified, customer chat messages with the in-product assistant |\n| Langfuse GmbH | Observability for AI requests — the full prompt and the full completion for each call are recorded as a trace so we can debug quality and cost. That means the same personal data that goes to the model provider is also stored here, in readable form. | Germany | complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace |\n| Functional Software, Inc. dba Sentry | Application error monitoring and performance tracing. Browser reports are sent to a path on our own domain and forwarded on, so that an extension blocking third-party requests does not silently hide our errors from us. Server-side logging is enabled, so console output can travel with a report. | United States | IP address and user agent, user identifier and email address attached as error context, URL and route, stack traces and breadcrumbs, console output, which can carry fragments of whatever request failed |\n| PostHog, Inc. | Product analytics — which pages and features are used, where people abandon a flow, and what fails. Captured both in the browser and on our servers. Consent-gated in the browser. | United States | IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer |\n| Jitsu Labs, Inc. | A second product-analytics event pipeline. Events are collected through an endpoint on the githands.com domain rather than a vendor hostname, which is worth saying plainly: an endpoint on our own domain that forwards to somebody else should never be a surprise. Consent-gated. | United States | IP address and user agent, in-product events and their properties, user identifier |\n| Trigger.dev Ltd. | The managed runtime that executes background work — extraction runs, enrichment, scoring, sequence steps and scheduled jobs. Job payloads and run logs are held there, and the runtime holds the credentials it needs to reach our database. | United Kingdom | job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data |\n| ui-avatars.com | Generated placeholder avatars, used 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. | Not published by the provider | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Google LLC | Sign in with Google. Engaged only where an individual chooses that sign-in method. | United States | email address, name, profile picture URL, Google account identifier |\n| LinkedIn Corporation | Sign in with LinkedIn, and the delivery of LinkedIn-hosted profile images where a signed-in user has one. Engaged only where an individual chooses that sign-in method. | United States | email address, name and profile fields, profile picture URL, LinkedIn member identifier |\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 | 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| Salesforce, Inc. | Two-way contact synchronisation, engaged only when a customer connects its own Salesforce organisation. | United States | contact and account records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Slack Technologies, LLC | Workspace notifications and in-Slack actions, engaged only when a customer installs the Slack application into its own workspace. | United States | workspace, channel and user identifiers, the notification content we send |\n| Stripe, Inc. | Payments and subscription billing. **Not engaged today** — the hosted Service is free, no payment method is collected and nothing is charged. Stripe becomes a sub-processor only if and when paid plans are switched on, and we will give notice before that happens. | United States | billing name and address, country and tax identification number, payment method token and card last four digits, invoice and subscription history |\n| Twilio SendGrid | An alternative outbound sending provider. The Service can be configured to send through it instead of the default. Not configured in the hosted Service. | United States | recipient email address and name, message content, delivery and engagement events |\n| Sinch Mailgun | An alternative outbound sending provider. Not configured in the hosted Service. | United States, with an optional European region | recipient email address and name, message content, delivery events |\n| Amazon Web Services, Inc. | Amazon SES as an alternative outbound sending provider, with Amazon SNS carrying bounce and complaint notifications back. Not configured in the hosted Service. | United States | recipient email address and name, message content, bounce and complaint events |\n| ActiveCampaign (Postmark) | An alternative outbound sending provider. Not configured in the hosted Service. | United States | recipient email address and name, message content, delivery events |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run GitHands on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| The email sending provider you choose | A self-hosted installation has no sending path of ours to fall back on — we removed the shared sending address deliberately. You bring your own sending account and your own verified sending domain. The software supports Resend, Twilio SendGrid, Sinch Mailgun, Amazon SES, Postmark and a plain SMTP relay. | Wherever the provider you choose processes | recipient email addresses and names, message content, delivery and engagement events |\n| The model provider you choose | Every AI feature in a self-hosted installation runs against a key you supply, to a provider you pick. Nothing routes through us and we see none of it. | Wherever the provider you choose processes | prompts and completions, including any personal data your installation puts in them |\n| The GitHub or GitLab account you connect | A self-hosted installation reads the source platforms under your own credentials and in your own name. The rate limits, the platform's acceptable use rules and the consequences of breaching them attach to your account, not ours. | The platform's own infrastructure | the queries your installation makes, your own account identity and access token |\n| The database, object storage and job runtime you choose | You select and operate the PostgreSQL database, the object storage and the background-job runtime. Trigger.dev can be pointed at its hosted service or at an instance you run yourself. | Wherever you deploy them | all application data in your installation |\n| The error-monitoring and analytics projects you choose | Sentry, PostHog and Jitsu wiring ships in the software but is inert until you supply your own project keys. Supply them and the data goes to your projects, under your account. | Wherever the provider you choose processes | error reports, console output, product analytics events and the identifiers attached to them |\n| Mem0 AI, Inc. | Long-term memory for the command-line client and the MCP server. Disabled in the hosted Service and available only to a self-hoster who switches it on with a key of their own. | United States | stored agent conversation memory, which can contain customer and developer details |\n\n### Data about developers who are not our users\n\nMost of the personal data in GitHands is about people who never signed up. The sub-processors\nabove process that data on our instructions in the same way as any other — but two points follow that a\nplain table does not convey.\n\n- **The source platforms are not our sub-processors.** GitHub, GitLab and similar platforms are where the\n data comes from, not parties we send it to. Their terms govern what may be collected from them and what\n may be done with it afterwards.\n- **We do not sell this data, and no provider above receives it for their own purposes.** Every one of them\n acts on our instructions under a written contract.\n\nIf you are a developer whose data is here and you want it removed, you do not need to work out which\nprovider holds what. Use the objection route in the privacy annex and it is handled across all of them.\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://githands.com/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://githands.com/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 GitHands, 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://githands.com/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://githands.com/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://githands.com/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.1 of the sub-processor list for\n[githands.com](https://githands.com), 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://githands.com/subprocessors](https://githands.com/subprocessors)."
154
154
  }
@@ -476,7 +476,7 @@ and mark the letter for the attention of the privacy team. We correspond in Engl
476
476
  Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
477
477
  <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
478
478
  to the authority for the country where you live or work.</p>
479
- <p>This document is version 1.0.0 of the sub-processor list for
479
+ <p>This document is version 1.0.1 of the sub-processor list for
480
480
  <a href="https://hust.so">hust.so</a>, in force from 2026-08-02. It lists the providers engaged
481
481
  as at that date. Earlier versions, with the dates they applied, are at
482
482
  <a href="https://hust.so/subprocessors">https://hust.so/subprocessors</a>.</p>
@@ -6,9 +6,9 @@
6
6
  "entity": "Ever Technologies LTD",
7
7
  "entityId": "ever-technologies-bg",
8
8
  "locale": "en",
9
- "version": "1.0.0",
9
+ "version": "1.0.1",
10
10
  "effectiveDate": "2026-08-02",
11
- "sha256": "523f9f44a2fc3ec4fdbf93201b3b6c66f9c0bcfe80c50d0bd70660234cf49aae",
11
+ "sha256": "f2250cbc981d1a12eb985aa4665915c62cd8dc414282971a20044fd14f5ae218",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/subprocessors/010-purpose",
@@ -150,5 +150,5 @@
150
150
  }
151
151
  ],
152
152
  "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.0 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)."
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.1 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
154
  }
@@ -356,7 +356,7 @@ and mark the letter for the attention of the privacy team. We correspond in Engl
356
356
  Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
357
357
  <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
358
358
  to the authority for the country where you live or work.</p>
359
- <p>This document is version 1.0.0 of the sub-processor list for
359
+ <p>This document is version 1.0.1 of the sub-processor list for
360
360
  <a href="https://traduora.co">traduora.co</a>, in force from 2026-08-02. It lists the providers engaged
361
361
  as at that date. Earlier versions, with the dates they applied, are at
362
362
  <a href="https://traduora.co/subprocessors">https://traduora.co/subprocessors</a>.</p>
@@ -6,9 +6,9 @@
6
6
  "entity": "Ever Technologies LTD",
7
7
  "entityId": "ever-technologies-bg",
8
8
  "locale": "en",
9
- "version": "1.0.0",
9
+ "version": "1.0.1",
10
10
  "effectiveDate": "2026-08-02",
11
- "sha256": "54027d5338a005a3aa7a0d92e8c23ba13b3380874fbae0e9b75c698627ac5ba3",
11
+ "sha256": "9f6a18027ca38551e724037de03c2624e44d53a5ca6ffe5e9a10dac82c308623",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/subprocessors/010-purpose",
@@ -150,5 +150,5 @@
150
150
  }
151
151
  ],
152
152
  "path": "content/subprocessors/traduora/en.html",
153
- "markdown": "## Why this page exists\n\nWhen you use Ever Traduora 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://traduora.co/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 [traduora.co](https://traduora.co), for Ever Traduora\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://traduora.co/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://traduora.co/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://traduora.co/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 Traduora\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | DNS, content delivery, TLS termination, web application firewall and bot protection in front of traduora.co, docs.traduora.co and the content management hosts. Every request to those sites passes through it before it reaches our infrastructure. | United States, with traffic terminated at the edge location nearest the visitor anywhere in the world | IP address, user agent and device characteristics, requested URLs, referrer and request headers, TLS and connection metadata, security cookies set by the provider |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Functional Software, Inc. d/b/a Sentry | Error and crash diagnostics on traduora.co, and browser SESSION REPLAY — a masked reconstruction of what happened in the page. Replay is sampled at roughly one in ten visits and captured for every visit in which an error occurs, with all text masked and all media blocked. Engaged only where you consent to the analytics category. | United States | IP address, user agent, operating system, browser and screen size, page URL and referrer, error events and stack traces, a masked session replay — page structure, navigation and interaction timing, with text masked and media blocked |\n| PostHog, Inc. | Product analytics on traduora.co — page views and page-leave events, so we can see which pages are read and which are abandoned. Engaged only where you consent to the analytics category. | United States | a persistent visitor identifier generated by the provider, IP address, user agent and device characteristics, pages viewed, referrer and event timestamps |\n| Google Ireland Limited | Google Analytics on traduora.co, loaded from googletagmanager.com. The measurement identifier in the page is a legacy Universal Analytics property, so the request discloses your visit to Google whether or not anything is still measured behind it. Engaged only where you consent to the analytics category. | Ireland, with processing by Google LLC in the United States | a client identifier stored in a first-party cookie, IP address, user agent and device characteristics, pages viewed and referrer |\n| New Relic, Inc. | Browser performance monitoring on traduora.co — page load and rendering timings, and front-end errors. The agent is configured with its own cookies switched off, so it stores nothing on your device, but the beacon request itself is still a disclosure. Engaged only where you consent to the analytics category. | European Union — the agent reports to the provider's EU beacon endpoint. The provider is established in the United States. | IP address, user agent and device characteristics, page URL and referrer, page timing and performance measurements |\n| SolarWinds Worldwide, LLC (Pingdom) | Real user monitoring on traduora.co — how long pages actually took to load for real visitors. Engaged only where you consent to the analytics category. | United States | IP address, user agent and device characteristics, page URL, page timing measurements |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Traduora on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| The database you provide — MySQL, MariaDB, PostgreSQL or SQLite | Holds everything in your instance: users, projects, terms, translations, labels, invitations and API client records. You choose the engine, the host and the operator, and you hold the credentials. | Wherever you run it | user name, email address and hashed password, password-reset tokens and expiry, sign-in attempt counts and last sign-in time, invitation email addresses, status and project role, project API client names, roles and secrets, term keys, context strings and translation values, which are free text and can contain anything your team types into them |\n| The SMTP mail relay you configure | Sends the transactional email your instance generates — welcome messages, password-change and password-reset messages, project invitations and platform invitations. The software has no default relay and no relay of ours. | Wherever your relay operates | recipient email address and name, password-reset links and invitation links, the project or instance the message concerns |\n| Google Ireland Limited / Google LLC — Google Sign-In | Optional Google sign-in for your instance, active only where you switch it on and register your own OAuth client with your own Google account. It is off in the default configuration. | Ireland and the United States | your users' Google account identifier, email address, display name |\n| Elestio | A one-click deployment of Ever Traduora offered by that vendor and linked from the project's documentation. If you use it, it hosts your instance and your contract is with it. We receive nothing and are not a party to it. | As stated by that vendor | everything in your instance, because it hosts it |\n\n### There is no hosted service, so this list is short\n\nEver Traduora is open source and self-hosted. **We do not run a cloud version of it**, which means we\nhold none of your translation data and engage no sub-processor for it. Tier 1 above covers only the\ntraduora.co website and its documentation.\n\nIf you run Ever Traduora, every provider it talks to is one you configured, under your own account.\nThat is the whole of tier 3, and none of it involves us.\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://traduora.co/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://traduora.co/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 Traduora, 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://traduora.co/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://traduora.co/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://traduora.co/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.0 of the sub-processor list for\n[traduora.co](https://traduora.co), 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://traduora.co/subprocessors](https://traduora.co/subprocessors)."
153
+ "markdown": "## Why this page exists\n\nWhen you use Ever Traduora 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://traduora.co/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 [traduora.co](https://traduora.co), for Ever Traduora\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://traduora.co/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://traduora.co/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://traduora.co/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 Traduora\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | DNS, content delivery, TLS termination, web application firewall and bot protection in front of traduora.co, docs.traduora.co and the content management hosts. Every request to those sites passes through it before it reaches our infrastructure. | United States, with traffic terminated at the edge location nearest the visitor anywhere in the world | IP address, user agent and device characteristics, requested URLs, referrer and request headers, TLS and connection metadata, security cookies set by the provider |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Functional Software, Inc. d/b/a Sentry | Error and crash diagnostics on traduora.co, and browser SESSION REPLAY — a masked reconstruction of what happened in the page. Replay is sampled at roughly one in ten visits and captured for every visit in which an error occurs, with all text masked and all media blocked. Engaged only where you consent to the analytics category. | United States | IP address, user agent, operating system, browser and screen size, page URL and referrer, error events and stack traces, a masked session replay — page structure, navigation and interaction timing, with text masked and media blocked |\n| PostHog, Inc. | Product analytics on traduora.co — page views and page-leave events, so we can see which pages are read and which are abandoned. Engaged only where you consent to the analytics category. | United States | a persistent visitor identifier generated by the provider, IP address, user agent and device characteristics, pages viewed, referrer and event timestamps |\n| Google Ireland Limited | Google Analytics on traduora.co, loaded from googletagmanager.com. The measurement identifier in the page is a legacy Universal Analytics property, so the request discloses your visit to Google whether or not anything is still measured behind it. Engaged only where you consent to the analytics category. | Ireland, with processing by Google LLC in the United States | a client identifier stored in a first-party cookie, IP address, user agent and device characteristics, pages viewed and referrer |\n| New Relic, Inc. | Browser performance monitoring on traduora.co — page load and rendering timings, and front-end errors. The agent is configured with its own cookies switched off, so it stores nothing on your device, but the beacon request itself is still a disclosure. Engaged only where you consent to the analytics category. | European Union — the agent reports to the provider's EU beacon endpoint. The provider is established in the United States. | IP address, user agent and device characteristics, page URL and referrer, page timing and performance measurements |\n| SolarWinds Worldwide, LLC (Pingdom) | Real user monitoring on traduora.co — how long pages actually took to load for real visitors. Engaged only where you consent to the analytics category. | United States | IP address, user agent and device characteristics, page URL, page timing measurements |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Traduora on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| The database you provide — MySQL, MariaDB, PostgreSQL or SQLite | Holds everything in your instance: users, projects, terms, translations, labels, invitations and API client records. You choose the engine, the host and the operator, and you hold the credentials. | Wherever you run it | user name, email address and hashed password, password-reset tokens and expiry, sign-in attempt counts and last sign-in time, invitation email addresses, status and project role, project API client names, roles and secrets, term keys, context strings and translation values, which are free text and can contain anything your team types into them |\n| The SMTP mail relay you configure | Sends the transactional email your instance generates — welcome messages, password-change and password-reset messages, project invitations and platform invitations. The software has no default relay and no relay of ours. | Wherever your relay operates | recipient email address and name, password-reset links and invitation links, the project or instance the message concerns |\n| Google Ireland Limited / Google LLC — Google Sign-In | Optional Google sign-in for your instance, active only where you switch it on and register your own OAuth client with your own Google account. It is off in the default configuration. | Ireland and the United States | your users' Google account identifier, email address, display name |\n| Elestio | A one-click deployment of Ever Traduora offered by that vendor and linked from the project's documentation. If you use it, it hosts your instance and your contract is with it. We receive nothing and are not a party to it. | As stated by that vendor | everything in your instance, because it hosts it |\n\n### There is no hosted service, so this list is short\n\nEver Traduora is open source and self-hosted. **We do not run a cloud version of it**, which means we\nhold none of your translation data and engage no sub-processor for it. Tier 1 above covers only the\ntraduora.co website and its documentation.\n\nIf you run Ever Traduora, every provider it talks to is one you configured, under your own account.\nThat is the whole of tier 3, and none of it involves us.\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://traduora.co/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://traduora.co/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 Traduora, 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://traduora.co/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://traduora.co/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://traduora.co/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.1 of the sub-processor list for\n[traduora.co](https://traduora.co), 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://traduora.co/subprocessors](https://traduora.co/subprocessors)."
154
154
  }
@@ -1,6 +1,6 @@
1
1
  <h1 id="terms-of-service" tabindex="-1">Terms of Service</h1>
2
2
  <p><strong>Ever</strong> — <a href="https://ever.co">ever.co</a></p>
3
- <p>Version 1.0.0 · In force from 2026-08-02</p>
3
+ <p>Version 1.0.1 · In force from 2026-08-02</p>
4
4
  <p>These Terms of Service (&quot;<strong>Terms</strong>&quot;) govern your access to and use of the Ever website and the
5
5
  websites, applications and application programming interfaces we make available at <a href="https://ever.co">ever.co</a>
6
6
  (together, the &quot;<strong>Service</strong>&quot;).</p>
@@ -762,7 +762,7 @@ does today.</p>
762
762
  <h2 id="changes-to-these-terms" tabindex="-1">Changes to these Terms</h2>
763
763
  <p>We will change these Terms from time to time — because the Service changes, because the law changes, or
764
764
  because something here turned out to be unclear. Every version carries a version number and an effective
765
- date, printed at the top of the document. This one is version 1.0.0, in force from
765
+ date, printed at the top of the document. This one is version 1.0.1, in force from
766
766
  2026-08-02.</p>
767
767
  <h3 id="changes-that-take-effect-immediately" tabindex="-1">Changes that take effect immediately</h3>
768
768
  <p>Corrections, clarifications, formatting, new contact details, and terms covering a new feature you are
@@ -968,6 +968,6 @@ English text applies.</p>
968
968
  <p>By post: <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company
969
969
  number 204599535.</p>
970
970
  <p>We correspond in English.</p>
971
- <p>This document is version 1.0.0 of the Terms of Service for
971
+ <p>This document is version 1.0.1 of the Terms of Service for
972
972
  <a href="https://ever.co">ever.co</a>, in force from 2026-08-02. Earlier versions, with the
973
973
  dates they applied, are at <a href="https://ever.co/tos">https://ever.co/tos</a>.</p>