Neither party can claim lost profits, indirect damages, or consequential damages from the other, regardless of the circumstances or whether the harm was foreseeable.
This analysis describes what Supabase'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
If Supabase's platform fails and causes your business to lose revenue or customers, this clause limits your ability to recover those losses, even if the failure was caused by Supabase's negligence.
Interpretive note: Enforceability of the full exclusion depends on jurisdiction; EU member state law, UK UCTA, and Singapore UCTA may limit exclusions for gross negligence or wilful misconduct.
The relocation of Supabase's legal entity from Delaware to Singapore may affect which jurisdiction's courts and laws apply to disputes, potentially impacting your ability to pursue claims in US court…
If a Supabase outage or data loss causes your business to lose revenue, customers, or opportunities, the agreement limits your recoverable damages to direct losses only, excluding lost profits and consequential harm. This is a standard SaaS limitation but is material for businesses running revenue-critical applications on the platform.
How other platforms handle this
TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER WHATNOT NOR ITS SERVICE PROVIDERS INVOLVED IN CREATING, PRODUCING, OR DELIVERING THE SERVICES WILL BE LIABLE FOR ANY INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOST PROFITS, LOST REVENUES, LOST SAVINGS, LOST BUSINESS OPPORT...
In no event will either party's aggregate liability arising out of or related to this Agreement exceed the total fees paid or payable by Customer in the twelve (12) months preceding the claim. In no event will either party be liable for any indirect, incidental, special, consequential, or punitive d...
Except as stated in Section L.3.b, the liability of each party, and its affiliates and licensors, for any damages arising out of or related to these Terms (i) excludes damages that are consequential, incidental, special, indirect, or exemplary damages, including lost profits, business, contracts, re...
Monitoring
Supabase has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"IN NO EVENT WILL EITHER PARTY BE LIABLE TO THE OTHER PARTY OR ANY THIRD PARTY FOR ANY LOSS OF USE, REVENUE, OR PROFIT OR DIMINUTION IN VALUE, OR FOR ANY CONSEQUENTIAL, INCIDENTAL, INDIRECT, EXEMPLARY, SPECIAL, OR PUNITIVE DAMAGES WHETHER ARISING OUT OF BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, REGARDLESS OF WHETHER SUCH DAMAGES WERE FORESEEABLE AND WHETHER OR NOT SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.— Excerpt from Supabase's Supabase Terms of Service
REGULATORY LANDSCAPE: Limitation of liability clauses in commercial SaaS agreements are generally enforceable under US and English law, subject to unconscionability and negligence carve-outs. EU member state laws may limit exclusions of liability for gross negligence, wilful misconduct, or personal injury. Singapore law, which governs this agreement per the governing law clause, similarly limits exclusion of liability for fraud and wilful misconduct under the Unfair Contract Terms Act (UCTA). GOVERNANCE EXPOSURE: Medium. The exclusion of lost revenue and profit damages is standard in cloud services agreements but creates meaningful financial exposure for customers whose core business operations depend on platform availability. The mutual nature of the clause provides some symmetry but Supabase as the service provider is the more likely defendant. JURISDICTION FLAGS: EU customers should assess whether national law limits the exclusion of consequential damages in B2B agreements, particularly for gross negligence. UK customers should note the Unfair Contract Terms Act 1977 may apply to exclusion clauses in certain commercial contexts. CONTRACT AND VENDOR IMPLICATIONS: Enterprise customers should negotiate an aggregate liability cap tied to fees paid and assess whether cyber liability insurance can cover losses not recoverable under the agreement. The exclusion of third-party claims means customers cannot recover on behalf of their own end users affected by a Supabase failure. COMPLIANCE CONSIDERATIONS: Risk management teams should evaluate whether the limitation of liability is acceptable given the criticality of Supabase to business operations, and consider negotiating enhanced SLA remedies or specific performance obligations in the Order.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
If Supabase's platform fails and causes your business to lose revenue or customers, this clause limits your ability to recover those losses, even if the failure was caused by Supabase's negligence.
If a Supabase outage or data loss causes your business to lose revenue, customers, or opportunities, the agreement limits your recoverable damages to direct losses only, excluding lost profits and consequential harm. This is a standard SaaS limitation but is material for businesses running revenue-critical applications on the platform.
ConductAtlas has identified this type of provision across 228 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Supabase.