At Observant, we're obsessed with privacy. Not only is our SDK is built from-the-ground-up with privacy in mind, but we also rigorously enforce strict guidelines around usage of our SDK. Your data and your kitchen counter are sacred.
But you probably hear enough of that kind of corporate-speak these days. Here's how we walk the walk.
Research vs. The Wild
We built Observant to be primarily used for internal testing, in research labs, focus groups, and other environments where users are fully aware they're being observed.
However, in some cases Observant can be used in production applications to enhance user experience; for example, social networking apps that generate emoji, or mental health apps that can measure cognitive decline. For anything public-facing, we take several extra steps of precaution to ensure users' privacy is guarded religiously.
For production apps, Observant strictly enforces two separate layers of permissions before users can opt-in.
One layer is surfaced automatically by the Observant SDK, to inform users how Observant works and to request consent.
The second layer is an iOS-mandated camera permission dialog.
Observant performs all processing on-device, and never uploads any photos, videos, depth data, biometric data, or other sensitive data.
When an application has been approved by us, and an end-user has expressed clear consent, Observant provides developers with the following data: