Sub-processors

Last updated: October 27, 2026

The third parties Spatio uses to provide the Service. Where Spatio processes data for a business customer, the providers in the first table are its sub-processors under the customer’s data processing agreement.

Hosting by region

Each workspace’s application data, database, backups and stored files are hosted in one region. The regions available today are listed below; new regions are added here before they host customer data.

RegionWorkspacesApplication, database, backups, secrets and logsStored files
European UnionWorkspaces hosted in this region (today, all workspaces)Google Cloud, Madrid, Spain (europe-southwest1): application, database, backups, secrets and logsCloudflare R2 bucket with EU jurisdiction: files stay in the EU (currently placed in Eastern Europe)

Sub-processors of customer workspace data

These providers process customer workspace data for all customers. Where a provider’s location depends on the workspace’s hosting region, the row says so. Providers outside the hosting region receive only the data listed for them.

ProviderPurposeDataLocationTransfer safeguard
Google Cloud (Google Cloud EMEA Ltd / Google LLC)Application hosting, database, backups, secrets, logs, PDF report renderingAll customer workspace dataThe workspace’s hosting region. EU: Madrid, Spain (europe-southwest1)Stored in the hosting region. Google Cloud data processing terms, including SCCs for any access from outside the EEA
Cloudflare, Inc.File storage (photos, signatures, report PDFs, ERP files); delivery of the web app and technician job sheet; DNSUploaded files; IP address and request metadata of web visitorsFiles: the workspace’s hosting region (EU: R2 EU jurisdiction). Delivery: global edge networkFiles stored in the hosting region. Cloudflare data processing terms, including SCCs
ResendTransactional email: sign-in codes, invitations, technician job links (when the office emails them), service reports to the customer’s own clients, and email sent from Spatio MailRecipient name and email address; email content and attachments (for example the service report PDF)Sent from Ireland (eu-west-1) for all workspaces; company in the United StatesResend data processing terms, including SCCs
Twilio Inc. (optional)WhatsApp messages with each technician’s daily job link, only when the office sends links by WhatsAppTechnician phone number and first name; the job-sheet link. Messages contain no end-customer dataUnited States, for all workspacesTwilio Data Protection Addendum: EU-US Data Privacy Framework and Binding Corporate Rules, with SCCs as a fallback
Meta Platforms, Inc. (WhatsApp, optional)Delivery of the WhatsApp messages sent through TwilioTechnician phone number and the message (first name and job-sheet link)United States and global WhatsApp infrastructure, for all workspacesWhatsApp Business terms, including the EU-US Data Privacy Framework and SCCs
Cerebras Systems Inc. (optional)AI model inference for the Spatio Agent, only in workspaces where the Spatio Agent is switched onThe request and the workspace data the agent needs to carry it out. Prompts and responses are not retainedUnited StatesCerebras Data Processing Agreement, including SCCs and the UK Addendum
Google LLC (Google Workspace)Support email: messages customers and users send to Spatio support, and Spatio’s repliesWhatever the sender includes in a support messageGlobal, for all workspacesGoogle Workspace data processing terms, including SCCs and the EU-US Data Privacy Framework

Independent controllers

These recipients receive some customer workspace data as independent controllers under their own terms, not as Spatio’s sub-processors. Spatio Field Ops uses Google Maps Platform to find addresses on the map, estimate travel times and plan routes; Google may use this data to provide and improve its own products under the Google Privacy Policy. Spatio sends addresses, map coordinates and time windows, never names or contact details. Users who choose Sign in with Google share their Google profile with Google. Business customers authorize these disclosures in their data processing agreement.

ProviderPurposeDataLocationTransfer safeguard
Google Maps Platform (Google LLC)Geocoding addresses, travel times and route planningSite, depot and technician start/end addresses, coordinates, working hours and visit time windows (no names)GlobalGoogle Maps Platform Terms and Google’s Controller-Controller Data Protection Terms
Google LLC (Sign in with Google)Sign-in for users who choose to sign in with their Google accountName, email address and profile pictureGlobalGoogle’s own terms with the user

Other service providers

These providers process data for which Spatio is the controller, such as payments for self-serve plans. They don’t receive customer workspace data.

ProviderPurposeDataLocationTransfer safeguard
Stripe, Inc.Card payments for self-serve plansName, email, billing details, payment card data (handled by Stripe, not stored by Spatio)United StatesSCCs, and the EU-US Data Privacy Framework where certified

AI agents in the desktop app

The Spatio Agent uses Cerebras, listed above, as a sub-processor. Separately, the desktop app can run AI coding agents (Claude Code by Anthropic, or Codex by OpenAI) that each user signs in to with their own Anthropic or OpenAI account. When a user asks one of these agents to work with workspace data, that data is sent to the provider the user chose, under that user’s agreement with them. Spatio does not engage Anthropic or OpenAI for this.

Customer systems

Integrations a customer connects, such as Sage 200, are the customer’s own systems. Data exchanged with them is under the customer’s control, and they are not Spatio sub-processors.

Changes

We update this page before a new sub-processor starts processing customer data. Business customers with a data processing agreement are notified in advance as set out in that agreement and may object. Questions: hello@spatio.app.