No facial recognition
Detection models identify object classes — “person”, “forklift” — not faces, gait, or any biometric template. There is no re-identification capability.
Privacy
Counts, not identities.
Privacy is not a feature toggle in OperaLens — it is the architecture. The system produces numeric operational signals and is designed so that identifying an individual is not part of how it works.
What the system needs
- Presence — something is here
- Count — how many
- Class — person, vehicle, configured object
- Zone — where
- Timestamp — when
- Event — what rule fired
What it does not need
- Name
- Face identity
- Biometric profile
- Employee or customer identity
How this works technically
The architecture behind the claims.
Ephemeral tracking only
Tracker IDs are small in-memory integers used to avoid double counting. They are recycled continuously, reset on stream restarts, and never associated with a person.
No continuous video upload
Frames are processed in memory on an edge device at the location. What is stored is numeric: metric, camera, value, timestamp. Evidence clips are retained only where an operator configures them.
On-premise processing
Video is analyzed on hardware you control, inside your network. Raw video does not need to leave the site for the listed use cases.
Minimal alert payloads
An outbound alert contains the rule name, metric, numeric value, and timestamp — nothing else. You choose which destinations exist at all.
Retention you control
Stored data is numeric time series in storage you own. Retention, authorized access, and deletion procedures are configured for each deployment.
Policy
Data collected
Pilot configurations can retain operational metrics and event records, such as traffic counts, zone occupancy, movement, and timing data. Anonymous temporary object IDs can be used; facial recognition is not required. The dashboards in the Live Demo are built entirely from this kind of aggregated, anonymous count data.
Placement and notice
We recommend pairing any deployment with your own notice practices, and placing cameras to cover work and customer areas — not break rooms or other privacy-sensitive spaces. Requirements for notice, consent, and retention vary by location (for example CCPA or BIPA considerations) and should be reviewed with appropriate advisors.
Assessment requests
Contact details submitted through the assessment form are used to respond to the request. A production policy will specify the form provider, retention period, and contact process before public launch.
What we do not claim
This page describes product architecture. It is not legal advice, and OperaLens does not claim certification under, or guaranteed compliance with, any specific privacy statute. Evaluate any deployment with your own counsel and policies.
Questions
Email privacy questions to hello@operalens.example.
Bring your privacy team to the first call.
The architecture answers their questions better than a brochure can.