Data Processing Agreement
DRAFT — DO NOT PUBLISH WITHOUT LEGAL REVIEW. Annex to the Terms of Service, concluded when creating an account.
Data Processing Agreement
Parties: the Customer (controller) and Recharged B.V., Hooipolderweg 20, 2635 CZ Den Hoorn, Nederland, CoC 89243188 (processor).
1. Subject matter
1.1 The processor processes personal data on behalf of the controller to provide the Platform: building, hosting and managing the Customer's Apps, including databases, files, end-user accounts, notifications (email, WhatsApp, SMS) and payments. 1.2 Data subjects: end users of the Apps (customers, members, staff, patients/clients, visitors), the Customer's contacts. 1.3 Data categories: as defined by the Customer in its App, including contact, account/login, transaction data, message and document content and — if the Customer so chooses — special categories (e.g. health data). The Customer assesses lawfulness and the need for a DPIA. 1.4 Duration: term of the main agreement plus the 30-day export period.
2. Instructions
The processor acts only on documented instructions; the App configuration and build-conversation requests are instructions. No use for own purposes or AI model training. The processor flags instructions it considers unlawful.
3. Confidentiality and staff access (support access policy)
3.1 Staff are bound by confidentiality and access data only as needed. 3.2 Log in as customer: only platform administrators may temporarily log in on the Customer's behalf, with a mandatory recorded reason (Customer support request, outage, security incident or abuse investigation), for at most 1 hour per session, without the ability to make payments or change account details in that session, and fully logged in the audit log (person, time, reason, actions). 3.3 Build conversations: platform administrators may view them read-only for the same purposes; such viewing is logged. 3.4 Access to an App's database or files only takes place within a session under 3.2 or where necessary to resolve an incident, and is logged. 3.5 The controller may request an overview of access events.
4. Security (Art. 32 GDPR)
TLS, encryption at rest, logical separation (one database per App), role-based least-privilege access, two-factor authentication for administrators, logging, backups with restore procedures, vulnerability management and automated security checks of generated code. The Customer is responsible for security settings it configures within its App (roles, users, share links).
5. Sub-processors
General authorisation is given for the sub-processors below. Changes are announced 30 days in advance; the controller may object on reasonable grounds and terminate if no solution is found. Equivalent obligations are imposed on sub-processors.
| Sub-processor | Purpose | Location / transfer |
|---|---|---|
| Cloudflare, Inc. | Hosting (Workers), databases (D1), storage (R2), network, security, speech recognition | Global network; US entity — DPF/SCC |
| Anthropic, PBC | AI model for building Apps and assistants | US — DPF/SCC |
| Openprovider (Hosting Concepts B.V.) | Domain registration and management | Netherlands/EU |
| Google LLC / Google Ireland Ltd. | Business email (Google Workspace), only if connected by the Customer | EU/US — DPF/SCC |
| Microsoft Corporation / Microsoft Ireland | Business email (Microsoft 365), only if connected | EU/US — DPF/SCC |
| Mollie B.V. | Payments (Customer subscriptions and in-App payments) — partly independent controller | Netherlands/EU |
| Meta Platforms Ireland Ltd. | WhatsApp Business Platform, only if connected | EU/US — DPF/SCC |
| Twilio Inc. | SMS and phone numbers, only if used | US — DPF/SCC |
To be verified by counsel: exact entities, locations and certifications; add a separate email delivery provider if used.
6. Transfers
Only with appropriate safeguards (adequacy decision/EU-US Data Privacy Framework or SCCs with supplementary measures).
7. Assistance
The processor assists with data subject requests (including per-person export and deletion functions in Apps), DPIAs and prior consultation, where reasonable.
8. Personal data breaches
Notified without undue delay and where possible within 48 hours of discovery, with the information needed for notifications, plus mitigation measures.
9. Audits
Information demonstrating compliance is made available. An independent audit is possible once a year with 30 days' notice at the controller's cost, unless it reveals a material shortcoming.
10. End
After termination the controller can export all data for 30 days; afterwards data is deleted, including backups within the regular cycle (max 35 days), unless retention is legally required.
11. Liability
The liability provisions of the Terms of Service apply insofar as the GDPR permits.