Last updated: 6 October 2026
This Data Processing Agreement (“DPA”) governs how SORIONAI LTD processes personal data on behalf of merchants who use SorionAI, and forms part of the SorionAI Terms of Service.
The Merchant decides why and how its customers’ personal data is processed and acts as controller. SorionAI processes that data only to provide the service, on the Merchant’s behalf, and acts as processor. This DPA applies to all personal data of the Merchant’s customers, prospective customers and site visitors that SorionAI processes while providing the service (“Customer Personal Data”).
Applicable data protection law means the UK GDPR and the UK Data Protection Act 2018, the EU General Data Protection Regulation (EU) 2016/679 (“GDPR”), and any other data protection law that applies to the Merchant’s processing. Terms such as “controller”, “processor”, “personal data breach” and “data subject” have the meaning given in the GDPR.
If this DPA and the Terms of Service conflict on the protection of personal data, this DPA prevails.
SorionAI processes Customer Personal Data only to answer the Merchant’s customers on the Merchant’s channels and to help them place and track orders.
| Subject matter | An AI assistant that answers customer messages and handles orders for the Merchant |
|---|---|
| Nature of processing | Receiving, storing, analysing and replying to messages; creating draft and confirmed orders in the Merchant’s store; sending order confirmations and reminders |
| Purpose | Customer service, order taking and order follow-up for the Merchant |
| Data subjects | The Merchant’s customers, prospective customers and visitors who message the Merchant or place an order |
| Categories of personal data | Messaging platform identifiers (Instagram or Messenger user ID), display name, message content, order details (products, quantities, amounts), and, when the customer provides them to complete an order: name, phone number, email address and delivery address |
| Data received from Shopify | Order metadata (order ID, totals, line items, status, city and country) only. SorionAI does not read customer names, email addresses, phone numbers or street addresses through the Shopify Admin API |
| Special category data | None. The service is not designed to process special category data, and Merchants must not instruct it to |
| Duration | For the term of the Merchant’s subscription, then deletion as described in section 7 |
SorionAI commits to the obligations of a processor under Article 28 of the GDPR and the UK GDPR. In particular, SorionAI will:
customers/data_request, customers/redact and shop/redact webhooks.SorionAI does not sell Customer Personal Data, does not use it for its own marketing, and does not use it to train AI models offered to other customers.
The Merchant remains responsible for having a lawful basis for the processing, for informing its customers, and for collecting any consent the law requires, including consent to marketing messages.
The Merchant gives SorionAI a general authorisation to use the sub-processors below. SorionAI binds each of them to data protection terms that are at least as protective as this DPA, and stays responsible for their work.
| Sub-processor | Service | Data processed | Location |
|---|---|---|---|
| Supabase | Database, authentication, file storage | All Customer Personal Data | European Union (Frankfurt, Germany) |
| Contabo | Application server hosting | All Customer Personal Data in transit through the application | European Union |
| DeepInfra | AI language model inference | Message content and order context sent to generate replies | United States |
| Upstash | Cache and rate limiting | Technical identifiers and short-lived session data | European Union (Ireland) |
| Resend | Transactional email | Email address and email content, when an email is sent | United States |
SorionAI will tell Merchants about any new or replacement sub-processor at least 30 days before it starts processing Customer Personal Data, by email or a notice in the dashboard. A Merchant may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, the Merchant may terminate the affected service.
The messaging and commerce platforms the Merchant connects (Meta for Instagram and Messenger, Shopify) and the payment provider for SorionAI subscriptions (Paddle, or Shopify Billing) are chosen by the Merchant or act as independent controllers. They are not SorionAI sub-processors.
Customer Personal Data is stored in the European Union. Some processing happens outside the UK and the European Economic Area:
SorionAI will not transfer Customer Personal Data to any other country without an appropriate safeguard under applicable data protection law.
SorionAI maintains the following technical and organisational measures, and may improve them over time without lowering the overall level of protection.
| Area | Measure |
|---|---|
| Encryption in transit | All traffic between customers, merchants, SorionAI and its sub-processors uses TLS |
| Encryption at rest | Database storage is encrypted at rest by Supabase (AES-256); platform access tokens (Meta, Shopify) are additionally encrypted by the application before storage |
| Tenant isolation | Each Merchant’s data is isolated by row-level security policies in the database |
| Access control | Production access is limited to SorionAI’s director, on a least-privilege basis, with strong passwords and multi-factor authentication on administrative accounts |
| Webhook integrity | Incoming Shopify and Meta webhooks are verified by signature (HMAC) before processing |
| Abuse protection | Rate limiting on public endpoints |
| Backups | Automated daily database backups by Supabase, encrypted at rest |
| Logging | Application and administrative actions are logged; logs are kept for a limited period (section 7) |
| Data minimisation | Only the data needed for the service is collected; protected customer fields are not read from the Shopify Admin API |
| Incident response | A documented procedure to contain, assess and notify personal data breaches (section 8) |
SorionAI keeps Customer Personal Data only as long as the service needs it, then deletes or anonymises it automatically.
| Data | Kept for | Then |
|---|---|---|
| Raw webhook payloads (Shopify, Meta) and webhook logs | 30 days | Deleted |
| AI request logs | 90 days | Deleted |
| Automated flow logs (order confirmations, reminders) | 90 days | Customer identifiers and message text removed |
| Website chat widget conversations | 90 days | Deleted |
| Audit logs | 90 days | Deleted |
| Instagram and Messenger conversations and messages | 12 months after the last message | Deleted |
| Customer records | 12 months after the last activity and the last order | Name, email and phone removed |
| Orders | 24 months after the order | Name, email, phone and street address removed; amounts, products, city and country kept for the Merchant’s statistics |
At the end of the service:
shop/redact request.customers/redact request.Backups expire on the backup provider’s rotation schedule and are not restored except to recover the service.
SorionAI will notify the Merchant without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data.
The notice will describe, as far as known at the time: what happened, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. SorionAI will send further information as it becomes available, take reasonable steps to contain the breach, and help the Merchant meet its own obligations to notify supervisory authorities and data subjects.
Notifying a breach is not an admission of fault or liability.