Security & compliance

Private by design.

HIPAA baked in from the first line of code — and engineering habits that treat every patient detail as something entrusted, not just stored.

No PHI where it doesn't belong

Patient information never rides in push notifications, logs, URLs, analytics, or error messages. It exists behind an authenticated, role-checked session — and nowhere else.

Permissions enforced at the server

Every request is role-checked in the backend. The app on the screen is never the security boundary — it’s just the window.

An append-only audit log

Every patient search, record view, and export is written down — who, what, when — in a log that can be added to but never edited.

Locked-down sessions

Every new device must prove access to the nurse’s email before a password works there. Five failed attempts lock the account; sessions end after 12 hours, with a 15-minute inactivity lock.

A BAA-backed stack, maps included

Hosting, geocoding, routing, and map tiles all run under business associate agreements. Patient addresses never touch consumer map services.

Respectful location sharing

You decide when nurses share location — many agencies limit it to on-call hours. The sharing state is always visible to the nurse, and position history is deleted on a schedule you control (60 days by default).

Deliberately not an EMR.

Dispatch holds the minimum needed to get the right nurse to the right door: names, addresses, visit details, timing. Clinical documentation stays where it belongs — in your EMR. Less data held means less data at risk.

Have a compliance team? Bring them.

We're happy to walk your privacy officer through the architecture, the audit log, and our agreements.

Try it free