Is my v0 app safe?
You cannot tell from using it. The issues that matter live in the shipped code, the response headers, and the database behind your app, none of which are visible in the normal view. This page tests the live app for you.
Check your v0 app now
What it means
Your database tables can be read by anyone, not just logged-in users. Someone could open your app's data — customer emails, orders, private records — without ever creating an account.
Why AI tools cause it
Supabase only protects a table once you turn on Row Level Security (RLS) and write access rules for it. AI tools frequently build a working app without doing that, so the tables are wide open by default.
How xlogs checks it
xlogs finds your public Supabase URL and anon key in your app (the same ones your frontend uses), asks the database as an anonymous user which tables it can read, and flags any that return real rows. Read-only: it never writes or deletes.
What to actually check on a v0 app
Start with the database: if your v0 app uses Supabase, confirm an anonymous request cannot read your tables. Then check the frontend: no secret keys in the bundle, no public source maps, and the standard security headers in place.
The scan below does all of that in one pass and hands you a plain-English fix for anything it flags.
How to fix it
The goal: Row Level Security is enabled on every table, with policies so a table only returns rows to users allowed to see them; no table returns private data to an anonymous request.
- Enable Row Level Security (RLS) on every table, especially the affected spot
- Add a policy per table so only authenticated users can read/write their own rows (keep intentionally-public tables public on purpose)
- Re-check that an anonymous request no longer returns private rows
In my app (the spot the scan shows): anyone can read this database table. Please make this true: Row Level Security is enabled on every table, with policies so a table only returns rows to users allowed to see them; no table returns private data to an anonymous request. Steps: Enable Row Level Security (RLS) on every table, especially the spot the scan shows; Add a policy per table so only authenticated users can read/write their own rows (keep intentionally-public tables public on purpose); Re-check that an anonymous request no longer returns private rows. Then tell me exactly what you changed, and do not print any secret values back to me.
Then verify: After you deploy the policies, xlogs repeats the same anonymous read test and confirms the table no longer returns data without a login.
Full step-by-step fix guide, with a copy-paste block for each AI tool →
Common questions
Is a v0 app on Vercel automatically secure?
No. Hosting on Vercel handles things like HTTPS, but it does not set your database access rules, remove source maps, or add a Content-Security-Policy. Those are app-level choices. The scan tells you which ones are missing on your app.