Privacy by design
Health data is some of the most sensitive data there is. Plotoo is built so that yours never has to leave your device.
Nothing is uploaded, ever
Whatever you drop in — an Apple Health export.xml, a Google Takeout folder, a CGM or recovery CSV, or a .FIT/.TCX file — is read and parsed entirely inside your browser, in a background worker. It is never sent to a server — there is no backend for this app to send it to.
No accounts, no analytics, no tracking
There's no sign-up, no login, and no analytics or tracking scripts. The app doesn't know who you are, and no network requests carry your health data.
A local cache, fully under your control
After parsing, a summarized copy of your data is cached in your browser's IndexedDB storage so you don't have to re-upload your export every time you open the app. This cache lives only on your device. You can clear it at any time with the “Clear data” button in the app header — this immediately and permanently deletes the cached copy.
Large files, handled responsibly
Some exports — especially Apple Health and years of Fitbit/Google Takeout data — can be hundreds of megabytes to several gigabytes. Parsing happens in a background thread (a Web Worker) so the interface stays responsive, and only the summarized results — not the raw files — are kept afterward.
Open processing, no surprises
Every chart you see is computed from your cached summary using the same logic that runs in your browser. If you clear your data or revoke the file, the app returns to its empty state with nothing left behind.
Subscriptions are kept separate from your health data
Each dashboard requires an active subscription (or an all-access plan). The only network requests this involves are checking your license key(s) with Lemon Squeezy when you activate them and periodically afterward — your health data is never included in these requests, and Lemon Squeezy never sees it. You can remove a license from a device at any time from the dashboard hub.