Legal
This policy explains what FaceTrack collects, why it is collected, how it is protected, and what responsibilities remain with each customer using face recognition, attendance, and alert workflows.
FaceTrack is a face recognition attendance and security response platform with a web dashboard, mobile companion app, and edge capture components. It is used to review alerts, manage cameras, register devices, monitor attendance exceptions, and investigate watchlist or unknown-person events.
The organization that deploys FaceTrack is the primary controller of the people, cameras, face images, watchlists, attendance records, and alert rules configured in its tenant. FaceTrack acts as the service provider that processes this information to deliver the product.
We may process account details, tenant details, camera metadata, device identifiers, login sessions, notification tokens, audit logs, uploaded images, alert history, attendance events, watchlist records, and related operational settings.
We process data to authenticate users, register mobile devices, deliver alerts, review evidence, manage attendance workflows, secure the service, troubleshoot failures, and maintain auditable security operations.
Face images and related recognition outputs are sensitive. Customers must ensure they have the required notice, consent, legal basis, workplace authorization, or other permission required by their jurisdiction before enrolling or monitoring people with FaceTrack.
The mobile companion app may store device names, platform type, push notification tokens, notification preferences, and last-seen timestamps so alerts can be delivered to authenticated operators. Signed image links may be generated temporarily for alert evidence review.
FaceTrack uses authenticated sessions, tenant-scoped access rules, audit events, signed URLs, revocable mobile devices, and permission-gated actions to reduce unauthorized access. No security control is perfect, so customers should still enforce strong passwords, trusted devices, and least-privilege staff access.
Retention depends on customer configuration, operational needs, and legal requirements. Customers are responsible for choosing appropriate retention windows for images, attendance data, alerts, and watchlist records. Privacy and deletion workflows should be triggered through the customer tenant or the agreed support channel.
If you are an end user monitored by a customer deployment, contact that organization first because it controls the enrolled data. If you are a customer and need policy, support, or legal follow-up, use the contact path published on robonexa.app or your existing support channel.
For account deletion requests, use the dedicated Delete Account request page.
