Privacy

Signing in stores your email address and nothing else. There is no password: you get a magic link, and Supabase — the database and authentication service Uzers runs on — handles the session. Your email is how your projects are identified as yours and how we reach you if something about your account needs saying.

Everything you create is scoped to your account at the database level, not in application code. Every table has row-level security switched on, so a query for a project that is not yours returns nothing rather than relying on a check somewhere in the app that someone could forget to write.

Your project descriptions, price lines, your own questions for a panel, the assumptions you set and the notes you add to a brief are stored so the product can work and so you can come back to them. They are yours. They are not used to train any model, not sold, and not shared with anyone.

One exception, and you choose it: a project can be published as a public example, which puts it on the leaderboard and makes its brief readable by anyone with the link. That only happens if you ask for it. It cannot be switched on from the browser at all — the database refuses the write from a signed-in user, so it takes a deliberate action on our side.

Delete a project and its segments, panels, runs and briefs go with it.

Stripe takes payments. Card numbers are entered on Stripe’s own checkout page and never touch Uzers — we never see them, and there is nowhere in this system they could be stored.

What we keep is what is needed to know you paid: a Stripe checkout session ID, a payment intent ID, and the time the payment cleared. Stripe’s own privacy policy covers what they hold, and their terms govern the payment itself.

Generating segments, personas and their reactions means sending your project description and price line to model providers. Uzers uses Anthropic (Claude) for segments, personas, reactions and summaries, and OpenAI for an optional second-opinion panel that is off unless switched on.

That means your pitch text leaves our systems and reaches those providers as part of a request. It is sent to produce your results, and to each provider’s API under their commercial terms — not to their consumer products. We do not send your email address or any account identifier with it: a model only ever sees the text of the project.

If a pitch contains something you would not want a third-party API to process, do not put it in the box.

When you override one of our default numbers — a conversion rate, a market size — we record that an override happened, so defaults can improve for people working in the same vertical and market. This is the only thing in Uzers that pools across accounts, and it is built so that pooling cannot leak backwards.

The log of those overrides has row-level security switched on and no read policy whatsoever. Not a restrictive one: none. No account can read a single row of it, including yours — it exists only to be aggregated. A nightly job rolls it up by vertical, market, segment role and field, counting each founder once per field no matter how many times they saved, and the aggregate only ever becomes a default once at least thirty distinct founders sit behind it.

What is recorded is the number, the field, the vertical and the market. What is never exposed is who typed it. And if you reset a figure back to our default, nothing is logged at all — that tells us nothing worth keeping.

Cost-per-click, search volume and competition figures come from the Google Ads API, through its keyword planning endpoints. That access is read-only and it is used for one thing: looking up what keywords cost.

No advertiser account data is accessed. Uzers does not read campaigns, does not read spend, does not read performance, and cannot create or change an ad. It does not connect to your Google Ads account and never asks you to link one.

Keyword figures are cached for thirty days so the same lookup is not repeated. The cache holds keywords and their market — nothing about you.

No advertising trackers, no analytics pixels, no third-party cookies, no selling or sharing of personal data, and no profiling of you. The only cookie Uzers sets is the one that keeps you signed in.

Ask for a copy of what is held about you, ask for it corrected, or ask for your account and everything in it deleted: email the.edry@gmail.com and it gets done. There is no form and no retention period to wait out.