@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": "348b289b9b3f34b2b48e1d3fdb91ce59a7568efae4d97064a90bf728e3cb1a6f",
11
+ "sha256": "c7b86f09dfb6e83377863516c82ecaa150903bbebe25c449942f3b608277fa75",
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/ever-works/en.html",
153
- "markdown": "## Why this page exists\n\nWhen you use Ever Works Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://ever.works/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [ever.works](https://ever.works), for Ever Works\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\nbetween them — do not read this one as covering a product it does not name.\n\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\nexists to make that distinction visible rather than to blur it.\n\nThis page is versioned and dated. The version in force, and the date it took effect, are at the end.\n\n## How to read this list\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://ever.works/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where that is outside the European Economic Area, the transfer mechanism we\n rely on for it is described in the international transfers section of our\n [Privacy Policy](https://ever.works/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### What is deliberately not in the tables\n\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\n container platform are not sub-processors, because there is no third party involved. The next section\n describes what we run and what really does sit in front of it.\n- **Recipients that are not processors** — payment providers acting under their own regulatory\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\n are covered in the [Privacy Policy](https://ever.works/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 Works\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | DNS, reverse proxy, TLS termination and content delivery for ever.works, for the platform, and for every site we provision, which reaches the internet through a Cloudflare tunnel. Also Turnstile, the anti-bot check on registration and onboarding. | United States, with traffic terminated at the edge location nearest the visitor | IP address, user agent and device signals, request metadata such as URL, referrer and cookies, anti-bot challenge signals |\n| PostHog, Inc. | Product analytics for the platform and the marketing site — page views, interaction capture, feature flags, and session recording with form inputs masked. Signed-in users are identified to it. Our server-side application logs are forwarded to the same account. | United States (PostHog US Cloud) | account identifier, email address, name, IP address, page views and interface interactions, masked session recordings, server log lines and error messages |\n| GitHub, Inc. (Microsoft Corporation) | Sign-in with GitHub and the platform GitHub App; the repositories that hold a Work's website and its content, which for a platform-managed Work are private repositories in an organisation we own; the container registry that holds the image of the platform and of each provisioned site; and our build pipeline. | United States | GitHub account identity and access token, avatar URL, commit author name and email address, repository contents, including whatever a Work's content contains, pull request and issue text |\n| OpenRouter, Inc. | The model gateway every agent run and generation pipeline goes through by default, including the automated research that runs when an account is created. It selects an upstream model provider to serve each request. | United States | prompts and completions, which routinely contain account identity and user-generated content, name, email address, sign-in provider, avatar URL and social profile URLs at registration, search results about a named person |\n| Tavily | The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created — where the search queries are built from the new account holder's name and email domain. | United States | search queries, including a person's name and their employer's domain, the addresses of pages retrieved |\n| Google LLC (Google Analytics 4 and Google Tag Manager) | Web analytics and tag delivery on the ever.works marketing site. Not used in the signed-in platform. | United States | IP address, analytics identifier, page views and events, device, browser and approximate location |\n| Google LLC (reCAPTCHA) | Bot protection on the forms on the ever.works marketing site. | United States | IP address, browser and interaction signals |\n| Google LLC (Google Fonts) | The documentation sites fetch a webfont from Google at the moment a page loads, so a visitor's browser contacts Google directly. The application and the site template do not — they build the font in and serve it themselves. | United States | IP address, user agent, the page being read |\n| Intuit Inc. (Mailchimp) | Holds the newsletter list for the marketing site, and receives an address when someone subscribes. | United States | email address, subscription status and date, IP address |\n| ActiveCampaign, LLC (Postmark) | Delivers the message when someone writes to us through the contact form on the marketing site. | United States | name, email address, the content of the message |\n| jsDelivr | A public content delivery network that serves the WebAssembly file behind the animation on the sign-in and registration pages. The fetch happens before anyone has signed in or made a cookie choice, so it is listed rather than left implied. | Global anycast network | IP address, user agent, referring page |\n| unpkg | The fallback for the same file, used when the primary content delivery network does not answer. | Global anycast network | IP address, user agent, referring page |\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. (Sentry) | Error tracking and performance traces, where an account is configured with a Sentry project. On a provisioned site the template can additionally run Sentry in the visitor's browser, including its own session replay, if the Work Owner enables it. | United States | IP address, account identifier attached to an error, stack traces and request metadata, which can contain fragments of content, browser session replay on a Work site, where enabled |\n| Resend, Inc. | Sends transactional email — verification, password reset, notifications — where it is selected as the mail provider, and outbound agent mail where it is selected as the agent mail provider. | United States | recipient name and email address, subject and body of the message |\n| Stripe, Inc. | Checkout, subscriptions and invoicing for paid plans and credit packs, where billing is enabled on the account. Separately, a Work Owner can connect their own Stripe account to take payments from their own site's visitors. | United States | name and email address, billing address entered at checkout, customer and payment method references, purchase and invoice history, IP address collected by Stripe on its own pages |\n| Google LLC (Google Identity) | Sign in with Google, where you choose it — on the platform, or on a Work site where the site owner has enabled it. | United States | Google account identifier, email address, name, profile photo URL |\n| Meta Platforms, Inc. | Sign in with Facebook, where you choose it and where the site owner has enabled it. | United States | Facebook account identifier, email address, name, profile photo URL |\n| LinkedIn Corporation (Microsoft Corporation) | Sign in with LinkedIn, where you choose it and where the site owner has enabled it. | United States | LinkedIn account identifier, email address, name, profile photo URL |\n| Composio Inc. | Brokers an agent's access to third-party tools using accounts you have connected yourself, and receives the events those tools send back. | United States | access tokens for the accounts you connect, whatever those accounts return into an agent run |\n| Novu Inc. | The in-application notification inbox and a delivery channel for notifications, where it is configured against Novu's hosted service rather than an instance you run. | United States | a hashed subscriber identifier, notification content, email address where used as a delivery channel |\n| Twenty S.A.S. | Two-way sync of companies and people with a Twenty workspace, where you supply the workspace and an API key. Also available on a provisioned Work site. | France, unless you point it at a Twenty instance you run | contact name and email address, company and role, notes and activity records |\n| Langfuse GmbH | Prompt versioning and model observability, where keys for it are supplied. | European Union, unless you point it at a Langfuse instance you run | prompt and completion text, which can contain account identity and user-generated content |\n| Jitsu Labs, Inc. | Forwards activity-log events — who did what, to which Work, and whether it succeeded — to an analytics pipeline, where one is configured. Also available on a provisioned Work site. | United States, unless you point it at a Jitsu instance you run | account identifier and Work identifier, action, status and summary of an event, IP address, for the browser-side variant on a Work site |\n| Trigger.dev Inc. | Runs background jobs for agent work, where an account is pointed at Trigger.dev's hosted service rather than the instance we run ourselves. | United States | job payloads, which can contain identifiers, email addresses and user-generated content |\n| Vercel Inc. | An alternative place to deploy a Work site, chosen by the Work Owner and connected with their own account and token. The site template can also run Vercel's analytics and performance measurement if the Work Owner switches them on. | United States | deployment metadata, the account token the Work Owner supplies, site visitor IP address and page views, where its analytics are enabled |\n| ScreenshotOne | Captures a screenshot of a website so that a directory entry has a thumbnail. | European Union | the address of the page to be captured, whatever that page displays |\n| Algolia SAS | Search on the documentation sites, where search keys are configured. | European Union and United States | search queries, IP address |\n| OpenAI, L.L.C. | An upstream model provider. Our default pipelines are routed to an OpenAI model through the gateway above. Where you instead supply your own OpenAI key, OpenAI is your provider under your own agreement with it and not our sub-processor. | United States | prompt and completion text, which can contain account identity and user-generated content |\n| Anthropic, PBC | A model provider for the Claude-based agent pipelines, engaged where those are enabled or where you supply your own key. | United States | prompt and completion text, which can contain account identity and user-generated content |\n| Google LLC (Gemini) | A model provider, engaged only where you select it and supply your own key. | United States | prompt and completion text |\n| Amazon Web Services, Inc. | Object storage for uploads, where you point storage at an S3 bucket of your own instead of ours. | The region of the bucket you choose | uploads and attachments |\n| Plausible Insights OÜ | Cookieless site analytics on a Work site, where the Work Owner enables it. | European Union | page views and referrer, coarse device and country |\n| Twilio Inc. (Segment) | Event collection and routing on a Work site, where the Work Owner enables it. | United States | IP address, visitor identifier and traits where the visitor is identified, events and page views |\n| DataFast | Product and marketing analytics on a Work site, where the Work Owner enables it. | United States | IP address, page views and events, campaign attribution |\n| Google LLC (Google Maps Platform) | Renders maps and clusters markers for location-based listings on a Work site, where the Work Owner enables it. | United States | IP address, the area of the map being viewed and locations searched |\n| Mapbox, Inc. | The alternative map renderer for the same purpose on a Work site. | United States | IP address, the area of the map being viewed and locations searched |\n| Lemon Squeezy, LLC | Takes payments from a Work site's own visitors as merchant of record, where the Work Owner connects it. The Work Owner contracts with it directly. | United States | name and email address, billing address and tax location, payment identifiers and purchase history |\n| Polar Software Inc. | An alternative payment and subscription provider for a Work site's own visitors. | United States | name and email address, billing and tax location, payment identifiers and subscription history |\n| SolidGate | A further card payment option for a Work site's own visitors. | European Union | cardholder name, email address, billing address, payment identifiers |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Works 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| Supabase, Inc. | An authentication and database adapter that ships in the directory site template and can be used instead of a PostgreSQL server. **No site we host uses it** — every site we provision runs on the PostgreSQL cluster we operate. It is here so that a self-hoster can see the option exists. | The region you choose when you create the project | site visitor account records, if you configure it |\n| Ollama, LM Studio or a vLLM server you run yourself | Local model runtimes the software can be pointed at instead of a hosted model provider. Listed because it is the one configuration in which no third party sees a prompt at all. | Your own infrastructure | nothing leaves your deployment |\n\n### Sites we provision for you\n\nWhere we provision and host a directory site for you, **that site's visitors are your data subjects, not\nours.** You are the controller for what the site collects from them; we are your processor for hosting it.\n\nThe providers above are the ones in the path for the platform. A site you have us provision may bring in\nfurther providers because **you** configured them — an analytics tool, a form handler, a payment provider,\na comment system. Those are yours: you choose them, you contract with them, and they belong in the privacy\nnotice you publish on that site, not in ours.\n\nIf you are unsure which of your site's providers we engage and which you do, ask at privacy@ever.co\nand we will tell you exactly what the platform touches.\n\n## Hosting and infrastructure\n\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\noperate ourselves.\n\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\n[Security page](https://ever.works/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://ever.works/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 Works, the\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\n\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\ntable says so.\n\n### The regions you should design around\n\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\nsmall number of named providers established outside the European Economic Area, each with its own transfer\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\ninternational transfers section of the [Privacy Policy](https://ever.works/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://ever.works/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://ever.works/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.0 of the sub-processor list for\n[ever.works](https://ever.works), in force from 2026-08-02. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://ever.works/subprocessors](https://ever.works/subprocessors)."
153
+ "markdown": "## Why this page exists\n\nWhen you use Ever Works Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://ever.works/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [ever.works](https://ever.works), for Ever Works\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\nbetween them — do not read this one as covering a product it does not name.\n\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\nexists to make that distinction visible rather than to blur it.\n\nThis page is versioned and dated. The version in force, and the date it took effect, are at the end.\n\n## How to read this list\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://ever.works/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where that is outside the European Economic Area, the transfer mechanism we\n rely on for it is described in the international transfers section of our\n [Privacy Policy](https://ever.works/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### What is deliberately not in the tables\n\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\n container platform are not sub-processors, because there is no third party involved. The next section\n describes what we run and what really does sit in front of it.\n- **Recipients that are not processors** — payment providers acting under their own regulatory\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\n are covered in the [Privacy Policy](https://ever.works/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 Works\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | DNS, reverse proxy, TLS termination and content delivery for ever.works, for the platform, and for every site we provision, which reaches the internet through a Cloudflare tunnel. Also Turnstile, the anti-bot check on registration and onboarding. | United States, with traffic terminated at the edge location nearest the visitor | IP address, user agent and device signals, request metadata such as URL, referrer and cookies, anti-bot challenge signals |\n| PostHog, Inc. | Product analytics for the platform and the marketing site — page views, interaction capture, feature flags, and session recording with form inputs masked. Signed-in users are identified to it. Our server-side application logs are forwarded to the same account. | United States (PostHog US Cloud) | account identifier, email address, name, IP address, page views and interface interactions, masked session recordings, server log lines and error messages |\n| GitHub, Inc. (Microsoft Corporation) | Sign-in with GitHub and the platform GitHub App; the repositories that hold a Work's website and its content, which for a platform-managed Work are private repositories in an organisation we own; the container registry that holds the image of the platform and of each provisioned site; and our build pipeline. | United States | GitHub account identity and access token, avatar URL, commit author name and email address, repository contents, including whatever a Work's content contains, pull request and issue text |\n| OpenRouter, Inc. | The model gateway every agent run and generation pipeline goes through by default, including the automated research that runs when an account is created. It selects an upstream model provider to serve each request. | United States | prompts and completions, which routinely contain account identity and user-generated content, name, email address, sign-in provider, avatar URL and social profile URLs at registration, search results about a named person |\n| Tavily | The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created — where the search queries are built from the new account holder's name and email domain. | United States | search queries, including a person's name and their employer's domain, the addresses of pages retrieved |\n| Google LLC (Google Analytics 4 and Google Tag Manager) | Web analytics and tag delivery on the ever.works marketing site. Not used in the signed-in platform. | United States | IP address, analytics identifier, page views and events, device, browser and approximate location |\n| Google LLC (reCAPTCHA) | Bot protection on the forms on the ever.works marketing site. | United States | IP address, browser and interaction signals |\n| Google LLC (Google Fonts) | The documentation sites fetch a webfont from Google at the moment a page loads, so a visitor's browser contacts Google directly. The application and the site template do not — they build the font in and serve it themselves. | United States | IP address, user agent, the page being read |\n| Intuit Inc. (Mailchimp) | Holds the newsletter list for the marketing site, and receives an address when someone subscribes. | United States | email address, subscription status and date, IP address |\n| ActiveCampaign, LLC (Postmark) | Delivers the message when someone writes to us through the contact form on the marketing site. | United States | name, email address, the content of the message |\n| jsDelivr | A public content delivery network that serves the WebAssembly file behind the animation on the sign-in and registration pages. The fetch happens before anyone has signed in or made a cookie choice, so it is listed rather than left implied. | Global anycast network | IP address, user agent, referring page |\n| unpkg | The fallback for the same file, used when the primary content delivery network does not answer. | Global anycast network | IP address, user agent, referring page |\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. (Sentry) | Error tracking and performance traces, where an account is configured with a Sentry project. On a provisioned site the template can additionally run Sentry in the visitor's browser, including its own session replay, if the Work Owner enables it. | United States | IP address, account identifier attached to an error, stack traces and request metadata, which can contain fragments of content, browser session replay on a Work site, where enabled |\n| Resend, Inc. | Sends transactional email — verification, password reset, notifications — where it is selected as the mail provider, and outbound agent mail where it is selected as the agent mail provider. | United States | recipient name and email address, subject and body of the message |\n| Stripe, Inc. | Checkout, subscriptions and invoicing for paid plans and credit packs, where billing is enabled on the account. Separately, a Work Owner can connect their own Stripe account to take payments from their own site's visitors. | United States | name and email address, billing address entered at checkout, customer and payment method references, purchase and invoice history, IP address collected by Stripe on its own pages |\n| Google LLC (Google Identity) | Sign in with Google, where you choose it — on the platform, or on a Work site where the site owner has enabled it. | United States | Google account identifier, email address, name, profile photo URL |\n| Meta Platforms, Inc. | Sign in with Facebook, where you choose it and where the site owner has enabled it. | United States | Facebook account identifier, email address, name, profile photo URL |\n| LinkedIn Corporation (Microsoft Corporation) | Sign in with LinkedIn, where you choose it and where the site owner has enabled it. | United States | LinkedIn account identifier, email address, name, profile photo URL |\n| Composio Inc. | Brokers an agent's access to third-party tools using accounts you have connected yourself, and receives the events those tools send back. | United States | access tokens for the accounts you connect, whatever those accounts return into an agent run |\n| Novu Inc. | The in-application notification inbox and a delivery channel for notifications, where it is configured against Novu's hosted service rather than an instance you run. | United States | a hashed subscriber identifier, notification content, email address where used as a delivery channel |\n| Twenty S.A.S. | Two-way sync of companies and people with a Twenty workspace, where you supply the workspace and an API key. Also available on a provisioned Work site. | France, unless you point it at a Twenty instance you run | contact name and email address, company and role, notes and activity records |\n| Langfuse GmbH | Prompt versioning and model observability, where keys for it are supplied. | European Union, unless you point it at a Langfuse instance you run | prompt and completion text, which can contain account identity and user-generated content |\n| Jitsu Labs, Inc. | Forwards activity-log events — who did what, to which Work, and whether it succeeded — to an analytics pipeline, where one is configured. Also available on a provisioned Work site. | United States, unless you point it at a Jitsu instance you run | account identifier and Work identifier, action, status and summary of an event, IP address, for the browser-side variant on a Work site |\n| Trigger.dev Inc. | Runs background jobs for agent work, where an account is pointed at Trigger.dev's hosted service rather than the instance we run ourselves. | United States | job payloads, which can contain identifiers, email addresses and user-generated content |\n| Vercel Inc. | An alternative place to deploy a Work site, chosen by the Work Owner and connected with their own account and token. The site template can also run Vercel's analytics and performance measurement if the Work Owner switches them on. | United States | deployment metadata, the account token the Work Owner supplies, site visitor IP address and page views, where its analytics are enabled |\n| ScreenshotOne | Captures a screenshot of a website so that a directory entry has a thumbnail. | European Union | the address of the page to be captured, whatever that page displays |\n| Algolia SAS | Search on the documentation sites, where search keys are configured. | European Union and United States | search queries, IP address |\n| OpenAI, L.L.C. | An upstream model provider. Our default pipelines are routed to an OpenAI model through the gateway above. Where you instead supply your own OpenAI key, OpenAI is your provider under your own agreement with it and not our sub-processor. | United States | prompt and completion text, which can contain account identity and user-generated content |\n| Anthropic, PBC | A model provider for the Claude-based agent pipelines, engaged where those are enabled or where you supply your own key. | United States | prompt and completion text, which can contain account identity and user-generated content |\n| Google LLC (Gemini) | A model provider, engaged only where you select it and supply your own key. | United States | prompt and completion text |\n| Amazon Web Services, Inc. | Object storage for uploads, where you point storage at an S3 bucket of your own instead of ours. | The region of the bucket you choose | uploads and attachments |\n| Plausible Insights OÜ | Cookieless site analytics on a Work site, where the Work Owner enables it. | European Union | page views and referrer, coarse device and country |\n| Twilio Inc. (Segment) | Event collection and routing on a Work site, where the Work Owner enables it. | United States | IP address, visitor identifier and traits where the visitor is identified, events and page views |\n| DataFast | Product and marketing analytics on a Work site, where the Work Owner enables it. | United States | IP address, page views and events, campaign attribution |\n| Google LLC (Google Maps Platform) | Renders maps and clusters markers for location-based listings on a Work site, where the Work Owner enables it. | United States | IP address, the area of the map being viewed and locations searched |\n| Mapbox, Inc. | The alternative map renderer for the same purpose on a Work site. | United States | IP address, the area of the map being viewed and locations searched |\n| Lemon Squeezy, LLC | Takes payments from a Work site's own visitors as merchant of record, where the Work Owner connects it. The Work Owner contracts with it directly. | United States | name and email address, billing address and tax location, payment identifiers and purchase history |\n| Polar Software Inc. | An alternative payment and subscription provider for a Work site's own visitors. | United States | name and email address, billing and tax location, payment identifiers and subscription history |\n| SolidGate | A further card payment option for a Work site's own visitors. | European Union | cardholder name, email address, billing address, payment identifiers |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Works 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| Supabase, Inc. | An authentication and database adapter that ships in the directory site template and can be used instead of a PostgreSQL server. **No site we host uses it** — every site we provision runs on the PostgreSQL cluster we operate. It is here so that a self-hoster can see the option exists. | The region you choose when you create the project | site visitor account records, if you configure it |\n| Ollama, LM Studio or a vLLM server you run yourself | Local model runtimes the software can be pointed at instead of a hosted model provider. Listed because it is the one configuration in which no third party sees a prompt at all. | Your own infrastructure | nothing leaves your deployment |\n\n### Sites we provision for you\n\nWhere we provision and host a directory site for you, **that site's visitors are your data subjects, not\nours.** You are the controller for what the site collects from them; we are your processor for hosting it.\n\nThe providers above are the ones in the path for the platform. A site you have us provision may bring in\nfurther providers because **you** configured them — an analytics tool, a form handler, a payment provider,\na comment system. Those are yours: you choose them, you contract with them, and they belong in the privacy\nnotice you publish on that site, not in ours.\n\nIf you are unsure which of your site's providers we engage and which you do, ask at privacy@ever.co\nand we will tell you exactly what the platform touches.\n\n## Hosting and infrastructure\n\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\noperate ourselves.\n\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\n[Security page](https://ever.works/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://ever.works/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 Works, the\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\n\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\ntable says so.\n\n### The regions you should design around\n\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\nsmall number of named providers established outside the European Economic Area, each with its own transfer\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\ninternational transfers section of the [Privacy Policy](https://ever.works/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://ever.works/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://ever.works/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[ever.works](https://ever.works), in force from 2026-08-02. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://ever.works/subprocessors](https://ever.works/subprocessors)."
154
154
  }
