Connect v0
v0 deploys through Vercel, so connecting your Vercel account is the quickest accurate path.
How the connection works
- Connect VercelApprove the read-only integration on Vercel's own screen.
- Select deploymentYour v0 projects appear with their live addresses.
- Detection stays onEach scan re-reads the project, so a new service is noticed.
What it looks like once connected
An illustration of this connection inside your Poliogo dashboard — not live data.
Detected in this project
- STRIPE_SECRET_KEYname only — value never read
- POSTHOG_API_KEYname only — value never read
- SUPABASE_URLname only — value never read
- OPENAI_API_KEYname only — value never read
Exact permissions requested
Every permission this connection asks for, named as v0 names it on its own consent screen — so you can compare this table to what you are shown.
| Permission | Grant | What it is used for |
|---|---|---|
| Projects: Read | Read | List your projects and their production URLs. |
| Environment variables: Read (names) | Read | Read variable names to detect services. Values are never requested. |
| Deployments | Not requested | Not requested. Poliogo never deploys, redeploys or cancels anything. |
Setting it up
What you do, and what you will be looking at while you do it.
Connect Vercel
Press Connect below to link your Vercel account. Your v0 deployments appear in the project list with their live addresses.
Pick the deployment
Choose the project this product lives in. Its production URL is what your policies will name.
Or connect the repository instead
If you have pushed your v0 project to GitHub, connecting that repository gives the deeper scan: it adds the source sweep on top of the variable names, which is what finds services called without a package.
Check what it found and generate
Review the detected services, correct anything, and generate your policies.
Choose how to scan your app
Pick one. We scan your code and settings to find the services your app uses — the scan keeps that list, not your files.
In v0: Code → Push to GitHub, then pick that repository below.
Your v0 project deploys through Vercel — connect Vercel for the most accurate scan.
Connect your Vercel account
Granted on Vercel's own screen — this panel can show it, never widen it.
Connect VercelPick a deployment
Environment variables detected
STRIPE_SECRET_KEYStripePOSTHOG_API_KEYPostHogSUPABASE_URLSupabaseNames only. No value is requested, and no table in the database has a column to keep one in.
Project synced · 7 minutes agoRead my projectWhat Poliogo detects from v0
The right-hand column is the part worth reading: it is what this connection cannot reach even if we wanted it to.
What it reads
- Your project or site list, so you can pick the right one instead of typing an address.
- The production URL, which is what your policies name as the service they cover.
- Environment variable names — enough to prove which services you use.
What it never reads
- Environment variable values. They are never requested and never stored.
- Your source code — a hosting connection does not grant repository access.
- Anything writable. Nothing is deployed, changed or redeployed.
Ready to connect v0?
The free plan covers one project with no credit card. You approve everything before a single document is written.
Poliogo is a compliance management platform, not a law firm. What it produces is not legal advice. See exactly what each connection reads.