Concrete, plain-English description of how we protect your data and your generated code. Last reviewed 2026-10-08.
All traffic to buildliy.com is encrypted in transit with HTTPS. Database backups, project files, and uploaded assets are stored encrypted at rest by our database and storage providers.
You can sign in with Google or GitHub, or with an email and password handled by Supabase Auth. Your password goes straight from your browser to Supabase Auth, which stores only a one-way hash of it, never the password itself. Buildliy's own servers never receive it.
Hosted on Vercel and Supabase, which both maintain SOC 2 Type II reports. Sandboxed code execution runs inside isolated E2B sandboxes that shut down automatically after a period of inactivity.
Only Buildliy admins can access customer data, through tools built for fixing problems and handling support and billing — for example, reviewing a failed build and the prompt behind it. Admin actions such as refunds are logged.
All API keys and tokens (Anthropic, OpenRouter, Stripe, E2B, Supabase service role) live in our hosting provider's encrypted secret store. They are not committed to any repo and not visible to our frontend. Keys you add for your own apps are encrypted before we store them.
Per-account and per-IP rate limits protect against accidental loops and intentional abuse. A build that gets stuck or runs too long is stopped automatically.
Our main database is backed up daily, and each backup is kept for 7 days.
We use established, widely used providers for the services that handle your data, such as Vercel, Supabase, Anthropic, E2B, and Stripe. Our privacy policy lists every provider and what each one does.
Buildliy itself doesn't have a SOC 2 report. Our infrastructure providers (Vercel and Supabase) maintain SOC 2 Type II reports. Your data, including data from customers in the EU, may be processed in the United States. If you have specific compliance requirements, get in touch.
If you believe you've found a security issue, please email security@buildliy.com. We aim to acknowledge reports within 24 hours and to triage them within 72. We don't have a paid bug bounty yet.