Checkout.com's updated privacy policy adds explicit disclosure that call recordings with merchant representatives are used for training, product development, and marketing purposes. Previously, the policy did not disclose this specific use of recorded conversations. The updated language now requires merchants to be aware that their calls may be recorded and used beyond the immediate transaction or support context.
The updated privacy policy now explicitly states that Checkout.com uses recordings of calls with merchant representatives for training, product development, and marketing purposes. Previously, this specific use case was not disclosed in the policy. Merchants should be aware that conversations with Checkout support staff may be recorded and used beyond immediate transaction or support contexts. The updated language does not indicate that consent mechanisms or opt-out procedures are available.
The updated policy now explicitly discloses that merchant calls may be recorded and used for training, product development, and marketing. This transparency addition affects how merchants understand the scope of data use in their relationship with Checkout, though it does not appear to create new consent requirements or operational restrictions.
The policy now explicitly states that recordings of calls with merchant representatives are used for training, product development, and marketing purposes.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
Checkout.com's privacy policy adds a discrete disclosure that recorded calls with merchants are used for training, product development, and marketing. This appears to be a transparency disclosure change rather than a substantive operational change. Organizations that contract with Checkout for payment processing should verify that their own data processing agreements and privacy notices reflect this practice, particularly if they are acting as data controllers in relation to merchant communications. No new vendor obligation is created by this change itself, but downstream organizations may need to update their own privacy disclosures to reflect practices of their service providers.
GDPR (Article 6 lawful basis, Article 13 transparency); CCPA (California Consumer Privacy Act, disclosure requirements). The disclosure of call recording use may engage lawful basis requirements under GDPR if merchants are EU residents, and disclosure requirements under CCPA if merchants are California residents. Specific articles depend on jurisdiction of merchants and determination of whether recorded merchant representatives are personal data of those individuals.
Full compliance analysis
Obligation analysis, escalation trigger, board language, and recommended action.
Monitor: regulatory citations + obligations. Compliance: full compliance memo.
ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-C-003550.
See the full side-by-side comparison of every sentence added, removed, and modified.
🔒 Full diff — MonitorWe read the privacy policies and terms of service of 38 AI platforms. Here is what they say about training, retention, arbitration, and lia…
Get alerted when this policy changes again — including what changed and why it matters.
Prefer a weekly summary instead?
Get the biggest policy changes across 352+ platforms every Sunday.