Last updated: 27 May 2026
This page lists the subprocessors that Smart Segments Pty. Ltd. (“Smart Segments”) engages to process Customer Data on behalf of its customers, in connection with the Smart Segments software-as-a-service products. It supplements Annex III of the Smart Segments Data Processing Addendum (the “DPA”) and is incorporated into the DPA by reference.
Current subprocessors
| Subprocessor | Entity | Purpose | Location | Transfer mechanism |
|---|---|---|---|---|
| Google Cloud | Google Cloud EMEA Limited (for EU customers); Google LLC and affiliates (for other customers) | Cloud infrastructure hosting all Smart Segments services, including Firestore, BigQuery, Cloud Run, Cloud Functions, App Engine, Pub/Sub, Cloud Storage, Cloud Logging, and Firebase Authentication (used to authenticate Customer staff users to the Smart Segments application). | EU regions (europe-west1 Belgium and europe-west4 Netherlands for BigQuery EU multi-region; europe-west1 for Firestore, Cloud Storage, Cloud Run, Cloud Functions, App Engine, Pub/Sub) for EEA customers. Other regions where applicable for non-EEA customers. | EU Standard Contractual Clauses (where applicable) as incorporated in Google Cloud’s data processing terms. |
| dbt Labs | dbt Labs, Inc. | SQL transformation orchestration on Customer’s data warehouse, used to operate analytics and reporting workloads on the Customer’s behalf. | United States | EU Standard Contractual Clauses as incorporated in dbt Labs’ data processing terms. |
| Anthropic | Anthropic, PBC | Large language model service (Claude, Commercial / Team tier) used by authorised Smart Segments personnel under Anthropic’s Commercial Terms and Data Processing Addendum, to assist with the investigation, debugging, and analysis of Customer-reported issues. Inputs and outputs are not used to train Anthropic’s models. Used only on the minimum Customer Data necessary to resolve the relevant issue. | United States | EU Standard Contractual Clauses as incorporated in Anthropic’s Commercial DPA. |
Notice of changes
Smart Segments will give customers at least 30 days’ prior notice of the addition or replacement of a subprocessor by updating this page. Customers may subscribe to email notifications of changes by emailing jeroen@smartsegments.ai with the subject line “Subprocessor change notifications — subscribe” and the email address(es) to be notified.
If a customer has a reasonable, data-protection-related objection to a new subprocessor, the objection process is set out in Section 5.4 of the DPA.
What is not a subprocessor
For the avoidance of doubt, the following are not subprocessors of Smart Segments. They receive Customer Data because the customer has chosen to connect them, on the customer’s own contractual terms with the relevant provider:
- Marketing, CRM, engagement, and customer feedback platforms (for example Mailchimp, Klaviyo, Salesforce Marketing Cloud, HubSpot, Brevo, AskNicely).
- Point-of-sale, accounting, invoicing, and fiscal compliance systems (for example Vendus, Xero, NetSuite, QuickBooks Online).
- Other customer-chosen operational or reporting systems (for example workforce management systems such as Deputy, business intelligence platforms, customer support systems).
- Meta and Google (and their respective advertising platforms), which receive Customer Data via the optional Conversion Tracking Integration as independent controllers, or, depending on the configured feature, as joint controllers with the customer.
- Large language models, AI services, or other tools that the customer connects to its own data through the Smart Segments Model Context Protocol (MCP) endpoint or similar customer-configurable integrations.
A non-binding list of supported customer-configurable integrations is published at smartsegments.ai/integrations.
Questions
For questions about this list or any of the entities above, please contact jeroen@smartsegments.ai.
