Version history

DeepL expanded its disclosure of payment data collection for Pro subscribers. The updated policy now explicitly lists payment method information received from its payment service provider (token, card brand, last four digits, BIN, country of issue, and card fingerprint) as data collected during Pro signup. The policy also adds disclosure that DeepL uses Payrails GmbH as a payment orchestration service, which stores payment methods and processes initial payments, with a data processing agreement in place.

DeepL expanded its privacy policy to add detailed disclosures about DeepL Voice and Voice-to-Voice services, including how audio data, transcripts, and translations are processed and retained. The updated policy now specifies retention periods (20 seconds to 30 days depending on organization settings), describes speaker matching and voice characteristic processing, and clarifies that audio is deleted after transcription and translation unless retention settings apply. The policy also discloses use of ElevenLabs as a subprocessor for backup voices in languages where DeepL does not have its own voice model.

DeepL's privacy policy was restructured to add three new sections describing customization features: Translation Memories (8.1), Translation Memory Generation (8.2), and Adaptive Translation (8.3). These sections explain how DeepL stores language assets in user accounts, generates translation memories from uploaded documents, and uses embeddings to personalize translations. The policy clarifies that uploaded source documents used for memory generation are deleted immediately after processing and are not used to train models, and that all stored content and embeddings remain within the user's account only.

DeepL restructured its privacy policy to clarify its corporate structure and complaint procedures. The policy now identifies DeepL as a group of legal entities across multiple countries (Germany, UK, Netherlands, Poland, US, Japan) rather than solely DeepL SE, and expanded complaint procedures to include specific contact information for German, EU, and UK regulators. The policy also added disclosure that when users access DeepL through third-party AI tools via MCP integration, DeepL receives user ID and organization name for authentication, and clarified that translated content is not stored.