Hi HN, I built 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 Blog and docs 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