CCrisisCore-Systems4d ago
@CrisisCoreSystems
CrisisCore-Systems
@CrisisCoreSystems
Building privacy first health tools that fail safely when users are already under pressure.
Vernon, BC, CanadaJoined November 2025
About
I’m the founder of CrisisCore Systems and the developer behind PainTracker.ca, a privacy-first, offline-first pain journal built for people who’ve been failed by “normal” health apps. I build PWAs that run entirely on your device, use real encryption, and respect trauma and crisis instead of exploiting them. Here I write about Web Crypto, IndexedDB, workers’ comp evidence, and building software that still works when life doesn’t.
Available for
Freelance consulting on offline-first PWAs, Web Crypto / client-side encryption, and trauma-informed product design. Open to collaborations and sponsorships around PainTracker.ca and privacy-respecting health tech. If you’re shipping health tech or developer tools and want an offline-first, trauma-informed review, reach out via X or Hashnode DMs. PainTracker.ca is the reference implementation behind CrisisCore’s Protective Computing work: local-first software designed for users under pain, stress, instability, and low-trust conditions.
CrisisCore-Systems's blogs
Threads
CCrisisCore-Systems4d ago
I just published a piece on why health apps should not put sensitive user data in the cloud by default.
The argument is simple: chronic pain users are often interacting with software while exhausted, foggy, stressed, or trying to preserve records for doctors, insurers, or claims. That changes the archit
CCrisisCore-Systems commentedCCrisisCore-Systems4d ago
I built a chronic pain tracker that works without an account, without a required backend, and without turning health data into someone else's asset.
Most health apps assume the user is stable. They assume the user has energy. They assume the user can log consistently. They assume the user remembers what happened three days ago. They assume privacy
Join discussion