20 Total

Key Facts · in the document’s own words

What does Databricks prohibit users from taking any actions resulting in?
“...or any actions resulting in a denial of service”
Version CA-V-006771, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Databricks prohibits users from taking any actions resulting in a denial of service.
What does Databricks prohibit users from using any means to do?
“(c) use any means to bypass usage limitations...”
Version CA-V-006771, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Databricks prohibits users from using any means to bypass usage limitations.
What does Databricks prohibit users from causing or violating?
“cause harm to or violate the human rights of any person, including without limitation privacy rights”
Version CA-V-006771, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Databricks prohibits users from causing harm to or violating the human rights of any person, including without limitation privacy rights.
What does Databricks prohibit users from engaging in or promoting?
“engage in or promote any fraudulent, corrupt, deceptive or similarly objectionable activities”
Version CA-V-006771, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Databricks prohibits users from engaging in or promoting any fraudulent, corrupt, deceptive, or similarly objectionable activities.
What does Databricks prohibit users from attempting to do?
“attempt to (a) interfere with, harm, or disrupt the Databricks Services...”
Version CA-V-006771, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Databricks prohibits users from attempting to interfere with, harm, or disrupt the Databricks Services.
What does Databricks prohibit users from developing or offering?
“develop or offer a service, product, feature, functionality, or interface that substitutes for, replicates, replaces or circumvents any Databricks Services, or portion thereof, including through reverse engineering, intermediation, or use of outputs...”
Version CA-V-006771, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Databricks prohibits users from developing or offering a service, product, feature, functionality, or interface that substitutes for, replicates, replaces, or circumvents any Databricks Services or portion thereof, including through reverse engineering, intermediation, or use of outputs.
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.
Summary
Generated by a model from the captured document; not read by a person

This policy sets out the rules for what you can and cannot do when using Databricks Services. You cannot use the platform to attack or disrupt services, build competing products, automate interactions outside approved integrations, or harm others' rights. If you use Databricks AI features, additional terms in Databricks's Documentation may also apply to you.

Analysis

This Acceptable Use Policy establishes a comprehensive set of conduct prohibitions governing user interaction with Databricks Services, with particular emphasis on AI and automated use. Users are prohibited from any actions that cause denial-of-service outcomes, bypass usage limitations, interfere with or disrupt the Services, or use any automated means of interaction outside of a Databricks validated integration. The policy imposes broad restrictions on competitive and derivative use, prohibiting users from building substitute, replacement, or circumventing products or services—whether directly, through third parties they permit, or through use of AI outputs—except where the Agreement expressly authorizes such use. Users are additionally prohibited from causing harm to or violating the human rights of any person, engaging in fraudulent or deceptive activities, or scraping and persistently copying metadata including audit logs and credentials. A reciprocal benchmarking obligation applies to users who disclose Benchmark results.

What this means for you

As a user of Databricks Services, you are bound by a wide range of conduct restrictions: you cannot interfere with or disrupt the Services, scrape or bulk-export metadata such as audit logs or credentials, use automated tools unless authorized through a Databricks validated integration, or use AI outputs to create or improve AI systems unless the Agreement expressly permits it. You are also responsible for ensuring that any third parties you permit to use the Services comply with the same restrictions. If you use AI or machine learning features within Databricks Services, you should review the Documentation to identify any additional terms or use policies that apply to that use.

Institutional Analysis
Stay ahead of the changes

Institutional analysis available with Insight

Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.

Clauses withheld

We withheld clauses we had published from this document. Each withholding is recorded in our correction log:

Featured provisions
Generated by a model from the captured document; not read by a person

Complete Provision Index

Every distinct legal provision identified in this document. Featured provisions appear above with analysis.

20 provisions
12 featured
5 clause types
AI / Automated Decision-Making 1
Disclosure and Transparency Requirements 1
Stay ahead of the changes

Monitoring

We have not recorded a change to this document since we began capturing it. Monitor includes alerts from a daily check, structured change summaries, and monitoring for up to 20 platforms.

Stay ahead of the changes

Governance Intelligence

Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.

Cross-platform context

See how other platforms handle Prohibition on Actions Causing Denial of Service and similar clauses.

Compare across platforms →
Archival ProvenanceSource & Archival Record
This version captured September 11, 2026 00:56 UTC
Last successful capture October 14, 2026 00:43 UTC
Date stated by the document March 20, 2026 (as printed in this version)
Capture Method Automated scheduled archival capture
Document ID CA-D-000838
Version ID CA-V-006771
SHA-256 (extracted text, extractor v5) 312f00b500a9fd269ca0e4242af45247b7c4c33fcdcbec301436763d79356e22
Archived bytes SHA-256 (anchor) 2aaf7a2013c0b8a178bfc6d4c8b8f0a6fa0d1ddb516cb46b986a6f0871d0fcc3
✓ Snapshot stored ✓ Archived bytes anchored (verified Sept. 11, 2026)

Governance Monitoring

Monitor governance changes across the platforms you rely on.

Structured alerts for policy changes, governance events, and provision updates across 343 platforms.

Start monitoring → Compare plans