Data Safety
Designed for the worst-case scenario.
Emergency data is produced by people at their most vulnerable — injured, displaced, or under threat. Mysafehub's architecture assumes the network is hostile and the phone may be searched, and protects the person anyway.
On-device biometric checks
Tier 1 liveness verification runs entirely on your phone. The camera image is analyzed locally and discarded; only a cryptographic signature — produced inside the device's secure enclave — ever enters the mesh.
Minimal, structured payloads
Every emergency message is a structured payload under 250 bytes: a category, coarse location, timestamp, and verification level. No free-form media, no contact lists, no browsing data — nothing extra to expose.
Encrypted store-and-forward
When a message cannot reach a responder immediately, it waits in encrypted queues on nearby devices. Relay phones cannot read what they carry; only the destination responder holds the keys.
Institutional keys for responders
Tier 2 responder status is anchored in pre-authorized institutional credentials, not self-declared accounts. Organizations issue, audit, and revoke access — a stolen password alone cannot create a responder.
Duress protections
The incident and evidence log supports a decoy PIN: under coercion, a user can unlock a plausible, sanitized view while the real encrypted log stays sealed and unprovable.
Anonymous by default
A Tier 0 SOS requires no account, no name, and no phone number. People in the most dangerous situations can call for help without creating an identity that could later be used against them.
Standing commitments
- ✓No sale of personal data, ever.
- ✓No advertising or behavioral tracking.
- ✓No third-party analytics inside emergency flows.
- ✓Independent security review before every city-scale deployment.
For what we collect and how long we keep it, read the Privacy Policy.