Two kinds of Supabase key
Supabase gives each project a key for the browser and a key for servers. Supabase's API key docs call them the publishable key (the older name is the anon key) and the secret key (the older one is service_role).
- The publishable key is meant to be public. It's in your front-end code on purpose. Requests made with it run as the
anonrole, or asauthenticatedonce a user signs in. - The secret key must never reach a browser. It runs as
service_role, which skips Row Level Security entirely. Whoever has it can read and change everything.
So "is my key public?" is the wrong question. The right ones are: is the secret key anywhere it shouldn't be, and what can the public key do?
What the public key can reach
With the public key, a stranger can call the same API your app calls. Row Level Security policies decide which rows they get back (our RLS guide explains how). The same goes for files: storage access is controlled by policies too. And database functions you expose can be called with the public key unless you take that permission away.
Settings that live outside your code
Some important switches are in the Supabase dashboard, not in your repository: whether sign-ups must confirm their email, which addresses a social login may send users back to (Supabase redirect URL docs), and your project's Site URL. Defaults that were fine during development can be wrong at launch.
What Securick checks
From your public URL, on the free scan and Pro (Free runs 46 tests, Pro 130):
- #5 Supabase service key exposed Free
- #111 Supabase personal access token exposed Free
- #112 Database connection string with password exposed Free
- #10 Secret values in public env variables Free
- #117 Sign-ups confirm the email address Pro
- #118 Phone sign-ups confirm the number Pro
- #119 Anonymous sign-ins are treated differently Pro
- #120 Social login only returns to your own site Pro
- #121 Auth Site URL isn't localhost Pro
- #68 Bot protection on sign-up form Pro
On a domain you verify, the Deep scan uses the public key your app already ships, the way an attacker would, and reports what it could reach. It counts rows and never stores your data:
- #59 Supabase tables not readable with the public key Deep
- #60 Supabase storage buckets not listable Deep
- #147 Database functions not callable by anyone Deep
- #96 Data isolation between users Deep
- #97 User files and profiles isolated Deep
- #99 Login and sign-up rate limits Deep
- #101 Edge/serverless functions require login where needed Deep
What this isn't: we don't read your RLS policies or your SQL. We test their effect from outside. A table that's safe for the public key can still have a policy mistake that only shows up for signed-in users, which is what the Deep user-isolation tests (two test logins) are for.
What a finding looks like
Anyone can read your profiles and orders tables
Fix prompt to paste into your builder
Turn on Row Level Security for the profiles and orders tables in Supabase, then add policies so each user can only read their own rows (for example: auth.uid() = user_id). Don't add a policy that allows everyone to read unless the data is really meant to be public.
Free, Pro and Deep
Free
46 tests from your public URL, 2 scans a day, no sign-up. Every finding with proof.
Pro · $10 one time
30 scans within 30 days: all 130 tests, with a fix prompt for every finding and PDF reports.
Deep · part of Pro
17 more tests (147 in total) that touch your database and signed-in users, only on a domain you verify.
Questions
Is it a problem that my Supabase URL and anon key are in my front-end code?
No, that's how Supabase is designed. The public key is meant to be there. The risk is what that key can read, which depends on your Row Level Security policies, and whether the secret service key leaked too.
Do you need my Supabase password or service key?
No. Never send us a secret key. The free and Pro scans read only public information; Deep tests use the public key your app already gives every visitor.
Why are the database tests only on verified domains?
Reading someone's database, even with a public key, is an active test. We only run it for the person who proved they own the site, and only after they agree to it.
Can you check my RLS policies directly?
Not from a public URL. We test what the policies allow from outside: what the public key can read, and on Deep, whether one test user can see another's data.