What Builvio can access, and why

Builvio asks for access to three accounts you own so it can publish your app into them. Here is the exact scope of each, what we do with it, and how to take it back.

Before you publish: nothing

Building and previewing needs no outside accounts. Your sentence and the generated code live on our build server, and the preview runs in a sandboxed frame in your browser that cannot reach your Builvio session or any other site.

GitHub

Asked for: read:user, user:email, repo.
Used for: creating one repository for your app and pushing its code there. That’s the whole use. GitHub’s permission model is coarse: repo is the only scope that lets us create and push to a private repository, and it technically covers your other repositories too. Builvio never reads, lists, or changes any repository other than the one it created for your app.

Supabase

Asked for: an OAuth connection to your Supabase organization.
Used for: creating one database project for your app and setting up its tables and access rules. We don’t touch other projects in your organization, and your app talks to its database directly with its own keys, not through Builvio.

Vercel

Asked for: an OAuth connection to your Vercel account.
Used for: creating one hosting project linked to the repository above, setting its environment variables, and deploying. Custom domains, analytics, and billing stay in your Vercel account.

How the tokens are kept

  • Each token is encrypted at rest with AES-256-GCM under a server-side key that never leaves our infrastructure.
  • Tokens are decrypted only for the seconds a publish step needs them, on the build server, and are never sent to the AI models.
  • They are not used for anything on a schedule. If you never click Publish, they are never used at all.

Taking access back

Disconnect any account in Settings, which deletes the token on our side. You can also revoke Builvio directly at the provider: GitHub → Settings → Applications, Supabase → Organization → OAuth apps, Vercel → Settings → Integrations. Your app keeps running either way, because it lives in your accounts, not ours.

Your data

  • We keep your prompts, the code snapshots of your app, and usage records so billing and version history work.
  • Your prompt and your app’s code are sent to AI models (Anthropic, OpenAI, and others via OpenRouter) to plan and build. They are not used to train models.
  • We don’t sell data and we don’t run third-party ad trackers inside your app.
  • Card payments are handled by Stripe. We never see your card number.

Reporting a problem

Found something that looks wrong? Email support and put “security” in the subject. It is read by the person who runs Builvio, not a queue. See also the privacy policy and terms.