Supabase Updates Its Terms of Service: What Developers Should Know

Supabase has revised its Terms of Service, with an independent terms-tracking service recording the latest version on October 7, 2026. The most important new section for developers covers beta, preview and other features that have not yet reached general availability. The current official Terms of Service confirms the language.

The change is a useful reminder for anyone testing early-access software: a feature marked beta or preview may not offer the same assurances as a stable, generally available service.

What changed?

Section 9(c) of Supabase’s current terms addresses alpha, beta, pilot, preview, early-access and other pre-release products or features, grouped under the term “Beta Releases.” The terms say using these features is optional and they are provided “AS IS” and “AS AVAILABLE.” Supabase disclaims warranties for Beta Releases and says it has no support, service-level, indemnification or other obligations for them.

The section also says Beta Releases may contain bugs or defects and are used at the customer’s own risk. Supabase may modify, suspend or discontinue a Beta Release with or without notice, and it does not promise that an early-access feature will become generally available.

The data-backup point developers should not miss

The current terms specifically reserve Supabase’s right to delete customer data submitted to or through a Beta Release. They make the customer responsible for exporting or retaining backup copies of that data.

The clause says that, to the maximum extent permitted by applicable law, Supabase will not be liable for damages arising from use of a Beta Release, including data loss, business interruption or security vulnerabilities. It includes an exception for damages caused by Supabase’s willful misconduct.

That does not mean all data held in ordinary Supabase production services is automatically being deleted or that every generally available service has newly become a beta product. The provision specifically concerns features designated as alpha, beta, preview or similar pre-release offerings. Developers should still check the exact terms that apply to their projects and any separate agreement they have signed.

Other details in the updated terms

The current agreement also clarifies which Supabase legal entity the customer contracts with based on how the service is purchased. The agreement generally identifies Supabase Pte. Ltd. in Singapore for direct purchases, while purchases through AWS Marketplace identify Supabase, Inc. in the United States unless an order says otherwise.

The terms also explain that AWS Marketplace refunds are handled through that marketplace rather than paid directly by Supabase.

These provisions may matter to companies reviewing their contractual paperwork, but the beta-feature terms are the most practical issue for developers experimenting with unreleased functionality.

What should developers do?

• Check feature labels. Know whether a feature is generally available or explicitly marked alpha, beta, preview or early access.
• Keep independent backups. Export important information and confirm that you can restore it without relying on the beta feature itself.
• Avoid putting irreplaceable production data into previews. Test with non-critical or safely reproducible data when possible.
• Review the actual agreement. Read the current Supabase Terms of Service, Supplemental Terms, and any signed order or separate contract relevant to your account.

The takeaway: Supabase’s current Terms of Service spells out substantial limitations around beta and preview features, including the ability to delete data submitted through them. Developers do not need to panic, but they should treat pre-release features as experimental and keep their own backups.

Sources

• Supabase — Official Terms of Service
• ConductAtlas — Supabase Terms of Service change record, detected October 7, 2026 — independent tracker used to verify the revision date and summarize the changes.
• Supabase — Supplemental Terms