Provision record
Databricks · Databricks Privacy Notice · View original document ↗

Cross-service identification using device identifiers

Common · 272 of 343 platforms
Stay ahead of the changes
Track Databricks and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

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

How other platforms handle this

Uber

We use data for analysis, research and product development, including training machine learning models. This helps us make our services more convenient and easy to use, enhance the safety and security...

Palantir

We use your Contact Data, Communication Data, Professional Data, Technical Data, Transaction Data, Training and Educational Data, Inferred Data and Contact Preferences to understand who may be interested...to personalize our communications with you...

Kling AI

We may also aggregate and/or de-identify your Data and may use such aggregate or de-identified information for any other purposes to the extent permitted under applicable law and not attempt to re-identify the information, unless required by law.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
We may also use the information we collect automatically (for example, IP address, and unique device identifiers) to identify the same unique person across Services

Excerpt from Databricks's Privacy Notice

Provision details

Document information
Document
Databricks Privacy Notice
Entity
Databricks
Date stated by the document
Jan. 9, 2026
As printed in Databricks’s text (version CA-V-006769), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
April 29, 2026
Text quoted from version
CA-V-006769, captured Sept. 11, 2026
Record ID
CA-P-045700
Document ID
CA-D-000458
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-006769)
2f94cc8dc772b4bb883ed0f76b47f4309f6f11fb30ffa341ce279bf449a482b6
Analysis generated
May 10, 2026 16:34 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-006769, captured Sept. 11, 2026 (checked Oct. 5, 2026)
Citation Record
Entity: Databricks
Document: Databricks Privacy Notice
Record ID: CA-P-045700
Version: CA-V-006769
Captured: 2026-09-11 00:56:37 UTC
SHA-256: 2f94cc8dc772b4bb…
URL: https://conductatlas.com/platform/databricks/databricks-privacy-notice/provision/CA-P-045700/cross-service-identification-using-device-identifiers/
Accessed: Oct. 28, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Related Analysis

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Databricks's Cross-service identification using device identifiers clause do?

The clause states: “We may also use the information we collect automatically (for example, IP address, and unique device identifiers) to identify the same unique person across Services”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 272 platforms. See the full comparison.

Is ConductAtlas affiliated with Databricks?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Databricks.