Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
Users who access more than 1,000,000 posts in any 24-hour period in violation of the Terms are liable for liquidated damages of $15,000 USD (or EUR 15,000 for EU/UK users) per 1,000,000 posts accessed. The clause applies on a joint and several basis and does not cap X's ability to seek additional statutory or equitable relief.
This analysis describes what X'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
This provision establishes a quantified financial liability trigger for high-volume or automated access to the platform in violation of the Terms, which is particularly relevant for API developers, data researchers, and enterprise users who aggregate or scrape platform data. The clause asserts joint and several liability, meaning multiple parties involved in facilitating a violation may each be held fully liable for the full damages amount.
⚠ Users who access more than 1,000,000 posts in a 24-hour period in violation of the Terms are liable for liquidated damages of $15,000 USD per 1,000,000 posts as stated in the Terms.
⚠ X reserves the right to seek injunctive and equitable relief in addition to monetary damages for repeated violations.
Cross-platform context
See how other platforms handle Liquidated Damages for High-Volume Post Access and similar clauses.
Compare across platforms →Monitoring
X has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"You further agree that, to the extent permitted by applicable law, if you violate the Terms, or you induce or knowingly facilitate others to do so, in addition to all other legal remedies available to us, you will be jointly and severally liable to us for liquidated damages as follows for requesting, viewing, or accessing more than 1,000,000 posts (including reply posts, video posts, image posts, and any other posts) in any 24-hour period - $15,000 USD per 1,000,000 posts. You agree that these amounts are (i) a reasonable estimate of our damages; (ii) not a penalty; and (iii) not otherwise limiting of our ability to recover from you or others under any legal or equitable theory or claim, including but not limited to statutory damages and/or equitable relief. You further agree that repeated violations of these Terms will irreparably harm and entitle us to injunctive and/or other equitable relief, in addition to monetary damages.Excerpt from X's Terms of Service
1. REGULATORY LANDSCAPE: This provision is primarily a contractual enforcement mechanism rather than a regulatory compliance matter. However, its characterization as liquidated damages rather than a penalty may be subject to judicial scrutiny under applicable contract law in the US (Texas law governs for US users) and EU/UK jurisdictions. EU Directive 93/13/EEC on unfair contract terms may be relevant for EU/UK consumers if a court determines the clause creates a significant imbalance in the parties' rights and obligations. 2. GOVERNANCE EXPOSURE: High for developer and enterprise users. The 1,000,000-post-per-24-hour threshold may be reachable by automated systems, data analytics tools, or API integrations, making this a material financial risk for organizations that access X data programmatically. The joint and several liability structure means organizations could be held liable for the actions of employees or contractors who access the platform in violation of the Terms. 3. JURISDICTION FLAGS: The enforceability of pre-agreed liquidated damages clauses varies by jurisdiction. Under Texas law (applicable to US users), liquidated damages clauses are generally enforceable if they represent a reasonable estimate of actual damages and are not a penalty; the agreement asserts these criteria are met. In EU/UK jurisdictions, enforcement may face additional scrutiny under consumer protection frameworks. For business-to-business contracts, enforceability analysis differs from consumer contracts. 4. CONTRACT AND VENDOR IMPLICATIONS: Organizations using X data through third-party vendors or data aggregators should assess whether those vendors' access practices could create joint and several liability exposure under this clause. Developer Agreement compliance should be reviewed to confirm API usage volumes remain within permitted limits, as unauthorized access above the threshold creates direct financial exposure under these Terms. 5. COMPLIANCE CONSIDERATIONS: Legal teams should review whether current API or data access integrations with X remain within the boundaries of the Developer Agreement and these Terms, particularly regarding automated post access volumes. Risk management teams should assess whether indemnification provisions in vendor contracts with X data resellers adequately address this liquidated damages exposure.
Regulatory citations, enforcement risk, and due diligence action items.
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
This provision establishes a quantified financial liability trigger for high-volume or automated access to the platform in violation of the Terms, which is particularly relevant for API developers, data researchers, and enterprise users who aggregate or scrape platform data. The clause asserts joint and several liability, meaning multiple parties involved in facilitating a violation may each be held fully liable …
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by X.