4 ms·
Show HN: Paintracker.ca, a PWA pain tracker that keeps data on device by default
Hi HN, I built https://paintracker.ca https://paintracker.ca. It is an offline first, privacy first PWA for tracking chronic pain and related symptoms.
I made it because on bad days you do not want a whole app. You want something that opens fast, lets you log in a few taps, works even if you are offline, and does not force you into an account just to start.
A lot of tracking apps assume cloud accounts and constant connectivity. I wanted something that still works when you are exhausted, in pain, or traveling without reliable internet, and does not turn health data into default telemetry.
What it does
Quick logging for pain and symptoms, with optional context like sleep, triggers, meds, and notes
Installable PWA that works offline and stores data locally by default
Exports are available in CSV, JSON, PDF, and FHIR, and what is available may vary by plan
Optional paid tier for advanced features, but I am trying to keep the free core tracker genuinely useful
Privacy stance (high level)
Core tracking is local first on device. Optional features like weather correlation and subscriptions make network calls only when you enable or use them.
Optional analytics is opt in, disabled unless explicitly enabled and consented.
Data minimization, the app tries not to collect anything you do not explicitly use
Who it is for and who it is not for
For chronic pain, injury recovery, flare tracking, appointment prep, and keeping a clean history you can reference
Not for diagnosis, emergency use, or anything that replaces clinical judgment
Links
App https://paintracker.ca https://paintracker.ca
Blog and docs https://blog.paintracker.ca https://blog.paintracker.ca
Feedback I would love (blunt is fine)
1) If you have used trackers before, does the daily logging flow feel lightweight enough when you feel awful? Where does it drag?
2) Are the exports actually usable for clinicians or insurers, or would you want a different shape like a timeline, SOAP style, summaries, or graphs?
CrisisCore Systems
- footy 9mo agoI read the blog post linked at the top of your app and I just wanted to say I love your approach to privacy. I'm lucky enough to not be a good test user for this, but keep going. The crisis button seems like a great idea to me.
- crisiscore_sys 9mo agoThanks, I really appreciate that. Privacy is the hill I am building this on. If you have a quick instinct on the crisis button, I would love it. Should it stay fully local as a grounding checklist with quick contacts, or is there something you would expect it to do that still fits a privacy first tool.
- footy 9mo agoI'd think local contacts make sense. My instinct is also to say people should be able to add personal contacts they'd want to connect with in times of crisis (because when you're IN crisis you can't think of this, but when you aren't maybe you can) though of course I can see how that could make SOME people feel worse depending on wording.
- crisiscore_sys 9mo agoIf anyone wants the implementation details: the default mode is local-first storage with offline support (PWA). I’m deliberately trying to avoid “health data as telemetry.” Network usage is feature-scoped (e.g., correlation features only when enabled). If there are specific threat-model questions you want answered (“what do you store”, “where”, “how do exports work”), ask and I’ll be precise.