Privacy, plainly.
JFDS collects as little as it can. This page lists all of it: what is stored, where it lives, and how to take it out. Effective 21 July 2026.
Who runs JFDS
JFDS is an independent app. For anything on this page, email peter@justfds.com. That address is also the support contact inside the app.
What JFDS stores about you
Your Google sign-in. JFDS accounts work through Google. When you sign in, JFDS stores the name, email address and user id that Google shares. This identifies your account and nothing else; JFDS never posts anywhere or reads anything else from your Google account.
The reps you log. Every set you log (movement, reps, time of day) is saved to your account so your streak and history work on all your devices. This is the product. It is yours, and you can export or delete all of it at any time (see Your data, your call below).
Anonymous analytics
JFDS counts product events (a set logged, a day cleared, the app installed) with PostHog, hosted in the EU, in cookieless mode. Nothing is stored on your device for this, there is no fingerprinting, and events are not linked to your account. The temporary event id rotates daily on the web and every launch in the app, so events cannot be joined into a profile of you.
These are aggregate tallies that answer one question: is the app working and being used. They are never sold, never shared with advertisers, and never tied back to you.
Error reports
If JFDS crashes or a save fails, a technical error report goes to Sentry, hosted in the EU. Reports carry the error and app state around it, not your name, email or workout history. No session replay, no performance tracking.
What sits on your device
JFDS keeps a local copy of your own log on your device so the app works offline, plus your sign-in session, your theme choice, and the app shell itself if you install it. All of it exists so the app functions; none of it tracks you. JFDS sets no advertising or tracking cookies.
One note if you use a shared computer: the offline copy of your log lives in that browser. Deleting your account clears it from the browser you delete from (best effort: a second open JFDS tab can block it). On other devices the app signs out and can no longer read the log; clear the browser’s site data there if you want the local copy gone as well.
Where your data lives
Your log lives in Google’s Firestore database in the EU (the eur3 region); your sign-in is handled by Google’s Firebase Authentication. Analytics events: PostHog, EU servers. Error reports: Sentry, EU servers. If you open an embedded technique video in the Reference tab, that video streams from YouTube under YouTube’s own terms; JFDS sends YouTube nothing about you.
How long things are kept
Your log and account: until you delete them.
Recovery backups: JFDS keeps rolling backups so a bug cannot destroy everyone’s streaks. A deleted account falls out of every backup within 14 days.
Sign-in records: Google’s Firebase Authentication keeps its own record of a deleted account for up to 180 days, per Google’s data retention policy.
Analytics and error events: kept for fixed periods, then deleted automatically (error reports: 90 days; analytics events: one year). They were never linked to your account in the first place.
Email: if you write to peter@justfds.com, the thread is kept like any correspondence.
Your data, your call
Export. Settings has a Download my data button. It hands you a JSON file with your account details and every set you ever logged. No request forms, no waiting.
Delete. Settings has a Delete account flow (also at app.justfds.com/delete-account). It permanently removes your log, your account record and your sign-in, after confirming with Google that it is really you. There is no undo.
Anything else (a question, a complaint, a right you want to exercise that is not a button yet): email peter@justfds.com. If you are in the EU or UK you can also complain to your local data protection authority.
What JFDS does not do
No ads. No selling or sharing data with data brokers. No cross-site tracking. No advertising or tracking cookies. No profiling and no automated decisions about you. The legal bases for what JFDS does process are simple: your log and sign-in are needed to provide the service you signed up for, and the anonymous analytics and error reports are JFDS’s legitimate interest in keeping the app working.
When this page changes
If what JFDS collects ever changes, this page changes first and the effective date at the top moves. The promise underneath does not: as little data as possible, all of it yours to take out.