@ever-co/legal 0.6.0 → 0.7.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.
- package/dist/content/aup/ever-async/en.json +2 -2
- package/dist/content/aup/ever-corporate/en.json +2 -2
- package/dist/content/aup/ever-demand/en.json +2 -2
- package/dist/content/aup/ever-rec/en.json +2 -2
- package/dist/content/aup/ever-teams/en.json +2 -2
- package/dist/content/aup/ever-works/en.json +2 -2
- package/dist/content/aup/everiq/en.json +2 -2
- package/dist/content/aup/gauzy/en.json +2 -2
- package/dist/content/aup/githands/en.json +2 -2
- package/dist/content/aup/hust/en.json +2 -2
- package/dist/content/aup/traduora/en.json +2 -2
- package/dist/content/cookies/ever-async/en.json +2 -2
- package/dist/content/cookies/ever-corporate/en.json +2 -2
- package/dist/content/cookies/ever-demand/en.json +2 -2
- package/dist/content/cookies/ever-rec/en.json +2 -2
- package/dist/content/cookies/ever-teams/en.json +2 -2
- package/dist/content/cookies/ever-tech/en.json +2 -2
- package/dist/content/cookies/ever-works/en.json +2 -2
- package/dist/content/cookies/everiq/en.json +2 -2
- package/dist/content/cookies/gauzy/en.json +2 -2
- package/dist/content/cookies/githands/en.json +2 -2
- package/dist/content/cookies/hust/en.json +2 -2
- package/dist/content/cookies/traduora/en.json +2 -2
- package/dist/content/dpa/ever-async/en.json +2 -2
- package/dist/content/dpa/ever-demand/en.json +2 -2
- package/dist/content/dpa/ever-rec/en.json +2 -2
- package/dist/content/dpa/ever-teams/en.json +2 -2
- package/dist/content/dpa/ever-tech-services/en.json +2 -2
- package/dist/content/dpa/ever-works/en.json +2 -2
- package/dist/content/dpa/gauzy/en.json +2 -2
- package/dist/content/dpa/githands/en.json +2 -2
- package/dist/content/dpa/hust/en.json +2 -2
- package/dist/content/dpia/gauzy/en.json +2 -2
- package/dist/content/privacy/ever-async/en.json +2 -2
- package/dist/content/privacy/ever-corporate/en.json +2 -2
- package/dist/content/privacy/ever-demand/en.json +2 -2
- package/dist/content/privacy/ever-rec/en.json +2 -2
- package/dist/content/privacy/ever-teams/en.json +2 -2
- package/dist/content/privacy/ever-tech/en.html +90 -24
- package/dist/content/privacy/ever-tech/en.json +4 -4
- package/dist/content/privacy/ever-works/en.json +2 -2
- package/dist/content/privacy/everiq/en.json +2 -2
- package/dist/content/privacy/gauzy/en.json +2 -2
- package/dist/content/privacy/githands/en.json +2 -2
- package/dist/content/privacy/hust/en.json +2 -2
- package/dist/content/privacy/traduora/en.json +2 -2
- package/dist/content/refund/ever-corporate/en.json +2 -2
- package/dist/content/refund/ever-demand/en.json +2 -2
- package/dist/content/refund/ever-rec/en.json +2 -2
- package/dist/content/refund/ever-teams/en.json +2 -2
- package/dist/content/refund/ever-tech-services/en.json +2 -2
- package/dist/content/refund/ever-works/en.json +2 -2
- package/dist/content/refund/gauzy/en.json +2 -2
- package/dist/content/refund/githands/en.json +2 -2
- package/dist/content/refund/hust/en.json +2 -2
- package/dist/content/refund/traduora/en.json +2 -2
- package/dist/content/security/ever-async/en.json +2 -2
- package/dist/content/security/ever-corporate/en.json +2 -2
- package/dist/content/security/ever-demand/en.json +2 -2
- package/dist/content/security/ever-rec/en.json +2 -2
- package/dist/content/security/ever-teams/en.json +2 -2
- package/dist/content/security/ever-tech/en.html +21 -2
- package/dist/content/security/ever-tech/en.json +9 -4
- package/dist/content/security/ever-works/en.json +2 -2
- package/dist/content/security/gauzy/en.json +2 -2
- package/dist/content/security/githands/en.json +2 -2
- package/dist/content/security/hust/en.json +2 -2
- package/dist/content/security/traduora/en.json +2 -2
- package/dist/content/subprocessors/ever-async/en.json +2 -2
- package/dist/content/subprocessors/ever-corporate/en.json +2 -2
- package/dist/content/subprocessors/ever-demand/en.json +2 -2
- package/dist/content/subprocessors/ever-rec/en.json +2 -2
- package/dist/content/subprocessors/ever-teams/en.json +2 -2
- package/dist/content/subprocessors/ever-tech/en.html +27 -12
- package/dist/content/subprocessors/ever-tech/en.json +4 -4
- package/dist/content/subprocessors/ever-tech-services/en.json +2 -2
- package/dist/content/subprocessors/ever-works/en.json +2 -2
- package/dist/content/subprocessors/everiq/en.json +2 -2
- package/dist/content/subprocessors/gauzy/en.json +2 -2
- package/dist/content/subprocessors/githands/en.json +2 -2
- package/dist/content/subprocessors/hust/en.json +2 -2
- package/dist/content/subprocessors/traduora/en.json +2 -2
- package/dist/content/tos/ever-async/en.json +2 -2
- package/dist/content/tos/ever-corporate/en.json +2 -2
- package/dist/content/tos/ever-demand/en.json +2 -2
- package/dist/content/tos/ever-rec/en.json +2 -2
- package/dist/content/tos/ever-teams/en.json +2 -2
- package/dist/content/tos/ever-tech/en.html +25 -10
- package/dist/content/tos/ever-tech/en.json +4 -4
- package/dist/content/tos/ever-tech-services/en.json +2 -2
- package/dist/content/tos/ever-works/en.json +2 -2
- package/dist/content/tos/everiq/en.json +2 -2
- package/dist/content/tos/gauzy/en.json +2 -2
- package/dist/content/tos/githands/en.json +2 -2
- package/dist/content/tos/hust/en.json +2 -2
- package/dist/content/tos/traduora/en.json +2 -2
- package/dist/index.json +105 -100
- package/package.json +52 -52
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
"locale": "en",
|
|
9
9
|
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "f7d434ae1b55e9d42b01435137931f490a80585bee119ed2656464c9ea91cd13",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/subprocessors/010-purpose",
|
|
@@ -154,5 +154,5 @@
|
|
|
154
154
|
}
|
|
155
155
|
],
|
|
156
156
|
"path": "content/subprocessors/gauzy/en.html",
|
|
157
|
-
"markdown": "## Why this page exists\r\n\r\nWhen you use Ever Gauzy Cloud to process personal data, we act as your processor and you are the\r\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\r\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\r\n\r\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\r\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\r\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\r\ngiven through it.\r\n\r\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\r\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\r\nanswer should not be available only to the person paying the invoice.\r\n\r\n### What counts as a sub-processor\r\n\r\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\r\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\r\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\r\n\r\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\r\nmore complete:\r\n\r\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\r\n is not in the path of your data.\r\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\r\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\r\n part, not our processor. Those recipients are described in the\r\n [Privacy Policy](https://gauzy.co/privacy) instead.\r\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\r\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\r\n what genuinely sits in front of it.\r\n\r\n### What this page covers\r\n\r\nThe **hosted Service we operate** at [gauzy.co](https://gauzy.co), for Ever Gauzy\r\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\r\nbetween them — do not read this one as covering a product it does not name.\r\n\r\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\r\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\r\nexists to make that distinction visible rather than to blur it.\r\n\r\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\r\n\r\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\r\nyou the wrong answer.\r\n\r\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\r\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\r\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\r\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\r\ndeployment that somebody else runs, with their own account and their own credentials.\r\n\r\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\r\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\r\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\r\nthree tiers.\r\n\r\n### Tier 1 — always engaged\r\n\r\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\r\nbecause they are part of how the Service is delivered to everyone.\r\n\r\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\r\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\r\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\r\n\r\n### Tier 2 — engaged only if you turn something on\r\n\r\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\r\nEnable nothing and it is never involved, and no data of yours ever reaches it.\r\n\r\nWho does the enabling depends on the feature:\r\n\r\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\r\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\r\n connector.\r\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\r\n connecting their own third-party tool.\r\n\r\nThe table names the feature or setting that activates each provider, so you can check your own\r\nconfiguration against it rather than take our word for the current state. If you want to know precisely\r\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\r\n\r\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\r\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\r\n\r\n### Tier 3 — self-hosted deployments only\r\n\r\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\r\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\r\nusing your own accounts and your own credentials.\r\n\r\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\r\nThey are not our sub-processors, and they never become ours by appearing here.\r\n\r\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\r\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\r\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\r\nopen-source section of our [Terms of Service](https://gauzy.co/tos) sets out the same split.\r\n\r\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\r\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\r\n\r\n### What the columns mean\r\n\r\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\r\n separate European establishment that contracts with us, that is the one named.\r\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\r\n- **Location** — where the processing takes place, or the provider's place of establishment where\r\n processing is distributed. Where a provider contracts through a European establishment but processes\r\n elsewhere, this column says both, because the two are different facts and only naming the first would\r\n flatter us.\r\n- **Transfer mechanism** — for a provider outside the European Economic Area, the Chapter V instrument we\r\n actually rely on for that specific provider: an adequacy decision, the Standard Contractual Clauses, or\r\n nothing yet. **Where it reads \"To be confirmed\", we have not yet evidenced an instrument for that\r\n provider, and we would rather say so here than print one we cannot produce.** That is a live piece of\r\n work, not a formula. Providers established inside the EEA need no mechanism and say so. For the third\r\n tier the transfer is not ours at all — you choose the provider and hold the contract.\r\n The general rules behind this column are in the international transfers section of our\r\n [Privacy Policy](https://gauzy.co/privacy), and we will give you a copy of the safeguards for a named\r\n provider on request.\r\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\r\n provider that receives email addresses receives them for the people who trigger the feature, not for\r\n everyone.\r\n\r\n### Why this list is deliberately longer than it needs to be\r\n\r\n**We list providers we may engage, not only the ones engaged today.** Where we have configured a\r\nprovider, kept one available behind a feature flag, used one recently, or expect to use one for a\r\npurpose already described here, it appears in the tables below — even if no data has reached it this\r\nmonth, and even where we currently run the equivalent ourselves.\r\n\r\nWe do this on purpose, and you should read the tables with it in mind:\r\n\r\n- **A provider appearing here is not proof that your data has reached it.** It means the provider is\r\n within the scope of what we have told you we may do, at the tier shown. The tier is the part that\r\n tells you when it is engaged.\r\n- **Where we self-host something today** — our analytics, our job runner, our databases, our object\r\n storage — we say so, and we also name the hosted service we would move to, so that a later change is\r\n covered by a disclosure you have already seen rather than by a fresh surprise.\r\n- **The alternative is worse.** A list that names only today's exact set has to be re-issued, and\r\n re-consented, every time an engineer changes a setting. A list drawn slightly wide stays true through\r\n ordinary operational change, which is what makes it dependable.\r\n\r\n**What we will not do is use this as cover.** Breadth here does not license a purpose we have not\r\ndescribed, a category of data we have not listed, or a transfer without a mechanism. If we start\r\nsending a new *kind* of personal data, or sending it for a new *reason*, that is a change to this page\r\nand to the notice period below — not something the width of a table quietly absorbs.\r\n\r\nIf you need to know precisely which providers are live for your workspace today, rather than which ones\r\nmay be, ask us at privacy@ever.co and we will tell you.\r\n\r\n### What is deliberately not in the tables\r\n\r\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\r\n container platform are not sub-processors, because there is no third party involved. The next section\r\n describes what we run and what really does sit in front of it.\r\n- **Recipients that are not processors** — payment providers acting under their own regulatory\r\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\r\n are covered in the [Privacy Policy](https://gauzy.co/privacy).\r\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\r\n site, their notice applies.\n\n## Annex: Ever Gauzy\r\n\r\nThe tiers below follow the explanation above. Read the tier, not just the name — a provider in the second\r\nor third table is not processing your data unless the condition next to it is true.\r\n\r\n### Tier 1 — always engaged\r\n\r\nThese are in the path for every customer of Ever Gauzy Cloud. There is no setting that removes them.\r\nThis is the Article 28 sub-processor list proper.\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | DNS, content delivery, TLS termination, web application firewall and the tunnels that carry traffic from the edge to our own infrastructure for gauzy.co, app.gauzy.co, api.gauzy.co and docs.gauzy.co. Every request to the Service passes through it. | United States, with edge termination worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, requested URLs and request headers, TLS and connection metadata, cookies in transit |\n| ActiveCampaign, LLC (Postmark) | Delivery of transactional and notification email — workspace invitations, email verification, sign-in codes, password resets, invoice and estimate emails, timesheet and approval notifications, and replies to the contact form on gauzy.co. | United States | Standard Contractual Clauses (EU 2021/914) | recipient name and email address, message subject and body, which can contain invoice, timesheet and HR content, single-use sign-in and verification codes, delivery, bounce and open metadata |\n| Chargebee Inc. | Subscription billing and hosted checkout for licence and subscription purchases started from gauzy.co. Card details are entered on Chargebee's own hosted page and never reach us. | United States | To be confirmed — we do not yet evidence a mechanism | billing name and email address, billing address and tax identification number, plan, invoice and payment history, IP address |\n| GitHub, Inc. (a Microsoft Corporation company) | Source hosting, continuous integration and the container registry that serves the production images for the Service. It is how the Service is built and deployed, not where your data lives. | United States | Standard Contractual Clauses (EU 2021/914) | build, release and deployment metadata, developer and automation account identifiers, no workspace content and no captured media |\n| DigitalOcean, LLC | Object storage and content delivery for the public desktop, agent and server installers offered on the download page of gauzy.co. It serves the installer files themselves and nothing else. | United States | Standard Contractual Clauses (EU 2021/914) | IP address of the person downloading, user agent and requested file |\n| iubenda s.r.l. | Consent management on gauzy.co — presenting the banner and preference centre, recording your choice and making it available to the scripts that wait on it. | Italy, European Union | None needed — established in the EEA | IP address, user agent, consent preferences and the timestamp of the choice |\n| Google Ireland Limited (reCAPTCHA) | Bot protection on the public forms of gauzy.co — contact and newsletter — with server-side verification of the resulting token. Treated as strictly necessary for the reasons given in our Cookie Policy. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page |\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| 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| 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 |\r\n\r\n### Tier 2 — engaged only when a feature, integration or consent brings them in\r\n\r\nNone of these is engaged by default. Each one arrives because someone switched something on: an\r\nadministrator enabled a feature, connected an integration, or configured a provider; or a visitor consented\r\nto a cookie category.\r\n\r\nTwo of these deserve to be called out rather than left in a table.\r\n\r\n- **Integrations you connect are two-way.** Where your organisation connects Hubstaff, Upwork, Jira,\r\n GitHub or a similar platform, data moves in both directions and the other platform's own terms and\r\n privacy notice apply to its half. Connecting it is the act that authorises the exchange.\r\n- **AI providers are often yours, not ours.** Several AI features work on a bring-your-own-key basis. Where\r\n your organisation supplies its own API key, **your organisation is the one contracting with that\r\n provider**, and its terms and privacy notice govern what happens to the content sent there. We do not\r\n become that provider's customer on your behalf, and we cannot make commitments about it.\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Functional Software, Inc. d/b/a Sentry | Error, crash and performance reporting from the API, the web application, the desktop and agent applications and the gauzy.co website, where error reporting is enabled for the deployment. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and device or operating-system details, user identifier and email address attached to an error event, URLs, route parameters and stack traces, which can contain fragments of the failing request, a masked replay of the website session in which an error occurred |\n| PostHog, Inc. | Product analytics and, where it is switched on, session recording. Enabled per deployment and, on the website, gated on your consent to the analytics category. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, which the server-side integration uses to identify a visitor, user and workspace identifiers, page, screen and feature usage events, recordings of in-application sessions where session recording is enabled |\n| Google Ireland Limited (Google Analytics 4 and Google Tag Manager) | Website traffic measurement on gauzy.co. Loads only after you consent to the analytics category. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, analytics client identifier, pages viewed, referrer, device and browser details |\n| Liidio Oy (Leadfeeder), a Dealfront Group GmbH company | Business-audience identification on gauzy.co — resolving a visitor's IP address to the organisation it belongs to. Loads only after you consent to the marketing category. | Germany, European Union | None needed — established in the EEA | IP address, inferred employer or organisation, pages viewed and referrer |\n| Chatwoot Inc. | The live support chat widget, which loads on gauzy.co and also inside the signed-in application when support chat is enabled. | United States | Standard Contractual Clauses (EU 2021/914) | name and email address you give the widget, the content of the chat, IP address and session identifiers, the page or screen you were on when you opened it |\n| The Rocket Science Group LLC d/b/a Mailchimp | Newsletter and mailing-list management for people who subscribe on gauzy.co. | United States | Standard Contractual Clauses (EU 2021/914) | email address and name, subscription status and campaign engagement, IP address at the time of subscription |\n| Google Ireland Limited (Google Maps Platform) | Map display, address autocomplete and location selection inside the application, where your administrator enables location features. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, the address text a user types into autocomplete, selected coordinates and resolved addresses |\n| Algolia SAS | Hosted search on the documentation site at docs.gauzy.co, where search credentials are configured. | France, European Union | To be confirmed — we do not yet evidence a mechanism | search queries, IP address and user agent |\n| Hound Technology, Inc. (d/b/a Honeycomb.io) | Distributed tracing and operational metrics for the API, where tracing is enabled and pointed at this provider. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, request URLs and route parameters, user and workspace identifiers carried in trace attributes |\n| SigNoz Inc. | Distributed tracing and operational metrics for the API, as an alternative destination to the above, where tracing is enabled and pointed at this provider. | United States | To be confirmed — we do not yet evidence a mechanism | IP address, request URLs and route parameters, user and workspace identifiers carried in trace attributes |\n| Aspecto Ltd. | Distributed tracing for the API, as a further alternative destination, where tracing is enabled and pointed at this provider. | Israel, which holds a European Commission adequacy decision | Adequacy decision — Israel | IP address, request URLs, identifiers carried in trace attributes |\n| Jitsu Labs, Inc. | Event streaming to a product-analytics pipeline, where the hosted Jitsu service is configured as the destination rather than a destination we run ourselves. | United States | Standard Contractual Clauses (EU 2021/914) | user and workspace identifiers, product events and the changes that produced them, IP address and browser details |\n| Bricks Software AS (Unleash) | Feature-flag evaluation, where the hosted Unleash service is configured rather than an instance we run ourselves. | Norway, European Economic Area | None needed — established in the EEA | application and instance identifiers, flag evaluation context, which can include a user or workspace identifier |\n| Google Ireland Limited (Sign in with Google) | Sign-in, where a user chooses to authenticate with a Google account instead of a password. | United States | Standard Contractual Clauses (EU 2021/914) | Google account identifier, email address, display name and profile picture |\n| Microsoft Corporation (Microsoft Entra ID) | Sign-in, where a user or an administrator chooses to authenticate with a Microsoft work or personal account. Profile details are read from Microsoft Graph. | United States | Standard Contractual Clauses (EU 2021/914) | Microsoft account identifier, email address and display name |\n| LinkedIn Ireland Unlimited Company | Sign-in, where a user chooses to authenticate with a LinkedIn account. | United States | Standard Contractual Clauses (EU 2021/914) | LinkedIn account identifier, email address, name and profile picture |\n| Meta Platforms Ireland Limited (Facebook Login) | Sign-in, where a user chooses to authenticate with a Facebook account. | United States | Standard Contractual Clauses (EU 2021/914) | Facebook account identifier, email address, name and profile picture |\n| X Corp. (Twitter) | Sign-in, where a user chooses to authenticate with an X account. | United States | To be confirmed — we do not yet evidence a mechanism | X account identifier and screen name, email address where the provider releases it |\n| Okta, Inc. (Auth0) | Sign-in, where an organisation chooses to authenticate its people through a hosted Auth0 tenant. | United States | Standard Contractual Clauses (EU 2021/914) | subject identifier issued by the identity provider, email address and name |\n| Fiverr International Ltd. | Account linking for freelancer profiles, where a user connects a Fiverr account. | Israel, which holds a European Commission adequacy decision | Adequacy decision — Israel | Fiverr account identifier, the profile fields the connection returns |\n| Red Hat, Inc. (Keycloak) | Sign-in against a Keycloak realm, where an organisation configures one. Whoever operates that realm holds the data, and where the organisation operates it there is no third party at all. | Determined by whoever operates the realm | Not our transfer — you choose the provider | subject identifier issued by the realm, username and email address |\n| Anthropic, PBC | Model provider for the in-application AI assistant, connected by you with your own account and API key. Your agreement with this provider governs what it does with the content you send it. | United States | Standard Contractual Clauses (EU 2021/914) | prompts and conversation content, any workspace content a user includes in a prompt |\n| OpenAI, L.L.C. | Model provider for the in-application AI assistant, connected by you with your own account and API key. Also reachable indirectly where you supply an OpenAI key to our own AI service for image analysis. | United States | Standard Contractual Clauses (EU 2021/914) | prompts and conversation content, any workspace content a user includes in a prompt, screenshot-derived content where image analysis is routed to your OpenAI account |\n| Google Ireland Limited (Gemini API) | Model provider for the in-application AI assistant, connected by you with your own account and API key. | United States | Standard Contractual Clauses (EU 2021/914) | prompts and conversation content |\n| X.AI LLC | Model provider for the in-application AI assistant, connected by you with your own account and API key. | United States | To be confirmed — we do not yet evidence a mechanism | prompts and conversation content |\n| OpenRouter, Inc. | Model routing for the in-application AI assistant, connected by you with your own account or through an authorisation flow you complete yourself. | United States | To be confirmed — we do not yet evidence a mechanism | prompts and conversation content, OpenRouter account identity where you connect one |\n| Vercel Inc. (AI Gateway) | Gateway that forwards AI assistant requests to a downstream model provider, connected by you with your own account and API key. | United States | Standard Contractual Clauses (EU 2021/914) | prompts and conversation content |\n| Netsoft Holdings, LLC (Hubstaff) | Integration you connect, importing organisations, projects, people, timesheets, activity levels and screenshots from your Hubstaff account into your workspace. | United States | Standard Contractual Clauses (EU 2021/914) | names and email addresses of the people in your Hubstaff account, time logs and activity levels, screenshots captured by Hubstaff, project and task assignments |\n| Upwork Global Inc. | Integration you connect, importing contracts, freelancer profiles, time logs and income and expense reports from your Upwork account, and supporting job matching and proposal drafting. | United States | To be confirmed — we do not yet evidence a mechanism | freelancer name and profile details, contract, earnings and time-log data, screenshots captured by Upwork |\n| Atlassian Pty Ltd (Jira, Trello) | Integration you connect, synchronising projects, issues and worklogs between Jira and your workspace. | United States | Standard Contractual Clauses (EU 2021/914) | Jira account identifiers, display names and email addresses, issue, comment and worklog content |\n| GitHub, Inc. (a Microsoft Corporation company) | Integration you connect through a GitHub App, synchronising repositories, issues and labels with your workspace tasks. | United States | Standard Contractual Clauses (EU 2021/914) | GitHub account identifiers, usernames and email addresses, issue and repository content within the granted scope |\n| Zapier, Inc. | Automation integration you connect, which reads and receives whatever records you wire into a Zap. | United States | Standard Contractual Clauses (EU 2021/914) | any workspace record you route through an automation, including tasks, time logs, contacts and invoices |\n| Celonis SE (Make.com) | Automation integration you connect, which reads and receives whatever records you wire into a scenario. | Germany, European Union | None needed — established in the EEA | any workspace record you route through an automation |\n| Activepieces Inc. | Automation integration you connect, which reads and receives whatever records you wire into a flow. | United States | Standard Contractual Clauses (EU 2021/914) | any workspace record you route through an automation |\n| Sim Studio, Inc. (sim.ai) | AI workflow integration you connect, which receives the inputs you route into a workflow. | United States | To be confirmed — we do not yet evidence a mechanism | workflow inputs, which can contain workspace record content |\n| WakaTime, LLC | Integration a developer connects, ingesting coding-activity heartbeats as time and activity records in your workspace. | United States | To be confirmed — we do not yet evidence a mechanism | developer identity, names of files and projects being edited, editor, language and operating-system metadata with timestamps |\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| 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| 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| UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty | Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Twilio Inc. (SendGrid) | Sends and tracks marketing or transactional email for gauzy.co through dedicated sending, reply and link-tracking subdomains, and stands as an alternative sender for githands. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, open and click tracking events (links.gauzy.co), recipient IP and user agent via tracking pixels |\n| Twilio Inc. (Programmable Messaging) | Sends SMS where a tenant configures Twilio as its SMS gateway using its own account SID and token. | United States | Standard Contractual Clauses (EU 2021/914) | recipient telephone number, message body, which can contain a capture link or workspace content, delivery and status metadata |\n| self-hosted by us - no vendor. Cloud analogue: the Plane Cloud operator (entity name UNKNOWN/unverified; published by the makeplane team, US/India). | Syncs issues and projects with whatever Plane instance a customer configures - our own pm.gauzy.co, their own server, or Plane Cloud. | n/a (self-hosted on own EU hardware); United States / India for Plane Cloud | None needed — established in the EEA | issue, cycle and project records, assignee identity and team-member names, API tokens |\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| 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| 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| 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| 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| 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| Slack Technologies, LLC (a Salesforce, Inc. company) | Posts notifications into, and reads events from, a Slack workspace the customer connects by installing our app into its own workspace. | United States (group); Ireland (EEA contracting for Slack's own customers) | Standard Contractual Clauses (EU 2021/914) | channel and workspace identifiers, message content we post or receive, Slack user identity, including member email addresses, OAuth tokens and webhook payloads, shared recordings, screenshots and their links (ever-rec) |\n| 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| 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 |\r\n\r\n### Tier 3 — self-hosted deployments only\r\n\r\nEver Gauzy can be run on your own infrastructure. If you do that, you choose these providers, you\r\nhold the credentials, and you contract with them directly.\r\n\r\n**We are not a processor for anything in a deployment you run.** We do not receive that data, we cannot\r\nreach it, and we have no relationship with the providers you configure. They appear here only so that\r\nreaders running their own copy know which external services the software can be configured to use.\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Amazon Web Services, Inc. (S3) | One of the object-storage backends the open-source software can be pointed at for uploads, avatars, attachments and captured media in a deployment you run yourself. | The region you select in your own account | Not our transfer — you choose the provider | whatever your deployment stores, including screenshots, webcam stills, audio, video and uploaded documents |\n| Wasabi Technologies, Inc. | An S3-compatible object-storage backend the open-source software can be pointed at in a deployment you run yourself. | The region you select in your own account | Not our transfer — you choose the provider | whatever your deployment stores, including captured media and uploaded documents |\n| Cloudinary Ltd. | An image and media storage and delivery backend the open-source software can be pointed at in a deployment you run yourself. | The region you select in your own account | Not our transfer — you choose the provider | whatever your deployment stores, including screenshots, avatars and uploaded images |\n| DigitalOcean, LLC (Spaces) | An S3-compatible object-storage backend the open-source software can be pointed at in a deployment you run yourself. Distinct from the installer delivery listed in the always-engaged table above. | The region you select in your own account | Not our transfer — you choose the provider | whatever your deployment stores, including captured media and uploaded documents |\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| 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 |\r\n\r\n### Storage of monitoring media\r\n\r\nScreenshots, webcam stills, audio and video captured by the desktop applications are stored through the\r\nfile-provider configured for the deployment. **For Ever Gauzy Cloud that is our own object storage,\r\non our own infrastructure**, which is why the commercial object-storage providers the software supports\r\nappear in tier 3 rather than tier 1. If that ever changes for the hosted Service, this list changes with\r\nit and the change is announced under the notification process above.\n\n## Hosting and infrastructure\r\n\r\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\r\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\r\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\r\noperate ourselves.\r\n\r\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\r\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\r\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\r\n[Security page](https://gauzy.co/security).\r\n\r\n### Where processing actually happens\r\n\r\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\r\n Union.** That is the primary location for accounts, content, files and the databases behind them.\r\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\r\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\r\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\r\n transfer mechanism for it is described in our [Privacy Policy](https://gauzy.co/privacy).\r\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\r\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\r\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\r\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\r\n third party and it is disclosed as one.\r\n\r\n### Where a product does something different\r\n\r\nA small number of products use a third-party managed database, managed storage or hosted platform for a\r\nspecific function instead of our own infrastructure. **Where that is the case for Ever Gauzy, the\r\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\r\n\r\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\r\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\r\ntable says so.\r\n\r\n### The regions you should design around\r\n\r\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\r\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\r\nsmall number of named providers established outside the European Economic Area, each with its own transfer\r\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\r\ninternational transfers section of the [Privacy Policy](https://gauzy.co/privacy).\r\n\r\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\r\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\r\n\r\n### The notice period\r\n\r\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\r\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\r\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\r\nabout afterwards.\r\n\r\n### How you find out\r\n\r\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\r\n the page itself is the notice.\r\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\r\n notification list. We then email you before each change, at the same time the page is updated. **We\r\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\r\n organisation has been sent and not received.\r\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\r\n administrators.\r\n\r\n### What the notice tells you\r\n\r\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\r\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\r\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\r\n\r\n### Urgent replacements\r\n\r\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\r\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\r\nleaving.\r\n\r\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\r\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\r\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\r\nplainly why the normal period was not followed.\r\n\r\n### Changes that do not need notice\r\n\r\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\r\nprovider changing its own name, or the group entity that contracts with us changing without a change in\r\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\r\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\r\nthe full notice.**\r\n\r\n### The record\r\n\r\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\r\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\r\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\r\nas it stood on a particular date.\n\n## Objecting to a sub-processor\r\n\r\n### Who can object\r\n\r\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\r\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\r\n[Privacy Policy](https://gauzy.co/privacy), and if your data sits in an employer's workspace, your employer\r\nis the controller and the request goes to them.\r\n\r\n### How to object\r\n\r\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\r\n\r\n- which provider you are objecting to;\r\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\r\n commitment you have given your own users, a regulator's position that applies to you, a documented\r\n security concern;\r\n- which of your workspaces or environments the objection covers.\r\n\r\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\r\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\r\nis and we can usually solve it.\r\n\r\n### What we do next\r\n\r\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\r\nbetween we look for a way to make the objection unnecessary:\r\n\r\n- **A different provider** for your workspace, where one exists that does the job.\r\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\r\n that needs the provider at all, if you can live without it.\r\n- **Excluding your workspace** from the provider, where that is technically possible.\r\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\r\n the provider as a whole.\r\n\r\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\r\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\r\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\r\nclock run out on you.\r\n\r\n### If we cannot resolve it\r\n\r\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\r\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\r\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\r\n\r\nGive us notice within 30 days of our final response, and we will keep your data available for export for\r\nthe usual 30-day window described in the [Terms of Service](https://gauzy.co/tos) so that leaving does not\r\ncost you the data.\r\n\r\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\r\nService and export your data.\r\n\r\n### Objecting to a provider already on the list\r\n\r\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\r\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\r\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\r\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\r\nstraight no with the reason.\n\n## How to reach us about this list\r\n\r\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\r\n change notification list** — privacy@ever.co.\r\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\r\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\r\n legal@ever.co.\r\n\r\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\r\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\r\nown processing and your processor for the data in your workspace. By post, write to the registered office\r\nand mark the letter for the attention of the privacy team. We correspond in English.\r\n\r\nYou may also complain to a data protection supervisory authority. Ours is the\r\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\r\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\r\nto the authority for the country where you live or work.\r\n\r\nThis document is version 1.0.2 of the sub-processor list for\r\n[gauzy.co](https://gauzy.co), in force from 2026-08-02. It lists the providers engaged\r\nas at that date. Earlier versions, with the dates they applied, are at\r\n[https://gauzy.co/subprocessors](https://gauzy.co/subprocessors)."
|
|
157
|
+
"markdown": "## Why this page exists\n\nWhen you use Ever Gauzy Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://gauzy.co/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [gauzy.co](https://gauzy.co), for Ever Gauzy\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\nbetween them — do not read this one as covering a product it does not name.\n\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\nexists to make that distinction visible rather than to blur it.\n\nThis page is versioned and dated. The version in force, and the date it took effect, are at the end.\n\n## How to read this list\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://gauzy.co/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where 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://gauzy.co/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### 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://gauzy.co/privacy).\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\n site, their notice applies.\n\n## Annex: Ever Gauzy\n\nThe tiers below follow the explanation above. Read the tier, not just the name — a provider in the second\nor third table is not processing your data unless the condition next to it is true.\n\n### Tier 1 — always engaged\n\nThese are in the path for every customer of Ever Gauzy Cloud. There is no setting that removes them.\nThis is the Article 28 sub-processor list proper.\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | DNS, content delivery, TLS termination, web application firewall and the tunnels that carry traffic from the edge to our own infrastructure for gauzy.co, app.gauzy.co, api.gauzy.co and docs.gauzy.co. Every request to the Service passes through it. | United States, with edge termination worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, requested URLs and request headers, TLS and connection metadata, cookies in transit |\n| ActiveCampaign, LLC (Postmark) | Delivery of transactional and notification email — workspace invitations, email verification, sign-in codes, password resets, invoice and estimate emails, timesheet and approval notifications, and replies to the contact form on gauzy.co. | United States | Standard Contractual Clauses (EU 2021/914) | recipient name and email address, message subject and body, which can contain invoice, timesheet and HR content, single-use sign-in and verification codes, delivery, bounce and open metadata |\n| Chargebee Inc. | Subscription billing and hosted checkout for licence and subscription purchases started from gauzy.co. Card details are entered on Chargebee's own hosted page and never reach us. | United States | To be confirmed — we do not yet evidence a mechanism | billing name and email address, billing address and tax identification number, plan, invoice and payment history, IP address |\n| GitHub, Inc. (a Microsoft Corporation company) | Source hosting, continuous integration and the container registry that serves the production images for the Service. It is how the Service is built and deployed, not where your data lives. | United States | Standard Contractual Clauses (EU 2021/914) | build, release and deployment metadata, developer and automation account identifiers, no workspace content and no captured media |\n| DigitalOcean, LLC | Object storage and content delivery for the public desktop, agent and server installers offered on the download page of gauzy.co. It serves the installer files themselves and nothing else. | United States | Standard Contractual Clauses (EU 2021/914) | IP address of the person downloading, user agent and requested file |\n| iubenda s.r.l. | Consent management on gauzy.co — presenting the banner and preference centre, recording your choice and making it available to the scripts that wait on it. | Italy, European Union | None needed — established in the EEA | IP address, user agent, consent preferences and the timestamp of the choice |\n| Google Ireland Limited (reCAPTCHA) | Bot protection on the public forms of gauzy.co — contact and newsletter — with server-side verification of the resulting token. Treated as strictly necessary for the reasons given in our Cookie Policy. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page |\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| 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| 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\nNone of these is engaged by default. Each one arrives because someone switched something on: an\nadministrator enabled a feature, connected an integration, or configured a provider; or a visitor consented\nto a cookie category.\n\nTwo of these deserve to be called out rather than left in a table.\n\n- **Integrations you connect are two-way.** Where your organisation connects Hubstaff, Upwork, Jira,\n GitHub or a similar platform, data moves in both directions and the other platform's own terms and\n privacy notice apply to its half. Connecting it is the act that authorises the exchange.\n- **AI providers are often yours, not ours.** Several AI features work on a bring-your-own-key basis. Where\n your organisation supplies its own API key, **your organisation is the one contracting with that\n provider**, and its terms and privacy notice govern what happens to the content sent there. We do not\n become that provider's customer on your behalf, and we cannot make commitments about it.\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Functional Software, Inc. d/b/a Sentry | Error, crash and performance reporting from the API, the web application, the desktop and agent applications and the gauzy.co website, where error reporting is enabled for the deployment. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and device or operating-system details, user identifier and email address attached to an error event, URLs, route parameters and stack traces, which can contain fragments of the failing request, a masked replay of the website session in which an error occurred |\n| PostHog, Inc. | Product analytics and, where it is switched on, session recording. Enabled per deployment and, on the website, gated on your consent to the analytics category. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, which the server-side integration uses to identify a visitor, user and workspace identifiers, page, screen and feature usage events, recordings of in-application sessions where session recording is enabled |\n| Google Ireland Limited (Google Analytics 4 and Google Tag Manager) | Website traffic measurement on gauzy.co. Loads only after you consent to the analytics category. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, analytics client identifier, pages viewed, referrer, device and browser details |\n| Liidio Oy (Leadfeeder), a Dealfront Group GmbH company | Business-audience identification on gauzy.co — resolving a visitor's IP address to the organisation it belongs to. Loads only after you consent to the marketing category. | Germany, European Union | None needed — established in the EEA | IP address, inferred employer or organisation, pages viewed and referrer |\n| Chatwoot Inc. | The live support chat widget, which loads on gauzy.co and also inside the signed-in application when support chat is enabled. | United States | Standard Contractual Clauses (EU 2021/914) | name and email address you give the widget, the content of the chat, IP address and session identifiers, the page or screen you were on when you opened it |\n| The Rocket Science Group LLC d/b/a Mailchimp | Newsletter and mailing-list management for people who subscribe on gauzy.co. | United States | Standard Contractual Clauses (EU 2021/914) | email address and name, subscription status and campaign engagement, IP address at the time of subscription |\n| Google Ireland Limited (Google Maps Platform) | Map display, address autocomplete and location selection inside the application, where your administrator enables location features. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, the address text a user types into autocomplete, selected coordinates and resolved addresses |\n| Algolia SAS | Hosted search on the documentation site at docs.gauzy.co, where search credentials are configured. | France, European Union | To be confirmed — we do not yet evidence a mechanism | search queries, IP address and user agent |\n| Hound Technology, Inc. (d/b/a Honeycomb.io) | Distributed tracing and operational metrics for the API, where tracing is enabled and pointed at this provider. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, request URLs and route parameters, user and workspace identifiers carried in trace attributes |\n| SigNoz Inc. | Distributed tracing and operational metrics for the API, as an alternative destination to the above, where tracing is enabled and pointed at this provider. | United States | To be confirmed — we do not yet evidence a mechanism | IP address, request URLs and route parameters, user and workspace identifiers carried in trace attributes |\n| Aspecto Ltd. | Distributed tracing for the API, as a further alternative destination, where tracing is enabled and pointed at this provider. | Israel, which holds a European Commission adequacy decision | Adequacy decision — Israel | IP address, request URLs, identifiers carried in trace attributes |\n| Jitsu Labs, Inc. | Event streaming to a product-analytics pipeline, where the hosted Jitsu service is configured as the destination rather than a destination we run ourselves. | United States | Standard Contractual Clauses (EU 2021/914) | user and workspace identifiers, product events and the changes that produced them, IP address and browser details |\n| Bricks Software AS (Unleash) | Feature-flag evaluation, where the hosted Unleash service is configured rather than an instance we run ourselves. | Norway, European Economic Area | None needed — established in the EEA | application and instance identifiers, flag evaluation context, which can include a user or workspace identifier |\n| Google Ireland Limited (Sign in with Google) | Sign-in, where a user chooses to authenticate with a Google account instead of a password. | United States | Standard Contractual Clauses (EU 2021/914) | Google account identifier, email address, display name and profile picture |\n| Microsoft Corporation (Microsoft Entra ID) | Sign-in, where a user or an administrator chooses to authenticate with a Microsoft work or personal account. Profile details are read from Microsoft Graph. | United States | Standard Contractual Clauses (EU 2021/914) | Microsoft account identifier, email address and display name |\n| LinkedIn Ireland Unlimited Company | Sign-in, where a user chooses to authenticate with a LinkedIn account. | United States | Standard Contractual Clauses (EU 2021/914) | LinkedIn account identifier, email address, name and profile picture |\n| Meta Platforms Ireland Limited (Facebook Login) | Sign-in, where a user chooses to authenticate with a Facebook account. | United States | Standard Contractual Clauses (EU 2021/914) | Facebook account identifier, email address, name and profile picture |\n| X Corp. (Twitter) | Sign-in, where a user chooses to authenticate with an X account. | United States | To be confirmed — we do not yet evidence a mechanism | X account identifier and screen name, email address where the provider releases it |\n| Okta, Inc. (Auth0) | Sign-in, where an organisation chooses to authenticate its people through a hosted Auth0 tenant. | United States | Standard Contractual Clauses (EU 2021/914) | subject identifier issued by the identity provider, email address and name |\n| Fiverr International Ltd. | Account linking for freelancer profiles, where a user connects a Fiverr account. | Israel, which holds a European Commission adequacy decision | Adequacy decision — Israel | Fiverr account identifier, the profile fields the connection returns |\n| Red Hat, Inc. (Keycloak) | Sign-in against a Keycloak realm, where an organisation configures one. Whoever operates that realm holds the data, and where the organisation operates it there is no third party at all. | Determined by whoever operates the realm | Not our transfer — you choose the provider | subject identifier issued by the realm, username and email address |\n| Anthropic, PBC | Model provider for the in-application AI assistant, connected by you with your own account and API key. Your agreement with this provider governs what it does with the content you send it. | United States | Standard Contractual Clauses (EU 2021/914) | prompts and conversation content, any workspace content a user includes in a prompt |\n| OpenAI, L.L.C. | Model provider for the in-application AI assistant, connected by you with your own account and API key. Also reachable indirectly where you supply an OpenAI key to our own AI service for image analysis. | United States | Standard Contractual Clauses (EU 2021/914) | prompts and conversation content, any workspace content a user includes in a prompt, screenshot-derived content where image analysis is routed to your OpenAI account |\n| Google Ireland Limited (Gemini API) | Model provider for the in-application AI assistant, connected by you with your own account and API key. | United States | Standard Contractual Clauses (EU 2021/914) | prompts and conversation content |\n| X.AI LLC | Model provider for the in-application AI assistant, connected by you with your own account and API key. | United States | To be confirmed — we do not yet evidence a mechanism | prompts and conversation content |\n| OpenRouter, Inc. | Model routing for the in-application AI assistant, connected by you with your own account or through an authorisation flow you complete yourself. | United States | To be confirmed — we do not yet evidence a mechanism | prompts and conversation content, OpenRouter account identity where you connect one |\n| Vercel Inc. (AI Gateway) | Gateway that forwards AI assistant requests to a downstream model provider, connected by you with your own account and API key. | United States | Standard Contractual Clauses (EU 2021/914) | prompts and conversation content |\n| Netsoft Holdings, LLC (Hubstaff) | Integration you connect, importing organisations, projects, people, timesheets, activity levels and screenshots from your Hubstaff account into your workspace. | United States | Standard Contractual Clauses (EU 2021/914) | names and email addresses of the people in your Hubstaff account, time logs and activity levels, screenshots captured by Hubstaff, project and task assignments |\n| Upwork Global Inc. | Integration you connect, importing contracts, freelancer profiles, time logs and income and expense reports from your Upwork account, and supporting job matching and proposal drafting. | United States | To be confirmed — we do not yet evidence a mechanism | freelancer name and profile details, contract, earnings and time-log data, screenshots captured by Upwork |\n| Atlassian Pty Ltd (Jira, Trello) | Integration you connect, synchronising projects, issues and worklogs between Jira and your workspace. | United States | Standard Contractual Clauses (EU 2021/914) | Jira account identifiers, display names and email addresses, issue, comment and worklog content |\n| GitHub, Inc. (a Microsoft Corporation company) | Integration you connect through a GitHub App, synchronising repositories, issues and labels with your workspace tasks. | United States | Standard Contractual Clauses (EU 2021/914) | GitHub account identifiers, usernames and email addresses, issue and repository content within the granted scope |\n| Zapier, Inc. | Automation integration you connect, which reads and receives whatever records you wire into a Zap. | United States | Standard Contractual Clauses (EU 2021/914) | any workspace record you route through an automation, including tasks, time logs, contacts and invoices |\n| Celonis SE (Make.com) | Automation integration you connect, which reads and receives whatever records you wire into a scenario. | Germany, European Union | None needed — established in the EEA | any workspace record you route through an automation |\n| Activepieces Inc. | Automation integration you connect, which reads and receives whatever records you wire into a flow. | United States | Standard Contractual Clauses (EU 2021/914) | any workspace record you route through an automation |\n| Sim Studio, Inc. (sim.ai) | AI workflow integration you connect, which receives the inputs you route into a workflow. | United States | To be confirmed — we do not yet evidence a mechanism | workflow inputs, which can contain workspace record content |\n| WakaTime, LLC | Integration a developer connects, ingesting coding-activity heartbeats as time and activity records in your workspace. | United States | To be confirmed — we do not yet evidence a mechanism | developer identity, names of files and projects being edited, editor, language and operating-system metadata with timestamps |\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| 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| 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| UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty | Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Twilio Inc. (SendGrid) | Sends and tracks marketing or transactional email for gauzy.co through dedicated sending, reply and link-tracking subdomains, and stands as an alternative sender for githands. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, open and click tracking events (links.gauzy.co), recipient IP and user agent via tracking pixels |\n| Twilio Inc. (Programmable Messaging) | Sends SMS where a tenant configures Twilio as its SMS gateway using its own account SID and token. | United States | Standard Contractual Clauses (EU 2021/914) | recipient telephone number, message body, which can contain a capture link or workspace content, delivery and status metadata |\n| self-hosted by us - no vendor. Cloud analogue: the Plane Cloud operator (entity name UNKNOWN/unverified; published by the makeplane team, US/India). | Syncs issues and projects with whatever Plane instance a customer configures - our own pm.gauzy.co, their own server, or Plane Cloud. | n/a (self-hosted on own EU hardware); United States / India for Plane Cloud | None needed — established in the EEA | issue, cycle and project records, assignee identity and team-member names, API tokens |\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| 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| 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| 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| 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| 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| Slack Technologies, LLC (a Salesforce, Inc. company) | Posts notifications into, and reads events from, a Slack workspace the customer connects by installing our app into its own workspace. | United States (group); Ireland (EEA contracting for Slack's own customers) | Standard Contractual Clauses (EU 2021/914) | channel and workspace identifiers, message content we post or receive, Slack user identity, including member email addresses, OAuth tokens and webhook payloads, shared recordings, screenshots and their links (ever-rec) |\n| 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| 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\nEver Gauzy can be run on your own infrastructure. If you do that, you choose these providers, you\nhold the credentials, and you contract with them directly.\n\n**We are not a processor for anything in a deployment you run.** We do not receive that data, we cannot\nreach it, and we have no relationship with the providers you configure. They appear here only so that\nreaders running their own copy know which external services the software can be configured to use.\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Amazon Web Services, Inc. (S3) | One of the object-storage backends the open-source software can be pointed at for uploads, avatars, attachments and captured media in a deployment you run yourself. | The region you select in your own account | Not our transfer — you choose the provider | whatever your deployment stores, including screenshots, webcam stills, audio, video and uploaded documents |\n| Wasabi Technologies, Inc. | An S3-compatible object-storage backend the open-source software can be pointed at in a deployment you run yourself. | The region you select in your own account | Not our transfer — you choose the provider | whatever your deployment stores, including captured media and uploaded documents |\n| Cloudinary Ltd. | An image and media storage and delivery backend the open-source software can be pointed at in a deployment you run yourself. | The region you select in your own account | Not our transfer — you choose the provider | whatever your deployment stores, including screenshots, avatars and uploaded images |\n| DigitalOcean, LLC (Spaces) | An S3-compatible object-storage backend the open-source software can be pointed at in a deployment you run yourself. Distinct from the installer delivery listed in the always-engaged table above. | The region you select in your own account | Not our transfer — you choose the provider | whatever your deployment stores, including captured media and uploaded documents |\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| 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### Storage of monitoring media\n\nScreenshots, webcam stills, audio and video captured by the desktop applications are stored through the\nfile-provider configured for the deployment. **For Ever Gauzy Cloud that is our own object storage,\non our own infrastructure**, which is why the commercial object-storage providers the software supports\nappear in tier 3 rather than tier 1. If that ever changes for the hosted Service, this list changes with\nit and the change is announced under the notification process above.\n\n## Hosting and infrastructure\n\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\noperate ourselves.\n\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\n[Security page](https://gauzy.co/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://gauzy.co/privacy).\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\n third party and it is disclosed as one.\n\n### Where a product does something different\n\nA small number of products use a third-party managed database, managed storage or hosted platform for a\nspecific function instead of our own infrastructure. **Where that is the case for Ever Gauzy, the\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\n\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\ntable says so.\n\n### The regions you should design around\n\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\nsmall number of named providers established outside the European Economic Area, each with its own transfer\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\ninternational transfers section of the [Privacy Policy](https://gauzy.co/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://gauzy.co/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://gauzy.co/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.2 of the sub-processor list for\n[gauzy.co](https://gauzy.co), in force from 2026-08-02. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://gauzy.co/subprocessors](https://gauzy.co/subprocessors)."
|
|
158
158
|
}
|
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
"locale": "en",
|
|
9
9
|
"version": "1.1.0",
|
|
10
10
|
"effectiveDate": "2026-10-05",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "68b126b4c9c1a76291033485edca95524a04c918a7842055994fbb573a4ad614",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/subprocessors/010-purpose",
|
|
@@ -154,5 +154,5 @@
|
|
|
154
154
|
}
|
|
155
155
|
],
|
|
156
156
|
"path": "content/subprocessors/githands/en.html",
|
|
157
|
-
"markdown": "## Why this page exists\r\n\r\nWhen you use GitHands Cloud to process personal data, we act as your processor and you are the\r\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\r\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\r\n\r\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\r\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\r\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\r\ngiven through it.\r\n\r\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\r\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\r\nanswer should not be available only to the person paying the invoice.\r\n\r\n### What counts as a sub-processor\r\n\r\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\r\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\r\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\r\n\r\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\r\nmore complete:\r\n\r\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\r\n is not in the path of your data.\r\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\r\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\r\n part, not our processor. Those recipients are described in the\r\n [Privacy Policy](https://githands.com/privacy) instead.\r\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\r\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\r\n what genuinely sits in front of it.\r\n\r\n### What this page covers\r\n\r\nThe **hosted Service we operate** at [githands.com](https://githands.com), for GitHands\r\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\r\nbetween them — do not read this one as covering a product it does not name.\r\n\r\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\r\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\r\nexists to make that distinction visible rather than to blur it.\r\n\r\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\r\n\r\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\r\nyou the wrong answer.\r\n\r\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\r\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\r\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\r\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\r\ndeployment that somebody else runs, with their own account and their own credentials.\r\n\r\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\r\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\r\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\r\nthree tiers.\r\n\r\n### Tier 1 — always engaged\r\n\r\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\r\nbecause they are part of how the Service is delivered to everyone.\r\n\r\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\r\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\r\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\r\n\r\n### Tier 2 — engaged only if you turn something on\r\n\r\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\r\nEnable nothing and it is never involved, and no data of yours ever reaches it.\r\n\r\nWho does the enabling depends on the feature:\r\n\r\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\r\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\r\n connector.\r\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\r\n connecting their own third-party tool.\r\n\r\nThe table names the feature or setting that activates each provider, so you can check your own\r\nconfiguration against it rather than take our word for the current state. If you want to know precisely\r\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\r\n\r\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\r\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\r\n\r\n### Tier 3 — self-hosted deployments only\r\n\r\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\r\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\r\nusing your own accounts and your own credentials.\r\n\r\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\r\nThey are not our sub-processors, and they never become ours by appearing here.\r\n\r\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\r\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\r\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\r\nopen-source section of our [Terms of Service](https://githands.com/tos) sets out the same split.\r\n\r\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\r\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\r\n\r\n### What the columns mean\r\n\r\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\r\n separate European establishment that contracts with us, that is the one named.\r\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\r\n- **Location** — where the processing takes place, or the provider's place of establishment where\r\n processing is distributed. Where a provider contracts through a European establishment but processes\r\n elsewhere, this column says both, because the two are different facts and only naming the first would\r\n flatter us.\r\n- **Transfer mechanism** — for a provider outside the European Economic Area, the Chapter V instrument we\r\n actually rely on for that specific provider: an adequacy decision, the Standard Contractual Clauses, or\r\n nothing yet. **Where it reads \"To be confirmed\", we have not yet evidenced an instrument for that\r\n provider, and we would rather say so here than print one we cannot produce.** That is a live piece of\r\n work, not a formula. Providers established inside the EEA need no mechanism and say so. For the third\r\n tier the transfer is not ours at all — you choose the provider and hold the contract.\r\n The general rules behind this column are in the international transfers section of our\r\n [Privacy Policy](https://githands.com/privacy), and we will give you a copy of the safeguards for a named\r\n provider on request.\r\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\r\n provider that receives email addresses receives them for the people who trigger the feature, not for\r\n everyone.\r\n\r\n### Why this list is deliberately longer than it needs to be\r\n\r\n**We list providers we may engage, not only the ones engaged today.** Where we have configured a\r\nprovider, kept one available behind a feature flag, used one recently, or expect to use one for a\r\npurpose already described here, it appears in the tables below — even if no data has reached it this\r\nmonth, and even where we currently run the equivalent ourselves.\r\n\r\nWe do this on purpose, and you should read the tables with it in mind:\r\n\r\n- **A provider appearing here is not proof that your data has reached it.** It means the provider is\r\n within the scope of what we have told you we may do, at the tier shown. The tier is the part that\r\n tells you when it is engaged.\r\n- **Where we self-host something today** — our analytics, our job runner, our databases, our object\r\n storage — we say so, and we also name the hosted service we would move to, so that a later change is\r\n covered by a disclosure you have already seen rather than by a fresh surprise.\r\n- **The alternative is worse.** A list that names only today's exact set has to be re-issued, and\r\n re-consented, every time an engineer changes a setting. A list drawn slightly wide stays true through\r\n ordinary operational change, which is what makes it dependable.\r\n\r\n**What we will not do is use this as cover.** Breadth here does not license a purpose we have not\r\ndescribed, a category of data we have not listed, or a transfer without a mechanism. If we start\r\nsending a new *kind* of personal data, or sending it for a new *reason*, that is a change to this page\r\nand to the notice period below — not something the width of a table quietly absorbs.\r\n\r\nIf you need to know precisely which providers are live for your workspace today, rather than which ones\r\nmay be, ask us at privacy@ever.co and we will tell you.\r\n\r\n### What is deliberately not in the tables\r\n\r\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\r\n container platform are not sub-processors, because there is no third party involved. The next section\r\n describes what we run and what really does sit in front of it.\r\n- **Recipients that are not processors** — payment providers acting under their own regulatory\r\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\r\n are covered in the [Privacy Policy](https://githands.com/privacy).\r\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\r\n site, their notice applies.\n\n## Annex: GitHands\r\n\r\n### Tier 1 — always engaged\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination and the tunnel that is the only public route into our infrastructure. Every request to any GitHands hostname passes through it. | United States, with edge termination worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, connection and TLS metadata, full request URLs and headers, cookies in transit |\n| GitHub, Inc. (a Microsoft Corporation company) | Three distinct roles. It hosts our source code, our container images and our build pipeline. It is the identity provider when a customer signs in with GitHub. And its public API is the primary source from which the developer database is built — profiles, stargazer and forker lists, contributor and participant lists, public commit metadata and public event streams. | United States | Standard Contractual Clauses (EU 2021/914) | the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity |\n| Resend, Inc. | Delivery of outbound email — account and invitation mail, and the campaign messages a customer sends through the Service's default sending path — together with the delivery, open, click, bounce, complaint and reply events that come back. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, personalised subject line and message body, delivery, open, click, bounce and unsubscribe events, recipient IP address and user agent captured by open and click tracking, the content of a reply |\n| OpenRouter, Inc. | Routing of every AI request the Service makes to the model provider selected for it. This is the only AI provider configured in the hosted Service. OpenRouter forwards the prompt on to the upstream model provider it routes to, and that provider receives the same content. | United States, and onward to the selected model provider | To be confirmed — we do not yet evidence a mechanism | developer names, usernames, email addresses, biographies and repository lists embedded in prompts, drafted outreach messages and the inbound replies being classified, customer chat messages with the in-product assistant |\n| Langfuse GmbH | Observability for AI requests — the full prompt and the full completion for each call are recorded as a trace so we can debug quality and cost. That means the same personal data that goes to the model provider is also stored here, in readable form. | Germany | None needed — established in the EEA | complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace |\n| Functional Software, Inc. d/b/a Sentry | Application error monitoring and performance tracing. Browser reports are sent to a path on our own domain and forwarded on, so that an extension blocking third-party requests does not silently hide our errors from us. Server-side logging is enabled, so console output can travel with a report. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and user agent, user identifier and email address attached as error context, URL and route, stack traces and breadcrumbs, console output, which can carry fragments of whatever request failed |\n| PostHog, Inc. | Product analytics — which pages and features are used, where people abandon a flow, and what fails. Captured both in the browser and on our servers. Consent-gated in the browser. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer |\n| Jitsu Labs, Inc. | A second product-analytics event pipeline. Events are collected through an endpoint on the githands.com domain rather than a vendor hostname, which is worth saying plainly: an endpoint on our own domain that forwards to somebody else should never be a surprise. Consent-gated. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and user agent, in-product events and their properties, user identifier |\n| Trigger.dev Ltd. | The managed runtime that executes background work — extraction runs, enrichment, scoring, sequence steps and scheduled jobs. Job payloads and run logs are held there, and the runtime holds the credentials it needs to reach our database. | United Kingdom | None — we run this ourselves in the EU | job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data |\n| ui-avatars.com | Generated placeholder avatars, used where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser. | Not published by the provider | 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| 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| 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| 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| 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| 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 |\r\n\r\n### Tier 2 — engaged only when a feature, integration or consent brings them in\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Google LLC | Sign in with Google. Engaged only where an individual chooses that sign-in method. | United States | Standard Contractual Clauses (EU 2021/914) | email address, name, profile picture URL, Google account identifier |\n| LinkedIn Ireland Unlimited Company | Sign in with LinkedIn, and the delivery of LinkedIn-hosted profile images where a signed-in user has one. Engaged only where an individual chooses that sign-in method. | United States | Standard Contractual Clauses (EU 2021/914) | email address, name and profile fields, profile picture URL, LinkedIn member identifier |\n| HubSpot, Inc. | Two-way contact synchronisation, engaged only when a customer connects its own HubSpot account. Data moves in both directions once connected. | United States | 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| Slack Technologies, LLC (a Salesforce, Inc. company) | Two-way contact synchronisation, engaged only when a customer connects its own Salesforce organisation. | United States | Standard Contractual Clauses (EU 2021/914) | contact and account records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Slack Technologies, LLC (a Salesforce, Inc. company) | Workspace notifications and in-Slack actions, engaged only when a customer installs the Slack application into its own workspace. | United States | Standard Contractual Clauses (EU 2021/914) | workspace, channel and user identifiers, the notification content we send |\n| Stripe, Inc. | Payments and subscription billing for paid plans, engaged when you buy one. The free plan never reaches it, and we never receive your full card number. | United States | Standard Contractual Clauses (EU 2021/914) | billing name and address, country and tax identification number, payment method token and card last four digits, invoice and subscription history |\n| Twilio Inc. (SendGrid) | An alternative outbound sending provider. The Service can be configured to send through it instead of the default. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery and engagement events |\n| Sinch Mailgun | An alternative outbound sending provider. Not configured in the hosted Service. | United States, with an optional European region | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery events |\n| Amazon Web Services, Inc. | Amazon SES as an alternative outbound sending provider, with Amazon SNS carrying bounce and complaint notifications back. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, bounce and complaint events |\n| ActiveCampaign, LLC (Postmark) | An alternative outbound sending provider. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery events |\n| Google Ireland Limited (Sign in with Google) | Authenticates a user who chooses 'sign in with Google', returning their email, name and picture, and in ever-rec also exports recordings to the user's own Google Drive when they connect it. | Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | email address, name and profile picture, Google account identifier, OAuth access and refresh tokens, Google Drive file metadata and content the user chooses to export, where the Drive scope is granted (ever-rec) |\n| 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| Google Ireland Limited (Google Fonts) | Delivers typefaces to the visitor's browser at page load on the properties that hot-link them, disclosing the visitor's IP to Google before any consent choice. | Ireland (contracting entity); processing in Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| Vercel Inc. | Hosts the cloc platform; routes AI prompts to downstream model providers for gauzy through the AI Gateway; and remains the deployment target of surviving workflows and DNS delegations for several frontends that have since moved to our own cluster. | United States | Standard Contractual Clauses (EU 2021/914) | for cloc: full application traffic and runtime data (the platform actually runs there), IP address and user agent of visitors where a site is served from Vercel, page-view and Web Vitals events, for gauzy: prompt content and model responses routed through the AI Gateway, plus routing and usage metadata, deployment metadata |\n| DigitalOcean, LLC | Serves desktop installer downloads from the gauzy.co download page, holds media in Spaces where a deployment selects it as the file provider, still carries legacy container images and gated deploy workflows, and for cloc provisions servers on a customer's behalf. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files, screenshots and captured media held in Spaces, IP address and user agent of anyone downloading an asset or a desktop installer, container images and build metadata (no personal data), for cloc: server handles, sizes and lifecycle state of infrastructure provisioned on a customer's behalf |\n| Uptime Robot Service Provider Ltd - UNVERIFIED. The commonly cited registration is Cyprus (Nicosia); confirm from the current Terms or Imprint before publishing any location claim. | Hosts the public status page at status.<our-domain>, so anyone who opens it hands their IP and user agent to the vendor. | Cyprus (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address and user agent of every visitor to a status page, cookies set by the status page, monitored endpoint URLs and response metadata |\n| Wasabi Technologies, Inc. | Holds avatars, task attachments and time-tracker screenshots wherever the platform's or a tenant's file provider is set to Wasabi. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files and document attachments, avatars, employee time-tracker screenshots and captured monitoring media |\n| Cloudinary Ltd. | Stores and transforms images and video where a deployment's or the platform's media provider is set to Cloudinary, and serves them to viewers directly from its own CDN. | Israel | Adequacy decision — Israel | uploaded images and video, screenshots and captured media, IP address and user agent of every viewer fetching an asset |\n| UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty | Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Twilio Inc. (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 Analytics 4 and Google Tag Manager) | Measures marketing-site and, on some properties, in-application usage through the GA4 tag loaded via Tag Manager, keyed to a persistent client-id cookie. | Ireland (contracting) / United States (processing) | Standard Contractual Clauses (EU 2021/914) | IP address (anonymize_ip is set on some sites, not all), _ga / _gid / _gat cookies (GA client identifier), page URLs, referrer and UTM parameters, device, browser and approximate location, conversion events, tied to a user id on gauzy.co |\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| 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| PayPal (Europe) S.à r.l. et Cie, S.C.A. | Takes payments for a commerce deployment, where the merchant running that deployment contracts with PayPal directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Luxembourg (EEA users) / United States (PayPal, Inc.) | None needed — established in the EEA | payer identity and email address, transaction amount and order reference, payment status and history |\n| Atlassian Pty Ltd (Jira, Trello) | Syncs tasks, issues and attachments with a Jira or Trello site the customer connects using its own account. | Australia (Atlassian Pty Ltd) / Netherlands (Atlassian B.V.) / United States (Atlassian, Inc.) | Standard Contractual Clauses (EU 2021/914) | issue, project, card and board records, reporter and assignee identity, attachments, screenshots and recordings pushed to an issue, API key and OAuth tokens |\n| 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| Chatwoot Inc. | Runs the support chat widget that visitors and signed-in users type into, receiving the whole conversation plus the page context. | United States | Standard Contractual Clauses (EU 2021/914) | visitor or user name and email when supplied, full chat message content, IP address, page URL and browser details |\n| iubenda s.r.l. | Delivers hosted legal documents to visitors who open the /legal route in the Gauzy application, which still fetches the policy from iubenda in the visitor's browser. | Italy | None needed — established in the EEA | IP address, user agent, consent preferences and the timestamp of the choice |\n| 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 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 |\r\n\r\n### Tier 3 — self-hosted deployments only\r\n\r\nIf you run GitHands on your own infrastructure, you choose these providers and hold the\r\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\r\nwe cannot reach it, and we have no relationship with the providers you configure.\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| The Rocket Science Group LLC d/b/a Mailchimp | A self-hosted installation has no sending path of ours to fall back on — we removed the shared sending address deliberately. You bring your own sending account and your own verified sending domain. The software supports Resend, Twilio SendGrid, Sinch Mailgun, Amazon SES, Postmark and a plain SMTP relay. | Wherever the provider you choose processes | Not our transfer — you choose the provider | recipient email addresses and names, message content, delivery and engagement events |\n| The Rocket Science Group LLC d/b/a Mailchimp | Every AI feature in a self-hosted installation runs against a key you supply, to a provider you pick. Nothing routes through us and we see none of it. | Wherever the provider you choose processes | Not our transfer — you choose the provider | prompts and completions, including any personal data your installation puts in them |\n| The Rocket Science Group LLC d/b/a Mailchimp | A self-hosted installation reads the source platforms under your own credentials and in your own name. The rate limits, the platform's acceptable use rules and the consequences of breaching them attach to your account, not ours. | The platform's own infrastructure | Not our transfer — you choose the provider | the queries your installation makes, your own account identity and access token |\n| The database, object storage and job runtime you choose | You select and operate the PostgreSQL database, the object storage and the background-job runtime. Trigger.dev can be pointed at its hosted service or at an instance you run yourself. | Wherever you deploy them | Not our transfer — you choose the provider | all application data in your installation |\n| The Rocket Science Group LLC d/b/a Mailchimp | Sentry, PostHog and Jitsu wiring ships in the software but is inert until you supply your own project keys. Supply them and the data goes to your projects, under your account. | Wherever the provider you choose processes | Not our transfer — you choose the provider | error reports, console output, product analytics events and the identifiers attached to them |\n| Mem0 AI, Inc. | Long-term memory for the command-line client and the MCP server. Disabled in the hosted Service and available only to a self-hoster who switches it on with a key of their own. | United States | Not our transfer — you choose the provider | stored agent conversation memory, which can contain customer and developer details |\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 |\r\n\r\n### Data about developers who are not our users\r\n\r\nMost of the personal data in GitHands is about people who never signed up. The sub-processors\r\nabove process that data on our instructions in the same way as any other — but two points follow that a\r\nplain table does not convey.\r\n\r\n- **The source platforms are not our sub-processors.** GitHub, GitLab and similar platforms are where the\r\n data comes from, not parties we send it to. Their terms govern what may be collected from them and what\r\n may be done with it afterwards.\r\n- **We do not sell this data, and no provider above receives it for their own purposes.** Every one of them\r\n acts on our instructions under a written contract.\r\n\r\nIf you are a developer whose data is here and you want it removed, you do not need to work out which\r\nprovider holds what. Use the objection route in the privacy annex and it is handled across all of them.\n\n## Hosting and infrastructure\r\n\r\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\r\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\r\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\r\noperate ourselves.\r\n\r\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\r\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\r\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\r\n[Security page](https://githands.com/security).\r\n\r\n### Where processing actually happens\r\n\r\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\r\n Union.** That is the primary location for accounts, content, files and the databases behind them.\r\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\r\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\r\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\r\n transfer mechanism for it is described in our [Privacy Policy](https://githands.com/privacy).\r\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\r\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\r\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\r\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\r\n third party and it is disclosed as one.\r\n\r\n### Where a product does something different\r\n\r\nA small number of products use a third-party managed database, managed storage or hosted platform for a\r\nspecific function instead of our own infrastructure. **Where that is the case for GitHands, the\r\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\r\n\r\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\r\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\r\ntable says so.\r\n\r\n### The regions you should design around\r\n\r\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\r\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\r\nsmall number of named providers established outside the European Economic Area, each with its own transfer\r\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\r\ninternational transfers section of the [Privacy Policy](https://githands.com/privacy).\r\n\r\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\r\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\r\n\r\n### The notice period\r\n\r\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\r\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\r\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\r\nabout afterwards.\r\n\r\n### How you find out\r\n\r\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\r\n the page itself is the notice.\r\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\r\n notification list. We then email you before each change, at the same time the page is updated. **We\r\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\r\n organisation has been sent and not received.\r\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\r\n administrators.\r\n\r\n### What the notice tells you\r\n\r\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\r\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\r\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\r\n\r\n### Urgent replacements\r\n\r\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\r\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\r\nleaving.\r\n\r\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\r\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\r\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\r\nplainly why the normal period was not followed.\r\n\r\n### Changes that do not need notice\r\n\r\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\r\nprovider changing its own name, or the group entity that contracts with us changing without a change in\r\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\r\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\r\nthe full notice.**\r\n\r\n### The record\r\n\r\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\r\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\r\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\r\nas it stood on a particular date.\n\n## Objecting to a sub-processor\r\n\r\n### Who can object\r\n\r\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\r\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\r\n[Privacy Policy](https://githands.com/privacy), and if your data sits in an employer's workspace, your employer\r\nis the controller and the request goes to them.\r\n\r\n### How to object\r\n\r\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\r\n\r\n- which provider you are objecting to;\r\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\r\n commitment you have given your own users, a regulator's position that applies to you, a documented\r\n security concern;\r\n- which of your workspaces or environments the objection covers.\r\n\r\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\r\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\r\nis and we can usually solve it.\r\n\r\n### What we do next\r\n\r\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\r\nbetween we look for a way to make the objection unnecessary:\r\n\r\n- **A different provider** for your workspace, where one exists that does the job.\r\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\r\n that needs the provider at all, if you can live without it.\r\n- **Excluding your workspace** from the provider, where that is technically possible.\r\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\r\n the provider as a whole.\r\n\r\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\r\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\r\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\r\nclock run out on you.\r\n\r\n### If we cannot resolve it\r\n\r\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\r\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\r\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\r\n\r\nGive us notice within 30 days of our final response, and we will keep your data available for export for\r\nthe usual 30-day window described in the [Terms of Service](https://githands.com/tos) so that leaving does not\r\ncost you the data.\r\n\r\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\r\nService and export your data.\r\n\r\n### Objecting to a provider already on the list\r\n\r\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\r\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\r\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\r\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\r\nstraight no with the reason.\n\n## How to reach us about this list\r\n\r\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\r\n change notification list** — privacy@ever.co.\r\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\r\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\r\n legal@ever.co.\r\n\r\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\r\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\r\nown processing and your processor for the data in your workspace. By post, write to the registered office\r\nand mark the letter for the attention of the privacy team. We correspond in English.\r\n\r\nYou may also complain to a data protection supervisory authority. Ours is the\r\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\r\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\r\nto the authority for the country where you live or work.\r\n\r\nThis document is version 1.1.0 of the sub-processor list for\r\n[githands.com](https://githands.com), in force from 2026-10-05. It lists the providers engaged\r\nas at that date. Earlier versions, with the dates they applied, are at\r\n[https://githands.com/subprocessors](https://githands.com/subprocessors)."
|
|
157
|
+
"markdown": "## Why this page exists\n\nWhen you use GitHands Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://githands.com/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [githands.com](https://githands.com), for GitHands\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\nbetween them — do not read this one as covering a product it does not name.\n\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\nexists to make that distinction visible rather than to blur it.\n\nThis page is versioned and dated. The version in force, and the date it took effect, are at the end.\n\n## How to read this list\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://githands.com/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where 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://githands.com/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### 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://githands.com/privacy).\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\n site, their notice applies.\n\n## Annex: GitHands\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination and the tunnel that is the only public route into our infrastructure. Every request to any GitHands hostname passes through it. | United States, with edge termination worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, connection and TLS metadata, full request URLs and headers, cookies in transit |\n| GitHub, Inc. (a Microsoft Corporation company) | Three distinct roles. It hosts our source code, our container images and our build pipeline. It is the identity provider when a customer signs in with GitHub. And its public API is the primary source from which the developer database is built — profiles, stargazer and forker lists, contributor and participant lists, public commit metadata and public event streams. | United States | Standard Contractual Clauses (EU 2021/914) | the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity |\n| Resend, Inc. | Delivery of outbound email — account and invitation mail, and the campaign messages a customer sends through the Service's default sending path — together with the delivery, open, click, bounce, complaint and reply events that come back. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, personalised subject line and message body, delivery, open, click, bounce and unsubscribe events, recipient IP address and user agent captured by open and click tracking, the content of a reply |\n| OpenRouter, Inc. | Routing of every AI request the Service makes to the model provider selected for it. This is the only AI provider configured in the hosted Service. OpenRouter forwards the prompt on to the upstream model provider it routes to, and that provider receives the same content. | United States, and onward to the selected model provider | To be confirmed — we do not yet evidence a mechanism | developer names, usernames, email addresses, biographies and repository lists embedded in prompts, drafted outreach messages and the inbound replies being classified, customer chat messages with the in-product assistant |\n| Langfuse GmbH | Observability for AI requests — the full prompt and the full completion for each call are recorded as a trace so we can debug quality and cost. That means the same personal data that goes to the model provider is also stored here, in readable form. | Germany | None needed — established in the EEA | complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace |\n| Functional Software, Inc. d/b/a Sentry | Application error monitoring and performance tracing. Browser reports are sent to a path on our own domain and forwarded on, so that an extension blocking third-party requests does not silently hide our errors from us. Server-side logging is enabled, so console output can travel with a report. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and user agent, user identifier and email address attached as error context, URL and route, stack traces and breadcrumbs, console output, which can carry fragments of whatever request failed |\n| PostHog, Inc. | Product analytics — which pages and features are used, where people abandon a flow, and what fails. Captured both in the browser and on our servers. Consent-gated in the browser. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer |\n| Jitsu Labs, Inc. | A second product-analytics event pipeline. Events are collected through an endpoint on the githands.com domain rather than a vendor hostname, which is worth saying plainly: an endpoint on our own domain that forwards to somebody else should never be a surprise. Consent-gated. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and user agent, in-product events and their properties, user identifier |\n| Trigger.dev Ltd. | The managed runtime that executes background work — extraction runs, enrichment, scoring, sequence steps and scheduled jobs. Job payloads and run logs are held there, and the runtime holds the credentials it needs to reach our database. | United Kingdom | None — we run this ourselves in the EU | job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data |\n| ui-avatars.com | Generated placeholder avatars, used where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser. | Not published by the provider | 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| 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| 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| 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| 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| 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| Google LLC | Sign in with Google. Engaged only where an individual chooses that sign-in method. | United States | Standard Contractual Clauses (EU 2021/914) | email address, name, profile picture URL, Google account identifier |\n| LinkedIn Ireland Unlimited Company | Sign in with LinkedIn, and the delivery of LinkedIn-hosted profile images where a signed-in user has one. Engaged only where an individual chooses that sign-in method. | United States | Standard Contractual Clauses (EU 2021/914) | email address, name and profile fields, profile picture URL, LinkedIn member identifier |\n| HubSpot, Inc. | Two-way contact synchronisation, engaged only when a customer connects its own HubSpot account. Data moves in both directions once connected. | United States | 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| Slack Technologies, LLC (a Salesforce, Inc. company) | Two-way contact synchronisation, engaged only when a customer connects its own Salesforce organisation. | United States | Standard Contractual Clauses (EU 2021/914) | contact and account records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Slack Technologies, LLC (a Salesforce, Inc. company) | Workspace notifications and in-Slack actions, engaged only when a customer installs the Slack application into its own workspace. | United States | Standard Contractual Clauses (EU 2021/914) | workspace, channel and user identifiers, the notification content we send |\n| Stripe, Inc. | Payments and subscription billing for paid plans, engaged when you buy one. The free plan never reaches it, and we never receive your full card number. | United States | Standard Contractual Clauses (EU 2021/914) | billing name and address, country and tax identification number, payment method token and card last four digits, invoice and subscription history |\n| Twilio Inc. (SendGrid) | An alternative outbound sending provider. The Service can be configured to send through it instead of the default. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery and engagement events |\n| Sinch Mailgun | An alternative outbound sending provider. Not configured in the hosted Service. | United States, with an optional European region | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery events |\n| Amazon Web Services, Inc. | Amazon SES as an alternative outbound sending provider, with Amazon SNS carrying bounce and complaint notifications back. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, bounce and complaint events |\n| ActiveCampaign, LLC (Postmark) | An alternative outbound sending provider. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery events |\n| Google Ireland Limited (Sign in with Google) | Authenticates a user who chooses 'sign in with Google', returning their email, name and picture, and in ever-rec also exports recordings to the user's own Google Drive when they connect it. | Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | email address, name and profile picture, Google account identifier, OAuth access and refresh tokens, Google Drive file metadata and content the user chooses to export, where the Drive scope is granted (ever-rec) |\n| 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| Google Ireland Limited (Google Fonts) | Delivers typefaces to the visitor's browser at page load on the properties that hot-link them, disclosing the visitor's IP to Google before any consent choice. | Ireland (contracting entity); processing in Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| Vercel Inc. | Hosts the cloc platform; routes AI prompts to downstream model providers for gauzy through the AI Gateway; and remains the deployment target of surviving workflows and DNS delegations for several frontends that have since moved to our own cluster. | United States | Standard Contractual Clauses (EU 2021/914) | for cloc: full application traffic and runtime data (the platform actually runs there), IP address and user agent of visitors where a site is served from Vercel, page-view and Web Vitals events, for gauzy: prompt content and model responses routed through the AI Gateway, plus routing and usage metadata, deployment metadata |\n| DigitalOcean, LLC | Serves desktop installer downloads from the gauzy.co download page, holds media in Spaces where a deployment selects it as the file provider, still carries legacy container images and gated deploy workflows, and for cloc provisions servers on a customer's behalf. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files, screenshots and captured media held in Spaces, IP address and user agent of anyone downloading an asset or a desktop installer, container images and build metadata (no personal data), for cloc: server handles, sizes and lifecycle state of infrastructure provisioned on a customer's behalf |\n| Uptime Robot Service Provider Ltd - UNVERIFIED. The commonly cited registration is Cyprus (Nicosia); confirm from the current Terms or Imprint before publishing any location claim. | Hosts the public status page at status.<our-domain>, so anyone who opens it hands their IP and user agent to the vendor. | Cyprus (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address and user agent of every visitor to a status page, cookies set by the status page, monitored endpoint URLs and response metadata |\n| Wasabi Technologies, Inc. | Holds avatars, task attachments and time-tracker screenshots wherever the platform's or a tenant's file provider is set to Wasabi. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files and document attachments, avatars, employee time-tracker screenshots and captured monitoring media |\n| Cloudinary Ltd. | Stores and transforms images and video where a deployment's or the platform's media provider is set to Cloudinary, and serves them to viewers directly from its own CDN. | Israel | Adequacy decision — Israel | uploaded images and video, screenshots and captured media, IP address and user agent of every viewer fetching an asset |\n| UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty | Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Twilio Inc. (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 Analytics 4 and Google Tag Manager) | Measures marketing-site and, on some properties, in-application usage through the GA4 tag loaded via Tag Manager, keyed to a persistent client-id cookie. | Ireland (contracting) / United States (processing) | Standard Contractual Clauses (EU 2021/914) | IP address (anonymize_ip is set on some sites, not all), _ga / _gid / _gat cookies (GA client identifier), page URLs, referrer and UTM parameters, device, browser and approximate location, conversion events, tied to a user id on gauzy.co |\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| 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| PayPal (Europe) S.à r.l. et Cie, S.C.A. | Takes payments for a commerce deployment, where the merchant running that deployment contracts with PayPal directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Luxembourg (EEA users) / United States (PayPal, Inc.) | None needed — established in the EEA | payer identity and email address, transaction amount and order reference, payment status and history |\n| Atlassian Pty Ltd (Jira, Trello) | Syncs tasks, issues and attachments with a Jira or Trello site the customer connects using its own account. | Australia (Atlassian Pty Ltd) / Netherlands (Atlassian B.V.) / United States (Atlassian, Inc.) | Standard Contractual Clauses (EU 2021/914) | issue, project, card and board records, reporter and assignee identity, attachments, screenshots and recordings pushed to an issue, API key and OAuth tokens |\n| 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| Chatwoot Inc. | Runs the support chat widget that visitors and signed-in users type into, receiving the whole conversation plus the page context. | United States | Standard Contractual Clauses (EU 2021/914) | visitor or user name and email when supplied, full chat message content, IP address, page URL and browser details |\n| iubenda s.r.l. | Delivers hosted legal documents to visitors who open the /legal route in the Gauzy application, which still fetches the policy from iubenda in the visitor's browser. | Italy | None needed — established in the EEA | IP address, user agent, consent preferences and the timestamp of the choice |\n| 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 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 GitHands on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| The Rocket Science Group LLC d/b/a Mailchimp | A self-hosted installation has no sending path of ours to fall back on — we removed the shared sending address deliberately. You bring your own sending account and your own verified sending domain. The software supports Resend, Twilio SendGrid, Sinch Mailgun, Amazon SES, Postmark and a plain SMTP relay. | Wherever the provider you choose processes | Not our transfer — you choose the provider | recipient email addresses and names, message content, delivery and engagement events |\n| The Rocket Science Group LLC d/b/a Mailchimp | Every AI feature in a self-hosted installation runs against a key you supply, to a provider you pick. Nothing routes through us and we see none of it. | Wherever the provider you choose processes | Not our transfer — you choose the provider | prompts and completions, including any personal data your installation puts in them |\n| The Rocket Science Group LLC d/b/a Mailchimp | A self-hosted installation reads the source platforms under your own credentials and in your own name. The rate limits, the platform's acceptable use rules and the consequences of breaching them attach to your account, not ours. | The platform's own infrastructure | Not our transfer — you choose the provider | the queries your installation makes, your own account identity and access token |\n| The database, object storage and job runtime you choose | You select and operate the PostgreSQL database, the object storage and the background-job runtime. Trigger.dev can be pointed at its hosted service or at an instance you run yourself. | Wherever you deploy them | Not our transfer — you choose the provider | all application data in your installation |\n| The Rocket Science Group LLC d/b/a Mailchimp | Sentry, PostHog and Jitsu wiring ships in the software but is inert until you supply your own project keys. Supply them and the data goes to your projects, under your account. | Wherever the provider you choose processes | Not our transfer — you choose the provider | error reports, console output, product analytics events and the identifiers attached to them |\n| Mem0 AI, Inc. | Long-term memory for the command-line client and the MCP server. Disabled in the hosted Service and available only to a self-hoster who switches it on with a key of their own. | United States | Not our transfer — you choose the provider | stored agent conversation memory, which can contain customer and developer details |\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### Data about developers who are not our users\n\nMost of the personal data in GitHands is about people who never signed up. The sub-processors\nabove process that data on our instructions in the same way as any other — but two points follow that a\nplain table does not convey.\n\n- **The source platforms are not our sub-processors.** GitHub, GitLab and similar platforms are where the\n data comes from, not parties we send it to. Their terms govern what may be collected from them and what\n may be done with it afterwards.\n- **We do not sell this data, and no provider above receives it for their own purposes.** Every one of them\n acts on our instructions under a written contract.\n\nIf you are a developer whose data is here and you want it removed, you do not need to work out which\nprovider holds what. Use the objection route in the privacy annex and it is handled across all of them.\n\n## Hosting and infrastructure\n\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\noperate ourselves.\n\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\n[Security page](https://githands.com/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://githands.com/privacy).\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\n third party and it is disclosed as one.\n\n### Where a product does something different\n\nA small number of products use a third-party managed database, managed storage or hosted platform for a\nspecific function instead of our own infrastructure. **Where that is the case for GitHands, the\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\n\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\ntable says so.\n\n### The regions you should design around\n\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\nsmall number of named providers established outside the European Economic Area, each with its own transfer\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\ninternational transfers section of the [Privacy Policy](https://githands.com/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://githands.com/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://githands.com/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.1.0 of the sub-processor list for\n[githands.com](https://githands.com), in force from 2026-10-05. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://githands.com/subprocessors](https://githands.com/subprocessors)."
|
|
158
158
|
}
|