Hi Stephen,

Data security and hardware protection are key considerations in the design of Heidi Remote.

Rather than relying only on a delayed remote-wipe command, which may require the device to come back online, Heidi Remote is designed with device-level and account-level protections to reduce the risk of data exposure if a device is lost or stolen.

In particular:

Encrypted local storage: Audio and session data stored on the Remote is encrypted at rest. The data is designed not to be readable from the device’s raw storage without the required authorised account/device context.

Account/device binding: A Remote is registered to a Heidi user account during pairing. If a device is lost, the device can be managed through the authorised account flow, and unauthorised attempts to pair or sync the device are restricted by Heidi’s backend controls.

Data minimisation: Audio data is synced securely and cleared from local device storage once sync has completed, reducing the amount of data retained on the hardware.

These controls are designed to make a lost or stolen Remote unusable to an unauthorised person and to protect clinical data even in a lost-device scenario.

If your institution’s security or IT team needs more detail, we can share the relevant Heidi security and compliance documentation through the appropriate channel.

Best,

Peter

Engineering | Heidi Health