123 Total
Stay ahead of the changes
Track Supabase 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 document is Supabase's Terms of Service, which binds you the moment you access or use the services—not just when you click accept. All disputes must go through private, individual arbitration rather than court, though new customers have thirty days to opt out by emailing legal@supabase.io. Fees you pay are non-refundable, damages you can recover are strictly capped, and health data cannot be stored on Supabase without a separate agreement.

Analysis

This agreement establishes the terms under which Supabase provides its services, binding users upon clicking 'I Accept' or upon first access or use. It imposes mandatory individual arbitration with express jury-trial and court-relief waivers, and a class-action prohibition, subject to a thirty-day opt-out right for new customers via email to legal@supabase.io. Both parties' aggregate liability is capped at fees paid or payable in the twelve months preceding a claim, and all consequential, incidental, indirect, exemplary, special, enhanced, and punitive damages are excluded; all fees paid are non-refundable and all services are provided 'as is' with all warranties disclaimed. Supabase prohibits storage or processing of HIPAA-defined protected health information without a signed Business Associate Agreement and storage of payment cardholder data without prior written approval, while providing customers with indemnification against third-party claims that Supabase's services infringe or misappropriate US copyrights or trade secrets.

What this means for you

As a Supabase user, you are bound by this agreement from the moment you access or use the services. Your ability to recover damages is limited to fees paid in the prior twelve months, and categories of loss such as lost business or consequential harm are entirely excluded. You cannot join class actions or bring claims in court, and any fees you pay are non-refundable. If you are a new customer and wish to preserve your right to litigate, you can opt out of the arbitration agreement by emailing legal@supabase.io within thirty days of accepting this agreement.

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.

2 important changes detected

6 versions captured · Latest change detected by ConductAtlas: October 2026

What changed Supabase revised its Terms of Service to clarify the contracting entity and expand the definition of Customer Data to include Beta Releases. The company added new provisions governing Beta Releases (alpha, beta, and preview features), which are provided 'AS IS' with no warranties, support obligations, or liability for damages including data loss. The terms also expanded fee payment mechanisms to include direct account purchases and cloud marketplace purchases, and introduced Supplemental Terms that apply to certain services or features.
Why this matters The updated terms introduce new provisions for Beta Releases, which are provided without warranties, support obligations, or liability for damages including data loss, business interruption, or security vulnerabilities. Supabase reserves the right to delete all Customer Data submitted to Beta Releases at any time without notice, and may modify, suspend, or discontinue any Beta Release without advance notice. The terms also clarify that the contracting entity depends on your purchase method: Supabase Inc. (US) if purchased through a cloud marketplace, or Supabase Pte. Ltd. (Singapore) otherwise. Fee payment mechanisms now include direct account purchases and cloud marketplace purchases, with refunds processed through the marketplace rather than directly by Supabase.
View full change record →
What changed Supabase revised its Terms of Service with primarily formatting and clarification changes. The most substantive change adds language stating that if a customer has entered into a separate Order or agreement with Supabase that expressly incorporates different terms, those other terms will govern instead of the standard Terms of Service. Additionally, the terms now include a defined term for 'Data Processing Addendum' that references Supabase's DPA available at a specific URL. Most other changes are punctuation standardization (quotation mark style, spacing) with no operational impact.
Why this matters The updated terms clarify that if you have entered into a separate Order or agreement with Supabase that expressly incorporates different terms, those other terms will govern your use of the Services instead of the standard Terms of Service. The terms also now explicitly reference Supabase's Data Processing Addendum, which is available at supabase.com/legal/customer-resources/data-processing-addendum. These changes do not alter your rights or obligations unless you have a separate agreement in place.
View full change record →

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.

123 provisions
12 featured
21 clause types
Disclosure and Transparency Requirements 1
Stay ahead of the changes

Monitoring

Supabase has updated this document before. 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 Aggregate Liability Cap at Twelve Months Fees and similar clauses.

Compare across platforms →
Archival ProvenanceSource & Archival Record
This version captured October 12, 2026 01:18 UTC
Last successful capture October 14, 2026 00:57 UTC
Capture Method Automated scheduled archival capture
Document ID CA-D-000681
Version ID CA-V-007490
SHA-256 (extracted text, extractor v5) f280d68460261e92c1a8b18877121cf19c1f4398a68c90501ff10ab8b0220dfd
Archived bytes SHA-256 (anchor) 03000aeb58cb04610fce6a39850b0bf0ecb54c4792e1eac247d54b9181f14e93
✓ Snapshot stored ✓ Archived bytes anchored (verified Oct. 12, 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