Supabase
Database · supabase.com · last read 2026-11-16
At a glance
- Is Supabase GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Supabase itself publishes, each answer linked to its source and the date we read it.
- Does Supabase have a data processing agreement (DPA)?
- Yes. Supabase publishes a data processing agreement at supabase.com. It gives 30 days' notice before a new subprocessor is added. It commits to telling you of a personal data breach within 48 hours. Source and date
- Which version of the Supabase DPA is current?
- On 2026-11-09, Supabase's DPA at supabase.com printed “Version 1 — August 1, 2026”. Source and date
- Does Supabase have a SOC 2 report?
- Supabase says a SOC 2 Type 2 report is available on request. In Supabase's words: “Supabase is SOC 2 Type 2 compliant. This is an important security policy when handling sensitive customer data. Enterprise and Team customers can access our SOC 2 Type 2 report on the dashboard.” We read this on 2026-10-08. Source and date
- Is Supabase ISO 27001 certified?
- Supabase states ISO/IEC 27001 certification, and says the certificate or audit report is available on request. We read this on 2026-10-08. Source and date
- How does Supabase transfer personal data out of the EU?
- Supabase's agreement relies on the EU standard contractual clauses and the UK transfer addendum. We found no entry for Supabase on the official Data Privacy Framework List. Source and date
- Does Supabase offer EU data residency?
- The vendor documents an EU region but states nothing about which plan reaches it or what it costs. Source and date
- Who are Supabase's subprocessors?
- Supabase lists 23 third-party subprocessors; 0 of them name at least one processing country outside the EEA. We last read the list on 2026-10-08. Source and date
- How do you report a security vulnerability to Supabase?
- Supabase publishes a security.txt at supabase.com naming https://hackerone.com/supabase. The file falls short of RFC 9116: no Expires field. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Supabase Pte. Ltd. |
|---|---|
| HQ | SG |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Not determined from the sources read |
| Source | supabase.com · 2026-10-08 |
Supabase data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Terms not stated | — | supabase.com | 2026-10-08 |
EU: The document lists EU regions you can pick for a project, such as West EU (Ireland), Central EU (Frankfurt), West EU (Paris) and North EU (Stockholm), and says the region you choose also determines where your primary project data is stored. It doesn't name a plan or a cost for picking these regions.
The same question for every vendor: where SaaS vendors store EU data.
Supabase's subprocessor list names AWS and Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
23 third parties · 1 of the vendor's own group companies · 0 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Active Campaign, LLC d/b/a Postmark | — | Communication with Authorized Users in connection with the provision of the Services and support |
| Amazon Web Services, Inc | — | Provision of hosting services |
| Atlassian Corporation Plc | — | Provision of status page services |
| Braintrust Data, Inc | — | Provision of monitoring and tracing |
| Clay Labs Inc. | — | Provision of customer insight services |
| Clazar, Inc | — | Provision of marketplace services |
| Cloudflare, Inc | — | Provision of hosting services |
| ConfigCat Korlátolt Felelősségű Társaság | — | Feature flagging |
| Fly.io, Inc | — | Provision of hosting services |
| FrontApp, Inc | — | Communication with Authorized Users in connection with the provision of the Services and support |
| Functional Software, Incd/b/a Sentry | — | Error monitoring and tracing |
| Github, Inc | — | Authorized Users account authentication |
| Google, LLC | — | Provision of hosting services |
| Hex Technologies, Inc | — | Provision of data analytics services |
| Hubspot, Inc | — | Communication with Authorized Users in connection with the provision of the Services and support |
| Latacora, LLC | — | Managed Security Service Provider |
| Notion Labs, Inc | — | Communication with Authorized Users in connection with the provision of the Services and support |
| OpenAI, LLC | — | Provision of natural language processing and generation services |
| PandaDoc, Inc | — | Communication with Authorized Users in connection with the provision of the Services and support |
| Slack Technologies, LLC | — | Communication with Authorized Users in connection with the provision of the Services and support |
| Sublime Security Inc | — | Email Security |
| Upstash, Inc | — | Provision of serverless data hosting services |
| Vercel, Inc | — | Provision of hosting services |
Supabase's own group companies listed as subprocessors (1)
| Company | Country | Purpose |
|---|---|---|
| Supabase, Inc. | — | Provision of support services |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · supabase.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC module 1 |
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | SCC module 4 |
| Transfer mechanism | Swiss FADP clauses |
| Transfer mechanism | UK Addendum |
| Notice of new subprocessors | At least 30 days' notice of proposed changes, to customers who subscribe to notifications via the Subprocessor List page |
| If you object to one | If no mutually acceptable resolution within a reasonable timeframe not exceeding 30 days, customer may terminate the portion of the Agreement for the affected Services |
| If you object to one | Written objection within 5 days of notice; parties work in good faith on a resolution; if none within a reasonable time (max 30 days), customer may terminate the affected portion of the Agreement |
| Obligations passed to subprocessors | written agreement with each Authorized Sub-processor with data protection obligations no less protective than this DPA; Supabase remains liable |
| Breach notification | without undue delay and, where feasible, within 48 hours |
| Deletion when the service ends | deletes all copies of Covered Data, including those held by Authorized Sub-processors, when the Retention Period ends (30 days after the Agreement expires) |
| Getting your data back | on Customer's request within 30 days of the Agreement's expiry (the Retention Period), a copy of all Covered Data in a commonly used format or self-service download |
| Requests from data subjects | promptly notifies Customer of requests received; does not respond except to say the request was forwarded to Customer; provides reasonable assistance |
| Audit | Audit Reports (certifications/documentation) on request, accepted in lieu if dated within 12 months; otherwise customer audit no more than once per calendar year, on 30 days' written notice, during business hours, at customer's sole expense; third-party auditor permitted |
| Processing on your instructions | only on behalf of and under Customer's instructions; the Agreement and DPA constitute those instructions |
| Confidentiality of staff | personnel with access are subject to protective obligations, including duties of confidentiality |
| Security measures | appropriate technical and organizational measures meeting the minimum standards in Schedule 1 |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Version 1 — August 1, 2026
at supabase.com
Version 1 · Last updated 2026-08-01
This version is in our copies from 2026-10-09.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
Does Supabase have a SOC 2 report?
Supabase says a SOC 2 Type 2 report is available on request. We read this on 2026-10-08.
- Available on request “Supabase is SOC 2 Type 2 compliant. This is an important security policy when handling sensitive customer data. Enterprise and Team customers can access our SOC 2 Type 2 report on the dashboard.”
Source: supabase.com, 2026-10-08
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
Is Supabase ISO 27001 certified?
Supabase states ISO/IEC 27001 certification, and says the certificate or audit report is available on request. We read this on 2026-10-08.
- Available on request “Supabase is ISO 27001 certified.”
Source: supabase.com, 2026-10-08
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| GDPR | Claimed | Projects hosted in EU regions keep your primary database data in-region, and a Data Processing Agreement (DPA) is available | supabase.com | 2026-10-08 |
| HIPAA | Claimed | You can store Protected Health Information (PHI) on our hosted platform once you enter into a Business Associate Agreement (BAA) with us and fulfill your HIPAA obligations under our shared responsibility model. | supabase.com | 2026-10-08 |
| ISO 27001 · ISO27001 | Available on request | information security management systems (ISMS); Enterprise and Team customers can access our ISO 27001 certificate on the dashboard. | supabase.com | 2026-10-08 |
| SOC 2 Type 2 · SOC2T2 | Available on request | Enterprise and Team customers can access our SOC 2 Type 2 report on the dashboard. | supabase.com | 2026-10-08 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- Data Privacy Framework List (US): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Supabase; Supabase Pte. Ltd.
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| Self-hosted Supabase | — | Not declared | unknown | supabase.com | 2026-10-19 |
Vulnerability reporting: hackerone.com (security.txt, no Expires field; read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-10-08 |
| dpa | Public | full | 200 | 2026-10-09 |
| lifecycle | Public | full | 200 | 2026-10-19 |
| residency | Public | full | 200 | 2026-10-08 |
| subprocessors | Public | full | 200 | 2026-10-08 |
| tia | Public | full | 200 | 2026-10-20 |
History
Nothing has moved since we started watching this vendor on 2026-10-08. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.