If your company uses Databricks' platform to process data, that data is covered by a separate contract with Databricks, not this privacy policy. This notice only covers information Databricks collects directly about you as a visitor, prospect, or contact.
This analysis describes what Databricks'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
Enterprise customers cannot rely on this public privacy notice to understand how their platform data is protected. The actual obligations and rights depend on separately negotiated contract terms.
Simplified and streamlined the explanation of processor/controller distinction, removing the guidance to contact customers and focusing on the governing agreements (DPA added explicitly).
View full change record →If you interact with Databricks as a business customer whose organization processes data on the Databricks platform, your data rights and Databricks' obligations regarding that data are governed by a DPA, not this notice, meaning you need to review a separate document to understand your protections.
How other platforms handle this
At Ledger, earning and maintaining our users' trust is a top priority. That's why we are deeply committed not only to protecting your privacy and securing your personal data, but also to being fully transparent about how we handle it.
If you are located in the European Economic Area, Switzerland, or the United Kingdom, you have the right to access, correct, or erase your personal data; the right to restrict or object to our processing of your personal data; the right to data portability; and, where our processing is based on your...
We use information to enhance the quality, reliability, and/or accuracy of our AI Features by creating, developing, training, testing, improving, and maintaining AI and ML models run by Strava or our service providers. We use aggregated, de-identified data for this purpose. We also use personal info...
Monitoring
Databricks has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"The data that Databricks' customers process using Databricks products or services is governed by the applicable customer agreement and Data Processing Addendum, not this Privacy Notice.— Excerpt from Databricks's Databricks Privacy Notice
REGULATORY LANDSCAPE: This carve-out has direct GDPR Article 28 implications, as it establishes Databricks as a data processor for customer platform data and requires a written data processing agreement. The relevant enforcement authorities include EU supervisory authorities and, for UK operations, the ICO. Under CCPA and analogous state laws, Databricks' role as a service provider or contractor for enterprise customers triggers separate contractual requirements and limits on downstream data use. GOVERNANCE EXPOSURE: High. Enterprise customers who have not reviewed and executed a current DPA with Databricks may have a gap in their vendor management documentation required under GDPR Article 28, CCPA service provider requirements, and analogous state law processor contract obligations. The public notice does not substitute for this documentation. JURISDICTION FLAGS: Heightened exposure in EU/EEA where GDPR Article 28 mandates specific written processor agreements. California organizations are similarly exposed under CCPA's service provider contract requirements. Healthcare and financial services organizations subject to HIPAA or GLBA should separately assess whether Databricks agreements include appropriate BAA or data handling addenda. CONTRACT AND VENDOR IMPLICATIONS: Procurement and legal teams should verify that a current, executed DPA is in place with Databricks and that it reflects current regulatory requirements including sub-processor lists, international transfer mechanisms, and data subject rights assistance obligations. The carve-out in this notice signals that the DPA is the operative document and should be prioritized in vendor assessments. COMPLIANCE CONSIDERATIONS: Compliance teams should audit vendor records to confirm DPA execution, review sub-processor disclosures in the DPA, and assess whether Databricks' DPA satisfies requirements under all applicable jurisdictions where the organization operates.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
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.
Enterprise customers cannot rely on this public privacy notice to understand how their platform data is protected. The actual obligations and rights depend on separately negotiated contract terms.
If you interact with Databricks as a business customer whose organization processes data on the Databricks platform, your data rights and Databricks' obligations regarding that data are governed by a DPA, not this notice, meaning you need to review a separate document to understand your protections.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Databricks.