Decisioner Subprocessors
Last updated: 2026-10-18
Operator: Lalettayin LTD. Questions: [email protected].
We give 30 days' notice before we add or replace a subprocessor (DPA §6).
| Subprocessor | Purpose | Customer personal data it receives | Location | Transfer safeguard |
|---|---|---|---|---|
| Google Cloud (Google Cloud EMEA Ltd. / Google LLC) | Hosting: Cloud Run, Cloud SQL (database), Secret Manager, Cloud Logging | All App data | EU, europe-west1 (Belgium) | Google Cloud Data Processing Addendum incl. SCCs |
| Google Vertex AI (Gemini), same Google Cloud contract | AI drafting of message variants from the merchant's own template text and brand voice; offline authoring of synthetic personas | None. Inputs are merchant-written text only; email addresses and phone numbers are removed before sending. Google does not use the data to train its models (Google Cloud terms) | EU multi-region eu | Google Cloud DPA incl. SCCs |
| Klaviyo, Inc. | Delivery of recovery emails — only when the merchant connects its own Klaviyo account | Email address, message content (subject, body, offer line, discount code, recovery link, decision reference); consent state lookup; time zone | US | Klaviyo DPA + SCCs. The merchant has its own contract with Klaviyo |
| PostHog Inc. (PostHog EU Cloud) | Product analytics, feature flags and error tracking of merchant staff use of the App, including masked session replay of App screens | None (no shopper personal data; staff usage only; admin URL tokens removed) | EU (Frankfurt) | PostHog DPA; SCCs for any access from outside the EU |
| TypeSafe (Jev decision model), TypeSafe AI, Inc. | Decision model that scores send/timing/variant/discount options | Pseudonymous banded features only. No store domain, customer ID, email, checkout token, name or other identifier. Real-store data only after the TypeSafe data-processing addendum is signed | US | TypeSafe data-processing addendum + SCCs (required before real-store data) |
| Supabase, Inc. / Supabase Pte. Ltd. | Pre-release staging database only | None from merchants — development-store test data only | EU, AWS eu-central-1 (Frankfurt) | Supabase DPA incl. SCCs. Removed from this list when staging moves to Google Cloud |
Training. No subprocessor may train or improve its own models with merchant or customer data. Google Vertex AI: excluded by the Google Cloud service terms. TypeSafe (Jev): inference only; the no-training commitment is part of the data-processing addendum that must be signed before real store data is sent. PostHog: staff usage analytics only, no model training on our data. Learning that Decisioner itself does is per store and only with that store's consent (Terms §8).
Tools you connect (not subprocessors)
When you connect one of these tools, or hand messages to your own Shopify Flow workflow, the tool is a destination you chose and your own processor (see DPA 6.5). Decisioner sends it only what is needed to deliver a message you approved. You hold the contract with the vendor.
| Tool | Channels | Data sent | Data region (vendor) |
|---|---|---|---|
| Klaviyo | email address, message properties | US | |
| Shopify Flow (your workflow) | email, SMS, WhatsApp | customer reference, message fields | Shopify |
| Omnisend | email, SMS | email or phone, event properties | EU |
| Twilio | SMS, WhatsApp, RCS | phone number, message body or template variables | US, or IE1/AU1 when chosen |
| Brevo | email, SMS, WhatsApp | email or phone, event properties | EU |
| Mailchimp | email (hashed in the URL), event properties | US | |
| ActiveCampaign | email, event and optional contact fields | US | |
| Customer.io | email, SMS | email (and phone for SMS), event data | US or EU (your choice) |
Tools your Shopify Flow workflow calls. Decisioner hands the message to your own Shopify Flow workflow, and your workflow (with your own credentials) calls the tool. These tools are destinations you chose and configure in Flow; they are not Decisioner subprocessors.
| Tool | Channels | Data sent by Decisioner | Data region (vendor) |
|---|---|---|---|
| Postscript | SMS (US/CA) | via your Shopify Flow workflow (Decisioner sends nothing to this tool) | US |
| Wati | via your Shopify Flow workflow (Decisioner sends nothing to this tool) | not documented |
SMS, WhatsApp and RCS tools stay unavailable until phone consent can be verified (Shopify protected customer data Level 2 "Phone").
Platform (not a subprocessor)
Shopify is the platform the merchant uses. The App reads store data from Shopify's Admin API, writes discount codes and App metafields to the merchant's store, and starts the merchant's Shopify Flow workflow. Shopify processes this data under its own terms with the merchant, so it is listed here for transparency, not as our subprocessor.
Change log
| Date | Change |
|---|---|
| 2026-10-18 | First published version |