Minimization-first pain documentation built to reduce dangerous collection, keep core use on-device, and stay usable under degraded conditions.
Most pain tracking tools assume stable connectivity, high attention, accounts, and willingness to centralize intimate health data as a default operating condition.
Core logging stays on-device by default, primary use does not require sign-up, and sharing moves through explicit export instead of background collection or ambient sync.
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.
Core use refuses account-first collection and keeps day-to-day ownership on-device by default.
Stored categories are bounded to the working record needed for pain logging, not open-ended behavioral exhaust.
The working record persists locally until the user edits, exports, or removes it through explicit action.
Sharing is explicit and user-initiated, replacing silent sync assumptions with deliberate export behavior the buyer can inspect.