Sub-processors
Who else touches your data
The third parties we use to operate the platform, what each one receives, and why. Integrations that exist in our code but are not currently enabled are listed separately rather than omitted — so this page does not quietly become wrong the day one is switched on.
Last reviewed 25 October 2026 · Quarterly review · Owner: Fed Alcius
For how we make the underlying records checkable, see trust & security.
Active sub-processors
Anthropic
- Purpose
- AI analysis powering compliance and product features
- Data received
- Prompt content submitted for analysis
- Lawful basis
- Processor, under data processing terms
OpenAI
- Purpose
- AI analysis powering compliance and product features
- Data received
- Prompt content submitted for analysis
- Lawful basis
- Processor, under data processing terms
Stripe
- Purpose
- Payments and subscription billing
- Data received
- Billing identity — name, email, and payment details
- Lawful basis
- Necessary for performance of the contract
Resend
- Purpose
- Transactional email delivery, including AIUC-1 readiness-check results sent at the visitor’s request
- Data received
- Recipient email address and message content
- Lawful basis
- Necessary for performance of the contract
Slack
- Purpose
- Operational alerting to our engineering team, and follow-up on AIUC-1 readiness-check results when a visitor asks for them
- Data received
- Operational alerts, which include organization and actor identifiers. We disclose these as pseudonymous personal data rather than treating an identifier as anonymous. For the readiness check, and only when the visitor ticks the consent box: their email address and their answers.
- Lawful basis
- Legitimate interest in operating and monitoring the service; consent, for readiness-check results
Oracle Cloud Infrastructure
- Purpose
- Hosting for every service and the database
- Data received
- All customer data at rest
- Lawful basis
- Necessary for performance of the contract
Cloudflare
- Purpose
- Inbound traffic handling and TLS termination, and cookieless web analytics (Cloudflare Web Analytics)
- Data received
- Inbound request metadata, including IP addresses; page-view and page-performance data from visitors’ browsers, collected without cookies or other on-device storage
- Lawful basis
- Legitimate interest in securing and delivering the service, and in measuring how the site is used
GitHub
- Purpose
- Source control and continuous integration
- Data received
- No customer personal data
- Lawful basis
- Not applicable — no customer personal data is transferred
Integrated, not active
The code path exists but no credential is configured, so nothing is sent. They are listed because an integration that is one configuration change away from receiving data should not be invisible until the day it does.
Google (Gemini)
- Purpose
- AI analysis — integration present, not currently enabled
- Data received
- None today. No credential is configured, so no data is sent.
- Lawful basis
- Would be processor terms if enabled
SendGrid
- Purpose
- Email delivery — integration present, not currently enabled
- Data received
- None today. No credential is configured, so no data is sent.
- Lawful basis
- Would be processor terms if enabled
What this list is, and what it is not
It is an attestation with a named owner and a review date, supported by a mechanical cross-check of every outbound credential in our deployed environment. That cross-check bounds what we might have missed; it does not close it. Infrastructure providers need no credential and so cannot be found that way — they are here because the owner named them. If you need contractual assurance rather than a published page, ask us and we will put it in writing.
Authentication is handled by our own self-hosted identity service, so no third-party identity provider appears above.