Know where you stand.

Accounts and email verification.

Use an email address and password to sign up. If confirmation is required, check your inbox and open the verification link. The callback returns to login and then the builder. An unconfirmed email cannot create workspaces or projects in the frontend.

• Open the link on the same device to retain your draft.
• Expired links show an error; request a new verification email.
• Only /builder is accepted as the post-login destination.

Workspaces and project records.

Choose an existing authorized workspace. If you need a new workspace, create one explicitly; it is never silently created by the visitor website. New project asks for a required name and optional description.

• Project name: 1–80 trimmed characters.
• Description: up to 1,000 trimmed characters.
• Projects use the selected workspace and current user as creator; database access rules decide authorization.

Where your idea goes.

Drafts use tab-scoped browser storage. Signup makes a one-time device-local copy so the email verification tab can claim the idea. Opting to attach an idea saves it as the project description.

• No draft is sent to an AI service.
• Blocked browser storage can prevent cross-page retention.
• Do not include passwords, keys or sensitive personal information.

What is not enabled.

AI generation, live app previews, generated-code export, publishing, subscriptions and MCP connections are not enabled. The worker is a scaffold, not a functioning generator.

• No checkout or paid subscription is offered.
• Example designs are explicitly conceptual.
• No support SLA, certification or production audit is claimed.