Data processing agreement (DPA)
Last updated: 30 October 2026
between the customer (controller, "customer") and Hurst & Lang UG (haftungsbeschränkt), Königinstraße 101, 80802 Munich, Germany (processor, "Tokenlane").
This agreement sets out the parties' obligations under Art. 28 GDPR. It becomes part of the contract together with the Tokenlane terms of service and applies for as long as Tokenlane processes personal data on behalf of the customer.
1. Subject matter and duration
1.1 Tokenlane processes personal data on behalf of the customer to the extent it is contained in API requests, files and responses or arises when processing them. Subject matter, nature and purpose, types of data and categories of data subjects are set out in Annex 1.
1.2 The term corresponds to the term of the main contract. Obligations regarding deletion and return continue beyond it.
1.3 Data that Tokenlane processes as a controller in its own right (account, billing, usage data for billing, security and fraud prevention) is not covered by this agreement; the privacy policy applies to it.
2. Instructions
2.1 Tokenlane processes the data only on documented instructions from the customer, including with regard to transfers to third countries, unless Tokenlane is required to do so by law; in that case Tokenlane informs the customer of that legal requirement before processing, unless the law prohibits this.
2.2 Instructions are the terms of service, this agreement and the customer's settings and requests via the API and console, in particular rules on allowed providers, processing countries, data retention at providers, content storage ("capture") and its periods. The customer gives further instructions in text form to support@tokenlane.de.
2.3 If Tokenlane considers an instruction unlawful, it informs the customer without delay and may suspend execution until the instruction is confirmed or changed.
3. Confidentiality
Tokenlane only uses persons who are bound to confidentiality or are under a statutory obligation of confidentiality and who have access only to the extent required for their tasks.
4. Security of processing
4.1 Tokenlane implements the technical and organisational measures under Art. 32 GDPR described in Annex 2.
4.2 Tokenlane may develop the measures further as long as the level of protection is not reduced. Tokenlane documents material changes.
5. Sub-processors
5.1 The customer gives general authorisation to engage further processors. The sub-processors engaged when the contract is concluded are listed in Annex 3 and are deemed approved.
5.2 For forwarding requests to model providers, the customer determines through its rules and the routes it selects which of the providers named in Annex 3 and in the catalogue act. Routes excluded by a customer setting are not used.
5.3 Tokenlane informs the customer at least four weeks before engaging a new sub-processor or replacing one, by email or in the console. The customer may object within that period for an important reason relating to data protection. The customer can additionally exclude new model providers through its provider and country rules. If the parties cannot agree following an objection, the customer may terminate the contract as of the date the change takes effect.
5.4 Tokenlane contractually binds every sub-processor to data protection obligations essentially corresponding to this agreement.
5.5 The customer's own provider keys and custom endpoints are not sub-processors of Tokenlane. The customer concludes its own contract with that provider; Tokenlane merely forwards requests there on the customer's instruction.
6. Transfers to third countries
Tokenlane itself processes the data exclusively in the European Union. Transfers to countries outside the European Economic Area take place only on the customer's instruction, for example through routes it allows or through custom endpoints, and only under the conditions of Art. 44 et seq. GDPR.
7. Assistance to the customer
7.1 Tokenlane assists the customer with appropriate measures in responding to requests from data subjects. If a data subject contacts Tokenlane directly, Tokenlane forwards the request to the customer without delay.
7.2 Tokenlane assists the customer in complying with the obligations under Art. 32 to 36 GDPR, in particular data protection impact assessments, taking into account the nature of the processing and the information available.
8. Personal data breaches
Tokenlane notifies the customer of a personal data breach without undue delay, at the latest within 48 hours of becoming aware of it, by email to the organisation owners. The notification contains the information under Art. 33(3) GDPR where available; missing information is provided later. Tokenlane takes measures to contain and remedy the breach without delay.
9. Deletion and return
9.1 Tokenlane stores the content of requests and responses only to the extent necessary for processing the request, for retries with an Idempotency-Key or for content storage enabled by the customer, and deletes it when the respective period expires.
9.2 After the contract ends, Tokenlane deletes all data processed on behalf of the customer within 30 days unless a legal obligation requires storage. Before the contract ends, the customer can export stored content through the console or API. Backups expire no later than 30 days after deletion.
10. Evidence and audits
10.1 Tokenlane makes available to the customer on request all information necessary to demonstrate compliance with this agreement.
10.2 The customer may carry out audits, including inspections, or have them carried out by an auditor bound to confidentiality, with reasonable advance notice of usually 30 days, during normal business hours and without disrupting operations. Tokenlane primarily meets its obligation to provide evidence through written information and current certifications. The customer bears the costs of more than one inspection per year unless the inspection reveals a breach.
11. Liability and final provisions
11.1 Liability is governed by Art. 82 GDPR. Otherwise the liability provisions of the terms of service apply.
11.2 In the event of conflicts between this agreement and the terms of service, this agreement prevails on matters of data protection.
11.3 The laws of the Federal Republic of Germany apply. The place of jurisdiction is Munich to the extent permitted by law. The German version is authoritative.
---
Annex 1: Subject matter of processing
Nature and purpose: receiving API requests, forwarding them to model providers according to the customer's rules, returning responses, storing content on request ("capture") for viewing by the customer, briefly storing responses for retries, forwarding via provider keys and custom endpoints added by the customer.
Types of data: all personal data the customer submits in requests, system instructions, files, images and audio, and the related model output; identifiers the customer includes in requests (for example user, metadata). Special categories under Art. 9 GDPR only if the customer submits them.
Data subjects: employees, customers, users and other persons whose data the customer processes in requests.
Location: data centres in the European Union.
Annex 2: Technical and organisational measures
Physical access: operation in a certified data centre of Hetzner Online GmbH in Nuremberg with access control, video surveillance and visitor logs.
System access: server access only via SSH keys for named administrators; console with password hashing, passkeys and two-factor sign-in, mandatory for administrators and provider keys; access to the internal administration portal only via the company sign-in.
Data access: roles and permissions per organisation and workspace; strict tenant separation in all queries; API keys are stored only as hashes; provider keys are stored encrypted and decrypted only for the respective request; separate database roles with least privilege.
Separation: data of different customers is logically separated; test systems do not use customer data.
Transfer: TLS transport encryption for all external connections and for requests to providers; no logging of content, keys or request bodies in operational logs.
Input control: append-only audit log for keys, rules and permissions.
Availability and resilience: encrypted, regular database backups with tested restore; monitoring of services and providers with automatic fallback to alternative routes; limits on throughput and cost.
Data minimisation: content is not stored by default; content storage only when expressly enabled by the customer and for a limited period.
Review: regular review of the measures, automated security checks on every change, emergency and incident process.
Annex 3: Sub-processors
| Sub-processor | Registered in | Service | Location of processing |
|---|---|---|---|
| Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen | Germany | Hosting, databases, backups | Germany |
| IONOS Cloud GmbH, Berlin | Germany | Model inference | Germany |
| Lyceum Technology Germany GmbH, Berlin | Germany | Model inference | EU |
| OVH SAS, Roubaix | France | Model inference | France |
| Mistral AI, Paris | France | Model inference | EU |
| TensorX Ltd, Dublin | Ireland | Model inference | EU |
| Grunden AI AB, Solna | Sweden | Model inference | Sweden |
The customer's rules and the selected route determine which providers act for a request. The catalogue shows the provider and processing country of every route.