[00]Subprocessors

Subprocessor register

The material service providers we use to run client systems, what each one is for, and what data it touches.

Version PUBLIC_2026_08_v1 · Effective 20 August 2026

Verification in progress

Some entries are marked “to verify”. We publish the supplier and its purpose, and confirm the registered legal name, processing location and transfer mechanism against the actual contract before stating them here.

ProviderPurposeData categoriesProcessing locationApplies to
Vercel
legal name to verify
Application hosting, edge delivery and deploymentClient Data in transit; request and security logsTo verifycore, pro, max, enterprise, website
Supabase
legal name to verify
Managed database, authentication and file storageClient Data; authentication records; stored filesTo verifycore, pro, max, enterprise
Stripe
legal name to verify
Payment processing and connected-account integrationpayment and transaction metadata; billing contact details; card data handled by the processor, never by NullshiftTo verifycore, pro, max, enterprise
GoCardless
legal name to verify
Direct Debit collection for recurring plansbank mandate details; payment metadataTo verifycore, pro, max, enterprise
Resend
legal name to verify
Transactional email deliveryemail address; message content and delivery metadataTo verifypro, max, enterprise, website
Anthropic
legal name to verify
AI model inference for AI Features and internal agent workflowsconfigured AI Inputs and OutputsTo verifypro, max, enterprise
Xero
legal name to verify
Accounting records and invoice mirroringbilling contact details; invoice and payment recordsTo verifycore, pro, max, enterprise

Where we add or replace a material subprocessor that processes Client Data, we give affected clients at least 14 days' notice before the change takes effect, wherever practicable, and provide a route to object. Updating this page is not by itself contractual notice where the agreement requires direct notice.