DeepL collects your name, email address, and payment details when you create an account, and uses this to run your account and process charges.
This analysis describes what DeepL's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
Payment information is sensitive financial data, and understanding how it is collected and stored (including whether it is passed to third-party payment processors) is important for financial security.
The updated terms establish explicit procedures for three new account-based storage and processing features. Translation Memories allow users to store source and target language segments for reuse; Translation Memory Generation processes uploaded document pairs to generate Translation Memories, then deletes the source documents immediately; and Adaptive Translation uses stored Translation Memories and reference documents to customize translations, with numeric representations (embeddings) calculated and stored in the user's account. The policy states that all content and embeddings are used only within the user's own account, never shared with other customers, and never used to train or improve DeepL's models. The policy specifies GDPR Article 6(1)(b) as the legal basis for processing (contract performance). You can deactivate Adaptive Translation in the relevant Style Profile at any time.
View change record →Account holders share their name, email, and payment details with DeepL, which are used for service delivery and billing. Users should be aware that payment processing is typically handled by third-party payment processors, though the policy's specific subprocessors for payment handling are not named in the excerpt reviewed.
How other platforms handle this
You and your organization's administrator can access several types of Service Data directly from Google Cloud, including your account information, billing contact information, payment and transaction information, as well as product and communication settings and configurations.
to request that your data be transferred to a third party (data portability)
To stop us collecting your location information, you can update your device settings, stop using the Service, or uninstall our mobile apps.
"When you register for a DeepL account, we collect your name, email address, and payment information. We use this information to provide you with our services, process payments, and communicate with you about your account.Excerpt from DeepL's Privacy Policy
(1) REGULATORY LANDSCAPE: Collection of payment information engages PCI-DSS standards for payment card data security, GDPR for EU/EEA users (as payment data constitutes personal data), and applicable consumer financial protection laws.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
Payment information is sensitive financial data, and understanding how it is collected and stored (including whether it is passed to third-party payment processors) is important for financial security.
Account holders share their name, email, and payment details with DeepL, which are used for service delivery and billing. Users should be aware that payment processing is typically handled by third-party payment processors, though the policy's specific subprocessors for payment handling are not named in the excerpt reviewed.
ConductAtlas has identified this type of provision across 290 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by DeepL.