An early build, shared with a few people.
This is a working alpha. It is invitation only, it is being changed while you use it, and some of it will break. Everything below is what you are agreeing to when you sign in, written out plainly so you can decide before you upload a single photograph.
Your wardrobe is private
No other person using the app can see your pieces. There is no sharing, no public profile, and no browsing someone else's wardrobe. Photographs live in a private bucket and are read back through a route that checks the session asking for a file owns that file.
Said precisely, because the difference matters: the person running the alpha holds the database and the storage bucket, the way the operator of any service does. The app gives them a dashboard of whole-table counts with no wardrobe on it. Reaching a specific photograph means going to the database by hand, which happens to answer a support question or to fix a fault, and each time is a deliberate act with a reason behind it.
What leaves your account
Two things, both of them narrow. Each photograph you log is sent to a language model that reads its colour, category and material; that answer comes back and is stored on your piece. And your saves and discards are counted into an anonymous total across everyone using the app, which carries no account id and no garment id, and appears only once at least 3 outfits sit behind a figure.
That total is advice you can read on the Trending page. It has no effect on what the engine proposes to you. Your ranking comes from your own wardrobe and your own history, and it stays that way whether you open Trending or ignore it.
What it will get wrong
- The colour read on a photograph can miss. Bad light, a patterned fabric or a folded piece all move it. Every value is editable on the garment page, and correcting one improves what the engine argues from.
- There is a limit on how much the app will do in a day while it is in test. When it is reached, you still get the outfit and the measured reasoning behind it, with the written paragraph missing. Try the same thing again later.
- A small wardrobe gives thin proposals. The engine refuses a combination it cannot justify, so early on it may tell you what is missing more often than it dresses you.
Every claim is measured
When the app tells you two pieces work together it names the hex values it sampled, the angle between them on the colour wheel, the formality distance, and the dress code it applied. There are 5 of those codes in the reference, fixed at version 2026.1. If the data behind a claim is thin, the app says so and stops there.
Your data during the alpha
Treat it as impermanent. Schema changes during an alpha can mean a reset, and while nothing is deleted casually, you should keep your own copies of any photograph that matters to you. Ask and your account and everything in it will be removed.
Telling us it broke
Say what you did, what you expected, and what happened. A screenshot of the screen that went wrong is worth more than a description of it. Discards are useful too: the “Not for me” button is a real signal and the engine learns from it.