Data processing agreement for merchants
Version: draft-2026-11-03
This agreement is between the merchant (the controller of its customers' data) and Dyniq (the processor). It follows Article 28 of the GDPR. The headings match the data protection requirements for protected customer data in the Shopify app review.
Parties:
- Merchant: the store that installs the Dyniq app, named in the install record.
- Dyniq, KvK 77272471, Ceresstraat 13, 4811 CA Breda, the Netherlands. Contact: support@dyniq.ai. Dyniq® is a trademark registered in the Benelux (No. 1541227).
Dyniq runs an AI support chat on the merchant's store. Dyniq processes customer data only for that chat, on the merchant's written instructions. For its own data (website, trial form, outreach) Dyniq is a controller, and the privacy notice at dyniq.ai/privacy applies.
1. Purpose and minimum data
Purpose: answer customer questions in the store chat, look up one order for the customer who gives its number and matching email, and hand the customer to a person at the store.
Dyniq reads only this:
- Order data: order number, date, status, country, lines, amounts, refunds, payment method name, tracking.
- The customer's first name, taken from the billing address, else the shipping address.
- The customer's email address, stored only as a keyed hash (HMAC-SHA256). It is used to match an order, and it is not stored in readable form.
- Chat messages. Email addresses, card-like numbers and phone numbers in a message are masked before the message is stored or sent.
- The store's policies and public pages.
Dyniq never reads: the last name, the phone number, the street address, payment card data, the gift message, the discount code, order notes, or the Shopify customer object.
2. Telling merchants what is processed and why
| Data | Why | Where kept |
|---|---|---|
| Chat messages and replies | Answer the customer | Supabase, Ireland |
| Order data and first name | Answer questions about one order | Supabase, Ireland |
| Keyed email | Match the order to the customer | Supabase, Ireland |
| Email address typed for a hand-off | The store team can reply | Supabase, Ireland, with the hand-off |
| Salted hashes of IP address and visitor, counters | Limit abuse | Supabase, Ireland |
| Access log (time, store, accessor, order id; no email, no name) | Show who read an order | Supabase, Ireland |
The services that receive this data are listed in sub-processors.md. The privacy notice at dyniq.ai/privacy gives the same information to customers.
3. Limiting use to that purpose
Dyniq uses customer data only for the purpose in section 1, and for security: rate limits, spend caps and abuse checks. Dyniq does not use it for any other purpose. The first name reaches the model provider after a verified order lookup. It does not reach the third-party reply check or the quality traces.
4. Merchant agreement
This document is the agreement. Dyniq will show it in the app for the merchant to accept before the store goes live. Dyniq gives the merchant the information needed to show that Dyniq follows it.
Staff and contractors of Dyniq are bound by confidentiality. This agreement is governed by the law of the Netherlands. The courts of the district of Dyniq's seat (Breda) have jurisdiction.
5. Consent and no sale of data
Dyniq does not sell customer data. Dyniq does not train models on customer data. Dyniq will agree with each model provider that customer data is not used to train its models, where the provider's terms allow it.
6. Automated decisions and reaching a person
The chat answers with an AI model. It cannot issue refunds, cancel or change orders, or create discount codes. Return eligibility comes from the store's policy and is computed by code, not by the model. A customer can ask for a person at any time. The chat then hands the customer to the store team by email. The team replies by email.
7. Retention
| Data | Kept |
|---|---|
| Conversations, messages, hand-offs, feedback | 30 days after the last message |
| Orders and order lines | 12 months after the order date (longer only while a live chat refers to the order, until 30 days after its last message) |
| Access log | 12 months |
| Quality traces | 30 days |
| Data export copy | 7 days |
| Shopify webhook ids | 30 days |
| Shopify access tokens | Deleted when the app is uninstalled and Shopify confirms the access is removed |
| All other data of the shop | Deleted when Shopify sends shop/redact |
A deletion job runs each night. A customer can delete a chat at once with the "Delete my chat" button.
8. Privacy webhooks (GDPR webhooks)
Dyniq handles the three mandatory privacy webhooks. Each request is checked with the Shopify HMAC signature first. A request with a wrong signature or an unexpected body is refused. Each webhook writes one audit row with counts only, and no email, shop host or customer number.
customers/redact: Dyniq deletes the orders of that customer (matched by the keyed email), their order lines, the conversations linked to that customer with their messages, hand-offs, feedback and chat memory, and any pending data export. Dyniq does this when it receives the request.shop/redact: Dyniq deletes every record of the shop: orders, conversations, hand-offs, policies, pages, settings, tokens and the store record. Dyniq does this when it receives the request. If the shop has installed the app again and its access still works, Dyniq keeps the shop. If Dyniq cannot check this, it answers with an error and Shopify sends the request again.customers/data_request: Dyniq stores a copy of the customer's orders, linked conversations and hand-offs behind a link and emails the link to the merchant's hand-off address. The link works for 7 days. The copy holds the first name and not the email address. Dyniq sends nothing to the customer.
9. Encryption in transit
Dyniq's services and the Shopify webhooks use HTTPS.
10. Encryption at rest
Shopify access tokens are encrypted with AES-256-GCM before they are stored. Dyniq will confirm in writing with each provider that stores customer data that the provider encrypts it at rest, before the first store goes live.
11. Backups
Dyniq will keep any backup of customer data in encrypted form and under the retention periods in section 7.
12. Test and production data
Dyniq's demo store and its automated tests use fictional data. The demo store and real stores are in the same database. Row level security separates them by store id.
13. Data loss prevention
- Row level security limits each database role to the store of the request. The chat, the Shopify Worker and the order sync use separate roles. The chat role has no access to the token table.
- Logs hide Shopify tokens and the app secret.
- Secrets live in Worker secrets and are scanned for in the repository (gitleaks) on each change.
- Masking, rate limits, a daily spend cap and a kill switch limit misuse.
- The quality traces hold no message text.
14. Staff access
One person runs Dyniq and is the only person with access to production systems.
15. Access logging
Each read of a customer's order data writes one row to the access log: time, store, accessor, database role and order id. The log holds no email and no name. It is kept 12 months and deleted with the store at shop/redact.
16. Incident response and breach notice
Dyniq follows the incident response policy in incident-response-policy.md. Dyniq will tell the merchant of a personal data breach without undue delay and within 48 hours. The notice says what happened, which data and customers are affected, the likely effect, and what Dyniq did. The merchant decides whether to tell its authority and its customers. Dyniq helps with the facts.
Sub-processors
The sub-processors are in sub-processors.md. Dyniq will tell the merchant by email 30 days before a new sub-processor receives customer data. The merchant can object in that time. If the parties cannot agree, the merchant can stop using the service. Dyniq uses a provider outside the EU or EEA only under standard contractual clauses (Commission Decision 2021/914) or the EU-US Data Privacy Framework where the provider is certified.
Help with customer requests
Dyniq helps the merchant answer a customer request for access or deletion with the webhooks in section 8. Dyniq forwards a request that it gets directly from a customer to the merchant. Dyniq will answer the merchant within 5 working days. At the end of the agreement the merchant can ask for deletion at support@dyniq.ai, and Dyniq will confirm by email within 30 days.
Contact: support@dyniq.ai. Dyniq has no data protection officer.