Legal
Data Processing Agreement
How we handle your customers' personal data on your behalf. Last updated 20 November 2026.
1. Parties and scope
This Data Processing Agreement (“DPA”) forms part of the Terms of Service between the business that creates a Detoximex workspace (the “Controller”) and Detoximex Artificial Intelligence Development Services, a sole establishment licensed in Abu Dhabi under commercial licence CN-6818254 (the “Processor”). It applies automatically to all personal data the Processor handles on the Controller's behalf when operating the service. No separate signature is needed.
2. Roles
The Controller decides why and how its end customers' personal data (people who message the Controller through a connected channel) is processed. The Processor processes that data only on the Controller's documented instructions.
For the Controller's own account data (names, business email addresses, sign-in records, billing identifiers) the Processor acts as an independent controller, as described in the Privacy Policy.
Where the Controller is established in the United Arab Emirates, Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data applies, and “controller” and “processor” have the meaning given there.
3. Instructions
The Controller's instructions are the Terms of Service, the configuration it sets in its workspace (agent rules, working hours, staff, policies, integrations and usage controls), and any other reasonable and lawful written instruction. The Processor will tell the Controller if it believes an instruction breaks data protection law, and may pause that instruction until it is confirmed or withdrawn.
4. What is processed
- Subject matter: operating an AI assistant on the Controller's messaging channels.
- Duration: the subscription term, plus the deletion period in section 11.
- Purposes: answering and qualifying enquiries, answering from the Controller's approved documents, booking appointments, updating a connected CRM, alerting the Controller's staff, measuring quality and cost, and billing.
- People concerned: the Controller's customers and prospects, and the Controller's staff.
- Data: phone number, profile name, message content, details given in conversation, calculated lead score, appointment details and CRM identifiers; for staff, name, phone number, email and calendar identifier.
- Special categories: none by design. The Controller must not place health data, government identification, payment card numbers or passwords into the service (Terms, section 6).
5. Confidentiality
Everyone with access to the Controller's personal data is bound by confidentiality. Today that is the Processor's founder; the same duty binds any employee or contractor added later.
6. Security
- Each workspace's data is isolated in the database itself: every record carries a workspace identifier, and database rules limit every browser request to the caller's own workspace. Automated server processes add an explicit workspace check to every change, and an automated test rejects any that does not.
- Browsers never receive privileged credentials.
- Access tokens for Google, HubSpot and Meta are encrypted at rest (AES-256-GCM) and never sent to the browser.
- All connections use TLS.
- Customer messages and uploaded documents are treated as data, not instructions: text inside them cannot change the agent's role, reveal its configuration, or trigger actions.
- AI runs, configuration and connection changes, billing events, and data exports and deletions are recorded in an audit trail.
- Access to production systems is limited to the founder, with no shared accounts.
- Detoximex holds no third-party security certification and does not claim one. More detail is on the security page.
7. Sub-processors
The Controller gives general authorisation to the sub-processors listed in section 13. The Processor will email the account owner at least 30 days before adding or replacing one. The Controller may object on reasonable data protection grounds within that period; if the objection cannot be resolved, the Controller may end the affected service without penalty. The Processor remains responsible for its sub-processors' performance.
8. Requests from individuals
The Processor will pass to the Controller, within 5 business days, any request it receives from a person about their data, and will help the Controller respond, including through the export and deletion tools in workspace settings.
9. Assistance
The Processor will reasonably assist the Controller with security, breach notification, data protection impact assessments and dealings with a supervisory authority, taking into account the nature of the processing.
10. Personal data breaches
The Processor will notify the Controller without undue delay, and in any case within 72 hours of becoming aware, of a personal data breach affecting the Controller's data. The notice will include the information available at the time, with updates as more becomes known.
11. Deletion and return
When the service ends, the Controller can export its workspace data from Settings for 30 days. After that the Processor deletes the workspace's personal data, except where the law requires it to be kept. Copies held by sub-processors are deleted under each sub-processor's own retention terms.
12. Audit
The Processor will make available the information reasonably needed to show it complies with this DPA. Once a year, on 30 days' notice and at the Controller's cost, the Controller or an independent auditor bound by confidentiality may audit that compliance.
13. Sub-processors and where they process data
Model processing by OpenAI takes place in the United States, and the application database is in Japan. Data therefore leaves the Controller's country; each transfer relies on the sub-processor's own data processing terms and safeguards.
- Supabase, Inc.: Application database, authentication and server functions. Data: All workspace data, with integration tokens encrypted Where: Tokyo, Japan (AWS ap-northeast-1).
- OpenAI, L.L.C.: Language model replies, retrieval embeddings and quality checks. Data: The current message, a bounded conversation context, retrieved knowledge passages and agent instructions. API data is not used to train OpenAI's models. Where: United States.
- Meta Platforms, Inc.: WhatsApp Business messaging. Data: Phone numbers, message content, delivery statuses, template messages Where: Meta's global infrastructure.
- n8n GmbH (n8n Cloud): Workflow execution between the channel, the model, the database and connected providers. Data: The data that passes through a workflow run, and its execution log Where: European Union (Germany).
- Paddle.com Market Ltd.: Merchant of record: checkout, subscriptions, tax and payment. Data: Account owner name, email, billing address and transactions. Card data is handled by Paddle only. Where: United Kingdom and European Union.
- Vercel, Inc.: Hosting of the website and application. Data: Request logs (IP address, browser, address visited) Where: Global edge network.
- Google LLC: Calendar availability and bookings, only if a workspace connects Google Calendar. Data: Free and busy times, the appointments Detoximex creates Where: Google's global infrastructure.
- HubSpot, Inc.: CRM updates, only if a workspace connects HubSpot. Data: Lead name, phone, email, qualification fields, deal stage Where: United States, or the EU if the customer's HubSpot account is hosted there.
- Resend, Inc.: Transactional email. Data: Account owner email address and the notice sent Where: United States.
14. Liability, law and term
Liability under this DPA is subject to the limitation in the Terms of Service. This DPA is governed by the same law and courts as the Terms of Service, and applies for as long as the Processor processes personal data on the Controller's behalf.
