Privacy policy

Your photographs never leave your device. Your quiz answers and your email address do: they are saved to an account so that clearing your browser does not destroy your profile. Erasing your profile deletes both copies.

If you add a selfie, the file is read into memory in your browser and stored as a data URL alongside the rest of your profile. It is not uploaded, not analysed remotely, and not retained anywhere outside the device you are reading this on. The same is true of the before and after photographs in your gallery.

This is enforced in one place rather than promised in several: a single function assembles everything that is sent, and it removes every photograph before it does.

You can remove them at any time by signing out from your studio, which clears the entire stored profile.

Your answers, the looks you save, the products you tick off and your gallery notes are held by Supabase, our database provider, on servers in Frankfurt, Germany. An account is created for you automatically when you start the quiz; you are not asked to choose a password and you are not identified to us by name.

Each account can read and write only its own record. That is enforced by the database itself rather than by the app asking politely.

The address you give at the end of the quiz labels your profile and is stored with it. We use it to send sign-in links when you open your account on a new device, and it is passed to our payment processor if you subscribe, so that they can send you a receipt. It is not sold, and it is not shared with anyone beyond the providers named on this page.

Payments are handled by Stripe. Card details are entered into a form served by Stripe and go straight to them — they are never sent to, processed by, or stored on our servers, and we never see them. What we keep is what we need to know whether your subscription is live: the plan, its status, its renewal date, and the identifiers Stripe uses for your customer and subscription records.

Stripe is currently connected in test mode, so no real money moves and a genuine card will be declined.

There are no third-party analytics, advertising pixels or session recorders in this build. No cookies are set beyond what your browser needs to render the page.

Adding real payments or email delivery would require this policy to be rewritten again to describe those processors, and the section above on storage would need to state a legal basis for processing, a retention period, and your rights of access and erasure in the terms the GDPR uses. Treat this document as accurate for the current build only.

Questions about any of the above can go through the contact page.