Security and privacy
Your build is yours.
What happens to everything you give the Build Room, in plain words. If anything here stops being true, we'll change this page before we change the product.
It's yours to take
- G2 claims no rights in what you build.
- Download your app's code whenever you like: three files, every line, in one page you can open in any browser.
- The download carries its own copy of the code that draws it, so it fetches no code from anywhere. Its photos and fonts still need an internet connection.
- Free means free: you never need a card to try it.
What we keep, and for how long
- Your app
- Your browser and our database: until you delete it once it is saved to your account, 2 days if it never is
- Your description
- Our inbox, and with your app while it is kept
- Your logo
- Never uploaded
- Shared links
- 30 days, or until you delete one
- Your email address
- Your account, until you delete it on the sign-in page; our inbox, until you ask us to delete it
We don't sell your information. Every row, in full
The AI that writes your app
- We use Claude, made by Anthropic, through its service for businesses. What you type, and your app's code when you ask for a change, goes there to write your app.
- Neither Anthropic nor we train AI models on it. We train no models at all.
- Anthropic deletes it within 30 days. Anything its systems flag for abuse can be kept up to two years, and the law can require longer.
- Zero data retention, a stricter arrangement Anthropic grants on request, is not in place for us. If that changes, this page will say so.
How your preview is sealed
- Your app runs in a sandboxed frame that can't read this site, its cookies or your other saved builds.
- It blocks direct requests, image beacons and form posts to other websites.
- It loads only code and fonts from this site. The code is pinned to exact versions and checked against its fingerprint before it runs.
- When you give us your website, our server reads that one page, refuses private network addresses, and treats what it copies as facts about your business, never as instructions.
- If you use the mic, your browser turns speech into text. Where it can do that on your device, we ask it to; otherwise Chrome may send the audio to Google, and Safari to Apple.
One honest limit: no web page can fully stop code from steering its own frame somewhere else. So previews only ever hold sample data, and we watch for a preview that tries and shut it down.
We review it before it goes live
- One customer can never see another's data
- Owner sign-in uses two-step verification
- No passwords or keys left in the code
- Every package is checked
- The risky code is read by a person
Before an app we build takes real customers, one of us goes through its security with you, against a fixed list. Part of every G2 build.
An app made on your own in the Build Room hasn't been security reviewed until one of us has done this with you.
Before your app goes live: the go-live security review
The Build Room makes a working preview with sample data. Putting it in front of real customers is a different job: sign-ins, permissions, payments, backups and a security check. Before an app we build takes real customers, one of us goes through its security with you, against a fixed list. Part of every G2 build.
- 01One customer can never see another's dataWe test every screen and every request with two accounts, and the second can never read or change the first one's records.
- 02Owner sign-in uses two-step verificationThrough a managed sign-in provider, with sessions that expire and passwords checked against known leaks.
- 03No passwords or keys left in the codeA scanner checks the code and the built site, and secret keys stay on the server.
- 04Every package is checkedEach one is real, pinned to a version and scanned for known problems.
- 05The risky code is read by a personAn automated code scan, then one of us reads the sign-in, payment and data-export code.
- 06Payments are verifiedPayment notices are checked as coming from the payment company, a payment can't be counted twice, and no card numbers are stored.
- 07Backups are tested with a real restoreSeparate test and live databases, keys with only the access they need, and one restore drill before launch.
- 08The security headers are set and gradedEncryption and the browser protections are switched on, and an outside scanner's grade goes in your handover.
- 09AI features are fenced inIf your app uses AI, what it writes is treated as untrusted, it gets no power to change live data, and it has spending limits.
- 10The paperwork is doneA privacy policy, data processing terms, a contact for security reports, and a one-page security summary you can show your own customers.
An app made on your own in the Build Room hasn't been security reviewed until one of us has done this with you.
Not sure what yours needs yet? A Launch Review ($249) is the first step: a 45-minute call and a written go-live plan within 3 business days: what is still pretend, what making it real takes, and the do-it-yourself route first. It is credited in full toward a build if you go ahead with us within 90 days.
Limits, and builds that fail
- Your first build is always free, and you always get at least 3 free changes a day. That still holds once the day's spending cap is reached. Only pausing the whole Build Room stops it.
- If a build fails, or you press Stop, we tell you, and it doesn't use one of your builds.
- If you refresh, lose your connection or close the tab, the build carries on, and it is waiting when you come back.
- Before a new build is shown, we check it for the mistakes that stop an app from starting, and if we find one, we repair it once, free.
- A change that fails to build doesn't use one of your changes.
- The Build Room shows how many free changes you have left.
- We cap what the free Build Room can spend each day, so one person can't run it into the ground for everyone else.
Who helps us run this
- Anthropic writes your app.
- Vercel hosts the site, keeps its logs, stores shared links (private, and encrypted at rest by Vercel) and counts page views.
- Neon runs our database, through Vercel. It holds accounts and saved builds, usage counts, cost records and the review queue for shared links.
- Google Fonts serves the typefaces in a copy of your app you download.
- Resend sends our email.
- Stripe takes payment for a Launch Review, and Cal.com books calls.
Deleting things
- A shared link: press “Delete this link” in the Build Room. It stops working at once.
- A saved build: delete it from your list in the Build Room. Every version of it goes at once, and so does any link shared from it. One that was never saved to an account is deleted after 2 days on its own. A copy in your browser goes when you clear this site's data.
- Your account: delete it on the sign-in page while signed in. It goes at once, with every saved build, every version and every link shared from them.
- Your email and anything you sent us: ask through the contact page, and we will delete it from our inbox and confirm within 5 business days.
Reporting a problem
- Something wrong on a shared page? Use “Report this page” at the bottom of it. We aim to take it down within 24 hours if it breaks our rules.
- A security issue? Tell us through the contact page. It is also listed in our security.txt.
- Everything between your browser and this site travels over an encrypted connection, and browsers are told never to use anything else.
The full detail of what we collect is on our privacy page, and the rules for using the Build Room are in our terms.