@ever-co/legal 0.1.2 → 0.2.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 (88) hide show
  1. package/dist/content/aup/ever-async/en.html +778 -0
  2. package/dist/content/aup/ever-async/en.json +343 -0
  3. package/dist/content/aup/hust/en.html +9 -0
  4. package/dist/content/aup/hust/en.json +2 -2
  5. package/dist/content/cookies/ever-async/en.html +457 -0
  6. package/dist/content/cookies/ever-async/en.json +185 -0
  7. package/dist/content/cookies/ever-demand/en.html +5 -2
  8. package/dist/content/cookies/ever-demand/en.json +2 -2
  9. package/dist/content/cookies/ever-rec/en.html +5 -2
  10. package/dist/content/cookies/ever-rec/en.json +2 -2
  11. package/dist/content/cookies/ever-teams/en.html +5 -2
  12. package/dist/content/cookies/ever-teams/en.json +2 -2
  13. package/dist/content/cookies/ever-works/en.html +5 -2
  14. package/dist/content/cookies/ever-works/en.json +2 -2
  15. package/dist/content/cookies/gauzy/en.html +5 -2
  16. package/dist/content/cookies/gauzy/en.json +2 -2
  17. package/dist/content/cookies/githands/en.html +5 -2
  18. package/dist/content/cookies/githands/en.json +2 -2
  19. package/dist/content/cookies/hust/en.html +5 -2
  20. package/dist/content/cookies/hust/en.json +2 -2
  21. package/dist/content/dpa/ever-async/en.html +1848 -0
  22. package/dist/content/dpa/ever-async/en.json +640 -0
  23. package/dist/content/privacy/ever-async/en.html +1350 -0
  24. package/dist/content/privacy/ever-async/en.json +364 -0
  25. package/dist/content/privacy/ever-corporate/en.html +86 -3
  26. package/dist/content/privacy/ever-corporate/en.json +2 -2
  27. package/dist/content/privacy/ever-demand/en.html +99 -2
  28. package/dist/content/privacy/ever-demand/en.json +2 -2
  29. package/dist/content/privacy/ever-rec/en.html +110 -3
  30. package/dist/content/privacy/ever-rec/en.json +2 -2
  31. package/dist/content/privacy/ever-teams/en.html +97 -1
  32. package/dist/content/privacy/ever-teams/en.json +2 -2
  33. package/dist/content/privacy/ever-tech/en.html +86 -3
  34. package/dist/content/privacy/ever-tech/en.json +2 -2
  35. package/dist/content/privacy/ever-works/en.html +74 -5
  36. package/dist/content/privacy/ever-works/en.json +2 -2
  37. package/dist/content/privacy/everiq/en.html +107 -0
  38. package/dist/content/privacy/everiq/en.json +2 -2
  39. package/dist/content/privacy/gauzy/en.html +88 -3
  40. package/dist/content/privacy/gauzy/en.json +2 -2
  41. package/dist/content/privacy/githands/en.html +83 -2
  42. package/dist/content/privacy/githands/en.json +2 -2
  43. package/dist/content/privacy/hust/en.html +186 -37
  44. package/dist/content/privacy/hust/en.json +3 -3
  45. package/dist/content/privacy/traduora/en.html +93 -0
  46. package/dist/content/privacy/traduora/en.json +2 -2
  47. package/dist/content/refund/ever-rec/en.html +595 -0
  48. package/dist/content/refund/ever-rec/en.json +336 -0
  49. package/dist/content/security/ever-async/en.html +853 -0
  50. package/dist/content/security/ever-async/en.json +417 -0
  51. package/dist/content/security/ever-corporate/en.html +768 -0
  52. package/dist/content/security/ever-corporate/en.json +380 -0
  53. package/dist/content/security/ever-tech/en.html +768 -0
  54. package/dist/content/security/ever-tech/en.json +380 -0
  55. package/dist/content/security/traduora/en.html +768 -0
  56. package/dist/content/security/traduora/en.json +380 -0
  57. package/dist/content/subprocessors/ever-async/en.html +852 -0
  58. package/dist/content/subprocessors/ever-async/en.json +166 -0
  59. package/dist/content/subprocessors/ever-corporate/en.html +403 -9
  60. package/dist/content/subprocessors/ever-corporate/en.json +6 -2
  61. package/dist/content/subprocessors/ever-demand/en.html +443 -13
  62. package/dist/content/subprocessors/ever-demand/en.json +6 -2
  63. package/dist/content/subprocessors/ever-rec/en.html +493 -10
  64. package/dist/content/subprocessors/ever-rec/en.json +6 -2
  65. package/dist/content/subprocessors/ever-teams/en.html +435 -8
  66. package/dist/content/subprocessors/ever-teams/en.json +6 -2
  67. package/dist/content/subprocessors/ever-tech/en.html +443 -9
  68. package/dist/content/subprocessors/ever-tech/en.json +6 -2
  69. package/dist/content/subprocessors/ever-works/en.html +354 -13
  70. package/dist/content/subprocessors/ever-works/en.json +6 -2
  71. package/dist/content/subprocessors/everiq/en.html +484 -3
  72. package/dist/content/subprocessors/everiq/en.json +6 -2
  73. package/dist/content/subprocessors/gauzy/en.html +353 -20
  74. package/dist/content/subprocessors/gauzy/en.json +6 -2
  75. package/dist/content/subprocessors/githands/en.html +451 -13
  76. package/dist/content/subprocessors/githands/en.json +6 -2
  77. package/dist/content/subprocessors/hust/en.html +502 -12
  78. package/dist/content/subprocessors/hust/en.json +14 -2
  79. package/dist/content/subprocessors/traduora/en.html +461 -4
  80. package/dist/content/subprocessors/traduora/en.json +6 -2
  81. package/dist/content/tos/ever-async/en.html +1350 -0
  82. package/dist/content/tos/ever-async/en.json +687 -0
  83. package/dist/content/tos/ever-rec/en.html +40 -11
  84. package/dist/content/tos/ever-rec/en.json +5 -5
  85. package/dist/content/tos/hust/en.html +32 -8
  86. package/dist/content/tos/hust/en.json +10 -2
  87. package/dist/index.json +12493 -8166
  88. package/package.json +1 -1
