Privacy

If you have an account

Sign-in is handled by Clerk, a separate company. We keep the identifier Clerk gives us, your email address, and your name in our database, so we can tell your rooms apart from everyone else's and know who to bill. We never see your password. Clerk uses its own cookies to keep you signed in.

If you joined from a link

Guests do not have accounts. When you open an invite link we make up a random identifier and a display name — yours to change — and keep both in a cookie on your device for 30 days, so you are still the same person when you refresh. A second small cookie remembers that you have already been asked for a name.

That identifier and name also go into the room's member list, and onto any prompt you send, so the room remembers who asked for what. Your name is visible to everyone in the room, and anything you type there is treated exactly like a signed-in member's — including the next section.

What you type is sent to an AI company

This is the disclosure that matters most. To build anything, we send the prompt, the room's recent conversation — with the names people go by in the room — and the project's files to the outside company whose AI model writes the code. For this deployment that company is [AI PROVIDER — set per deployment. The code defaults to Anthropic and can instead be configured to use DeepSeek, MiniMax, Moonshot AI, or OpenRouter]. What they do with what they receive is covered by their privacy policy, not this one.

There is no way to build without this, so if you would not hand something to an AI company, do not type it into a room.

What your room makes

The prompts everyone writes, the conversation, and the code the AI produces are all stored so the room still exists tomorrow. Everyone in the room can see all of it — that is the point of the product — and so can anyone an invite link is forwarded to. Nobody else can, unless the owner publishes the app. Who is typing and where their cursor sits is shared live but not stored.

Each build is also archived as a version you can step back to. Free rooms keep the last 5; older archives are deleted, not just hidden. Paid rooms keep all of them.

Who else is involved

Coform is assembled from a few outside services. Each one is a separate company with its own privacy policy, and each receives only the part of your data its job needs:

• Clerk — sign-in. Holds your email, your name, and how you prove you are you.
• Neon — our database. Accounts, rooms, who is in them, every prompt and who sent it, version records, and build balances.
• PartyKit, on Cloudflare — the live room. The conversation, the shared draft, and the current state of the files.
• [AI PROVIDER] — writes the code. Receives prompts, conversation, and files, as described above.
• E2B — the sandbox where the app being built actually runs and is previewed.
• Cloudflare R2 — the archived copy of each version, and published sites.
• Stripe — payments. Your card details go directly to Stripe and never pass through us; we send them your email and name and keep a reference to your subscription.

That list is everything. The app contains no advertising and no analytics trackers, and nothing in it shares your information with anyone beyond the services above.

Publishing

Publishing puts your app on a public address that anyone on the internet can open. Only the owner of a room can do this, it never happens automatically, and taking the site down removes the files.

Deleting things

Deleting a room deletes its conversation, its archived versions, its sandbox, and its published site. That happens immediately and cannot be undone. Rooms nobody has opened in a week have their sandbox shut down to save resources; the archived versions stay, so the room can still be restored.

There is no button for deleting your whole account yet. Email [CONTACT EMAIL] and it will be done by hand.

Changes

If this changes in a way that matters, we will say so here and update the date at the top rather than changing it quietly.