Xovis sensors are privacy-by-design — no images are stored or transmitted. This article covers the built-in privacy levels, GDPR compliance, port management, and security configuration. Source: Xovis Knowledge Base.
Xovis 3D stereo vision sensors use two CMOS lenses to build a real-time stereo depth image inside the sensor. Only metadata leaves the sensor — count values, timestamps, path coordinates. The actual images are never stored and never transmitted. This is a hardware-level privacy guarantee, not a software setting.
Level 0 | No restrictions. Live video stream + full tracking visible in WebUI. For installation only — never leave at level 0 in production. |
Level 1 | No live video (still image on request only). Tracking bubbles visible. Xovis recommended minimum. Validation recordings disabled at this level and above. |
Level 2 | No image at all — grey background. Tracking (bubbles) visible only. |
Level 3 | No image, no tracking. Only counting values updated. Maximum privacy — suitable for highest-sensitivity deployments. |
Sensor Master Key (SMK) required to lower privacy level. The SMK is a unique key per sensor, only available from Xovis upon verified request. This prevents unauthorized reduction of privacy settings. Plan the appropriate privacy level during installation — changing it later requires the SMK.
Xovis sensors can be operated in a GDPR-compliant system. Key responsibilities:
The system provider (e.g. Vemco Group's customer) is responsible for Technical and Organizational Measures (TOM)
Control sensor access and user accounts
Control who has access to the Sensor Master Key
Define data processing, storage, and retention policies
The sensor itself is not sufficient — the entire system must be compliant, including the platform, integrations, and data storage. Xovis provides a Data Privacy Statement PDF (2023) and AI Note (2025) downloadable from the KB.
Set a strong, unique password per sensor on first setup — the default password must be changed immediately
Disable HTTP; access only via HTTPS
Upload a custom SSL certificate per sensor (replaces the Xovis default)
Place sensors behind a firewall; restrict to required outbound ports only (see Xovis network requirements article)
Update sensors to the latest firmware — each release includes security patches
Do not name sensors with location-identifying names (e.g. not "Oval Office" / "White House")
Rate limiter on authentication attempts
All remote connections over TLS 1.2 or 1.3 only (older TLS versions not supported)
Serial console access blocked at signal level
Secure boot chain — tamper protection for TLS certificates and cryptographic keys
Multisensor connections can use HTTPS
Diagnostic files (.xdg) are encrypted
Sensor backup files (.xbak) are encrypted
API (FW5+) requires authentication — no public API access except for basic sensor discovery
Administrators can change or disable any sensor port via Settings → Advanced network properties:
HTTP can be permanently disabled to prevent unencrypted access
Custom SSL keys and certificates can be uploaded to replace the Xovis default
Custom Certificate Authorities can be added or removed at any time
Select Xovis sensors (PC2RE) can monitor nearby WiFi and Bluetooth device IDs (MAC addresses, signal strength). This feature is subject to local legal requirements — in some countries (e.g. Germany) it is not permitted in public areas. The feature includes Allowlist and Denylist support. Administrators are responsible for ensuring legal compliance per deployment location.