Privacy & HIPAA

Every resident database is encrypted at rest.

Encryption isn't reserved for one flagship app — it's applied consistently across every app in the suite that stores resident data, with the three highest-use apps also requiring a biometric unlock before they open.

Get Started → See all apps ↓

By Design

Two layers, applied where each one matters

The suite's offline architecture already means resident data never leaves the device. Encryption and biometric lock protect that data on the device — the scenario that matters when a phone is lost, stolen, or picked up by someone who shouldn't be looking at it.

Each database is encrypted with SQLCipher, using a unique 256-bit key generated on first run and stored in the platform's hardware-backed secure storage — the Android Keystore or iOS Keychain. The key never touches the database file itself, and it's not recoverable by reading the app's files off a lost device.

Three apps — the ones used constantly, handed around during shifts, and left unlocked between uses — add a second layer: a fingerprint or face-unlock gate at launch, so even an unlocked phone doesn't hand over resident data to whoever's holding it.

6 / 6
Resident-data apps encrypted
256-bit
SQLCipher key strength
3
Apps with biometric lock
0
Keys stored in the database file

App-by-app coverage

The split isn't arbitrary: every app holding resident information is encrypted, full stop. Biometric lock is layered on top for the apps in constant, shared use during a shift — where the bigger risk is an unlocked phone in someone else's hands, not just a lost device.

Related

Keep reading

Get Started

Your DSPs deserve better tools.

Tell us about your organization and lock in founder pricing before it closes.

Contact Us Today →