Product boundary
Anonymous spatial intelligence, not individual identity
AnyVidi is designed around operational events and aggregate measurements tied to places, time bands, and journeys.
- No facial recognition
- No biometric identification
- No persistent individual profiling
What is measured?
Only the events required for the approved operational question should enter the measurement design.
- Traffic, occupancy, queues, and dwell
- Anonymous zone transitions and journey paths
- Team coverage by cohort, shift, time band, or zone
What does AnyVidi deliberately avoid?
Operational measurement must not drift into identity, personal tracking, gaze claims, or individual employee ranking.
- No gaze or eye-tracking claims
- No person-level HR score
- No purchase behavior without connected sales data
Where does processing happen?
Local or on-premise processing may be used where configured. The exact posture depends on the approved deployment design.
- Camera suitability is assessed first
- Operational outputs are separated from continuous raw video
- No universal deployment promise is implied
How are access, retention, and review controlled?
Access roles, retention windows, manager review, integrations, and agreed response procedures belong in the deployment agreement.
- Role-based access boundaries
- Defined retention windows
- Manager review and agreed response procedures
Which signals require additional approval?
Body, height, clothing-size, and gender outputs are not part of the current public capability set. Any future evaluation requires separate evidence, legal, and privacy approval.
- Not a current public capability
- Separate evidence and approval required
- No person-specific alert or treatment