Is my v0 app secure?
v0 writes the app and Vercel deploys it, with databases one click away. The line to watch is between the variables the server keeps and the ones the browser receives.
What v0 handles.
| Deployment on Vercel, served over HTTPS |
| One-click database integrations, including Supabase, Neon, Upstash and Vercel Blob |
| Environment variables added to the project by each integration, managed in project settings |
From the platform’s own documentation: v0 docs: Databases · Vercel docs: Framework environment variables
What stays yours.
| Which variables carry a public prefix, and so reach the browser |
| Row level security on the database tables, when the database is Supabase |
| Authorization in every API route and server action |
| Who can open preview deployments that hold real data |
| Security headers on the deployed app |
Documented.
Public reports that involve v0 or apps built on it, dated and linked. Each line says what its source says, and nothing more.
| June 2, 2026 | A scan of 1,072 Supabase-backed apps Symbiotic Security scanned 1,072 apps built with Lovable, v0, Bolt.new, Replit and Windsurf that use Supabase. It reports that 98% had at least one vulnerability, 308 exposed the anon key in JavaScript, 172 allowed data to be changed or deleted without signing in, and 197 had a CORS misconfiguration on the Supabase API. Source: Symbiotic Security, June 2, 2026 |
| May 8, 2026 | A scan of 5,600 live apps built with AI tools VentureBeat reports that Escape.tech scanned 5,600 publicly available apps built with AI tools in October 2025 and found more than 2,000 high-impact vulnerabilities, over 400 exposed secrets and 175 instances of exposed personal data. The report does not break the results down by platform. Source: VentureBeat, May 8, 2026 |
A five minute check.
In your own v0 dashboard, in this order.
| List the public variables | Open Project menu, Settings, Environment Variables. Any name starting with NEXT_PUBLIC_ (or the framework’s public prefix) ships to the browser, so none of them can be a secret. |
| Find the privileged keys | A Supabase secret or service_role key should appear only in server code: route handlers and server actions, never in a component the browser loads. |
| Check row level security | If Supabase is connected, open its dashboard and confirm RLS is on for every table in the public schema. |
| Read one API route | Open the route that returns customer data and confirm it checks the signed-in user on the server before answering. |
| Check preview links | Preview deployments get their own URLs. If they connect to real data, confirm in Vercel that they are protected. |
Questions.
Is it safe that v0 added keys to my project?
Integration keys are stored as environment variables, which is the right place. The risk is a secret key given a public prefix, or imported into code that runs in the browser.
Does Vercel secure my database?
Vercel hosts the app. Access to rows in the database is decided by the database: in Supabase, by row level security policies you set.
Can I keep generating with v0 after a fix?
Yes. Tests on the paths that touch money and customer data keep the next generation from quietly undoing a fix.
Check the public side now.
Ten seconds. We read only what any visitor’s browser already sees, and store nothing.
Opens the app security check on this site with your address filled in.
Check it on every push.
Add the 7IT Guard check to your repository. After every deploy it checks the live app from outside, preview and production, and keeps one comment on the pull request up to date. Nothing from your code is read or sent.
Add it to your repository.
Pick where your app deploys:
# .github/workflows/7it-guard.yml
name: 7IT Guard
on: deployment_status
permissions:
id-token: write
contents: write
pull-requests: write
jobs:
guard:
if: github.event.deployment_status.state == 'success'
runs-on: ubuntu-latest
steps:
- uses: XLSV777/7it-guard-check@v1
with:
site: https://yourapp.com# .github/workflows/7it-guard.yml
name: 7IT Guard
on:
push:
branches: [main]
pull_request:
permissions:
id-token: write
contents: write
pull-requests: write
jobs:
guard:
runs-on: ubuntu-latest
steps:
- uses: XLSV777/7it-guard-check@v1
with:
site: https://yourapp.comSave it as .github/workflows/7it-guard.yml with your own address. It never fails a build unless you set on-problem: block. Inputs and examples
Ask your AI builder.
Connect 7IT Guard once inside your builder, then ask in the chat:
Using 7IT Guard, check that my app is safe before I publish. Show me the 7IT Guard result as it is. My app: myapp.comEach guide shows where to add the connector and how to read the 7IT Guard answer.
Launch Review
Your AI built it. Nobody checked it. I will.
A senior engineer goes through your live app and tells you what is leaking, what is broken and what to fix first, with the exact prompt that fixes it. Written report in 48 hours.
- Fixed price
- Database rules, keys, payments, email
- Money back if nothing needs fixing
How it works, in four steps.
| Scan | Check the protections any visitor’s browser can see, then run the deeper scan on an app you prove is yours.Ten seconds, on this site | Run the scan |
| AI-Build Audit | A signed report within 48 hours: what is exposed, what you own, and the order to fix it in.Fixed price · 48 hours | Ask for the audit |
| Fix | The report’s list, fixed for a set price by a set date. If we miss the target, the next week is on me.Fixed price and date | Ask about the fix |
| Guard | A weekly automated scan, dependency and model updates, a monthly senior review, and one named person who answers.Monthly | Ask about Guard |