Privacy policy
Last updated: 30 October 2026
1. Controller
Hurst & Lang UG (haftungsbeschränkt) Königinstraße 101, 80802 Munich, Germany Email: support@tokenlane.de
You can reach our data protection officer at the same address, marked "Datenschutzbeauftragter" (data protection officer), or by email to support@tokenlane.de with that subject.
2. Two roles: controller and processor
We are the controller for the website, customer accounts, billing, support, security and fraud prevention. This policy describes those processing activities.
We process the content of your API requests (prompts, files, responses and any personal data they contain) solely on your behalf and on your instructions. Our data processing agreement (DPA) governs this. You, as the customer, are the controller for that data.
3. Visiting the website and calling the API
When you access tokenlane.de and api.tokenlane.de, our servers process technically necessary connection data: IP address, time, requested address, status code, amount of data transferred and browser identifier. We log failed requests (status codes 400 to 599) to detect faults and attacks. The legal basis is our legitimate interest in secure operation (Art. 6(1)(f) GDPR). We delete these logs after 14 days at the latest unless an incident requires longer retention.
We use no tracking or analytics services and no advertising cookies. We only use storage in your browser that is strictly necessary, for example for sign-in, language and colour scheme (Section 25(2) no. 2 TDDDG). That is why there is no cookie banner. We serve fonts and scripts ourselves. To protect against automated sign-ups we use a proof-of-work challenge (ALTCHA) that is verified on our own servers without external services.
4. Customer account and organisation
For sign-up and sign-in we process email address, name, credentials (passwords only as hashes, passkeys, two-factor settings), roles and memberships in organisations and workspaces, and settings. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR). We record security-relevant changes such as new keys, changed permissions or rules in an audit log (Art. 6(1)(f) GDPR).
5. Company, tax and sanctions checks
Tokenlane is available to businesses only. We therefore process company name, business address, country of registration, authority to represent and VAT identification number. We verify the VAT ID through the European Commission's VAT Information Exchange System (VIES). We also screen the company and its representatives against official sanctions lists. The legal bases are legal obligations (Art. 6(1)(c) GDPR, in particular sanctions and VAT law) and our legitimate interest in preventing fraud (Art. 6(1)(f) GDPR).
6. Payments and invoices
Payments are handled by Mollie B.V., Keizersgracht 126, 1015 CW Amsterdam, the Netherlands. Mollie receives the data needed for payment, fraud checks and chargebacks (amount, billing details, payment method). You enter card details directly with Mollie; we never see them. We store payment status, amounts, receipts and invoices. The legal bases are the performance of the contract and statutory retention obligations (Art. 6(1)(b) and (c) GDPR). We keep invoices and accounting records for up to ten years under commercial and tax law.
7. Using the API
For every request we store usage data: time, key used, workspace, model, provider, outcome, token counts, cost and response times. We need this for billing, records, quotas, abuse detection and the reports in your account (Art. 6(1)(b) and (f) GDPR).
By default we do not store the content of requests and responses. Only if your organisation explicitly enables content storage ("capture") for a key do we store content for the period you set. For retries with an Idempotency-Key we briefly keep a response. Both are processing on your behalf under the DPA.
8. Forwarding to model providers
So that a model can answer your request, we forward it to the provider of the selected route. Your rules determine which provider that is (for example "EU only", allowed providers, no retention for training). The catalogue lists the provider, processing country and data commitments of every route. We currently use only providers that process in the EU, such as IONOS (Germany), OVHcloud (France) and Mistral AI (France). The complete, current list is in the catalogue and in Annex 3 of the DPA.
If your organisation adds its own provider keys or custom endpoints, we forward requests to the provider you choose. Its processing is governed by your contract with it; custom endpoints are never considered EU-verified. We store provider keys encrypted and use them only for your requests.
9. Security and fraud prevention
To protect accounts, credit and payments we analyse payment and usage patterns, for example unusual cost spikes, new countries for API access (derived from the IP address without storing the IP address permanently), chargebacks or keys that have become public. The legal basis is our legitimate interest in preventing fraud and abuse (Art. 6(1)(f) GDPR).
Such signals can automatically lead to a warning, a temporary pause of individual keys or, after a confirmed chargeback, a temporary pause of new requests for your organisation. We tell you the reason where legally permitted, and a person reviews the case at your request or, for chargebacks, on our own initiative. We never impose a final suspension by automated means alone.
10. Emails
We send system messages such as confirmations, security notices, invoices and balance warnings through Resend (Resend, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA), sending from the Ireland region. This involves the recipient address, subject and content of the message. A data processing agreement with EU standard contractual clauses safeguards the transfer to the USA. The legal basis for the messages is the performance of the contract (Art. 6(1)(b) GDPR).
11. Support
We handle support requests made through the in-app form or by email with our own ticket system on our servers in Germany. We process your details, your message and any attachments to answer you (Art. 6(1)(b) and (f) GDPR) and delete them once they are no longer needed, at the latest three years after the request is closed.
12. Hosting
We run the website, API, databases and backups on servers of Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen, Germany, in its Nuremberg data centre. Hetzner processes the data as our processor.
13. Retention
We delete personal data once the purpose no longer applies and no statutory retention obligation exists. We delete account data after termination unless obligations prevent this. We keep billing-relevant usage and payment data for up to ten years. Deleted provider keys become unusable immediately and disappear from backups after 30 days at the latest. We keep data on fraud and sanctions cases for as long as needed for clarification, evidence and legal defence.
14. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). You can withdraw consent at any time with effect for the future. Write to support@tokenlane.de.
You may lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). Our competent authority is the Bavarian Data Protection Authority (Bayerisches Landesamt für Datenschutzaufsicht), Promenade 18, 91522 Ansbach, Germany.
15. Obligation to provide data
Without account, company and payment details we cannot conclude a contract or enable paid services. Other information is voluntary.
The German version is authoritative.