Security architecture
A short, plain-language tour of how Wellex is built to be secure.
Last updated: 2026-04-07
Threat model
Wellex protects against three classes of attack:
- Local theft — someone steals your phone or bracelet.
- Network interception — someone tries to read your data in transit.
- Server compromise — someone breaks into our cloud.
Defences
| Threat | Defence |
|---|---|
| Local theft (phone) | iOS/Android device encryption + app PIN |
| Local theft (band) | Band has no readable storage; useless without your phone |
| Network interception | TLS 1.3 end-to-end, certificate pinning |
| Server compromise | Per-user envelope encryption — even with the database, an attacker cannot read individual records without the per-user key |
Per-user encryption keys
Every member has a unique encryption key derived from their account credentials. Daily summaries are encrypted with this key before they hit our database. Even our own engineers cannot read your data without you logging in.
Audits
See Audits for the third-party reports.
Bug bounty
See Bug bounty for the program scope and rewards.