# Sub-processors

_Last Updated: 12 October 2026_

A sub-processor is a third party that receives data on Teralo's behalf in order to run the service. This page names every one of them.

Teralo publishes the complete list rather than a representative sample. An incomplete list is worse than no list, because a reader who finds one omission has no reason to trust the rest of it.

## How to read this list

**Platform providers** receive data that an organisation puts into a project. If you are assessing Teralo as a vendor, these are the ones that matter.

**Website providers** receive data only about visitors to teralo.co. They never see project data. Before a visitor consents, the analytics and advertising providers receive only cookieless pings that carry no cookie identifier. Their cookies and advertising identifiers are set only if the visitor consents.

The **location** column says where the provider processes the data. Where a location is a provider's placement decision rather than a contractual commitment, the [Privacy Policy](/legal/privacy-policy) says so explicitly. Teralo does not describe a best-effort placement as data residency.

## Notification and objection

Teralo notifies customers before a new sub-processor starts receiving data: it updates this page, changes the date below, and tells each customer through the Web Platform or by email, at least 30 days before the new provider begins processing Customer Material. Where a provider has to be replaced urgently to keep the service running or secure, the notice may be shorter, and the right to object runs from the date of the notice.

A customer may object to a new sub-processor on reasonable data protection grounds, within 30 days of notification. Teralo will work with them to find an alternative, and where none is workable, the customer may terminate the affected part of the service without penalty for the remainder of the term and receive a refund of pre-paid fees for the unused portion. The binding form of this commitment is clause 5 of the [Data Processing Agreement](/legal/dpa).

Questions and objections go to support@teralo.co.

## The list

This list last changed on 12 October 2026.

### Platform providers

| Provider | Purpose | Data it receives | Location |
| --- | --- | --- | --- |
| Supabase | Managed Postgres database behind the application | All customer project records, account details, induction records and biometric templates | Australia (AWS ap-southeast-2, Sydney) |
| Cloudflare | Application hosting, R2 object storage for uploaded files, CDN, DNS, WAF, bot protection (Turnstile) and transactional email delivery | Every uploaded file, plus request metadata, cached static content and outbound email content | Object storage in Oceania, delivered over a global edge network |
| Stripe | Payment processing and subscription billing | Billing contact details and payment method data, captured by Stripe and never held by Teralo | United States, with global processing |
| Google Gemini | AI features in the product | Prompt content and the project context submitted with it, and generated responses | Google global infrastructure |
| PostHog | Product analytics, session replay of the web application with all on-screen text masked, and how AI features perform | Account identifiers (user ID, name and email address), product usage events, session replays that show a page's layout and interactions without its text, and measurements of each AI call (model, token counts, cost, latency, outcome) carrying no prompt or response content | United States (PostHog US Cloud) |
| Mapbox | Address geocoding for project and site locations | Project address strings submitted for lookup | United States (AWS) |
| CARTO | Basemap tiles for maps in the product | Map tile requests, which carry the requesting IP address | Global content delivery network |
| Twilio | SMS delivery for site messages, evacuation alerts, worker registration links and verification codes | Recipient mobile numbers and the text of each message | United States (Twilio default region), delivered to mobile networks |
| Microsoft 365 | Microsoft 365 for the web, where a user opens an Office file to edit it in the browser, and Microsoft Graph, which converts Word contract templates to PDF in Teralo's own Microsoft 365 tenant | The Office file being edited or converted, with its file name; a converted file is deleted from Teralo's tenant once its PDF is returned | Microsoft global infrastructure |
| Visual Crossing | Weather forecasts and history for project sites | The project's street address, city and state as entered on the project | Provider-operated infrastructure (the provider is based in the United States) |
| Sectigo | Trusted timestamp on completed e-signature documents | A cryptographic hash of the signed PDF, which cannot be reversed into the document, and nothing else | Provider-operated infrastructure |

### Website providers

| Provider | Purpose | Data it receives | Location |
| --- | --- | --- | --- |
| Google Analytics | Website analytics on teralo.co | Website usage events. Before a visitor consents Google receives only cookieless pings with no cookie identifier; cookies and advertising identifiers are set only on consent | Google global infrastructure |
| Google Ads | Advertising and remarketing for teralo.co | Website conversion events and advertising identifiers. Cookies and advertising identifiers are set only on consent | Google global infrastructure |
| Umami | Cookieless website analytics on teralo.co | Aggregated page view events, with no cookies and no personal identifiers | United States and European Union (Umami Cloud) |


## Services a person connects or signs in with

These are not Teralo's sub-processors, because each receives data at the instruction of the person or organisation that connects it, under their own account with that service, and not on Teralo's behalf.

- **Sign-in.** A person who signs in with Google, Microsoft or Apple has that provider confirm their identity to Teralo, and the provider sees that they signed in.
- **Accounting systems and business registers.** An organisation that connects Xero, MYOB or QuickBooks sends the records it chooses to its own account there. A company number entered in the Web Platform is looked up in the Australian Business Register, the New Zealand Business Register or UK Companies House, according to the organisation's country.
- **AI assistants.** A person who connects an AI assistant such as Claude or ChatGPT to their Teralo account lets that assistant request the records their permissions allow. Those records are then handled under the person's own terms with the assistant's provider.
- **Embedded content.** Videos from YouTube or Vimeo and weather maps from Windy load directly from those services when a page that carries them is open.

## Related documents

The [Privacy Policy](/legal/privacy-policy) covers what Teralo collects and in what capacity. The [Security](/legal/security) page covers where data rests and how it is protected. The [AI Product Terms](/legal/ai-product-terms) cover the handling of AI prompts specifically.