@@ -290,7 +290,7 @@ and mark the letter for the attention of the privacy team. We correspond in Engl
290
290
  Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
291
291
  <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
292
292
  to the authority for the country where you live or work.</p>
293
- <p>This document is version 1.0.0 of the sub-processor list for
293
+ <p>This document is version 1.0.1 of the sub-processor list for
294
294
  <a href="https://everiq.co">everiq.co</a>, in force from 2026-08-02. It lists the providers engaged
295
295
  as at that date. Earlier versions, with the dates they applied, are at
296
296
  <a href="https://everiq.co/subprocessors">https://everiq.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": "27873777e430d836c865d771d27eb96407c8fb63d75ecaab80dc2a8cdb24cc21",
11
+ "sha256": "5bcb644f9e3603669716ce12a74c94b051497d0df5fd683fe0cc7958eb2447ce",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/subprocessors/020-how-to-read-this-list",
@@ -145,5 +145,5 @@
145
145
  }
146
146
  ],
147
147
  "path": "content/subprocessors/everiq/en.html",
148
- "markdown": "## How to read this list\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://everiq.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://everiq.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://everiq.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 IQ\n\n**Two companies. That is the whole list**, and it is short for the ordinary reason that\n[everiq.co](https://everiq.co) is one page with one form on it.\n\n### Tier 1 — always engaged\n\nIn the path for anyone who loads the page. There is no setting that removes them.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination, bot and abuse protection, and the tunnel that is the only public route to the server behind everiq.co. Every request to the site passes through it before it reaches our infrastructure. Its network error reporting also asks your browser to report failed connections to the provider directly. | United States, with your connection terminated at the edge location nearest to you | IP address, user agent and device characteristics, requested URLs, referrer and request headers, TLS and connection metadata, network error reports generated by your browser, a short-lived bot-management or challenge cookie where a request looks automated |\n\n### Tier 2 — engaged only when you do something specific\n\nNot engaged by visiting. The provider below is reached only when you submit the launch form, and never\notherwise.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| The Rocket Science Group LLC d/b/a Mailchimp | Holds the launch-notification list and sends the announcement when Ever IQ opens. Engaged only when you submit the form on everiq.co — visiting the page never reaches it. The record it creates is your address, the single interest tag you selected, and the technical details its own service records about the subscription and about any message it later sends you. | United States | email address, the interest tag you selected, subscription status and the date you were added, IP address, delivery and open and click events recorded by the provider for messages it sends |\n\n### Tier 3 — self-hosted deployments only\n\n_None in this category._\n\n**Ever IQ is not published as open source and there is no deployment anyone else can run**, so\nthis tier is empty rather than filled with software that could theoretically be pointed somewhere. Where a\nproduct of ours does have a self-hosted edition, its own list carries that tier.\n\n### The site runs on our own infrastructure\n\nThe server behind [everiq.co](https://everiq.co) is ours: our own hardware, our own Kubernetes, in\nour own racks, reachable only through the tunnel our edge provider terminates. **There is no hosting\ncompany in this list because there is no hosting company involved.** Our databases, storage and container\nplatform are not sub-processors — there is no third party to disclose.\n\n### Two things you might expect to see here, and why they are not\n\n- **An email provider.** The domain carries the leftovers of an earlier mail configuration, and our sending\n policy names several providers that are permitted to send as everiq.co. **Nothing on the live\n site sends mail through any of them.** The only mail anyone receives from this product is the launch\n announcement, which comes from the newsletter provider in tier 2. A permission to send is not a\n processing activity, and we will not list a transfer that does not happen.\n- **Anything belonging to the unreleased Portal.** A messaging service needs a homeserver, media storage,\n mobile push relays, call servers and diagnostics, and every one of those is a provider or a system that\n will have to be named. **None of them is engaged, because none of them is running.** They arrive in the\n same change that opens the Portal, announced under the notification process above, and not one day\n earlier.\n\n### What that means for a launch\n\nWhen Ever IQ opens, this list will get materially longer in a single, announced change. Two of the\nadditions are worth flagging now, because they are the ones people are surprised by:\n\n- **Mobile push notifications pass through Apple and Google.** A push message tells your phone that\n something happened. Even when the message content is encrypted and the notification carries none of it,\n the fact that you received something, and when, reaches the platform operating your phone. That is\n unavoidable for any mobile messenger, and it will be listed rather than glossed over.\n- **A federated homeserver sends data to servers we do not run.** Those servers are not our sub-processors\n — nobody instructs them on our behalf — and the privacy annex explains what that means for deletion. They\n will be described there, not smuggled into this table as if we controlled 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://everiq.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://everiq.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 IQ, 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://everiq.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://everiq.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://everiq.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[everiq.co](https://everiq.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://everiq.co/subprocessors](https://everiq.co/subprocessors)."
148
+ "markdown": "## How to read this list\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://everiq.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://everiq.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://everiq.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 IQ\n\n**Two companies. That is the whole list**, and it is short for the ordinary reason that\n[everiq.co](https://everiq.co) is one page with one form on it.\n\n### Tier 1 — always engaged\n\nIn the path for anyone who loads the page. There is no setting that removes them.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination, bot and abuse protection, and the tunnel that is the only public route to the server behind everiq.co. Every request to the site passes through it before it reaches our infrastructure. Its network error reporting also asks your browser to report failed connections to the provider directly. | United States, with your connection terminated at the edge location nearest to you | IP address, user agent and device characteristics, requested URLs, referrer and request headers, TLS and connection metadata, network error reports generated by your browser, a short-lived bot-management or challenge cookie where a request looks automated |\n\n### Tier 2 — engaged only when you do something specific\n\nNot engaged by visiting. The provider below is reached only when you submit the launch form, and never\notherwise.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| The Rocket Science Group LLC d/b/a Mailchimp | Holds the launch-notification list and sends the announcement when Ever IQ opens. Engaged only when you submit the form on everiq.co — visiting the page never reaches it. The record it creates is your address, the single interest tag you selected, and the technical details its own service records about the subscription and about any message it later sends you. | United States | email address, the interest tag you selected, subscription status and the date you were added, IP address, delivery and open and click events recorded by the provider for messages it sends |\n\n### Tier 3 — self-hosted deployments only\n\n_None in this category._\n\n**Ever IQ is not published as open source and there is no deployment anyone else can run**, so\nthis tier is empty rather than filled with software that could theoretically be pointed somewhere. Where a\nproduct of ours does have a self-hosted edition, its own list carries that tier.\n\n### The site runs on our own infrastructure\n\nThe server behind [everiq.co](https://everiq.co) is ours: our own hardware, our own Kubernetes, in\nour own racks, reachable only through the tunnel our edge provider terminates. **There is no hosting\ncompany in this list because there is no hosting company involved.** Our databases, storage and container\nplatform are not sub-processors — there is no third party to disclose.\n\n### Two things you might expect to see here, and why they are not\n\n- **An email provider.** The domain carries the leftovers of an earlier mail configuration, and our sending\n policy names several providers that are permitted to send as everiq.co. **Nothing on the live\n site sends mail through any of them.** The only mail anyone receives from this product is the launch\n announcement, which comes from the newsletter provider in tier 2. A permission to send is not a\n processing activity, and we will not list a transfer that does not happen.\n- **Anything belonging to the unreleased Portal.** A messaging service needs a homeserver, media storage,\n mobile push relays, call servers and diagnostics, and every one of those is a provider or a system that\n will have to be named. **None of them is engaged, because none of them is running.** They arrive in the\n same change that opens the Portal, announced under the notification process above, and not one day\n earlier.\n\n### What that means for a launch\n\nWhen Ever IQ opens, this list will get materially longer in a single, announced change. Two of the\nadditions are worth flagging now, because they are the ones people are surprised by:\n\n- **Mobile push notifications pass through Apple and Google.** A push message tells your phone that\n something happened. Even when the message content is encrypted and the notification carries none of it,\n the fact that you received something, and when, reaches the platform operating your phone. That is\n unavoidable for any mobile messenger, and it will be listed rather than glossed over.\n- **A federated homeserver sends data to servers we do not run.** Those servers are not our sub-processors\n — nobody instructs them on our behalf — and the privacy annex explains what that means for deletion. They\n will be described there, not smuggled into this table as if we controlled 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://everiq.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://everiq.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 IQ, 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://everiq.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://everiq.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://everiq.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[everiq.co](https://everiq.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://everiq.co/subprocessors](https://everiq.co/subprocessors)."
149
149
  }
