Heap · Heap Terms of Service · View original document ↗

Limitation of Liability Cap

Medium severity High confidence Explicitdocumentlanguage Unique · 0 of 352 platforms
Get alerted the next time Heap changes these terms. Get same-day alerts →
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Heap Monitor emails you the same day this changes. The archive stays free.
Get same-day alerts →

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.

Document Record

What it is

Except for indemnification obligations, gross negligence, willful misconduct, and Contentsquare's fee collection rights, each party's total liability is capped at the fees paid by Customer in the 12 months preceding the liability-triggering event. Consequential, indirect, and punitive damages are excluded for both parties under Section 10.1.

This analysis describes what Heap'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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes a mutual 12-month fee-based liability cap and a broad exclusion of consequential and indirect damages. The carve-outs for gross negligence and willful misconduct are mutual, but the carve-out for unpaid fee collection applies exclusively to Contentsquare, allowing uncapped recovery of fees while Customer's breach of data obligations remains subject to the cap.

Consumer impact (what this means for users)

Under this clause, Customer's financial recourse against Contentsquare for most claims is limited to the fees paid in the preceding 12 months. The agreement excludes recovery for loss of profits, loss of data, business interruption, and similar indirect damages by either party, subject to the stated exceptions.

Cross-platform context

See how other platforms handle Limitation of Liability Cap and similar clauses.

Compare across platforms →

Monitoring

Heap has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
Except for: (a) the Parties' express obligations under Section 9 (Third-Party Claims); (b) damages resulting from death or bodily injury, or physical damage to tangible real or personal property, caused by either Party's gross negligence; (c) damages resulting from either Party's gross negligence or willful misconduct; and (d) Contentsquare's right to collect unpaid Fees due hereunder, to the extent permitted by law, the total, cumulative liability of each Party (and their respective Affiliates) arising out of or related to the Agreement will be limited to the amounts paid by Customer for the CS Service during the twelve (12) month period preceding the first event giving rise to liability.

Excerpt from Heap's Terms of Service

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

1) REGULATORY LANDSCAPE: Limitation of liability clauses in B2B contracts are generally enforceable under the governing commercial law, subject to jurisdiction-specific constraints. Under English law and certain EU member state laws, liability limitations may be assessed for reasonableness. The GDPR may impose regulatory fines on data controllers independent of contractual liability caps; such regulatory obligations are not eliminated by this clause. 2) GOVERNANCE EXPOSURE: Medium. The 12-month fee-based cap means that in high-value, long-term deployments, the recoverable damages for a significant data incident or service failure may be substantially lower than the actual loss incurred. The consequential damages exclusion specifically names loss of profits, loss of data, and business interruption as excluded categories. 3) JURISDICTION FLAGS: In the UK, UCTA (Unfair Contract Terms Act 1977) and the Consumer Rights Act 2015 impose reasonableness tests on liability exclusion clauses, though UCTA applies primarily to B2B contracts. EU member states have varying standards for exclusion clause enforceability in commercial contracts. Customers in highly regulated sectors (financial services, healthcare) may face regulatory obligations that exceed the contractual cap. 4) CONTRACT AND VENDOR IMPLICATIONS: Procurement and legal teams should assess whether the 12-month fee cap is adequate relative to the potential business impact of a data processing failure or security incident, and consider whether the Order Form or a separate addendum should negotiate a higher cap for specific risk categories such as data breaches. The mutual application of the cap means Contentsquare's liability for service failures is also limited. 5) COMPLIANCE CONSIDERATIONS: Risk management teams should model the maximum contractual recovery against the estimated business impact of foreseeable failure scenarios, including data loss, prolonged service unavailability, and unauthorized disclosure of Visitor Data. Cyber insurance coverage should be assessed against the gap between the contractual cap and the estimated loss exposure.

Full institutional analysis

Regulatory citations, enforcement risk, and due diligence action items.

Get same-day alerts when this changes → Get Analyst

Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.

Provision details

Document information
Document
Heap Terms of Service
Entity
Heap
Document last updated
May 5, 2026
Tracking information
First tracked
July 12, 2026
Last verified
July 12, 2026
Record ID
CA-P-074350
Document ID
CA-D-00705
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
2473664e4d72b3895db4decc2c14bf585534ef5a947445a906324608eafc4131
Analysis generated
July 12, 2026 15:50 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Heap
Document: Heap Terms of Service
Record ID: CA-P-074350
Captured: 2026-07-12 15:50:23 UTC
SHA-256: 2473664e4d72b389…
URL: https://conductatlas.com/platform/heap/heap-terms-of-service/provision/CA-P-074350/limitation-of-liability-cap/
Accessed: July 23, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Get Compliance

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does Heap's Limitation of Liability Cap clause do?

This provision establishes a mutual 12-month fee-based liability cap and a broad exclusion of consequential and indirect damages. The carve-outs for gross negligence and willful misconduct are mutual, but the carve-out for unpaid fee collection applies exclusively to Contentsquare, allowing uncapped recovery of fees while Customer's breach of data obligations remains subject to the cap.

How does this clause affect you?

Under this clause, Customer's financial recourse against Contentsquare for most claims is limited to the fees paid in the preceding 12 months. The agreement excludes recovery for loss of profits, loss of data, business interruption, and similar indirect damages by either party, subject to the stated exceptions.

Is ConductAtlas affiliated with Heap?

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