PRIVACY CONTROLS
Conceived for Privacy
Nobody wants to be tracked. We get that.
Unlike cameras, our sensors are anonymous by design. They can’t capture any personally identifiable information, and no data captures leave the sensors during normal operations. This gives our customers the benefit of highly accurate analytics and applications, while safeguarding occupant privacy.
Built with industry-standard best practices
Network Security & Data Transmission
Sensor data are continuously processed on the Chirp device to detect activities of interest (e.g. presence of people, yelling for help). Detected activity meta-data (e.g. time and duration of activity, number of people in room) are sent to cloud storage for access by caregivers.
On the detection of an emergency (e.g. yelling for help) by the Chirp device, audio and other sensor data (e.g. low resolution thermal) is sent to caregiver mobile devices for verification.
Device Hardware Security
The root filesystem on the Chirp device is read-only. Radar-data is collected and processed in-memory, analyzed by our on-board algorithm and determined to be an entrance or exit (“Event”). The Event data (+1/-1) along with a timestamp is stored on a read-write partition in a relational data-store. Depth data is never stored on the device. Density stores network credentials in a secure file onboard the read-write partition
Account Permissions
Chirp enables permission levels within the app to be set for your caregivers. Permissions can be set to give specific users access to view information or fully configure the system.
API Authentication
Chirp uses a RESTful API that requires Token Authentication for access. Access Tokens can be generated via logging into our Dashboard and creating them under our Developer Tools section..