Answers before you commit.

It collects a launch audience and keeps one record per person. That record holds the consent, the answers they gave, the verification state, where they came from, and what you have sent them.

No. Publish a hosted campaign page and you can start collecting the day you decide. If you do have a site, embed the form there instead with one script.

No. The free workspace needs no purchase and no card.

Yes. The demo gallery runs on synthetic data and creates no account, so you can see the real screens before you sign up.

A hosted campaign takes minutes: name it, add the questions you want, and publish. Connecting your own domain takes longer because DNS has to verify.

Yes. Free includes one live campaign, the hosted page, the embed, and up to 100 active signups.

The campaign stops accepting new signups. Everything already collected stays exactly as it is, and upgrading the workspace removes the cap.

Through Stripe, for the selected workspace. The subscription covers that workspace and the collaborators it allows.

Yes, from the workspace billing settings. Your audience data remains yours, and export is how you take it with you.

Not in the first release. WaitForge validates pre-launch demand. It does not process transactions, refunds, disputes, shipping, or fulfilment for campaign owners.

Yes, on the paid plans. The export carries the consent record, the attribution, the qualification answers, and the launch handoff fields — not just addresses.

You do. WaitForge processes it on your behalf so that you can run your launch.

Yes, and this one is not a promise you have to take on faith. Separation is enforced on every query, and the claim is backed by automated audits that fail the build if they stop passing.

That somebody controls the address they gave you. An unverified list is a delivery problem waiting for launch day.

Yes. Invite people into the workspace and give each the role that fits what they should reach.

Yes. Each campaign is separate inside the workspace, which is how a studio keeps one client's launch away from another's.

No. The security page documents implemented product controls. It does not imply SOC 2, ISO 27001, or any other certification that has not been completed.

On the security page and in the public tenant-isolation guide. Those pages are bound to automated audits. Changing the claim requires changing the check.

Yes. Add the domain, add the verification record, and the campaign serves from your hostname once it verifies.

Yes. Read and write the audience from your own systems, so a custom signup flow does not mean a custom database.

Signed webhooks push each event to your endpoint, signed so your receiver can verify it came from us. Nobody copies rows by hand.

Each signup gets a link, and anyone who joins through it attaches to the record that already exists rather than starting a new one.