TRAKEN

Subprocessors

Last updated: 19 July 2026

Traken engages the following subprocessors to provide the Service. For each we list the purpose, location of processing, and the transfer mechanism relied on for personal data originating in the EEA, the UK, or Switzerland. Traken's default infrastructure is EU-based. Because of the Zero-Data architecture, no AI prompt or response content is shared with any subprocessor. We will update this page at least 30 days before a new subprocessor handling personal data begins processing; business customers may subscribe to change notifications by emailing legal@traken.ai with the subject "Subprocessor notifications".

SubprocessorPurposeLocationTransfer mechanism
Hetzner Online GmbHCompute and hosting (application servers)Germany (EU)Within EEA — no transfer mechanism required
Cloudflare, Inc.DNS, CDN, Pages hosting, cookieless Web Analytics, network securityUnited States / global edge (EU data-localisation options)EU-U.S. Data Privacy Framework (Active, participant 5666); EU SCCs as fallback in Cloudflare's DPA
SupabasePostgreSQL database and authenticationEuropean Union (EU region)Within EEA — no transfer mechanism required
Mistral AIDefault LLM inference for Narrative Report generation (La Plateforme)European Union (France)Within EEA — no transfer mechanism required
Anthropic, PBCOptional premium LLM inference (Claude API), zero-data-retention configurationUnited StatesEU Standard Contractual Clauses (Decision 2021/914) + supplementary measures; not DPF-certified
n8n Cloud (n8n GmbH)Workflow automation / orchestrationEuropean Union (data stored in the EU)Within EEA — no transfer mechanism required
Paddle (Paddle.com Market Ltd / Paddle Payments)Payments, billing, invoicing, tax, refunds (Merchant of Record)United Kingdom / United StatesUK adequacy decision (EU→UK); EU SCCs / DPF for any onward US transfers