Provision record
Supabase · Supabase Privacy Policy · View original document ↗

Single Sign-On and Third-Party Authentication Data

Low severity High confidence Explicit document language Common · 290 of 352 platforms
Stay ahead of the changes
Track Supabase and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
Document Record

What it is

The policy states that when users authenticate via GitHub SSO, Supabase receives name, username, email address, language preference, and profile picture from the SSO provider, and uses this data to operate and maintain the service.

ⓘ

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes the data categories obtained through GitHub SSO authentication and the basis on which Supabase accesses third-party identity data. The scope of data received is determined by the authorization procedures of the SSO provider, not solely by Supabase.

Recent Activity

This document changed recently

Medium May 15, 2026

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 change record →

Consumer impact (what this means for users)

Under this clause, users who authenticate via GitHub SSO authorize Supabase to receive name, username, email address, language preference, and profile picture from GitHub. The agreement states this information is used to operate and maintain the service.

How other platforms handle this

Glassdoor Medium

We will also provide an individual opt-out choice, or opt-in for sensitive data, before we share your data with third parties other than our agents, or before we use it for a purpose other than which it was originally collected.

Square Medium

to request that your data be transferred to a third party (data portability)

Google Cloud Medium

Your organization may allow you to access and export your data in order to back it up or transfer it to a service outside of Google.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
We use single sign-on ("SSO") such as GitHub to allow a user to authenticate their account using one set of login information. We will have access to certain information from those third parties in accordance with the authorization procedures determined by those third parties, including, for example, your name, username, email address, language preference, and profile picture. We use this information to operate, maintain, and provide to you the features and

Excerpt from Supabase's Privacy Policy

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

1) REGULATORY LANDSCAPE: SSO data collection engages GDPR Article 6 (lawful basis, likely legitimate interest or contract performance) and CCPA disclosure requirements for categories of data collected.

Insight

Unlock the full institutional analysis

Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.

Applicable regulations

CCPA/CPRA
California, USA
Colorado AI Act
US-CO
Connecticut Data Privacy Act Amendments
US-CT
CAN-SPAM
United States Federal
FTC Act Section 5
United States Federal
GDPR
European Union
Indiana Consumer Data Protection Act
US-IN
Kentucky Consumer Data Protection Act
US-KY
Universal Opt-Out Mechanism Expansion 2026
US
VPPA
United States Federal

Provision details

Document information
Document
Supabase Privacy Policy
Entity
Supabase
Document last updated
May 5, 2026
Tracking information
First tracked
May 21, 2026
Last verified
May 21, 2026
Record ID
CA-P-012941
Document ID
CA-D-00682
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
2612a6b321182bf3baea7bed73960fe4fa4a2105a6ce3e8fcb5b9415b1db09bf
Analysis generated
May 21, 2026 03:12 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Supabase
Document: Supabase Privacy Policy
Record ID: CA-P-012941
Captured: 2026-05-21 03:12:55 UTC
SHA-256: 2612a6b321182bf3…
URL: https://conductatlas.com/platform/supabase/supabase-privacy-policy/provision/CA-P-012941/single-sign-on-and-third-party-authentication-data/
Accessed: Sept. 26, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Low
Categories

Other risks in this policy

Related Analysis

Get the 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.

Frequently Asked Questions

What does Supabase's Single Sign-On and Third-Party Authentication Data clause do?

This provision establishes the data categories obtained through GitHub SSO authentication and the basis on which Supabase accesses third-party identity data. The scope of data received is determined by the authorization procedures of the SSO provider, not solely by Supabase.

How does this clause affect you?

Under this clause, users who authenticate via GitHub SSO authorize Supabase to receive name, username, email address, language preference, and profile picture from GitHub. The agreement states this information is used to operate and maintain the service.

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 290 platforms. See the full comparison.

Is ConductAtlas affiliated with Supabase?

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