User-controlled export boundary: WorkSafeBC pain documentation tool If you want the short Layer 1 path into this argument, read these first: Keeping Your Health Data Out of Court If Your Health App Can't Explain Its Encryption, It Doesn't Have Any Client-Side Encryption for Healthcare Apps This piece is the bridge between the polemic and the implementation. If you want privacy-first, offline health tech to exist without surveillance funding it: sponsor the build → https://github.com/sponsors/CrisisCore-Systems When people say they want software to be subpoena-proof, they usually mean something too vague to build and too dramatic to defend. Not invincible. Not outside the law. Not protected from a compromised device, a coerced unlock, or a user who chooses to export their own records. Something narrower than that, and more real. It means reducing what the software operator can produce in the first place. Boundary notes, because truth matters This is not legal advice. This is not a claim of perfect secrecy.…