Sub-processors, dyniq.ai
Last updated: 13 November 2026
When a store installs the Dyniq app from Shopify, Dyniq is the processor of the data of the store's customers. These services process that data for Dyniq. The Privacy Policy says what we use the data for. The data processing agreement is published at dyniq.ai/legal/merchant-dpa.
Supabase
What it does. Database.
Customer data it receives. The data we store for a store: conversations, orders, hand-offs and settings.
Where. Ireland, EU.
Cloudflare
What it does. Runs the Dyniq services, the queues for order sync and the bot check (Turnstile).
Customer data it receives. Request data in transit and in memory: chat text, order data during sync and the IP address of the customer.
Where. Cloudflare network.
Anthropic
What it does. AI model that writes the reply.
Customer data it receives. The masked message, earlier messages of the chat, the store policies and pages, and the result of a verified order lookup, including the first name. Never the email address.
Where. USA.
TypeSafe (Jev)
What it does. Routes the question and checks the reply.
Customer data it receives. To route: the store name and up to 4 masked customer messages, with no order data. To check the reply: the draft reply, the masked customer messages and the evidence the reply relies on, without the first name and the gift message.
Where. USA.
Resend
What it does. Email delivery.
Customer data it receives. The hand-off email to the store (the last 6 messages of the chat and the contact address the customer gave), the store's answer emailed to the customer at the address the customer gave, and the data request link email.
Where. Sends from Ireland, EU. Account data in the USA.
Twilio
What it does. SMS and WhatsApp alerts to the merchant.
Customer data it receives. The mobile number of the merchant, the alert text and the answer the merchant types in WhatsApp. When the merchant taps "Reply here", the message also shows the case summary and the last 3 customer messages, with email addresses and card numbers masked, and phone numbers that start with +, 0 or a bracket. A name, a street address or an order number in the customer's own words is not masked.
Where. USA.
Contabo GmbH
What it does. Hosting of our own Langfuse server for quality traces.
Customer data it receives. Salted hash prefixes of the chat and the visitor, message length, cost, outcome and tool names. No message text, no tool result and no first name.
Where. Germany, EU.
Slack
What it does. Internal alerts to Dyniq.
Customer data it receives. Fixed text, reason codes and store ids. No customer text.
Where. USA.
Meta Platforms Ireland Limited is not a sub-processor: it never receives store customer data. It receives data only from our own pages: the waitlist page dyniq.ai/telefoon and the free trial pages (dyniq.ai/pilot and the pages around it), after the visitor clicks "Accepteren" or "Accept all", or clicks "Save choices" with the Marketing switch on, as described in our Privacy Policy.
What reaches the model provider
The first name reaches the model provider only after a verified order lookup, as part of the lookup result. It does not reach the third-party reply check or the quality traces. The email address is never sent to the model provider.
What reaches Slack
Alerts hold fixed English text, reason codes and store ids. A hand-off on a real store goes by email to the store, and Slack gets no customer text. An automated test checks that no customer text reaches a Slack message.
Transfers outside the EU
If a provider is outside the EU/EEA, we rely on a transfer mechanism such as the EU-US Data Privacy Framework or standard contractual clauses. Email support@dyniq.ai for a copy of the safeguards.