Draft: not yet in force
This document is a draft waiting for legal review. Text in [brackets] is still to be filled in. This notice only shows outside production.
These are the companies that handle personal data for Anterra. "Platform" means they handle data about Anterra's own users (you). "Apps" means they also handle data inside the apps you build, for which we are your processor under our Data Processing Agreement.
We will tell workspace owners at least 30 days before we add or replace a sub-processor that handles app data. You can object, as the Data Processing Agreement explains.
Sub-processors
| Sub-processor | What they do | Personal data | Where | Transfer safeguard | Covers | When used |
|---|---|---|---|---|---|---|
| Google Cloud (Google Cloud EMEA Ltd; Google LLC) | Hosting, databases, file storage, backups, logs, secrets, build sandboxes | All data we hold, including app data | London, UK (europe-west2); backups in the UK | UK region. Google support may access data from other countries under Google's Cloud Data Processing Addendum (IDTA / UK Addendum) | Platform, Apps | Always |
| OpenAI (OpenAI, L.L.C.; OpenAI Ireland Ltd) | Main AI models: planning, building, checking and chat; image generation; apps' AI features | Descriptions, chat messages, code, attached files, and what apps send to their AI features | United States | UK Addendum to the EU standard contractual clauses in OpenAI's data processing addendum; requests sent with storage off | Platform, Apps | Always |
| Anthropic (Anthropic, PBC; Anthropic Ireland Ltd) | Backup AI models when OpenAI is unavailable | As for OpenAI, only during an OpenAI outage | United States | UK Addendum in Anthropic's data processing addendum | Platform, Apps | When OpenAI is unavailable |
| Google Vertex AI (Gemini, embeddings) | Apps' AI features that use Google models: the "lite" and "long" tiers, and search embeddings | What apps send to those AI features | Global endpoint; embeddings in the United States (us-central1) | Google's Cloud Data Processing Addendum (IDTA / UK Addendum) | Apps | When an app uses these features |
| Stripe (Stripe Payments Europe Ltd; Stripe, Inc.) | Payments for Anterra plans, credits and add-ons; fraud checks | Billing name, email, address, VAT number, card details (Stripe only), payment history | Ireland and United States | UK–US data bridge; UK Addendum | Platform | Always |
| Resend (Plus Five Five, Inc.) | Sending email: sign-in links, receipts, notifications, and apps' emails from the shared sending domain | Email addresses, names, email content | United States | UK Addendum to the EU standard contractual clauses | Platform, Apps | Always |
| Twilio (Twilio Inc.) | Text-message codes to confirm a phone number when we need an extra check | Phone number, message status | United States | Twilio's binding corporate rules (approved by the ICO) | Platform | If switched on |
| Cloudflare (Cloudflare, Inc.) | Turnstile check that a sign-up is made by a person, not a bot | IP address, browser signals | Global network | UK–US data bridge; UK Addendum | Platform | If switched on |
| Weave ([Company that runs Weave]) | Version history: stores every version of your apps' code and who made each change | Code, change history, names and email addresses of the people who made changes | [Where Weave stores data] | [Weave transfer safeguard] | Platform, Apps | Always |
| FunctionalWeave ([Company that runs FunctionalWeave]) | Verified building blocks (sign-in, payments, email and others) that apps use, and their registry | Workspace and app identifiers; data that apps pass through hosted building blocks | [Where FunctionalWeave stores data] | [FunctionalWeave transfer safeguard] | Apps | When an app uses a hosted building block |
Services you choose to connect
These companies are not our sub-processors. When you or your app connect to them, they handle data under their own terms with you:
- Google and GitHub, if you sign in with them;
- Google Sheets, Airtable and other data connectors you add to an app;
- your own Stripe account, if your app takes payments (Stripe Connect);
- Slack, webhooks and other channels you set up for notifications.
Services that don't receive personal data
We also use some services that don't receive personal data. For example, to check whether a new password has appeared in a known data breach, we send only the first five characters of a scrambled code made from it ("k-anonymity", Have I Been Pwned). We also look up software security advisories (OSV.dev) and download open-source packages (npm).
[Company name] · company number [Company number] · [Registered office address]