Privacy & HIPAA

Resident data stays where it belongs.

No accounts. No cloud. No data leaving the device. The DSP Suite uses anonymous identifiers only and processes everything locally — so there's no central store of protected health information to leak.

Get Started → See all apps ↓

By Design

Privacy isn't a feature. It's the architecture.

The DSP Suite was built offline-first specifically so that protected health information never has to travel. There is no server to breach, no account database to compromise, and no third-party processor handling your residents' data.

Apps reference residents and homes by anonymous identifiers — codes like R1–R10 and H1–H10. The mapping to real people lives outside the apps, with authorized staff. So the data inside the apps isn't, by itself, tied to an identifiable individual.

No audio is ever transmitted to Google, Apple, or anyone else. Voice notes are transcribed on the device.

0
Bytes sent to cloud
100%
On-device processing
0
User accounts required
Designed for HIPAA compliance

A note on HIPAA, stated honestly

The apps are designed to support HIPAA compliance through that offline-first, anonymous-identifier architecture — no PHI is transmitted, and the apps don't require directly identifying information to function. HIPAA compliance itself is ultimately the responsibility of the covered entity using the software: securing the device, controlling access, and using the apps consistent with your organization's obligations. The architecture is built to make that as easy as possible. Full detail is in the Privacy Policy.

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 →