The policy states that credit card details, billing addresses, and transaction history are collected at the point of purchase and processed by PCI DSS-compliant third-party payment service providers.
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
This provision discloses that payment card data is handled by external payment processors operating under PCI DSS compliance standards, rather than being stored directly by DeepL. The specific payment service providers are not named in this excerpt.
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 →Under this provision, payment card details, billing address, and transaction history submitted during subscription purchase are processed by third-party payment service providers described as PCI DSS compliant. Users' financial data is handled by these external processors rather than retained directly by DeepL.
How other platforms handle this
to request that your data be transferred to a third party (data portability)
Your organization may allow you to access and export your data in order to back it up or transfer it to a service outside of Google.
Further, you may take legal actions in relation to any potential breach of your rights regarding the processing of your Personal Information, as well as to lodge complaints before the competent data prot...
"When you purchase a subscription or make a payment, we collect payment information such as your credit card details, billing address, and transaction history. Payment data is processed by our payment service providers who are PCI DSS compliant.Excerpt from DeepL's Privacy Policy
1) REGULATORY LANDSCAPE: PCI DSS compliance for payment card data is an industry standard requirement enforced through card network agreements rather than a statutory framework.
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.
This provision discloses that payment card data is handled by external payment processors operating under PCI DSS compliance standards, rather than being stored directly by DeepL. The specific payment service providers are not named in this excerpt.
Under this provision, payment card details, billing address, and transaction history submitted during subscription purchase are processed by third-party payment service providers described as PCI DSS compliant. Users' financial data is handled by these external processors rather than retained directly by DeepL.
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.