The list identifies subprocessors engaged for billing and payment processing functions, indicating that financial account data and transaction information related to Datadog subscriptions may be processed by third-party payment vendors.
This analysis describes what Datadog'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
Billing and payment subprocessors may process financial identifiers and transaction records, engaging both data protection obligations under GDPR and, depending on the entity, PCI DSS compliance requirements, which controllers and customers should verify.
Interpretive note: The specific billing and payment subprocessors listed could not be confirmed from the extracted HTML; description reflects standard subprocessor list conventions for SaaS platforms.
This provision establishes that payment and billing data associated with Datadog subscriptions may be processed by third-party payment vendors identified in the subprocessor list, which business customers should account for in their vendor risk and financial data handling assessments.
Cross-platform context
See how other platforms handle Billing and Payment Subprocessors and similar clauses.
Compare across platforms →Monitoring
Datadog has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
1) REGULATORY LANDSCAPE: Billing and payment subprocessors engage GDPR data protection obligations where financial data constitutes personal data. PCI DSS requirements apply to entities handling payment card data. Relevant enforcement authorities include EU national supervisory authorities for data protection and the applicable card scheme compliance bodies for PCI DSS. 2) GOVERNANCE EXPOSURE: Medium. Financial data processed by billing subprocessors is generally limited in scope, but its sensitivity warrants confirmation of applicable security and compliance certifications. 3) JURISDICTION FLAGS: EU/EEA customers should confirm transfer mechanisms for billing subprocessors located in third countries. US customers should assess whether any applicable state financial privacy laws apply. 4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should confirm that billing subprocessors maintain PCI DSS compliance where applicable and that DPAs cover the financial data categories processed. 5) COMPLIANCE CONSIDERATIONS: Compliance teams should verify that financial data shared with billing subprocessors is limited to what is necessary and that retention periods are consistent with applicable requirements.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 3 platforms + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
Billing and payment subprocessors may process financial identifiers and transaction records, engaging both data protection obligations under GDPR and, depending on the entity, PCI DSS compliance requirements, which controllers and customers should verify.
This provision establishes that payment and billing data associated with Datadog subscriptions may be processed by third-party payment vendors identified in the subprocessor list, which business customers should account for in their vendor risk and financial data handling assessments.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Datadog.