Sub-processors
{COMPANY_LEGAL_NAME} uses the third-party sub-processors listed below to provide {PRODUCT_NAME}. The list names the vendors actually in use as of the date at the foot of this page. Rows marked only when enabled describe an optional feature: that sub-processor receives nothing at all unless the feature is switched on for your workspace.
Processing your workspace data
These handle the customer data you import, or the infrastructure it runs on.
| Sub-processor | Purpose | Data processed | Region(s) |
|---|---|---|---|
| Vercel | Application hosting and content delivery for the website and the admin app | All application data in transit; hosting infrastructure and edge cache only | United States and European Union edge locations |
| Convex | Application database and backend functions | All application data, including garage customer data | United States (US East). Transfers made under standard contractual clauses (see note below) |
| Resend | Transactional and campaign email delivery | Customer email addresses, message content | European Union region |
| Anthropic | Only when enabled. AI-assisted classification of MOT advisory text, triage of inbound customer replies, and drafting of suggested replies for staff to review | Vehicle facts, MOT advisory text, the body of an inbound message, and a customer's first name only. Never a customer's phone number or email address — these are removed before anything is sent (see note below). | {US — confirm region} |
| Twilio | Only when enabled. SMS delivery | Customer phone numbers, message content | {US / UK — confirm region} |
| Stripe | Billing and payment processing | Payment card details, billing contact info | {US / UK / EU — confirm per Stripe account config} |
Our own operations
These do not receive your imported customer data. They are listed because they process the business-contact details of the person who signs up, or because they carry our own correspondence and code, and a sub-processor list that only named the obvious ones would be less useful than one that named all of them.
| Sub-processor | Purpose | Data processed | Region(s) |
|---|---|---|---|
| Fastmail | Company mailboxes | Correspondence with you, including any personal data you choose to put in an email to us | European Union |
| Microsoft 365 or Gandi | Founder outreach mailbox | Business contact details of prospective customers and correspondence with them | {To be confirmed — the mailbox provider is not yet fixed} |
| Woodpecker.co S.A. | Outreach sequencing for our own business-to-business email | Business contact details of prospective customers (a company email address, and the content of our messages) | France (OVH) |
| DNSimple | DNS and domain registration | No customer personal data. DNS query metadata only | {US — confirm region} |
| GitHub | Source code hosting and continuous integration | Application source code. No customer personal data | United States |
Woodpecker offers a built-in mailbox warmup feature that routes mail through the Mailivery and Warmy pools. We do not use it, and those two are therefore not sub-processors of ours. The feature is switched off on our account; warmup is done by ordinary human correspondence from the mailbox itself. This is stated here because a reader who looks up Woodpecker will find those partners named in its own documentation.
Note on AI processing
Where AI assistance is used, the model provider operates under a commercial agreement with a no-training term: content submitted through the API is not used to train models. AI output is always a *suggestion* — a category or a draft message — that a member of garage staff reviews before it is acted on. No message is sent to a customer, and no price is calculated, on the basis of a model's output alone. Opt-out ("STOP") handling is performed entirely by deterministic code and never by a model.
Personal data is minimised before submission: phone numbers and email addresses are stripped and replaced with placeholders, and only a first name is included where a draft message needs one.
Note on international transfers
Our application database is hosted in the United States. Personal data you import is therefore transferred outside the United Kingdom, and that transfer is made under standard contractual clauses with the UK Addendum, as described in the Data Processing Agreement.
Changes to this list
We may add, remove, or replace sub-processors as the Service evolves. Where a change is material, we will give customers at least {14} days' notice (by email or in-app notice) before the new sub-processor begins processing personal data, in line with the notice period set out in our Data Processing Agreement. Customers may object to a new sub-processor on reasonable data protection grounds within that notice period, as set out in the DPA.
This page reflects the sub-processors in use as of the date below; it is not a permanent or exhaustive commitment to any single named vendor.
Last updated: {DATE}