What we collect
Derived metrics: People now, Total People, entries, exits, zone totals, busiest hour.
Heatmap data: computed overlays, position coordinates, and density metrics for the selected time range.
Configuration: camera settings, zones, and entry or exit lines.
Audit events: who changed what and when in the dashboard.
Counts are session based, not unique individuals. If someone leaves the frame and returns, that creates two sessions.
What we do not collect
No facial recognition.
No identity tracking or re-identification.
No biometric templates.
Processing flow
A video frame is received by the server.
Detection runs and is anonymised immediately after the detection script executes.
We keep derived outputs such as counts and heatmap density, not identifiable imagery.
Heatmaps and storage
Heatmaps are created from per pixel visit density with dilation and Gaussian blur for readability.
We store the computed overlays and coordinates required to draw heatmaps and report metrics.
Raw frames are not needed for analytics. Where frame storage is enabled for security or validation, see retention below.
Retention
Video frames: deleted after 6 months when frame storage is enabled for review or security.
Derived analytics: counts, heatmaps, and configuration are kept per your contract. Enterprise clients can request custom retention.
Exports: CSV files you download are under your control once exported.
Security
All data in transit uses HTTPS with TLS 1.2 or 1.3.
At rest protection available for enterprise deployments on request.
Role based access in the dashboard and a full audit trail of changes.
GDPR and privacy notes
Session based counting protects identity. We do not attempt to track unique people.
Staff filtering is not enabled by default. Enterprise clients can request worker identification options.
You can submit access or erasure requests through support. We will act on applicable records and logs.
Accuracy and environment
Typical counting accuracy is 85 to 90 percent under normal conditions.
Accuracy can be affected by crowding, occlusion, extreme lighting, and mirrors or reflective surfaces.
Camera placement matters. Mount high and angle down. Validate with a quick walk test.
Offline behaviour
If a camera is offline, counts are not buffered or backfilled. Gaps will appear for that period. Enterprise backfill can be added if required.
Roles and access
Admins and Managers can view analytics, zones, and configuration and see audit logs.
Viewers are read only.