10 Total
0 High severity
6 Medium severity
4 Low severity
Summary

This is Supabase's privacy policy covering how the company collects and uses personal information from developers and customers who use its open-source backend platform and website. The policy discloses that Supabase collects registration details (name, email, GitHub username), usage and device data, AI support tool inputs and outputs, and third-party data from business and marketing partners, and authorizes sharing this data with service providers, analytics providers, advertising partners, and acquirers in a corporate transaction. The policy separately states that data submitted by Supabase customers relating to their own end users (Customer Data) is processed under a distinct data processing addendum and is not covered by this notice, meaning end users of apps built on Supabase should consult the privacy policy of the application operator rather than this document.

Technical / Legal Breakdown

This privacy notice governs Supabase, Inc.'s collection, use, and disclosure of personal information in connection with its website (supabase.com) and associated developer services, operating under a dual controller/processor framework: Supabase acts as data controller for its own user data and as a data processor for Customer Data submitted through its platform, the latter governed by a separate data processing addendum. The policy states that Supabase collects registration information (name, email, GitHub username), payment transaction data routed through Stripe, communications content, SSO authentication data, usage and device data via cookies and analytics tools, and AI support tool inputs and outputs; it authorizes sharing with service providers, business partners, marketing partners, analytics providers, and in connection with corporate transactions including mergers and acquisitions. The document explicitly carves out Customer Data from the scope of this notice and directs affected individuals to the relevant customer's privacy policy, which is operationally significant for end users of applications built on Supabase who may not be aware their data is governed by a separate contractual chain. The policy engages GDPR (for EEA, UK, and Switzerland users), CCPA (for California residents), Nevada Chapter 603A, and general cross-border data transfer frameworks, with a dedicated EEA/UK/Switzerland section addressing lawful bases, data subject rights, and cookie governance; the document acknowledges that international transfers may involve countries without equivalent data protection standards, a disclosure that directly implicates GDPR Chapter V transfer requirements and UK adequacy frameworks.

Institutional Analysis

Institutional analysis available with Compliance

Regulatory exposure by statute, material risk assessment, vendor due diligence action items, and enforcement precedent. Available on Compliance.

Start Compliance free trial

1 important change detected

2 versions captured · Last updated: May 2026

May 15, 2026

medium
What changed Supabase updated its privacy policy on May 15, 2026 to disclose expanded use of business contact information for sales and marketing outreach, expanded sharing of personal information with the marketing service provider Customer.io, and clarified consent requirements for marketing communications including location-based and cross-source data analysis. The updated policy establishes that marketing-related consents are independent and can be managed separately.
Why this matters The updated policy discloses that Supabase may use business contact information, including email domains, to identify organizations for sales and marketing outreach. The policy now explicitly states that personal information will be shared with Customer.io, a marketing communications service provider. For marketing communications, the policy relies on user consent for three purposes: sending marketing messages, using approximate location information to determine relevant communications, and combining personal information from different sources for relevance determination. These three consents operate independently, meaning you can grant or withdraw any of them without affecting the others. You can manage these marketing-related consents separately through the consent mechanisms available in your account or in response to marketing communications.
View full change record →
Medium — 6 provisions
Low — 4 provisions

Monitoring

Supabase has updated this document before.

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

Start Monitor free trial Or create a free account →

Compliance Governance Intelligence

Need provision-level monitoring and regulatory mapping?

Compliance includes governance timelines, compliance memos, audit-ready analysis, and full provision tracking.

Start Compliance free trial

Cross-platform context

See how other platforms handle AI Support Tool Inputs and Outputs as User Content and similar clauses.

Compare across platforms →

Mapped Governance Frameworks

CCPA/CPRA
California, USA
View official text ↗
FTC Act Section 5
United States Federal
View official text ↗
GDPR
European Union
View official text ↗
Archival ProvenanceSource & Archival Record
Last Captured May 15, 2026 01:20 UTC
Capture Method Automated scheduled archival capture
Document ID CA-D-000682
Version ID CA-V-002658
SHA-256 7df721dc6d9c35ddc3e51a229e364e46fa9c80975d256d592eac70d7094298d3
✓ Snapshot stored ✓ Text extracted ✓ Change verified ✓ Hash verified

Governance Monitoring

Monitor governance changes across the platforms you rely on.

Structured alerts for policy changes, governance events, and provision updates across 318+ platforms.

Create free account Compare plans