Trust and legal
Account, brief, generated site, billing when you pay us. Not your Drive. Not a CRM of your customers unless you typed them into the brief.
Trust pages go purple with "256-bit" adjectives. We would rather list objects. If it is not on /privacy, do not invent it here either.
We store Google account identifiers and the content you generate so the project persists. We store what we need to bill Pro through Stripe. We do not sell that data. Customer card data on your shop is your processor's.
Identity
Google sign-in: id, name, email. So the shop is yours tomorrow.
Content
The brief, uploads, the generated site. That is the product.
Money to us
Pro $12 and domain purchases go through Stripe as hosting/registrar-related payments. That is not a cut of your GMV.
Money to you
Checkout on your payment account. We are not holding a marketplace float as a SKU.
What we do not store as a feature
A CRM of your walk-ins, a Drive mirror, analytics of your visitors as a suite. Empty cells stay empty.
Questions
[email protected], also on /privacy. Do not invent a DPO name we do not have (fake authors).
Limits and caveats
This restates the public privacy page. If they differ, /privacy wins. Not legal advice. Not a HIPAA product.
If a sentence would require a competitor SKU we have not verified, or a statistic we did not measure, it does not belong here.
What to do after you read this
If this page answered the query, open Create with the nouns from your own business, not a slogan. If it did not, you are probably in the wrong cluster: go back to the blog hub or Trust and legal. Do not spin a second URL for a synonym. One intent per page is the whole point of this library.
Tools that actually do this job
These are public pages. Use them when the job is this job. They are not a second product you have to buy.
Primary sources
Questions people actually ask
Do you train public models on my brief?
/privacy is the source. We do not sell this data.
Can I delete?
Follow the product and /privacy. Do not assume a one-click we have not shown.
Staff access?
Whoever has the Google login. See who owns the project.
Logs?
We will not invent a log-retention number. Empty cells stay empty rather than fake a SOC table.