PainTracker.ca
Minimization-first chronic pain tracking
Minimization-first pain documentation built to reduce dangerous collection, keep core use on-device, and stay usable under degraded conditions.
Use this dossier as supporting evidence for the service work on this site: problem, constraints, proof surface, and outputs.
Use PainTracker as the reference path for health product review
Building a health, wellness, or symptom-tracking app? PainTracker is the reference implementation behind CrisisCore's privacy review method for sensitive health products.
If your app collects symptoms, mood, disability, medication, location, notes, exports, or clinician-ready summaries, this is the same inspection lens used to review the product boundary before launch.
People living with chronic pain need consistent documentation for themselves, clinicians, and disability processes—without turning their body into a data exhaust product.
Most trackers assume stability: always-online sync, account creation, high attention, and high trust. Those assumptions fail precisely when the user needs the tool most.
- •Degraded-first: low battery, low bandwidth, interrupted sessions.
- •Cognitive overload: reduce steps, reduce choices, preserve progress.
- •Privacy-first: avoid default data centralization; minimize third-party surfaces.
- •Reversibility: exports are explicit; user remains the authority.
- •Collection discipline: each stored category needs a clear purpose, local default, and user-visible exit.
Local-first by default: entries persist on-device using browser storage so the system remains usable offline and under partial connectivity.
Collection is bounded to the categories needed for day-to-day pain logging, with the working record staying under local user control instead of default account capture.
Sharing is user-controlled: the primary proof artifact is an explicit export that can be used for clinicians or records when the user chooses.
Retention follows the same boundary: day-to-day records persist locally until the user edits, exports, or removes them through explicit action.
- •0 account requirement for core use: users can log entries without sign-up or default account capture.
- •0 background sharing by default: exports are user-initiated and explicit.
- •A clear minimization boundary: sensitive day-to-day records stay local unless the user deliberately exports them.
- •Core logging flow remains available offline under partial connectivity.
- •A working local-first PWA surface (live deployment) designed around protective UX primitives.