Subprocessors
Effective date: 2 October 2026
This page is the list. It names every sub-processor that handles customer content, and it is Annex 3 of our Data Processing Agreement and Annex III for the purposes of the Standard Contractual Clauses.
The named list
| Sub-processor | Purpose | Processing location | Principal place of business | Contact |
|---|---|---|---|---|
| Google Cloud | hosting, storage, backups | europe-west regions | Gordon House, Barrow Street, Dublin 4, Ireland | via the Google Cloud privacy contact form |
| OpenAI | AI processing of selected task context | United States | 3180 18th Street, San Francisco, CA 94110, USA | privacy@openai.com |
| Anthropic | AI processing of selected task context | United States | 548 Market Street, San Francisco, CA 94104, USA | privacy@anthropic.com |
| Cloudflare | CDN and security edge, TLS termination | United States company, global edge network | 101 Townsend Street, San Francisco, CA 94107, USA | privacydpo@cloudflare.com |
| Resend | notification emails for audit and Autofix results, which carry result summaries, project and repository names and result links | United States | Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA | privacy@resend.com |
| Google Workspace | our own mailboxes: your support correspondence and anything you attach to it. Operational alerts arrive here too, but they carry only a task identifier and a link — no content of yours | Europe. Data regions are set to Europe, which covers the subject, body, senders, recipients and attachments of mail, at rest and in processing. Data regions do not cover logs or cached content, so that data is not pinned to a region | Gordon House, Barrow Street, Dublin 4, Ireland | via the Google privacy contact form |
The contracting entity for each is the one named in its data processing agreement, which may be a regional subsidiary of the company above. Ask us and we will tell you which entity holds your contract and send you the relevant terms.
If a provider is not in this table, it does not receive customer content. Adding or replacing an entry triggers 30 days’ notice by email, with a right to object, under DPA section 5.
Everything else we use is listed further down, under Providers that receive no customer content. A provider that never sees your repository content, reports or task context is not a sub-processor under the DPA, and we are the controller for what it handles rather than your processor.
Agreements
Every sub-processor above is engaged under a data processing agreement incorporating the EU Standard Contractual Clauses and the UK Addendum.
| Sub-processor | Basis |
|---|---|
| Google Cloud | Google’s Cloud Data Processing Addendum, incorporating the EU SCCs and the UK Addendum. Processing is in europe-west regions, so no transfer out of Europe arises for storage |
| OpenAI | signed data processing agreement, EU SCCs and UK Addendum |
| Anthropic | signed data processing agreement, EU SCCs and UK Addendum |
| Cloudflare | Cloudflare’s data processing addendum, incorporating the EU SCCs and the UK Addendum, accepted on our account |
| Resend | Resend’s data processing addendum, which binds on entering its terms and needs no signature, incorporating the EU SCCs — Module Three where we act as your processor — and the UK Addendum |
| Google Workspace | the same Cloud Data Processing Addendum as Google Cloud — one document covers both services — incorporating the EU SCCs and the UK Addendum, and applying automatically without a separate signature |
Which module applies depends on whose data it is. For customer content we are your processor and they are our sub-processor, so Module Three applies. For the data we control ourselves — the content of a support conversation, say — we are the controller and Module Two applies. Each agreement above covers both modules, so no provider needs a separate instrument for each role.
Changes to this page
The updated version is posted here with a new effective date. We keep previous versions of this page — ask and we will send you the one in force on any date you name.
Where processing happens
The Service runs on Google Cloud in its europe-west regions, and your data is stored in Europe and does not leave it at rest.
Privacy Policy §12 is the authoritative description of the processing that reaches outside Europe and the safeguards that apply, and DPA section 10 carries what we commit to as your processor. This page names the providers on both sides of that line.
Providers that receive no customer content
These are the other providers in the picture. None of them is a sub-processor, because none receives your repository content, reports or task context — so none appears in the table above and none carries the 30 days’ notice. We are the controller for what they handle, and the Privacy Policy covers it.
- GitHub and GitLab — your repository hosting, not a provider of ours. We work inside the access you grant, on systems you control, which is why they are integrations rather than sub-processors. See GitHub App Permissions and GitLab Access.
- Freemius Inc — the seller. It takes card payments, determines and remits tax, issues receipts, and processes the refunds we issue, and it receives billing contact details, billing address and country, any tax registration number, card details and transaction records directly from you. Its role is split — our processor under its agreement with us, a controller for its own purposes as the seller — and Privacy Policy §1 sets out both halves.
- Google Sign-In — account identity. It provides the account identifier, email address, name and profile picture URL when you create or use an account.
- Calendly — demo booking, collecting what you enter on the booking page. Processed in the United States and the other locations its privacy notice describes.
- Google Analytics — on the public website and inside the application, each behind its own consent. Visit and usage data on the site, product milestones in the app. Google is a United States company. See the Cookie Policy.
- Cloudflare Web Analytics — a cookieless beacon on the public website only. It sets nothing in your browser; it is not behind the consent banner, and the Cookie Policy explains why and how to object.
Enji Guard