The paperwork

Privacy Policy

Last updated August 3, 2026

The short version: we collect what it takes to build and run your app, we send what you tell us to the AI providers that write your code, we never sell it, and you can ask support for a copy or deletion.

What we collect

Your account details: name, email, and a securely hashed password. We never see or store the password itself.

What you tell us in the interview: your business name, sector, website address, and your answers, which we use to write your proposal and build your demo.

Billing happens through Stripe. Card numbers go to Stripe, never to our servers; we keep only the subscription state Stripe reports back, such as your plan, its status, and your Stripe customer id.

Service records: your sign-in sessions, including the IP address and browser they were created from; a usage ledger when your plan draws on metered outside services; and a record of each build, which holds the details we sent to the model, the build log, and a copy of the source code it produced.

Cookies

We use two, and neither is for advertising. There are no analytics or tracking scripts on this site.

A sign-in cookie keeps you signed in. That session lasts 30 days and refreshes while you keep using the app.

A guest cookie named bb_guest remembers raises you started before making an account, so you can claim them when you register. It holds the id and claim token for those raises, scripts in your browser cannot read it, and it expires after 30 days. That expiry ends your browser's claim on a raise; it does not delete the raise. Deletion is a separate thing, covered below.

How we use it

To run BarnBuilder for you: writing your proposal, raising your demo, billing your plan, and emailing you the things you would expect, like password resets, a welcome note, and word that your demo is ready. We do not sell your data, and we do not send marketing you did not ask for.

AI, and how your app actually gets built

Building your app means sending your content to AI models that we do not run ourselves. This is the most important thing on this page, so here it is plainly.

When you approve a proposal, the details of your raise (your business name, your name, your sector, your interview answers, your website address, and your brand colors) are sent through the Vercel AI Gateway to a model from Anthropic, xAI, or Moonshot AI, and that model writes your app's code. The optional smart rewrite of your proposal sends the same sort of detail to Anthropic. The rewrite is open to guests, so this can happen before you ever make an account.

The build runs in a Vercel Sandbox: a temporary, isolated machine that installs the generated code and checks that it works. The finished demo is then deployed to Vercel at a public web address.

We do not train any model on your content, and we do not sell it. Each of these providers handles what it receives under its own terms.

Your demo is public

A demo is deployed to a public web address with no sign-in, and that address is usually a plain version of your business name. That is on purpose: it is a link you can send to anyone. It also means a demo is not the place for real customer records, anything confidential, or anything you would not put on a public page. Demos are built with sample data, and they can be reset or rebuilt.

Who else touches it

A short list of services runs BarnBuilder under the hood, and each receives only what its job needs. BarnBuilder is operated from the United States and intended for businesses there, and these services hold your data on our behalf in the United States. We do not currently offer BarnBuilder to customers in the European Union or the United Kingdom.

Vercel: hosting for this site, the AI Gateway your build runs through, the sandbox your build runs in, private storage for build artifacts, and hosting for your deployed demo. Neon: the database holding your account and your raises. Stripe: payments and card details. Resend: the email we send you. Anthropic, xAI, and Moonshot AI: the models that rewrite your proposal and write your app's code.

If we add or change a service that handles your content, we will update this page.

How long we keep it

Raises on an account stay until you ask support to delete them or close the account. Archiving is the everyday in-app control: it hides a raise from your barn book and switches off its demo link, but it does not erase the raise.

Unclaimed guest raises are deleted automatically once they have sat untouched for 90 days without ever reaching a live demo. If a guest raise was abandoned on the first question or two, with almost nothing in it, that timer is 14 days instead, which is still well past the 30 days your browser remembers it for. A guest raise that did get a demo, and any raise attached to an account, is not on either timer.

Behind a build we keep some working parts for a while, then clear them on a schedule. The copy of your app's generated code, and the record of what you told us that we sent to the AI, are removed about 30 days after a build. The temporary machine a build ran on is removed within about 7 days. Your deployed demo itself stays up so it keeps working, and the billing record of a build is kept. If you want a demo taken down sooner, email us and we will do it.

There is no self-service hard deletion or account deletion in the app. If you want a raise permanently deleted, or want your account and its data closed and deleted, email support@dreamforgeworld.com and we will handle the request.

Your choices

You can read your answers, your proposal, and your raises inside the app, archive and restore raises, and correct your details. Archive hides a raise but does not erase it. For things the app does not show you, like a build log or your usage ledger, ask us and we will send you a copy. You can request permanent raise deletion or account closure at any time by emailing support@dreamforgeworld.com.

Questions

Write to us at support@dreamforgeworld.com. A person reads it.

See also our Terms of Service.