Privacy

Short, because we hold very little. Last updated 29 August 2026.

What we collect

Your email address, collected by Stripe at checkout. It is the only identity we hold: uxgen has no passwords.
Your subscription state — plan, status, Stripe customer and subscription identifiers — so your agent can be told whether the tools are open.
The three answers you tap after paying (where you start, what you do, revenue band). They personalise your onboarding, and they also help us decide who we talk to and how we word our advertising.
What your agent asks the server, in order to run the tools and count your monthly allowance.

What we never do

We do not sell your data, and we do not share it with data brokers.
We never hand your email address to an advertising platform in a readable form. A purchase is reported to Meta from our server so that we can tell which campaigns pay for themselves, and the address is hashed before it leaves us — see Cookies below for exactly what goes with it.
We do not ask you to type anything into the questionnaire, so there is nothing free-form to leak.

Cookies

Where you are decides how it starts. In the United Kingdom, the European Economic Area and Switzerland, nothing is set until you say yes: the advertising pixel, and the server-side call that doubles it, are held back until you accept them in the banner. Everywhere else, including the United States, they start on. You are told so on your first visit — the same banner appears, with Decline first — and you can switch them off there, or at any time afterwards from Your privacy choices at the bottom of every page. In Europe that same link is called Cookie choice. If we cannot tell where you are — an unknown country, an anonymising proxy, Tor — you get the European treatment.
Global Privacy Control. If your browser or an extension raises the Global Privacy Control signal — we read navigator.globalPrivacyControl in the page — we treat it as a refusal and the measurement stays off, wherever in the world you are. It overrides the default; it does not override a button you pressed yourself on this site, so Accept still works if that is what you want.
Decline, and nothing leaves for Facebook — not a script, not an image, not a call — in either zone, and it stays that way on later visits.
The tool. One, and only one: the Meta pixel (fbevents.js, loaded from connect.facebook.net), paired with Meta's Conversions API, which reports the same events from our server so that an ad blocker does not silently halve the count.
The purpose. To know which advertising campaign brought you here and whether it paid for itself. That is the whole of it. We do not build audiences of you for other advertisers, and we do not use it to decide what you are shown on this site.
The data. Two cookies for Meta, written on our own domain: _fbp, a random identifier for your browser, and _fbc, the click identifier carried in the link — that one only if you arrived from an ad. What Meta receives alongside them: the page address, the name of the event (page view, checkout started, subscription), your IP address and your browser's user-agent string, and — on a purchase only, sent from our server at the moment payment succeeds — your email address and your account identifier, both hashed before they leave us.
The duration. Both cookies expire 90 days after they are set, and are refreshed on a later visit. Meta keeps the events it receives under its own retention rules, which we do not control.
One more cookie, and it is ours. uxgen_zone is written outside Europe only. It holds a single word — which privacy regime applies to you — no identifier, no profile, and no record of what you chose. It lasts 12 hours, and it is deleted the moment you show up from the United Kingdom, the EEA or Switzerland. In those countries it is never written at all: nothing whatsoever is placed on your device before you click.
Your answer is not a cookie. Accept or Decline is kept in your browser's local storage, under uxgen:consentement:v1, and it never leaves your device. Clearing your cookies therefore removes the identifiers above but not your answer — clearing this site's data, or pressing the link at the bottom of the page, changes the answer itself.
That is the whole list: two Meta cookies, one of ours, one entry in local storage. Everything else the site needs works without storing anything. We run no analytics of our own, and there is no third-party tracker beyond the one described here.

Who processes it

Stripe — payments, receipts and invoices.
Resend — the emails we send you.
Vercel — hosting, and the key-value store where accounts live.
Meta — advertising measurement, in your browser and from our server, unless you have turned it off (or, in Europe, never turned it on). Detailed under Cookies above.

Your say

Write to hello@uxgen.ai and ask for a copy of what we hold, a correction, or deletion. Deletion closes the account and cancels the subscription; billing records stay with Stripe as long as the law requires.
Cancelling is done from the Stripe receipt or by writing to us. We do not keep an account open to make leaving harder.

The data controller is UXGen AI, LLC. Its full identity is on the legal notice.

uxgen · hello@uxgen.ai · uxgen.ai