What we store, what we don't.
What stays on your device
When you save a profile, datfit writes it to your browser's
localStorage under the keys datfit:profiles,
datfit:user, datfit:session, and
datfit:avatar. None of this leaves your browser. If you
create an account with email + password, the password is hashed with
SHA-256 in your browser before being stored locally — there is no
server-side account database.
What we don't collect
- No analytics (no Google Analytics, Plausible, Fathom, or anything else)
- No third-party tracking pixels, beacons, or cookies
- No fingerprinting
- No advertising
- No selling or sharing of any data — there's nothing to sell
Uploaded charts
When you upload a size chart in upload mode, the file is read by your browser and used to display a recommendation. As of today the file isn't sent to any server — the recommendation is a simulated read. When real OCR ships, the chart will be processed server-side and discarded immediately after the response; we will not retain images.
What our hosting sees
datfit is hosted on Railway behind Fastly. Standard HTTP request logs (IP, user agent, path, status code) are kept by these providers per their own retention policies. We do not enrich, analyze, or share these logs.
Your rights
To delete everything datfit knows about you: open browser DevTools →
Application → Local Storage → https://datfit.net → delete
all datfit:* keys. Or sign out from the account dropdown
and clear site data. There is no "request my data" form because there
is nothing to request.
Contact
Questions: hello@datfit.net.
Last reviewed: 2 May 2026.