Connect Vercel
Connect your Vercel account to confirm which deployment your policies cover — no repository access needed.
How the connection works
- Connect accountApprove the integration on the provider's own screen.
- Select projectYour projects and their production URLs are listed for you.
- Detection stays onVariable names are re-read on each scan, 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 Vercel 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 your Vercel account
Press Connect Vercel below and approve the read-only integration. Poliogo only ever lists your projects.
Pick a project
Your projects and their production URLs are listed for you — nothing to type or misremember. The URL you pick is the one your policies will name as the service they cover.
Let it read the variable names
Poliogo reads the names of your environment variables and never the values. A variable called STRIPE_SECRET_KEY proves you take payments; its contents are neither requested nor stored, and no table in the database has a column to keep one in.
Check what it found and generate
Review the detected list and generate your documents.
Want the deeper scan? Add the repo
Variable names prove which services exist; the source sweep proves how they are called, including raw fetch calls with no SDK. Connecting the repository Vercel deploys from adds that on top — the two connections coexist on one project.
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.
Connect your Vercel account and pick a project — nothing to type.
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 · 3 minutes agoRead my projectWhat Poliogo detects from Vercel
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 Vercel?
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.