Privacy

What we keep, and who sees it.

StyleOS is a small wardrobe app run by one person, not a company. Anyone can sign up. This page says plainly what it stores, where that lives, and which other services it hands your data to. Last updated 11 September 2026.

What you give it

• Your account. Your email address, the name you chose, the public half of each passkey, and your password if you set one. The password is never stored as you typed it: the sign-in library (better-auth) keeps only a salted scrypt hash, which cannot be turned back into the password. The six-digit codes we email you are kept for a few minutes, until they are used or expire.
• Photos of clothing. The pictures you upload, and the standardised version made from each one.
• One full-body photo, if you add it. It exists so the stylist can show an outfit on you. Nothing else uses it.
• Your wardrobe. Every item and its attributes, your outfits, and the links to retailer pages you saved.
• Your profile. Height, weight, sizes, colouring, location, and the style notes you write.
• Your chats. The full history of what you asked the stylist and what it answered, plus the short memories it writes down about your taste. You can read and delete those memories on your profile page.
• Usage measurement. Google Analytics records page views and rough location from your IP address. It runs in its cookieless mode here, so it stores nothing in your browser and cannot follow you between visits.

Where it lives

Everything sits on Railway, in the operator’s account: a Postgres database for your text, and private storage buckets for your images, one of them a backup copy. Nothing is on a public bucket. Image URLs need your session cookie and only ever serve your own files.

Who else receives it

• Anthropic — your chat messages, your profile, and the wardrobe details the stylist looks up, so Claude can answer. Also the text of a retailer page, to pull out an item’s attributes.
• Google (Gemini) — your clothing photos, to standardise them; and your clothing photo together with your full-body photo, to render a try-on.
• Voyage AI — your item photos and descriptions and your stylist memories, turned into embeddings so search works.
• Firecrawl — the retailer URL you paste, so the page can be fetched and read.
• OpenWeather — the location on your profile, so the stylist can look up its forecast.
• Langfuse — a record of each request StyleOS makes to Anthropic, Google and Voyage AI: what was sent, including your messages, profile and wardrobe details, and what came back. It exists so the operator can find out why the stylist got something wrong. Each record carries your account id.
• Google (Gmail) — the emails StyleOS sends you: the code to confirm your address, the code for a sign-in with your password, and the code to reset it. They go out through Gmail, so Google processes each message, which holds your email address and the code.
• Have I Been Pwned — when you choose a password, the first five characters of a one-way hash of it, so a password known from a data breach can be refused. The password itself, and anything that identifies you, is not sent.
• Google Analytics — page views, device and browser, approximate location. No identifier that links one visit to the next.
• Railway — the host, so it holds all of the above at rest.

That is the whole list. Your data is not sold, not shared with advertisers, and not used to train anyone’s models by us. Each of those services runs under its own terms, which we do not control.

Cookies

Only the cookies that sign you in: the one that keeps you signed in, and short-lived ones that hold a step of signing in (a passkey check, or waiting for your emailed code) for a few minutes. Nothing else is stored in your browser: analytics runs without cookies, there is no advertising, and there is no tracker asking you to accept anything.

How long it is kept

Until you delete it. Delete an item and its photos go with it. An admin can ban an account, which signs it out everywhere and refuses every sign-in until the ban is lifted; the data, passkeys and password stay in place until the account is deleted. If you asked for a place on the old waitlist before signup opened, your name and email are kept only to send you one email saying StyleOS is open, and are deleted after that.

Deleting your account

On your profile page, on the web or in the iOS app, choose Delete account, type “delete” and confirm with your passkey, or with your password and an emailed code. It happens at once and cannot be undone: your wardrobe, photos, outfits, try-ons, chats, memories, profile, passkeys, password and any signup or reset codes still waiting are removed, from the database, the image storage and its backup copy. A password sign-in still waiting for its code is not removed; it expires on its own within 10 minutes. Every device and every app you connected is signed out. A second pass runs 15 minutes later to catch anything that was still being processed at that moment. It also deletes the Langfuse records of your requests, which Langfuse finishes removing within about 15 minutes. An admin removing a member does the same thing.

Two things are outside that button. The services listed above keep their own short-lived copies of what they processed, under their own API terms (Anthropic, for example, deletes API data within 30 days). And the database’s own backups age out on Railway’s schedule rather than on the spot.

What you can ask for

Ask for a copy of your data or a correction, and it will be done by hand — there is no automated export yet. Email princeupadhyay1401@gmail.com. That address is the operator and the admin, and is the only contact for this app.

Children

StyleOS is not for anyone under 16. Please do not sign up if you are younger.

Changes

If what the app does with your data changes, this page changes with it and the date at the top moves. Anything that would widen who receives your data will be said in the app before it happens.