@@ -8,7 +8,7 @@
8
8
  "locale": "en",
9
9
  "version": "1.0.2",
10
10
  "effectiveDate": "2026-08-02",
11
- "sha256": "6724ddc62bc53c93d5d41f3d0ac1c36a3c9d6308f90830ac603575bc17953771",
11
+ "sha256": "3e636816118b607cdfdb5087f88bff047af876c995c70e0c52222ebe019c5caa",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/subprocessors/010-purpose",
@@ -52,6 +52,10 @@
52
52
  "level": 3,
53
53
  "text": "What the columns mean"
54
54
  },
55
+ {
56
+ "level": 3,
57
+ "text": "Why this list is deliberately longer than it needs to be"
58
+ },
55
59
  {
56
60
  "level": 3,
57
61
  "text": "What is deliberately not in the tables"
@@ -150,5 +154,5 @@
150
154
  }
151
155
  ],
152
156
  "path": "content/subprocessors/ever-rec/en.html",
153
- "markdown": "## Why this page exists\n\nWhen you use Ever Rec 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://rec.so/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [rec.so](https://rec.so), for Ever Rec\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://rec.so/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where that is outside the European Economic Area, the transfer mechanism we\n rely on for it is described in the international transfers section of our\n [Privacy Policy](https://rec.so/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### What is deliberately not in the tables\n\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\n container platform are not sub-processors, because there is no third party involved. The next section\n describes what we run and what really does sit in front of it.\n- **Recipients that are not processors** — payment providers acting under their own regulatory\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\n are covered in the [Privacy Policy](https://rec.so/privacy).\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\n site, their notice applies.\n\n## Annex: Ever Rec\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination, content delivery and bot/DDoS filtering in front of rec.so, app.rec.so and api.rec.so, and the tunnel that reaches our origin. Every request to the Service passes through it. | United States, with connections terminated at the edge location nearest the visitor worldwide | IP address, request URL, headers and TLS metadata, cookies in transit |\n| Google Ireland Limited (Firebase) | The core store for the hosted Service. Firebase Authentication holds account identity and sign-in; Firebase Realtime Database holds item metadata, folder and workspace structure, sharing records, comments, likes and the view records described in the Privacy Policy; Firebase Cloud Storage holds the screenshots, recordings, edited images and whiteboards themselves. | European Union and United States | screenshots, screen recordings, webcam and audio recordings, edited images and whiteboards, item titles, descriptions, chapters, folder and workspace structure, account identifier, email address, display name, profile picture and authentication tokens, sharing records, comments, likes, and viewer IP addresses and identities |\n| Mux, Inc. | Transcoding, thumbnailing and adaptive streaming of screen recordings, and playback quality telemetry in the player. Mux and Api Video SAS are the two selectable video backends; the hosted Service uses one of them for every screen recording, and we will tell you which is in use for your account on request. Recording CONTENT reaches this provider, not only metadata. | United States | screen recording video content, which can contain anything that was on the capturer's screen, video thumbnails and asset identifiers, viewer IP address and playback telemetry |\n| Api Video SAS | The alternative video backend to Mux, on the same basis — transcoding, hosting and streaming of screen recordings, with direct upload from the browser extension. Recording CONTENT reaches this provider. | France, with delivery from servers worldwide | screen recording video content, video thumbnails and asset identifiers, viewer IP address on playback |\n| Functional Software, Inc. d/b/a Sentry | Error and performance telemetry from the web portal, the API and the browser extension, so that we can see what is failing and fix it. | United States | IP address, browser and device, the page or endpoint that failed, stack traces and breadcrumbs, account identifier where the error occurred while signed in, fragments of the failing request, which can incidentally contain other data |\n| ActiveCampaign, LLC (Postmark) | Delivery of the transactional email the Service sends — account welcome, password reset, workspace invitation, and the notification that someone has shared an image or a recording with you. | United States | recipient email address, sender display name, the free-text message a sharer chooses to include, the link to the shared item |\n| Twilio Inc. (Twilio Segment) | Product analytics for the hosted application. Events are emitted when an account registers, signs in and connects an integration, keyed to the account identifier. | United States | account identifier and account traits, product events and their timestamps, IP address |\n| GitHub, Inc. | Source hosting, continuous integration and the container registry the Service is built from and deployed out of. This is how the Service is made, not where your data lives. | United States | no capture content and no account content, contributor and developer identity in commits and build logs |\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| Twilio Inc. | Delivery of a capture to a WhatsApp or SMS recipient. Engaged only when a user chooses to send an item that way, and only for that send. | United States | recipient telephone number, message body, the link to the shared item |\n| Rebrandly S.r.l. | Shortening a share link. Engaged only when a user chooses to shorten one. Rebrandly holds the destination address and sees every click on the short link. | Italy | the destination address of the shared item, IP address, user agent and referrer of anyone opening the short link |\n| Google Ireland Limited (Sign in with Google, Google Drive) | Signing in with a Google account instead of a password, and saving a capture into your own Google Drive. Both are started by the individual user; neither runs unless you choose it. | European Union and United States | Google account identifier, email address, display name and profile picture, OAuth access and refresh tokens held so the connection keeps working, the capture you choose to copy into your own Drive |\n| Dropbox International Unlimited Company | Saving a capture into your own Dropbox, when you connect a Dropbox account and choose to send one. | Ireland and United States | Dropbox account identifier and OAuth tokens, the capture you choose to copy into your own Dropbox |\n| Salesforce, Inc. (Slack) | Posting a capture into a Slack channel, when a user connects a Slack workspace and chooses to send one there. | United States | Slack workspace and account identifiers, and OAuth tokens, the capture and the message posted with it |\n| Atlassian Pty Ltd (Jira, Trello) | Attaching a capture to a Jira issue or a Trello card, when a user connects that account and chooses to attach one. | Australia, with hosting in the European Union and United States | Atlassian or Trello account identifier and OAuth tokens, the capture attached, and the issue or card it is attached to |\n| Google Ireland Limited (Google Analytics 4, Google Tag Manager) | Website analytics on rec.so. Loads only after you accept analytics cookies in the consent banner, and never inside the signed-in application. | European Union and United States | IP address and a persistent analytics identifier, pages viewed, referrer, device, browser and operating system |\n| PostHog, Inc. | Website product analytics on rec.so — which pages are viewed and where people leave. Loads only after you accept analytics cookies. | United States | IP address and a persistent visitor identifier, pageview and page-leave events, referrer, device and browser |\n| Chatwoot Inc. | The support chat widget on the rec.so website, engaged when you open it and start a conversation. | United States | name and email address if you give them, the messages in the conversation, IP address and the page you were on |\n| The Rocket Science Group LLC (Mailchimp, an Intuit company) | The rec.so newsletter. Engaged only if you subscribe, and you can unsubscribe from any message we send. | United States | email address, subscription status, tags and the date you subscribed, the IP address the subscription came from |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Rec on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| The S3-compatible object storage provider you configure in the desktop application | The Ever Rec desktop application uploads its captures to a bucket YOU nominate. You enter the endpoint, region, bucket name, access key and secret, and they are held in your own operating system's keychain on your own machine. We never receive those captures and we never see those credentials. | Wherever the provider you chose stores it — you decide, and you contract with it | screenshots and recordings taken by the desktop application, the metadata the desktop application records alongside them |\n| Your own Google Firebase project | A self-hosted deployment of the open-source platform points at a Firebase project you create, with your own credentials, for authentication, metadata and capture storage. | The regions you select when you create the project | everything your deployment's users capture, and their account identities |\n| Your own video streaming account (Mux, Inc. or Api Video SAS) | A self-hosted deployment transcodes and streams recordings through whichever of the two you configure. | Determined by the account you open | the recordings your deployment's users make |\n| Your own email, messaging, analytics, error-tracking and link-shortening accounts (Postmark, Twilio, Twilio Segment, Sentry, Rebrandly) | A self-hosted deployment can be configured to send its mail, its WhatsApp messages, its product analytics, its error reports and its short links through accounts you open in your own name. Configure none of them and none of them is involved. | Determined by the accounts you open | whatever your deployment sends them, under your configuration and your contracts |\n\n### Where recordings are stored\n\nRecordings, screenshots and their thumbnails are held in our object storage on our own infrastructure.\n**No recording is sent to a third party for analysis, transcription or advertising.**\n\nWhere you share a recording by link, the recipient's access is served from that same storage. Sharing is\nthe act that exposes it — the link is the control, and the privacy annex explains how to withdraw it.\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://rec.so/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://rec.so/privacy).\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\n third party and it is disclosed as one.\n\n### Where a product does something different\n\nA small number of products use a third-party managed database, managed storage or hosted platform for a\nspecific function instead of our own infrastructure. **Where that is the case for Ever Rec, 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://rec.so/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://rec.so/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://rec.so/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.2 of the sub-processor list for\n[rec.so](https://rec.so), in force from 2026-08-02. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://rec.so/subprocessors](https://rec.so/subprocessors)."
157
+ "markdown": "## Why this page exists\n\nWhen you use Ever Rec 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://rec.so/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [rec.so](https://rec.so), for Ever Rec\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://rec.so/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where a provider contracts through a European establishment but processes\n elsewhere, this column says both, because the two are different facts and only naming the first would\n flatter us.\n- **Transfer mechanism** — for a provider outside the European Economic Area, the Chapter V instrument we\n actually rely on for that specific provider: an adequacy decision, the Standard Contractual Clauses, or\n nothing yet. **Where it reads \"To be confirmed\", we have not yet evidenced an instrument for that\n provider, and we would rather say so here than print one we cannot produce.** That is a live piece of\n work, not a formula. Providers established inside the EEA need no mechanism and say so. For the third\n tier the transfer is not ours at all — you choose the provider and hold the contract.\n The general rules behind this column are in the international transfers section of our\n [Privacy Policy](https://rec.so/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### Why this list is deliberately longer than it needs to be\n\n**We list providers we may engage, not only the ones engaged today.** Where we have configured a\nprovider, kept one available behind a feature flag, used one recently, or expect to use one for a\npurpose already described here, it appears in the tables below — even if no data has reached it this\nmonth, and even where we currently run the equivalent ourselves.\n\nWe do this on purpose, and you should read the tables with it in mind:\n\n- **A provider appearing here is not proof that your data has reached it.** It means the provider is\n within the scope of what we have told you we may do, at the tier shown. The tier is the part that\n tells you when it is engaged.\n- **Where we self-host something today** — our analytics, our job runner, our databases, our object\n storage — we say so, and we also name the hosted service we would move to, so that a later change is\n covered by a disclosure you have already seen rather than by a fresh surprise.\n- **The alternative is worse.** A list that names only today's exact set has to be re-issued, and\n re-consented, every time an engineer changes a setting. A list drawn slightly wide stays true through\n ordinary operational change, which is what makes it dependable.\n\n**What we will not do is use this as cover.** Breadth here does not license a purpose we have not\ndescribed, a category of data we have not listed, or a transfer without a mechanism. If we start\nsending a new *kind* of personal data, or sending it for a new *reason*, that is a change to this page\nand to the notice period below — not something the width of a table quietly absorbs.\n\nIf you need to know precisely which providers are live for your workspace today, rather than which ones\nmay be, ask us at privacy@ever.co and we will tell you.\n\n### What is deliberately not in the tables\n\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\n container platform are not sub-processors, because there is no third party involved. The next section\n describes what we run and what really does sit in front of it.\n- **Recipients that are not processors** — payment providers acting under their own regulatory\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\n are covered in the [Privacy Policy](https://rec.so/privacy).\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\n site, their notice applies.\n\n## Annex: Ever Rec\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination, content delivery and bot/DDoS filtering in front of rec.so, app.rec.so and api.rec.so, and the tunnel that reaches our origin. Every request to the Service passes through it. | United States, with connections terminated at the edge location nearest the visitor worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, request URL, headers and TLS metadata, cookies in transit |\n| Google Ireland Limited (Firebase) | The core store for the hosted Service. Firebase Authentication holds account identity and sign-in; Firebase Realtime Database holds item metadata, folder and workspace structure, sharing records, comments, likes and the view records described in the Privacy Policy; Firebase Cloud Storage holds the screenshots, recordings, edited images and whiteboards themselves. | European Union and United States | Standard Contractual Clauses (EU 2021/914) | screenshots, screen recordings, webcam and audio recordings, edited images and whiteboards, item titles, descriptions, chapters, folder and workspace structure, account identifier, email address, display name, profile picture and authentication tokens, sharing records, comments, likes, and viewer IP addresses and identities |\n| Mux, Inc. | Transcoding, thumbnailing and adaptive streaming of screen recordings, and playback quality telemetry in the player. Mux and Api Video SAS are the two selectable video backends; the hosted Service uses one of them for every screen recording, and we will tell you which is in use for your account on request. Recording CONTENT reaches this provider, not only metadata. | United States | Standard Contractual Clauses (EU 2021/914) | screen recording video content, which can contain anything that was on the capturer's screen, video thumbnails and asset identifiers, viewer IP address and playback telemetry |\n| api.video SAS | The alternative video backend to Mux, on the same basis — transcoding, hosting and streaming of screen recordings, with direct upload from the browser extension. Recording CONTENT reaches this provider. | France, with delivery from servers worldwide | None needed — established in the EEA | screen recording video content, video thumbnails and asset identifiers, viewer IP address on playback |\n| Functional Software, Inc. d/b/a Sentry | Error and performance telemetry from the web portal, the API and the browser extension, so that we can see what is failing and fix it. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, browser and device, the page or endpoint that failed, stack traces and breadcrumbs, account identifier where the error occurred while signed in, fragments of the failing request, which can incidentally contain other data |\n| ActiveCampaign, LLC (Postmark) | Delivery of the transactional email the Service sends — account welcome, password reset, workspace invitation, and the notification that someone has shared an image or a recording with you. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address, sender display name, the free-text message a sharer chooses to include, the link to the shared item |\n| Twilio Inc. (Segment) | Product analytics for the hosted application. Events are emitted when an account registers, signs in and connects an integration, keyed to the account identifier. | United States | Standard Contractual Clauses (EU 2021/914) | account identifier and account traits, product events and their timestamps, IP address |\n| GitHub, Inc. (a Microsoft Corporation company) | Source hosting, continuous integration and the container registry the Service is built from and deployed out of. This is how the Service is made, not where your data lives. | United States | Standard Contractual Clauses (EU 2021/914) | no capture content and no account content, contributor and developer identity in commits and build logs |\n| Cloudflare, Inc. (R2 object storage) | Holds the encrypted off-site copy of our backups - Postgres WAL and dumps, Velero, etcd, Proxmox configuration and MinIO mirrors - as the third tier of the backup chain (node8 NVMe, then Ceph RGW, then Cloudflare R2). Encrypted by us before it leaves our network. | United States | Standard Contractual Clauses (EU 2021/914) | client-side encrypted backup archives only - no plaintext is ever readable by the provider, the archives themselves derive from every category of data the products hold |\n| Google Ireland Limited (Google Workspace) | Hosts the corporate mailboxes that receive every support, privacy and rights request our own documents tell data subjects to write to, plus the recruitment mailbox that holds candidate CVs. | Ireland (contracting) / United States and global (Google LLC) | Standard Contractual Clauses (EU 2021/914) | all inbound and outbound company email, support, DSAR and privacy correspondence with data subjects, candidate CVs and application correspondence (ever-tech careers), customer and supplier correspondence and attachments |\n| Google Ireland Limited (reCAPTCHA) | Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made. | Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com |\n| Cloudflare, Inc. (Turnstile) | Checks that the person completing registration, onboarding or an anonymous flow is not a bot; on ever-works the API refuses the anonymous flow when no CAPTCHA provider is configured, which is why it is unconditional there. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device signals, mouse, touch and timing interaction signals, Turnstile challenge cookie |\n| Clerk, Inc. | Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name. | United States | Standard Contractual Clauses (EU 2021/914) | name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored |\n| Tavily | The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain. | United States | To be confirmed — we do not yet evidence a mechanism | search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata |\n| ui-avatars.com | Generates placeholder avatars where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser. | UNKNOWN - not published by the provider | To be confirmed — we do not yet evidence a mechanism | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n| Prospect One sp. z o.o. (jsDelivr) | Serves the Lottie animation runtime hard-coded into the ever-works login and register pages, so every person who opens the login page hands their IP to it before authenticating. | Poland (operator); delivery worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified | Second permitted origin for the Lottie animation runtime on the ever-works login and register pages. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Resend, Inc. | Sends transactional mail for the products and domains configured against it, relaying onward through Amazon SES. | United States | Standard Contractual Clauses (EU 2021/914) | recipient name and email address, message subject and body, delivery and bounce metadata |\n| Langfuse GmbH | Stores the full prompts and completions of AI features together with model, latency and cost metadata, so that agent behaviour can be traced and scored. | Germany | None needed — established in the EEA | full prompt and completion text, which can contain user-authored content and personal data, user and session identifiers, model, latency, token and cost metadata, developer scoring outputs |\n| OpenRouter, Inc. | Is the model provider behind the default 'Ever Works AI' option and the hard-coded default for AI Chat on every provisioned tenant site, receiving the raw prompt and forwarding it to whichever upstream model the selected model id resolves to. | United States | To be confirmed — we do not yet evidence a mechanism | full prompt text, including any customer or end-user content pasted into an agent - repo text, CVs, job descriptions, chat messages, generated completions, agent tool-call arguments, API key metadata and usage accounting |\n| Chargebee, Inc. - VERIFY; Chargebee Europe BV (Netherlands) is the EEA entity if it is the one contracting. | Handles subscription billing and invoicing for the hosted Gauzy service. | United States / Netherlands | To be confirmed — we do not yet evidence a mechanism | billing identity and address, plan, invoice and payment history |\n| Shopify International Limited | Runs the storefront and order pipeline for the shop product, holding customer, order and payment-status records. | Ireland (contracting) / Canada and United States (Shopify group) | Standard Contractual Clauses (EU 2021/914) | customer name, email address and shipping address, order and payment status, browsing and cart events on the storefront, cookies set by the storefront |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Twilio Inc. (SendGrid) | Delivery of a capture to a WhatsApp or SMS recipient. Engaged only when a user chooses to send an item that way, and only for that send. | United States | Standard Contractual Clauses (EU 2021/914) | recipient telephone number, message body, the link to the shared item |\n| Rebrandly S.r.l. | Shortening a share link. Engaged only when a user chooses to shorten one. Rebrandly holds the destination address and sees every click on the short link. | Italy | None needed — established in the EEA | the destination address of the shared item, IP address, user agent and referrer of anyone opening the short link |\n| Google Ireland Limited (Sign in with Google, Google Drive) | Signing in with a Google account instead of a password, and saving a capture into your own Google Drive. Both are started by the individual user; neither runs unless you choose it. | European Union and United States | Standard Contractual Clauses (EU 2021/914) | Google account identifier, email address, display name and profile picture, OAuth access and refresh tokens held so the connection keeps working, the capture you choose to copy into your own Drive |\n| Dropbox International Unlimited Company | Saving a capture into your own Dropbox, when you connect a Dropbox account and choose to send one. | Ireland and United States | Standard Contractual Clauses (EU 2021/914) | Dropbox account identifier and OAuth tokens, the capture you choose to copy into your own Dropbox |\n| Salesforce, Inc. (Slack) | Posting a capture into a Slack channel, when a user connects a Slack workspace and chooses to send one there. | United States | Standard Contractual Clauses (EU 2021/914) | Slack workspace and account identifiers, and OAuth tokens, the capture and the message posted with it |\n| Atlassian Pty Ltd (Jira, Trello) | Attaching a capture to a Jira issue or a Trello card, when a user connects that account and chooses to attach one. | Australia, with hosting in the European Union and United States | Standard Contractual Clauses (EU 2021/914) | Atlassian or Trello account identifier and OAuth tokens, the capture attached, and the issue or card it is attached to |\n| Google Ireland Limited (Google Analytics 4 and Google Tag Manager) | Website analytics on rec.so. Loads only after you accept analytics cookies in the consent banner, and never inside the signed-in application. | European Union and United States | Standard Contractual Clauses (EU 2021/914) | IP address and a persistent analytics identifier, pages viewed, referrer, device, browser and operating system |\n| PostHog, Inc. | Website product analytics on rec.so — which pages are viewed and where people leave. Loads only after you accept analytics cookies. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and a persistent visitor identifier, pageview and page-leave events, referrer, device and browser |\n| Chatwoot Inc. | The support chat widget on the rec.so website, engaged when you open it and start a conversation. | United States | Standard Contractual Clauses (EU 2021/914) | name and email address if you give them, the messages in the conversation, IP address and the page you were on |\n| The Rocket Science Group LLC d/b/a Mailchimp | The rec.so newsletter. Engaged only if you subscribe, and you can unsubscribe from any message we send. | United States | Standard Contractual Clauses (EU 2021/914) | email address, subscription status, tags and the date you subscribed, the IP address the subscription came from |\n| DigitalOcean, LLC | Serves desktop installer downloads from the gauzy.co download page, holds media in Spaces where a deployment selects it as the file provider, still carries legacy container images and gated deploy workflows, and for cloc provisions servers on a customer's behalf. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files, screenshots and captured media held in Spaces, IP address and user agent of anyone downloading an asset or a desktop installer, container images and build metadata (no personal data), for cloc: server handles, sizes and lifecycle state of infrastructure provisioned on a customer's behalf |\n| Amazon Web Services, Inc. | S3 is the object-storage backend an operator or tenant can select for uploads and monitoring media; CloudFront serves maintenance.ever.co and security.ever.co on our flagship domain; SES sits underneath our email relay as that relay's own sub-processor. | United States (Luxembourg for the EEA contracting entity) | Standard Contractual Clauses (EU 2021/914) | uploaded files, avatars and document images in S3, employee-monitoring screenshots, webcam stills, audio and screen recordings where S3 is the file provider, static assets served from CloudFront, exposing visitor IP and user agent, outbound email envelope and content where SES is in the path, certificate validation records (no personal data) |\n| Hashnode Inc. | Serves the product blog at blog.<our-domain> under our own branding, so every reader's IP, user agent and cookies go to a US platform the reader has no way of identifying from the address bar. | United States (Delaware) | To be confirmed — we do not yet evidence a mechanism | reader IP address and user agent, blog analytics and referrer, newsletter subscriber email addresses where the subscribe widget is enabled, cookies set under our own subdomain |\n| Twilio Inc. (Programmable Messaging) | Sends SMS where a tenant configures Twilio as its SMS gateway using its own account SID and token. | United States | Standard Contractual Clauses (EU 2021/914) | recipient telephone number, message body, which can contain a capture link or workspace content, delivery and status metadata |\n| Google Ireland Limited (Google Drive) | Exports a user's recordings into their own Google Drive when they grant the Drive scope. | Ireland (contracting entity); processing in Ireland (contracting) / United States (Google LLC) | Standard Contractual Clauses (EU 2021/914) | Drive file metadata and content the user chooses to export, OAuth access and refresh tokens |\n| Vercel Inc. | Hosts the cloc platform; routes AI prompts to downstream model providers for gauzy through the AI Gateway; and remains the deployment target of surviving workflows and DNS delegations for several frontends that have since moved to our own cluster. | United States | Standard Contractual Clauses (EU 2021/914) | for cloc: full application traffic and runtime data (the platform actually runs there), IP address and user agent of visitors where a site is served from Vercel, page-view and Web Vitals events, for gauzy: prompt content and model responses routed through the AI Gateway, plus routing and usage metadata, deployment metadata |\n| Uptime Robot Service Provider Ltd - UNVERIFIED. The commonly cited registration is Cyprus (Nicosia); confirm from the current Terms or Imprint before publishing any location claim. | Hosts the public status page at status.<our-domain>, so anyone who opens it hands their IP and user agent to the vendor. | Cyprus (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address and user agent of every visitor to a status page, cookies set by the status page, monitored endpoint URLs and response metadata |\n| Wasabi Technologies, Inc. | Holds avatars, task attachments and time-tracker screenshots wherever the platform's or a tenant's file provider is set to Wasabi. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files and document attachments, avatars, employee time-tracker screenshots and captured monitoring media |\n| Cloudinary Ltd. | Stores and transforms images and video where a deployment's or the platform's media provider is set to Cloudinary, and serves them to viewers directly from its own CDN. | Israel | Adequacy decision — Israel | uploaded images and video, screenshots and captured media, IP address and user agent of every viewer fetching an asset |\n| UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty | Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Jitsu Labs, Inc. | Collects product events into an event pipeline where a write key is configured, on Jitsu's US cloud. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user and workspace identifiers, page and feature events, device and browser characteristics |\n| Hound Technology, Inc. (d/b/a Honeycomb.io) | Receives OpenTelemetry traces from the API where Honeycomb is selected as the OTEL provider, including request URLs and database statements that routinely carry identifiers. | United States | Standard Contractual Clauses (EU 2021/914) | trace and span data including request URLs, route parameters and DB statements, service and host identifiers, anything a span attribute carries, which can include user and tenant ids |\n| SigNoz Inc. (Delaware, USA) for SigNoz Cloud; SigNoz itself is Apache-2.0 and self-hostable. | Receives OpenTelemetry traces, metrics and logs from the API wherever the OTLP endpoint is configured, including route parameters and SQL text. | United States | To be confirmed — we do not yet evidence a mechanism | distributed traces including HTTP routes, query strings and SQL statements, service and host metadata, metrics and logs, anything attached as a span attribute |\n| Better Stack, s.r.o. | Receives shipped application logs where a log token is configured, including the ChatGPT connector service in ever-teams and the cloc platform's observability pipeline. | Czech Republic | None needed — established in the EEA | application log lines, which may embed user ids, request paths and IP addresses, uptime probe results |\n| OpenAI, L.L.C. | Generates completions and transcribes audio for in-application AI features, using either a platform-held key (cloc) or a key the customer supplies (gauzy, ever-works, ever-teams, hust). | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, including workspace records, job posts, candidate and employee profile text, issue and task text and chat messages, audio submitted for transcription, model responses, OAuth device-auth identity for the Codex CLI plugin |\n| Anthropic, PBC | Generates completions for in-application AI features - the default model in hust, a plugin or bring-your-own-key option in gauzy and ever-works. | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, which can include workspace data the user pastes or references, model responses |\n| Google Ireland Limited (Gemini API) | Generates completions for the in-application AI assistant where a customer connects a Gemini key, through the AI Studio endpoint rather than Vertex AI. | Ireland (contracting entity); processing in United States (AI Studio) / Ireland (Vertex AI) | Standard Contractual Clauses (EU 2021/914) | prompt content, which can carry workspace, HR and candidate data, model responses |\n| Mistral AI SAS | Generates completions where the Mistral plugin is enabled for a Work. | France | None needed — established in the EEA | prompt text, completions |\n| X.AI LLC | Generates completions where a customer selects Grok and supplies a key. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, model responses |\n| Groq, Inc. | Serves completions where a user supplies a Groq key and selects it as the provider. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, model responses |\n| Together Computer, Inc. (trading as Together AI) | Serves completions where a user selects Together as the provider and supplies a key, called from our own Next.js server route. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, including chat message text, model responses |\n| Vercel Inc. | Routes AI prompts from the Gauzy assistant to whichever downstream model provider the customer's selected model resolves to. | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, model responses, request routing and usage metadata |\n| Intuition Machines, Inc. (hCaptcha) | Scores signup and login attempts wherever the CAPTCHA provider is set to hCaptcha. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and browser/device fingerprint signals, mouse, touch and timing interaction signals, challenge solution and token |\n| Meta Platforms Ireland Limited (Facebook Login) | Authenticates a user who chooses to sign in with Facebook, returning their email, name and profile picture. | Ireland (contracting entity); processing in Ireland (contracting for EEA users) / United States (Meta Platforms, Inc.) | Standard Contractual Clauses (EU 2021/914) | email address and name, Facebook user identifier, profile picture URL, OAuth tokens |\n| LinkedIn Ireland Unlimited Company | Authenticates a user who chooses to sign in with LinkedIn, returning their email, name and the profile fields in the granted scope. | Ireland (contracting entity); processing in Ireland (EEA contracting) / United States (processing) | Standard Contractual Clauses (EU 2021/914) | email address and name, LinkedIn member identifier, OAuth tokens, profile fields returned within the granted scope |\n| X Corp. (Twitter) | Authenticates a user who chooses to sign in with X, where that provider is enabled for the deployment. | United States | To be confirmed — we do not yet evidence a mechanism | handle and public profile, X user identifier, OAuth tokens |\n| Microsoft Corporation (Microsoft Entra ID) | Authenticates a user or administrator who chooses a Microsoft work or personal account, reading profile details from Microsoft Graph, where FEATURE_MICROSOFT_LOGIN is enabled. | United States | Standard Contractual Clauses (EU 2021/914) | email address and display name, Microsoft tenant identifier and user object id, OAuth access and refresh tokens, directory profile fields returned by Graph within the granted scope |\n| Okta, Inc. (Auth0) | Authenticates an organisation's people where that organisation chooses to route sign-in through its own hosted Auth0 tenant. | United States | Standard Contractual Clauses (EU 2021/914) | email address and profile, OAuth/OIDC tokens, login IP address, device and user agent, authentication and MFA event logs |\n| Stripe Payments Europe, Limited | Takes card payments and holds the resulting billing and invoice records for products that sell subscriptions. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Ireland (EEA), with onward group processing in the United States | Standard Contractual Clauses (EU 2021/914) | billing identity and address, plan, invoice and payment history, IP address, card data - entered on Stripe's own hosted page and never reaching us |\n| PayPal (Europe) S.à r.l. et Cie, S.C.A. | Takes payments for a commerce deployment, where the merchant running that deployment contracts with PayPal directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Luxembourg (EEA users) / United States (PayPal, Inc.) | None needed — established in the EEA | payer identity and email address, transaction amount and order reference, payment status and history |\n| Zapier, Inc. | Forwards workspace records into whatever third-party apps a customer wires into a Zap, so the onward destinations are the customer's choice and outside our contract. | United States | Standard Contractual Clauses (EU 2021/914) | records pushed through a Zap (tasks, timesheets, contacts), OAuth tokens and authorization codes, arbitrary event payloads forwarded to whatever apps the customer wires up |\n| Activepieces Inc. | Runs automation flows that read and receive whatever workspace records a customer wires in, on Activepieces' US cloud unless repointed at a self-hosted instance. | United States / Canada | Standard Contractual Clauses (EU 2021/914) | records pushed through a flow, which can be any workspace data, API keys, webhook payloads |\n| Celonis SE (Make.com) | Runs automation scenarios that read and receive whatever workspace records the customer wires in, from EU infrastructure. | Germany / Czech Republic | None needed — established in the EEA | records pushed through a scenario, webhook payloads, OAuth tokens |\n| Noti-Fire Apps Ltd. (Novu) | The in-application notification inbox and a delivery channel for notifications, where it is configured against Novu's hosted service rather than an instance you run. | Israel | Adequacy decision — Israel | a hashed subscriber identifier, computed server-side under NOVU_SECRET_KEY, notification content, email address where Novu is used as a delivery channel |\n| Plausible Insights OÜ | Cookieless site analytics on a Work site, where the Work Owner enables it. | Estonia | None needed — established in the EEA | page views and referrer, coarse device and country, derived and not stored as an IP address |\n| HubSpot, Inc. | Two-way contact synchronisation, engaged only when a customer connects its own HubSpot account. Data moves in both directions once connected. | United States (HubSpot, Inc.) / Ireland (HubSpot Ireland Limited, for HubSpot's own EEA customers) | Standard Contractual Clauses (EU 2021/914) | contact and company records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| iubenda s.r.l. | Delivers hosted legal documents to visitors who open the /legal route in the Gauzy application, which still fetches the policy from iubenda in the visitor's browser. | Italy | None needed — established in the EEA | IP address, user agent, consent preferences and the timestamp of the choice |\n| Algolia SAS | Answers the search box on the documentation sites, receiving each reader's query and IP where Algolia credentials are configured. | France (EEA) or United States, depending on the contracting entity and the index region | To be confirmed — we do not yet evidence a mechanism | search queries typed by the reader, IP address, user agent, indexed page content |\n| Google Ireland Limited (Google Fonts) | Delivers typefaces to the visitor's browser at page load on the properties that hot-link them, disclosing the visitor's IP to Google before any consent choice. | Ireland (contracting entity); processing in Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| Google Ireland Limited (Google Maps Platform) | Renders maps and completes typed addresses for contacts, clients and organisations where the Maps and Places features are enabled with an API key. | Ireland (contracting entity); processing in Ireland (contracting) / United States (processing) | Standard Contractual Clauses (EU 2021/914) | IP address, typed address fragments and place queries, latitude and longitude of contacts, clients and organisations, session tokens for autocomplete billing |\n| Lemon Squeezy, LLC | Takes payments from a Work site's own visitors as merchant of record where the Work Owner connects it, so the Work Owner contracts with it directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | United States (Delaware) | Not our transfer — you choose the provider | name and email address, billing address and tax location, payment identifiers and purchase history, card data entered on Lemon Squeezy's own hosted checkout and never reaching us |\n| Polar Software Inc. | An alternative payment and subscription provider for a Work site's own visitors, connected and contracted by the Work Owner. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | United States (Delaware) | Not our transfer — you choose the provider | name and email address, billing and tax location, payment identifiers and subscription history, card data entered on Polar's own hosted checkout and never reaching us |\n| SolidGate | A further card payment option for a Work site's own visitors, where the Work Owner enables it and contracts with the payment institution directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Cyprus (EEA) | None needed — established in the EEA | cardholder name, email address, billing address, payment identifiers |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run Ever Rec 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 | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| The Rocket Science Group LLC d/b/a Mailchimp | The Ever Rec desktop application uploads its captures to a bucket YOU nominate. You enter the endpoint, region, bucket name, access key and secret, and they are held in your own operating system's keychain on your own machine. We never receive those captures and we never see those credentials. | Wherever the provider you chose stores it — you decide, and you contract with it | Not our transfer — you choose the provider | screenshots and recordings taken by the desktop application, the metadata the desktop application records alongside them |\n| Google Ireland Limited (Firebase) | A self-hosted deployment of the open-source platform points at a Firebase project you create, with your own credentials, for authentication, metadata and capture storage. | The regions you select when you create the project | Not our transfer — you choose the provider | everything your deployment's users capture, and their account identities |\n| Your own video streaming account (Mux, Inc. or Api Video SAS) | A self-hosted deployment transcodes and streams recordings through whichever of the two you configure. | Determined by the account you open | Not our transfer — you choose the provider | the recordings your deployment's users make |\n| Your own email, messaging, analytics, error-tracking and link-shortening accounts (Postmark, Twilio, Twilio Segment, Sentry, Rebrandly) | A self-hosted deployment can be configured to send its mail, its WhatsApp messages, its product analytics, its error reports and its short links through accounts you open in your own name. Configure none of them and none of them is involved. | Determined by the accounts you open | Not our transfer — you choose the provider | whatever your deployment sends them, under your configuration and your contracts |\n| none in a self-hosted deployment - the reader (or we) runs the runtime. Ollama Inc. (US) publishes the software and would become a processor only if a hosted Ollama service were adopted. | Runs open-weight models inside the deployment itself, so prompts reach no third party at all. | n/a (self-hosted); United States for Ollama Inc. | Not our transfer — you choose the provider | chat and prompt text, which never leaves the deployment |\n| Red Hat, Inc. (Keycloak) | Authenticates users through a Keycloak realm that the organisation running the deployment operates itself. | United States (Red Hat, Inc.) / wherever the reader runs the realm | Not our transfer — you choose the provider | email address and profile, OIDC tokens |\n| Mixpanel, Inc. | Records in-app screens and named events - 'Order Delivered' from the courier application, 'Order Failed' from the merchant tablet and similar - against a device identifier, where the operator configures a Mixpanel token and publishes a build containing it. | United States | Not our transfer — you choose the provider | device identifier, screens viewed and in-app events, IP address, user identifier once the person has signed in, the Mixpanel project token, which is compiled into the distributed binary |\n| Intercom, Inc. | Runs the in-application support conversation in the shopping, merchant and courier mobile applications through cordova-plugin-intercom / @ionic-native/intercom, where the operator supplies Intercom credentials. | United States (Intercom, Inc.) / Ireland (Intercom R&D Unlimited Company) | Not our transfer — you choose the provider | user identifier and email address, full support conversation content, device and application context, the operator's Intercom app id and API key |\n\n### Where recordings are stored\n\nRecordings, screenshots and their thumbnails are held in our object storage on our own infrastructure.\n**No recording is sent to a third party for analysis, transcription or advertising.**\n\nWhere you share a recording by link, the recipient's access is served from that same storage. Sharing is\nthe act that exposes it — the link is the control, and the privacy annex explains how to withdraw it.\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://rec.so/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://rec.so/privacy).\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\n third party and it is disclosed as one.\n\n### Where a product does something different\n\nA small number of products use a third-party managed database, managed storage or hosted platform for a\nspecific function instead of our own infrastructure. **Where that is the case for Ever Rec, 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://rec.so/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://rec.so/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://rec.so/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.2 of the sub-processor list for\n[rec.so](https://rec.so), in force from 2026-08-02. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://rec.so/subprocessors](https://rec.so/subprocessors)."
154
158
  }