Data Processing Agreement (DPA/AVV)

pursuant to Art. 28 para. 3 GDPR

Based on the template provided by the Bavarian Data Protection Authority (BayLDA). Adapted for the SaaS service Tuurio ID.

Controller (Data Controller): The customer operating a Tuurio ID service account (hereinafter "Controller").

Processor (Data Processor): Tuurio GmbH, Muehlenstr. 8a, 14167 Berlin. Managing Directors: Marcus Jueptner, Daniel Kraus. HRB 180639, Amtsgericht Berlin-Charlottenburg. USt-IdNr.: DE305850010 (hereinafter "Processor").

1. Subject matter and duration

Provision of the SaaS solution "Tuurio ID" (id.tuurio.com) for identity management and authentication, including: OAuth 2.0/OIDC authentication and authorization of the controller's end users, storage and management of user identities, provision of token endpoints (Authorize, Token, UserInfo, JWKS), logging of authentication events (audit logs), provision of the vault module (encrypted data storage), and provision of the admin dashboard for tenant management.

The service is provided exclusively within a member state of the European Union (Hosting: Google Cloud Platform, Region Frankfurt/eu-west3, Germany). Any relocation of the service or parts thereof to a third country requires the prior consent of the controller and may only take place if the conditions of Art. 44 ff. GDPR are met.

The agreement is concluded for an indefinite term and applies for the duration of the controller's use of the Tuurio ID service. It ends automatically upon termination of the service contract.

2. Type and purpose, data categories, data subjects

Purpose of processing: Authentication, identity verification, and user management within the Tuurio ID platform for the controller's applications.

Data categories

Data subjects

3. Rights of the controller

The controller has the right to issue instructions regarding data processing at any time, audit the processor's compliance with this agreement (including on-site inspections with reasonable notice), and request information about processing activities. The processor must immediately inform the controller if an instruction, in the processor's opinion, violates data protection regulations.

4. Obligations of the processor

The processor processes personal data only on documented instructions from the controller, ensures that all persons authorized to process personal data have committed themselves to confidentiality, implements and maintains technical and organizational measures pursuant to Art. 32 GDPR, assists the controller in fulfilling data subject requests (Art. 12-22 GDPR), assists with data protection impact assessments (Art. 35 GDPR) and prior consultations (Art. 36 GDPR) where applicable, and makes available to the controller all information necessary to demonstrate compliance.

5. Notification obligations

The processor notifies the controller without undue delay (and in any case within 24 hours) of any personal data breach pursuant to Art. 33 GDPR. The notification includes the nature of the breach, affected data categories and approximate number of affected persons, likely consequences, and measures taken or proposed. Contact: security@tuurio.com.

6. Sub-processors

The current list of sub-processors is available at /public/legal/sub-processors. The controller agrees to the sub-processors listed there. Changes are notified at least 30 days in advance by email. The controller may object within 14 days for important data protection reasons.

7. Technical and organizational measures

The processor implements appropriate technical and organizational measures pursuant to Art. 32 GDPR. Details are described on our security page. Key measures include: AES-256 encryption at rest, TLS 1.3 in transit, Argon2id password hashing (64 MB RAM hardness), tenant isolation via database-level separation (Hibernate filters with tenant_id scoping), automated encrypted daily backups (30-day retention), RS256 JWT signing with tenant-specific key rotation, comprehensive access logging and audit trails.

8. Obligations upon termination

After contract termination, the controller can export all data within 30 days via the dashboard in a common, machine-readable format (JSON, CSV). After the 30-day export period, all personal data is irreversibly deleted within 30 additional days, unless legal retention obligations apply (e.g., tax records pursuant to GoBD: 10 years). The processor confirms deletion in writing upon request.

Version 1.0, March 9, 2026