Sub-processors
Last updated: October 27, 2026
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.
| Region | Workspaces | Application, database, backups, secrets and logs | Stored files |
|---|---|---|---|
| European Union | Workspaces hosted in this region (today, all workspaces) | Google Cloud, Madrid, Spain (europe-southwest1): application, database, backups, secrets and logs | Cloudflare 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.
| Provider | Purpose | Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Google Cloud (Google Cloud EMEA Ltd / Google LLC) | Application hosting, database, backups, secrets, logs, PDF report rendering | All customer workspace data | The 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; DNS | Uploaded files; IP address and request metadata of web visitors | Files: the workspace’s hosting region (EU: R2 EU jurisdiction). Delivery: global edge network | Files stored in the hosting region. Cloudflare data processing terms, including SCCs |
| Resend | Transactional 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 Mail | Recipient 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 States | Resend data processing terms, including SCCs |
| Twilio Inc. (optional) | WhatsApp messages with each technician’s daily job link, only when the office sends links by WhatsApp | Technician phone number and first name; the job-sheet link. Messages contain no end-customer data | United States, for all workspaces | Twilio 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 Twilio | Technician phone number and the message (first name and job-sheet link) | United States and global WhatsApp infrastructure, for all workspaces | WhatsApp 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 on | The request and the workspace data the agent needs to carry it out. Prompts and responses are not retained | United States | Cerebras 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 replies | Whatever the sender includes in a support message | Global, for all workspaces | Google 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.
| Provider | Purpose | Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Google Maps Platform (Google LLC) | Geocoding addresses, travel times and route planning | Site, depot and technician start/end addresses, coordinates, working hours and visit time windows (no names) | Global | Google 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 account | Name, email address and profile picture | Global | Google’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.
| Provider | Purpose | Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Stripe, Inc. | Card payments for self-serve plans | Name, email, billing details, payment card data (handled by Stripe, not stored by Spatio) | United States | SCCs, 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.