---
title: "Check that your vibe-coded app doesn't leak user data · Proxy Mail QA"
description: "Two checks for Supabase apps built with Lovable, Bolt, v0 or Replit: a curl with the anon key, and two real accounts that try to read each other's rows."
url: https://proxymail.qa/solve/vibe-coded-app-data-leaks
---

1. [Home](https://proxymail.qa/)
2. [What we solve](https://proxymail.qa/solve)

# Check that one user can't see another user's data

In November 2026 a scan of Lovable apps found thousands whose Supabase database handed out rows to anyone with the key the page gives every browser. The fix is Row Level Security with a policy per user. The usual check, a curl with that key, only covers visitors who aren't signed in. This page covers both cases: no login, and signed in as someone else.

Updated 13 November 2026

Figures below are from Crissy Field’s report on Lovable apps, as reported by Cybernews on 4 November 2026, and from UpGuard. Supabase details are from its documentation on 5 November 2026.

## What happened

Crissy Field, a German security firm, took 159,041 Lovable apps from the Common Crawl web archive. Of the 34,545 that used Supabase, 24,664 returned database rows to a request with no login, using only the anon key each page hands the browser. In 7,403 of them those rows included email addresses, across more than 10,500 tables. One app returned over 1,000 passport records; a forum, more than 200,000 chat messages and 80,000 profiles; event and restaurant apps, orders with payment details and ticket codes.

Lovable called it an industry-wide problem with how Supabase gets set up, and it isn’t only Lovable: [UpGuard](https://www.upguard.com/blog/everything-everywhere-systemic-data-exposure-in-supabase-apps) separately found 16,326 Supabase databases with tables anyone could read. Apps from Bolt, v0, Replit, Cursor and Claude Code use the same setup, so the same checks apply.

## Two ways the data gets out

A Supabase app’s browser talks to the database directly, with a key that’s in the page for anyone to copy. Row Level Security (RLS) decides which rows each request may see. It fails in two ways:

- **No login.** RLS is off for a table, or the table was made without it. Anyone with the key can read every row, and often add, change or delete them too. This is what the scan found.
- **Signed in.** RLS is on, but a policy lets any signed-in user through, for example `using (true)` for `authenticated`. Anyone who signs up, with any address, can read every other user’s rows. A request with no login gets nothing back, so the usual check passes.

## Check 1: a request with no login

Open your app, find the Supabase project’s address and the anon or publishable key (in the page’s code or your project’s **Project Settings → API Keys**), and ask for one row from a table that holds anything about people:

Terminal

```bash
curl "https://YOUR-PROJECT.supabase.co/rest/v1/profiles?select=*&limit=1" \
  -H "apikey: YOUR_ANON_KEY" \
  -H "Authorization: Bearer YOUR_ANON_KEY"

```

- **A row comes back:** anyone can read that table. Fix it before anything else.
- **`[]` comes back:** RLS is on with no policy for visitors, or the table is empty. Add a row and try again.
- **An error saying permission denied:** that table isn’t open to visitors at all.

Do it for every table in the `public` schema, and for views: a view runs as its owner and skips RLS unless it’s made with `security_invoker`. In the SQL editor, this lists the tables with RLS off:

sql

```sql
select c.relname as table_name
from pg_class c join pg_namespace n on n.oid = c.relnamespace
where n.nspname = 'public' and c.relkind = 'r' and not c.relrowsecurity;

```

## Check 2: two real accounts

The signed-in leak only shows when one user asks for another user’s data, so you need two accounts that have both finished sign-up, email confirmation included. Proxy Mail QA gives you both:

1. Create two addresses, each with a password, and sign up with each in your app. Open each confirmation link or code from its row.
2. Signed in as account A, create something private: a note, an order, a profile detail. Copy its id from the address bar or the network tab.
3. Signed in as account B, open A’s item by its link, list the table through the app, and try the curl above with B’s session token in place of the anon key in the `Authorization` header (copy it from the network tab).
4. As B, try to change and delete A’s item, and to create an item with A’s user id.

Every one of those should fail. If B can see or change anything of A’s, a policy is too broad.

With a coding agent, connect the [Proxy Mail QA MCP server](https://proxymail.qa/docs/mcp) and ask for the same check. The agent creates the two addresses, signs up and confirms both, has each create data, tries the reads and changes above, and records each attempt in a run, so the QA report shows which ones your app refused. Some agents, including Claude, will only sign up on an app running on your computer, so run it on localhost or have the agent write a Playwright test for staging.

Prompt

```text
Using the Proxy Mail QA MCP server, start a run and create two addresses with passwords. Sign up with each on my app at http://localhost:3000 and confirm both. As the first account, create a private item. As the second, try to open it by its link, find it through the app, read it with the Supabase key and the second account's session, change it, delete it, and create an item with the first account's user id. Add a run note for each attempt saying whether the app refused it, then finish the run and give me the report.

```

Use both checks only on apps you own or are allowed to test, in development or staging.

## The policies that fix it

Each table that holds a user’s data needs a column for its owner, RLS switched on, and one policy for each of select, insert, update and delete that compares that column with the signed-in user:

sql

```sql
alter table public.notes enable row level security;

create policy "Read own notes" on public.notes
  for select to authenticated using ((select auth.uid()) = user_id);

create policy "Add own notes" on public.notes
  for insert to authenticated with check ((select auth.uid()) = user_id);

create policy "Change own notes" on public.notes
  for update to authenticated
  using ((select auth.uid()) = user_id) with check ((select auth.uid()) = user_id);

create policy "Delete own notes" on public.notes
  for delete to authenticated using ((select auth.uid()) = user_id);

```

- **No policy for `anon`** means visitors who aren’t signed in get nothing.
- **`with check` on insert and update** stops a user writing a row with someone else’s id.
- **Shared data** (a team’s projects, say) compares with a membership table instead, for example `using (team_id in (select team_id from team_members where user_id = (select auth.uid())))`.

To find policies that let every row through, run this in the SQL editor and look for `true` in either column:

sql

```sql
select tablename, policyname, cmd, roles, qual, with_check
from pg_policies where schemaname = 'public';

```

Files work the same way: check that Storage buckets holding users’ files aren’t public and have policies on `storage.objects`.

## Copy-paste prompts for your builder

Prompt

```text
List every table and view in the public schema, whether Row Level Security is on, and each policy with its roles and its using and with check expressions. Flag any table with RLS off, any view without security_invoker, and any policy that is true or doesn't compare the row's owner with auth.uid().

```

Prompt

```text
For every table that holds a user's data, switch on Row Level Security and add select, insert, update and delete policies for authenticated users that only allow rows where user_id = auth.uid(). Give anon no access unless the table is meant to be public. Show me the SQL before running it.

```

Then run both checks again, with two new accounts. More on what generated apps get wrong at sign-in in [vibe-coded login problems](https://proxymail.qa/solve/vibe-coded-login-problems), and on testing every role in [roles and permissions](https://proxymail.qa/use-cases/roles-and-permissions).

## Automating this?

With the Proxy Mail QA MCP server connected, ask your coding agent to sign up two accounts on your app on localhost or staging, have each create data, and check that neither can read or change the other's. It records each attempt in a run, so the QA report shows which ones your app refused.

[Node.js client](https://proxymail.qa/docs/node) [Python](https://proxymail.qa/docs/python) [Set up your coding agent](https://proxymail.qa/docs/api#agent-setup)

## Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

[Create a free account](https://app.proxymail.qa/?mode=signup&from=site-solve-vibe-coded-app-data-leaks)

## Questions

### My app uses Supabase and the key is in the page. Is that the leak?

No. The anon (or publishable) key is meant to be public, like a site's address. What protects the data is Row Level Security and its policies. Without them, that public key can read the tables.

### Row Level Security is on for every table. Am I done?

Not yet. A policy such as using (true) for authenticated users lets anyone who signs up read every row, and the anon-key curl won't show it. Check with two real accounts, as on this page.

### Can I run these checks on someone else's app?

No. Run them only on apps you own or are allowed to test, in development or staging. Proxy Mail QA isn't a scanner for other people's sites.

### What if a table really should be public, like a list of products?

Give it a select policy for anon and authenticated that says so, and no insert, update or delete policy for them. Keep anything about a person in a separate table with per-user policies.

## Related guides

- [Test sign-up and email verification](https://proxymail.qa/solve/email-verification-testing): A fresh, private address for every sign-up test, with the verification link or code ready the moment it lands.
- [Test OTP and one-time login codes](https://proxymail.qa/solve/otp-code-testing): Codes pulled out of the email with a Copy button and a countdown when the email says how long they last.
- [Test magic links and passwordless sign-in](https://proxymail.qa/solve/magic-link-testing): Single-use links that are never opened or prefetched on our side, so they still work when you click them.
- [Test password reset emails](https://proxymail.qa/solve/password-reset-testing): Request, receive and use reset links, and keep the new password saved next to the test account.
- [Stop sharing one Gmail inbox for QA](https://proxymail.qa/solve/shared-test-inbox): Private, disposable addresses for every tester instead of one shared mailbox and a pile of plus-addresses.
- [Stop using Gmail for test codes](https://proxymail.qa/solve/gmail-test-inbox): Why reading codes from Gmail over its API or IMAP keeps breaking your tests, and how one address per test removes the inbox from the problem.
- [Email limits in auth providers while you test](https://proxymail.qa/solve/auth-email-limits): Supabase's 2 an hour, Firebase's 5 email links a day, Auth0's 10 a minute and Clerk's 100 a month, and how to send your own.
- [Let test addresses through a disposable-email block](https://proxymail.qa/solve/disposable-email-blocks): Keep the block for real users and let your test domains through in development and staging, with one setting you can't ship by mistake.
- [CAPTCHA, Google and Apple sign-in in tests](https://proxymail.qa/solve/captcha-and-social-sign-in-tests): Published test keys for reCAPTCHA, hCaptcha and Turnstile, and what to test instead of automating Google and Apple sign-in.
- [Take QA notes by voice with Wispr Flow](https://proxymail.qa/solve/voice-notes-wispr-flow): Dictate what each test account is for, its state and what you found, straight into its notes, in seconds.
- [Test phone-first sign-up without real SMS](https://proxymail.qa/solve/phone-first-sign-up-testing): Test numbers with fixed codes, a test-mode code kept out of release builds, and why virtual numbers usually fail.
- [Test sign-up for people in China](https://proxymail.qa/solve/china-sign-up-testing): Real-name rules, a 姓名 field and province menus, a safe test code, and 身份证 numbers that can't be anyone's.
- [Test sign-up for people in Japan](https://proxymail.qa/solve/japan-sign-up-testing): Furigana fields, 全角 and 半角, postcode lookups and LINE sign-in, with test accounts that have Japanese names.
- [Made-up test accounts, not masked production data](https://proxymail.qa/solve/synthetic-test-data): A masked copy of production still holds real people. Test sign-up with made-up accounts that no one owns instead.
- [Test sign-up for people in India](https://proxymail.qa/solve/india-sign-up-testing): Test accounts with one name, PIN codes that agree with the city, phone-first sign-up, Hindi labels, ID fields and card mandates.
- [Test sign-up for people in Pakistan](https://proxymail.qa/solve/pakistan-sign-up-testing): Test accounts with Pakistani names in both scripts, CNIC fields that never hold a real number, and phone-first sign-up.
- [Fill phone and ID fields safely](https://proxymail.qa/solve/phone-id-and-tax-number-fields): Numbers set aside for fiction, your app's own test numbers, ID values that never match a real person, and KYC sandbox values, filled the same way by agents and tests.
- [Verification link points to localhost:3000](https://proxymail.qa/solve/localhost-links): Why emails from staging link to localhost, how to fix it in Supabase, Firebase and other stacks, and how we flag it.
- [Common Supabase sign-up and login problems](https://proxymail.qa/solve/supabase-auth-problems): Emails that never arrive, links that expire or sign nobody in, and sign-ups that fail, with the fix for each.
- [Common Firebase sign-up and login problems](https://proxymail.qa/solve/firebase-auth-problems): Missing verification and reset emails, verified users who still look unverified, failing links and sign-up limits, with the fix for each.
- [Sign-up and login problems in vibe-coded apps](https://proxymail.qa/solve/vibe-coded-login-problems): The login bugs AI-built apps usually ship with: emails only you receive, links to the preview, missing pages, and what to ask the builder.
- [Triage sign-up and login bug reports with an agent](https://proxymail.qa/solve/bug-report-triage): An agent signs up with a new test address, watches the inbox, and answers replicated, not replicated or inconclusive, with the evidence.
- [A self-improvement loop for agents that build sign-up](https://proxymail.qa/solve/agent-self-improvement-loop): The agent builds, signs up with a test address, reads what the email did, fixes its own work and runs again. Proxy Mail QA is the tool it checks with.
- [Test sign-up emails in Playwright](https://proxymail.qa/solve/playwright-email-tests): A complete Playwright test for sign-up codes and links, from a fresh inbox to the report on the pull request.
- [Test sign-ups over several screens](https://proxymail.qa/solve/multi-step-sign-up-testing): One test account across every screen of the sign-up, with your form's own questions filled the same way each time.
- [Test sign-up emails in Cypress](https://proxymail.qa/solve/cypress-email-tests): A complete Cypress test for sign-up links and codes, with the email waits running as Cypress tasks.
- [Test sign-up emails with pytest](https://proxymail.qa/solve/pytest-email-tests): A complete pytest test for sign-up codes and links, with Playwright for Python or Selenium and a one-file helper.
- [Test coupon codes and welcome offers](https://proxymail.qa/solve/coupon-code-testing): The coupon with its discount, end date and arrival time, what checkout did with it, and a failure when an expired or reused one is accepted.
- [Test unsubscribe links and one-click unsubscribe](https://proxymail.qa/solve/unsubscribe-testing): The unsubscribe headers and link checked on every marketing email, and a watch that flags any marketing after unsubscribing, with no time limit.
- [Test that a welcome offer can't be claimed twice](https://proxymail.qa/solve/welcome-offer-abuse): Versions of one address that reach the same inbox, and a check that fails when the same person got the offer more than once.
- [AI sign-up page review](https://proxymail.qa/solve/ai-sign-up-page-review): Let an agent check the sign-up through to the email: delivery, the link, how it was sent, and that only one arrives.
- [AI registration page review](https://proxymail.qa/solve/ai-registration-page-review): An agent tries every field with values made for it, then finishes the registration through the email.
- [Review a sign-up page by hand](https://proxymail.qa/solve/how-to-review-my-sign-up-page): A checklist for your browser and phone, in the order that finds the most problems.
- [Review a simple sign-up form](https://proxymail.qa/solve/review-a-simple-sign-up-form): 12 checks for a form with an email, a password and perhaps a name.
- [Review a multi-page sign-up form](https://proxymail.qa/solve/review-a-multi-page-sign-up-form): One test account across every screen, and the verification email wherever it comes.
- [Review a financial sign-up form](https://proxymail.qa/solve/review-a-financial-website-sign-up-form): The emails, age and country rules and awkward values in a financial sign-up, and what needs other tools.
- [An email address for testing registration](https://proxymail.qa/solve/email-for-checking-my-registration-form): A new, real address for every registration try, with the code or link ready to use.
- [An email address for testing sign-in](https://proxymail.qa/solve/email-for-checking-my-sign-in-form): Test accounts with saved passwords and an inbox for codes, magic links and resets.
- [How long should a password be?](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be): NIST's numbers for password length and rules, and test passwords to check yours.
- [No error for a password that breaks the rules](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors): The eight usual causes of a silent password field, and how to tell which one it is.
- [Help me check my website](https://proxymail.qa/solve/help-me-check-my-website): A whole-site check in an afternoon, in the order that finds the costliest problems first.
- [Tools to build and check a website](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website): A toolkit by area, most of it free and none of it ours, except for account emails.
- [What tools do I need for a website?](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website): The full list, then which parts a simple site can skip.

[Built your app with an AI tool? Pick yours](https://proxymail.qa/built-with)

Lovable, Bolt, v0, Replit, Base44 and Supabase are products of their owners. Proxy Mail QA is independent and isn’t affiliated with or endorsed by them.
