Security and trust

Make it clear what happens to user data, prompts, files, and code.

Before launch, users need plain answers about privacy, uploads, authentication, billing, exports, and whether generated code belongs to them.

Launch ready

Private

projects by default

Yours

generated code

Stripe

billing handled

Plain language

Use short answers that normal users can understand.

Provider clarity

Name the systems used for auth, billing, hosting, database, and AI.

Action paths

Link users to privacy, terms, contact, and account settings.

Security and trust

What this page should answer

This is a buying-confidence page for serious users and teams.

Default

Projects stay private unless the user publishes or shares a specific link.

Inputs

Images and references are used to understand the requested app and are tied to the user's project.

Models

Prompts and references are sent to model providers only to generate or refine the requested output.

Generated app code belongs to the customer with no attribution requirement.

Auth

Account sessions and sign-in are handled through Clerk.

Payments

Payments, invoices, and card data are handled through Stripe.

Trust checklist

Use short answers that normal users can understand.

Name the systems used for auth, billing, hosting, database, and AI.

Link users to privacy, terms, contact, and account settings.

Start from the dashboard, choose a template, or use the docs if you want the details first.