@@ -597,7 +597,7 @@ and mark the letter for the attention of the privacy team. We correspond in Engl
597
597
  Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
598
598
  <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
599
599
  to the authority for the country where you live or work.</p>
600
- <p>This document is version 1.0.0 of the sub-processor list for
600
+ <p>This document is version 1.0.1 of the sub-processor list for
601
601
  <a href="https://gauzy.co">gauzy.co</a>, in force from 2026-08-02. It lists the providers engaged
602
602
  as at that date. Earlier versions, with the dates they applied, are at
603
603
  <a href="https://gauzy.co/subprocessors">https://gauzy.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": "469753696f58e4a4453fff3110d4c7c23b03ac56379cd6d4f0a5494f35203510",
11
+ "sha256": "0f1b736c1fc0273f3d0153208a1f261510aa1b4b9b4fd0451b9432ebe838840f",
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/gauzy/en.html",
153
- "markdown": "## Why this page exists\n\nWhen you use Ever Gauzy 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://gauzy.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 [gauzy.co](https://gauzy.co), for Ever Gauzy\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://gauzy.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://gauzy.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://gauzy.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 Gauzy\n\nThe tiers below follow the explanation above. Read the tier, not just the name — a provider in the second\nor third table is not processing your data unless the condition next to it is true.\n\n### Tier 1 — always engaged\n\nThese are in the path for every customer of Ever Gauzy Cloud. There is no setting that removes them.\nThis is the Article 28 sub-processor list proper.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | DNS, content delivery, TLS termination, web application firewall and the tunnels that carry traffic from the edge to our own infrastructure for gauzy.co, app.gauzy.co, api.gauzy.co and docs.gauzy.co. Every request to the Service passes through it. | United States, with edge termination worldwide | IP address, user agent and device characteristics, requested URLs and request headers, TLS and connection metadata, cookies in transit |\n| ActiveCampaign, LLC (Postmark) | Delivery of transactional and notification email — workspace invitations, email verification, sign-in codes, password resets, invoice and estimate emails, timesheet and approval notifications, and replies to the contact form on gauzy.co. | United States | recipient name and email address, message subject and body, which can contain invoice, timesheet and HR content, single-use sign-in and verification codes, delivery, bounce and open metadata |\n| Chargebee Inc. | Subscription billing and hosted checkout for licence and subscription purchases started from gauzy.co. Card details are entered on Chargebee's own hosted page and never reach us. | United States | billing name and email address, billing address and tax identification number, plan, invoice and payment history, IP address |\n| GitHub, Inc. | Source hosting, continuous integration and the container registry that serves the production images for the Service. It is how the Service is built and deployed, not where your data lives. | United States | build, release and deployment metadata, developer and automation account identifiers, no workspace content and no captured media |\n| DigitalOcean, LLC | Object storage and content delivery for the public desktop, agent and server installers offered on the download page of gauzy.co. It serves the installer files themselves and nothing else. | United States | IP address of the person downloading, user agent and requested file |\n| Iubenda S.r.l. | Consent management on gauzy.co — presenting the banner and preference centre, recording your choice and making it available to the scripts that wait on it. | Italy, European Union | IP address, user agent, consent preferences and the timestamp of the choice |\n| Google LLC (reCAPTCHA) | Bot protection on the public forms of gauzy.co — contact and newsletter — with server-side verification of the resulting token. Treated as strictly necessary for the reasons given in our Cookie Policy. | United States | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\nNone of these is engaged by default. Each one arrives because someone switched something on: an\nadministrator enabled a feature, connected an integration, or configured a provider; or a visitor consented\nto a cookie category.\n\nTwo of these deserve to be called out rather than left in a table.\n\n- **Integrations you connect are two-way.** Where your organisation connects Hubstaff, Upwork, Jira,\n GitHub or a similar platform, data moves in both directions and the other platform's own terms and\n privacy notice apply to its half. Connecting it is the act that authorises the exchange.\n- **AI providers are often yours, not ours.** Several AI features work on a bring-your-own-key basis. Where\n your organisation supplies its own API key, **your organisation is the one contracting with that\n provider**, and its terms and privacy notice govern what happens to the content sent there. We do not\n become that provider's customer on your behalf, and we cannot make commitments about it.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Functional Software, Inc. (Sentry) | Error, crash and performance reporting from the API, the web application, the desktop and agent applications and the gauzy.co website, where error reporting is enabled for the deployment. | United States | IP address and device or operating-system details, user identifier and email address attached to an error event, URLs, route parameters and stack traces, which can contain fragments of the failing request, a masked replay of the website session in which an error occurred |\n| PostHog, Inc. | Product analytics and, where it is switched on, session recording. Enabled per deployment and, on the website, gated on your consent to the analytics category. | United States | IP address, which the server-side integration uses to identify a visitor, user and workspace identifiers, page, screen and feature usage events, recordings of in-application sessions where session recording is enabled |\n| Google LLC (Google Analytics) | Website traffic measurement on gauzy.co. Loads only after you consent to the analytics category. | United States | IP address, analytics client identifier, pages viewed, referrer, device and browser details |\n| Dealfront Group GmbH (Leadfeeder) | Business-audience identification on gauzy.co — resolving a visitor's IP address to the organisation it belongs to. Loads only after you consent to the marketing category. | Germany, European Union | IP address, inferred employer or organisation, pages viewed and referrer |\n| Chatwoot Inc. | The live support chat widget, which loads on gauzy.co and also inside the signed-in application when support chat is enabled. | United States | name and email address you give the widget, the content of the chat, IP address and session identifiers, the page or screen you were on when you opened it |\n| Intuit Inc. (Mailchimp) | Newsletter and mailing-list management for people who subscribe on gauzy.co. | United States | email address and name, subscription status and campaign engagement, IP address at the time of subscription |\n| Google LLC (Maps Platform and Places) | Map display, address autocomplete and location selection inside the application, where your administrator enables location features. | United States | IP address, the address text a user types into autocomplete, selected coordinates and resolved addresses |\n| Algolia SAS | Hosted search on the documentation site at docs.gauzy.co, where search credentials are configured. | France, European Union | search queries, IP address and user agent |\n| Honeycomb.io, Inc. | Distributed tracing and operational metrics for the API, where tracing is enabled and pointed at this provider. | United States | IP address, request URLs and route parameters, user and workspace identifiers carried in trace attributes |\n| SigNoz Inc. | Distributed tracing and operational metrics for the API, as an alternative destination to the above, where tracing is enabled and pointed at this provider. | United States | IP address, request URLs and route parameters, user and workspace identifiers carried in trace attributes |\n| Aspecto Ltd. | Distributed tracing for the API, as a further alternative destination, where tracing is enabled and pointed at this provider. | Israel, which holds a European Commission adequacy decision | IP address, request URLs, identifiers carried in trace attributes |\n| Jitsu Labs, Inc. | Event streaming to a product-analytics pipeline, where the hosted Jitsu service is configured as the destination rather than a destination we run ourselves. | United States | user and workspace identifiers, product events and the changes that produced them, IP address and browser details |\n| Bricks Software AS (Unleash) | Feature-flag evaluation, where the hosted Unleash service is configured rather than an instance we run ourselves. | Norway, European Economic Area | application and instance identifiers, flag evaluation context, which can include a user or workspace identifier |\n| Google LLC (Sign in with Google) | Sign-in, where a user chooses to authenticate with a Google account instead of a password. | United States | Google account identifier, email address, display name and profile picture |\n| Microsoft Corporation (Microsoft Entra ID) | Sign-in, where a user or an administrator chooses to authenticate with a Microsoft work or personal account. Profile details are read from Microsoft Graph. | United States | Microsoft account identifier, email address and display name |\n| LinkedIn Corporation | Sign-in, where a user chooses to authenticate with a LinkedIn account. | United States | LinkedIn account identifier, email address, name and profile picture |\n| Meta Platforms, Inc. | Sign-in, where a user chooses to authenticate with a Facebook account. | United States | Facebook account identifier, email address, name and profile picture |\n| X Corp. | Sign-in, where a user chooses to authenticate with an X account. | United States | X account identifier and screen name, email address where the provider releases it |\n| Okta, Inc. (Auth0) | Sign-in, where an organisation chooses to authenticate its people through a hosted Auth0 tenant. | United States | subject identifier issued by the identity provider, email address and name |\n| Fiverr International Ltd. | Account linking for freelancer profiles, where a user connects a Fiverr account. | Israel, which holds a European Commission adequacy decision | Fiverr account identifier, the profile fields the connection returns |\n| Red Hat, Inc. (Keycloak) | Sign-in against a Keycloak realm, where an organisation configures one. Whoever operates that realm holds the data, and where the organisation operates it there is no third party at all. | Determined by whoever operates the realm | subject identifier issued by the realm, username and email address |\n| Anthropic PBC | Model provider for the in-application AI assistant, connected by you with your own account and API key. Your agreement with this provider governs what it does with the content you send it. | United States | prompts and conversation content, any workspace content a user includes in a prompt |\n| OpenAI, L.L.C. | Model provider for the in-application AI assistant, connected by you with your own account and API key. Also reachable indirectly where you supply an OpenAI key to our own AI service for image analysis. | United States | prompts and conversation content, any workspace content a user includes in a prompt, screenshot-derived content where image analysis is routed to your OpenAI account |\n| Google LLC (Gemini) | Model provider for the in-application AI assistant, connected by you with your own account and API key. | United States | prompts and conversation content |\n| X.AI LLC | Model provider for the in-application AI assistant, connected by you with your own account and API key. | United States | prompts and conversation content |\n| OpenRouter, Inc. | Model routing for the in-application AI assistant, connected by you with your own account or through an authorisation flow you complete yourself. | United States | prompts and conversation content, OpenRouter account identity where you connect one |\n| Vercel Inc. (AI Gateway) | Gateway that forwards AI assistant requests to a downstream model provider, connected by you with your own account and API key. | United States | prompts and conversation content |\n| Netsoft Holdings, LLC (Hubstaff) | Integration you connect, importing organisations, projects, people, timesheets, activity levels and screenshots from your Hubstaff account into your workspace. | United States | names and email addresses of the people in your Hubstaff account, time logs and activity levels, screenshots captured by Hubstaff, project and task assignments |\n| Upwork Global Inc. | Integration you connect, importing contracts, freelancer profiles, time logs and income and expense reports from your Upwork account, and supporting job matching and proposal drafting. | United States | freelancer name and profile details, contract, earnings and time-log data, screenshots captured by Upwork |\n| Atlassian Corporation (Jira) | Integration you connect, synchronising projects, issues and worklogs between Jira and your workspace. | United States | Jira account identifiers, display names and email addresses, issue, comment and worklog content |\n| GitHub, Inc. (repository integration) | Integration you connect through a GitHub App, synchronising repositories, issues and labels with your workspace tasks. | United States | GitHub account identifiers, usernames and email addresses, issue and repository content within the granted scope |\n| Zapier, Inc. | Automation integration you connect, which reads and receives whatever records you wire into a Zap. | United States | any workspace record you route through an automation, including tasks, time logs, contacts and invoices |\n| Celonis SE (Make.com) | Automation integration you connect, which reads and receives whatever records you wire into a scenario. | Germany, European Union | any workspace record you route through an automation |\n| Activepieces Inc. | Automation integration you connect, which reads and receives whatever records you wire into a flow. | United States | any workspace record you route through an automation |\n| Sim Studio, Inc. (sim.ai) | AI workflow integration you connect, which receives the inputs you route into a workflow. | United States | workflow inputs, which can contain workspace record content |\n| WakaTime | Integration a developer connects, ingesting coding-activity heartbeats as time and activity records in your workspace. | United States | developer identity, names of files and projects being edited, editor, language and operating-system metadata with timestamps |\n\n### Tier 3 — self-hosted deployments only\n\nEver Gauzy can be run on your own infrastructure. If you do that, you choose these providers, you\nhold the credentials, and you contract with them directly.\n\n**We are not a processor for anything in a deployment you run.** We do not receive that data, we cannot\nreach it, and we have no relationship with the providers you configure. They appear here only so that\nreaders running their own copy know which external services the software can be configured to use.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Amazon Web Services, Inc. (S3) | One of the object-storage backends the open-source software can be pointed at for uploads, avatars, attachments and captured media in a deployment you run yourself. | The region you select in your own account | whatever your deployment stores, including screenshots, webcam stills, audio, video and uploaded documents |\n| Wasabi Technologies, Inc. | An S3-compatible object-storage backend the open-source software can be pointed at in a deployment you run yourself. | The region you select in your own account | whatever your deployment stores, including captured media and uploaded documents |\n| Cloudinary Ltd. | An image and media storage and delivery backend the open-source software can be pointed at in a deployment you run yourself. | The region you select in your own account | whatever your deployment stores, including screenshots, avatars and uploaded images |\n| DigitalOcean, LLC (Spaces) | An S3-compatible object-storage backend the open-source software can be pointed at in a deployment you run yourself. Distinct from the installer delivery listed in the always-engaged table above. | The region you select in your own account | whatever your deployment stores, including captured media and uploaded documents |\n\n### Storage of monitoring media\n\nScreenshots, webcam stills, audio and video captured by the desktop applications are stored through the\nfile-provider configured for the deployment. **For Ever Gauzy Cloud that is our own object storage,\non our own infrastructure**, which is why the commercial object-storage providers the software supports\nappear in tier 3 rather than tier 1. If that ever changes for the hosted Service, this list changes with\nit and the change is announced under the notification process above.\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://gauzy.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://gauzy.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 Gauzy, 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://gauzy.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://gauzy.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://gauzy.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[gauzy.co](https://gauzy.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://gauzy.co/subprocessors](https://gauzy.co/subprocessors)."
153
+ "markdown": "## Why this page exists\n\nWhen you use Ever Gauzy 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://gauzy.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 [gauzy.co](https://gauzy.co), for Ever Gauzy\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://gauzy.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://gauzy.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://gauzy.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 Gauzy\n\nThe tiers below follow the explanation above. Read the tier, not just the name — a provider in the second\nor third table is not processing your data unless the condition next to it is true.\n\n### Tier 1 — always engaged\n\nThese are in the path for every customer of Ever Gauzy Cloud. There is no setting that removes them.\nThis is the Article 28 sub-processor list proper.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | DNS, content delivery, TLS termination, web application firewall and the tunnels that carry traffic from the edge to our own infrastructure for gauzy.co, app.gauzy.co, api.gauzy.co and docs.gauzy.co. Every request to the Service passes through it. | United States, with edge termination worldwide | IP address, user agent and device characteristics, requested URLs and request headers, TLS and connection metadata, cookies in transit |\n| ActiveCampaign, LLC (Postmark) | Delivery of transactional and notification email — workspace invitations, email verification, sign-in codes, password resets, invoice and estimate emails, timesheet and approval notifications, and replies to the contact form on gauzy.co. | United States | recipient name and email address, message subject and body, which can contain invoice, timesheet and HR content, single-use sign-in and verification codes, delivery, bounce and open metadata |\n| Chargebee Inc. | Subscription billing and hosted checkout for licence and subscription purchases started from gauzy.co. Card details are entered on Chargebee's own hosted page and never reach us. | United States | billing name and email address, billing address and tax identification number, plan, invoice and payment history, IP address |\n| GitHub, Inc. | Source hosting, continuous integration and the container registry that serves the production images for the Service. It is how the Service is built and deployed, not where your data lives. | United States | build, release and deployment metadata, developer and automation account identifiers, no workspace content and no captured media |\n| DigitalOcean, LLC | Object storage and content delivery for the public desktop, agent and server installers offered on the download page of gauzy.co. It serves the installer files themselves and nothing else. | United States | IP address of the person downloading, user agent and requested file |\n| Iubenda S.r.l. | Consent management on gauzy.co — presenting the banner and preference centre, recording your choice and making it available to the scripts that wait on it. | Italy, European Union | IP address, user agent, consent preferences and the timestamp of the choice |\n| Google LLC (reCAPTCHA) | Bot protection on the public forms of gauzy.co — contact and newsletter — with server-side verification of the resulting token. Treated as strictly necessary for the reasons given in our Cookie Policy. | United States | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\nNone of these is engaged by default. Each one arrives because someone switched something on: an\nadministrator enabled a feature, connected an integration, or configured a provider; or a visitor consented\nto a cookie category.\n\nTwo of these deserve to be called out rather than left in a table.\n\n- **Integrations you connect are two-way.** Where your organisation connects Hubstaff, Upwork, Jira,\n GitHub or a similar platform, data moves in both directions and the other platform's own terms and\n privacy notice apply to its half. Connecting it is the act that authorises the exchange.\n- **AI providers are often yours, not ours.** Several AI features work on a bring-your-own-key basis. Where\n your organisation supplies its own API key, **your organisation is the one contracting with that\n provider**, and its terms and privacy notice govern what happens to the content sent there. We do not\n become that provider's customer on your behalf, and we cannot make commitments about it.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Functional Software, Inc. (Sentry) | Error, crash and performance reporting from the API, the web application, the desktop and agent applications and the gauzy.co website, where error reporting is enabled for the deployment. | United States | IP address and device or operating-system details, user identifier and email address attached to an error event, URLs, route parameters and stack traces, which can contain fragments of the failing request, a masked replay of the website session in which an error occurred |\n| PostHog, Inc. | Product analytics and, where it is switched on, session recording. Enabled per deployment and, on the website, gated on your consent to the analytics category. | United States | IP address, which the server-side integration uses to identify a visitor, user and workspace identifiers, page, screen and feature usage events, recordings of in-application sessions where session recording is enabled |\n| Google LLC (Google Analytics) | Website traffic measurement on gauzy.co. Loads only after you consent to the analytics category. | United States | IP address, analytics client identifier, pages viewed, referrer, device and browser details |\n| Dealfront Group GmbH (Leadfeeder) | Business-audience identification on gauzy.co — resolving a visitor's IP address to the organisation it belongs to. Loads only after you consent to the marketing category. | Germany, European Union | IP address, inferred employer or organisation, pages viewed and referrer |\n| Chatwoot Inc. | The live support chat widget, which loads on gauzy.co and also inside the signed-in application when support chat is enabled. | United States | name and email address you give the widget, the content of the chat, IP address and session identifiers, the page or screen you were on when you opened it |\n| Intuit Inc. (Mailchimp) | Newsletter and mailing-list management for people who subscribe on gauzy.co. | United States | email address and name, subscription status and campaign engagement, IP address at the time of subscription |\n| Google LLC (Maps Platform and Places) | Map display, address autocomplete and location selection inside the application, where your administrator enables location features. | United States | IP address, the address text a user types into autocomplete, selected coordinates and resolved addresses |\n| Algolia SAS | Hosted search on the documentation site at docs.gauzy.co, where search credentials are configured. | France, European Union | search queries, IP address and user agent |\n| Honeycomb.io, Inc. | Distributed tracing and operational metrics for the API, where tracing is enabled and pointed at this provider. | United States | IP address, request URLs and route parameters, user and workspace identifiers carried in trace attributes |\n| SigNoz Inc. | Distributed tracing and operational metrics for the API, as an alternative destination to the above, where tracing is enabled and pointed at this provider. | United States | IP address, request URLs and route parameters, user and workspace identifiers carried in trace attributes |\n| Aspecto Ltd. | Distributed tracing for the API, as a further alternative destination, where tracing is enabled and pointed at this provider. | Israel, which holds a European Commission adequacy decision | IP address, request URLs, identifiers carried in trace attributes |\n| Jitsu Labs, Inc. | Event streaming to a product-analytics pipeline, where the hosted Jitsu service is configured as the destination rather than a destination we run ourselves. | United States | user and workspace identifiers, product events and the changes that produced them, IP address and browser details |\n| Bricks Software AS (Unleash) | Feature-flag evaluation, where the hosted Unleash service is configured rather than an instance we run ourselves. | Norway, European Economic Area | application and instance identifiers, flag evaluation context, which can include a user or workspace identifier |\n| Google LLC (Sign in with Google) | Sign-in, where a user chooses to authenticate with a Google account instead of a password. | United States | Google account identifier, email address, display name and profile picture |\n| Microsoft Corporation (Microsoft Entra ID) | Sign-in, where a user or an administrator chooses to authenticate with a Microsoft work or personal account. Profile details are read from Microsoft Graph. | United States | Microsoft account identifier, email address and display name |\n| LinkedIn Corporation | Sign-in, where a user chooses to authenticate with a LinkedIn account. | United States | LinkedIn account identifier, email address, name and profile picture |\n| Meta Platforms, Inc. | Sign-in, where a user chooses to authenticate with a Facebook account. | United States | Facebook account identifier, email address, name and profile picture |\n| X Corp. | Sign-in, where a user chooses to authenticate with an X account. | United States | X account identifier and screen name, email address where the provider releases it |\n| Okta, Inc. (Auth0) | Sign-in, where an organisation chooses to authenticate its people through a hosted Auth0 tenant. | United States | subject identifier issued by the identity provider, email address and name |\n| Fiverr International Ltd. | Account linking for freelancer profiles, where a user connects a Fiverr account. | Israel, which holds a European Commission adequacy decision | Fiverr account identifier, the profile fields the connection returns |\n| Red Hat, Inc. (Keycloak) | Sign-in against a Keycloak realm, where an organisation configures one. Whoever operates that realm holds the data, and where the organisation operates it there is no third party at all. | Determined by whoever operates the realm | subject identifier issued by the realm, username and email address |\n| Anthropic PBC | Model provider for the in-application AI assistant, connected by you with your own account and API key. Your agreement with this provider governs what it does with the content you send it. | United States | prompts and conversation content, any workspace content a user includes in a prompt |\n| OpenAI, L.L.C. | Model provider for the in-application AI assistant, connected by you with your own account and API key. Also reachable indirectly where you supply an OpenAI key to our own AI service for image analysis. | United States | prompts and conversation content, any workspace content a user includes in a prompt, screenshot-derived content where image analysis is routed to your OpenAI account |\n| Google LLC (Gemini) | Model provider for the in-application AI assistant, connected by you with your own account and API key. | United States | prompts and conversation content |\n| X.AI LLC | Model provider for the in-application AI assistant, connected by you with your own account and API key. | United States | prompts and conversation content |\n| OpenRouter, Inc. | Model routing for the in-application AI assistant, connected by you with your own account or through an authorisation flow you complete yourself. | United States | prompts and conversation content, OpenRouter account identity where you connect one |\n| Vercel Inc. (AI Gateway) | Gateway that forwards AI assistant requests to a downstream model provider, connected by you with your own account and API key. | United States | prompts and conversation content |\n| Netsoft Holdings, LLC (Hubstaff) | Integration you connect, importing organisations, projects, people, timesheets, activity levels and screenshots from your Hubstaff account into your workspace. | United States | names and email addresses of the people in your Hubstaff account, time logs and activity levels, screenshots captured by Hubstaff, project and task assignments |\n| Upwork Global Inc. | Integration you connect, importing contracts, freelancer profiles, time logs and income and expense reports from your Upwork account, and supporting job matching and proposal drafting. | United States | freelancer name and profile details, contract, earnings and time-log data, screenshots captured by Upwork |\n| Atlassian Corporation (Jira) | Integration you connect, synchronising projects, issues and worklogs between Jira and your workspace. | United States | Jira account identifiers, display names and email addresses, issue, comment and worklog content |\n| GitHub, Inc. (repository integration) | Integration you connect through a GitHub App, synchronising repositories, issues and labels with your workspace tasks. | United States | GitHub account identifiers, usernames and email addresses, issue and repository content within the granted scope |\n| Zapier, Inc. | Automation integration you connect, which reads and receives whatever records you wire into a Zap. | United States | any workspace record you route through an automation, including tasks, time logs, contacts and invoices |\n| Celonis SE (Make.com) | Automation integration you connect, which reads and receives whatever records you wire into a scenario. | Germany, European Union | any workspace record you route through an automation |\n| Activepieces Inc. | Automation integration you connect, which reads and receives whatever records you wire into a flow. | United States | any workspace record you route through an automation |\n| Sim Studio, Inc. (sim.ai) | AI workflow integration you connect, which receives the inputs you route into a workflow. | United States | workflow inputs, which can contain workspace record content |\n| WakaTime | Integration a developer connects, ingesting coding-activity heartbeats as time and activity records in your workspace. | United States | developer identity, names of files and projects being edited, editor, language and operating-system metadata with timestamps |\n\n### Tier 3 — self-hosted deployments only\n\nEver Gauzy can be run on your own infrastructure. If you do that, you choose these providers, you\nhold the credentials, and you contract with them directly.\n\n**We are not a processor for anything in a deployment you run.** We do not receive that data, we cannot\nreach it, and we have no relationship with the providers you configure. They appear here only so that\nreaders running their own copy know which external services the software can be configured to use.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Amazon Web Services, Inc. (S3) | One of the object-storage backends the open-source software can be pointed at for uploads, avatars, attachments and captured media in a deployment you run yourself. | The region you select in your own account | whatever your deployment stores, including screenshots, webcam stills, audio, video and uploaded documents |\n| Wasabi Technologies, Inc. | An S3-compatible object-storage backend the open-source software can be pointed at in a deployment you run yourself. | The region you select in your own account | whatever your deployment stores, including captured media and uploaded documents |\n| Cloudinary Ltd. | An image and media storage and delivery backend the open-source software can be pointed at in a deployment you run yourself. | The region you select in your own account | whatever your deployment stores, including screenshots, avatars and uploaded images |\n| DigitalOcean, LLC (Spaces) | An S3-compatible object-storage backend the open-source software can be pointed at in a deployment you run yourself. Distinct from the installer delivery listed in the always-engaged table above. | The region you select in your own account | whatever your deployment stores, including captured media and uploaded documents |\n\n### Storage of monitoring media\n\nScreenshots, webcam stills, audio and video captured by the desktop applications are stored through the\nfile-provider configured for the deployment. **For Ever Gauzy Cloud that is our own object storage,\non our own infrastructure**, which is why the commercial object-storage providers the software supports\nappear in tier 3 rather than tier 1. If that ever changes for the hosted Service, this list changes with\nit and the change is announced under the notification process above.\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://gauzy.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://gauzy.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 Gauzy, 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://gauzy.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://gauzy.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://gauzy.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[gauzy.co](https://gauzy.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://gauzy.co/subprocessors](https://gauzy.co/subprocessors)."
154
154
  }
@@ -459,7 +459,7 @@ and mark the letter for the attention of the privacy team. We correspond in Engl
459
459
  Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
460
460
  <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
461
461
  to the authority for the country where you live or work.</p>
462
- <p>This document is version 1.0.0 of the sub-processor list for
462
+ <p>This document is version 1.0.1 of the sub-processor list for
463
463
  <a href="https://githands.com">githands.com</a>, in force from 2026-08-02. It lists the providers engaged
464
464
  as at that date. Earlier versions, with the dates they applied, are at
465
465
  <a href="https://githands.com/subprocessors">https://githands.com/subprocessors</a>.</p>