Data Location
Profiles, face samples, alerts, visitor snapshots, and detection records can be stored on the customer's local device or server.
Privacy & Data Handling
Responsibleidentity monitoring
OIM is designed for local-first security workflows where organizations define access rules, retention policies, and appropriate use before production deployment.
Administrator Control
Organizations should define who can add profiles, review alerts, export records, and change camera or recognition settings.
Record Retention
Visitor snapshots, detection records, and alert history should be kept only as long as the customer's operating policy requires.
Human Review
Recognition events should support staff decisions. Security teams should review alerts and act according to site procedures.
Deployment Guidance
Recommended operating safeguards
Clear Use Policy
Document why the system is used, which areas are monitored, and which staff roles can operate it.
Profile Governance
Keep blacklist, member, and customer profiles accurate. Remove inactive or unnecessary profiles according to policy.
Backup Discipline
Plan secure backups for the database and define who can restore or access archived data.
Compliance Review
Customers are responsible for confirming local legal, privacy, notice, and consent requirements before deployment.
Plan Before Deployment
Discuss data handling during the demo
Use the demo to confirm local storage, staff access, retention expectations, camera zones, and integration requirements.