Daily Fashion
Privacy, in plain words.
What the app stores, what it can send, and who controls each part. Short enough to actually read.
Your log never leaves your device
Photographs, written notes, how your days felt, your training numbers, outfit costs — all of it is stored only on your device, in your browser or app's own storage. There is no account, no sign-up, and no server that holds any of it. Our server has no endpoint shaped like a photo or a note, and an automated test fails our builds if the log ever gains a way out.
You can export everything as an ordinary zip at any time, optionally sealed with a passphrase only you know. Deleting the app, or using “delete everything” in Settings, removes the log completely — we cannot recover it for you, because we never had it.
Usage sharing is off until you turn it on
In Settings there is a switch called “Share usage counts with us”. It ships off. If you turn it on, the app sends us event names — “a photo was taken today”, “a card was shared” — under a random identifier created at that moment. Never the photo, never a note, never how a day felt.
Next to that switch is an optional form where you can tell us an age range, gender, location and profession. Every field is optional, it is sent only when you press the button, and it is linked only to the same random identifier. Turning the switch off stops all of it — the very next event is not sent.
To have the server-side data behind your identifier deleted, contact us through the repository below and include the app’s share-usage identifier from Settings; we delete on request.
Offers are ours, not a network’s
The Offers page shows sponsor placements we put in our own database, served from our own domain. There is no advertising network, no tracking pixel, and no third-party script anywhere in the app — the security policy the app runs under refuses every request to any domain that is not ours, so nothing on that page can follow you.
The front page counts visits, anonymously
The dailyfashion.co front page records that it was viewed and that a button on it was pressed — to our own database, under one constant label shared by every visitor. No cookie, no per-visitor identifier, no third-party analytics service. It cannot tell one visitor from another, and it does not try to.
Third parties
The app makes no request to any third party. Links you choose to tap — the community, an offer, this repository — open in your browser and are governed by those sites from that point on. Our hosting provider (Railway) processes network traffic to serve the site, as any host does.