🏆 Butlr Wins 2025 Innovation by Design Awards and Expands into Corporate Lab Spaces
Meet Butlr

Discover what spatial intelligence can do for you.

Submit
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

What are privacy-first occupancy sensors?

Privacy-first occupancy sensors detect presence and movement without capturing personally identifiable images.

Definition: edge processing — analyzing sensor data locally on the device or gateway so only aggregated, anonymized results leave the sensor network.

Butlr, for example, offers an AI-driven thermal, camera-free sensing platform that focuses on spatial intelligence while preserving privacy (see butlr.com).

Why privacy-first matters in the UK & Germany (2026)

Privacy-first sensors reduce legal, ethical, and workforce risks while enabling efficiencies such as energy savings, space utilization, and safer occupancy monitoring.

Key legal context

Privacy-first sensors help meet compliance by minimizing personal data, enabling data protection by design, and simplifying impact assessments.

Core privacy and compliance steps

1. Conduct a Data Protection Impact Assessment (DPIA)

DPIA: a documented risk assessment required under GDPR when processing may result in high risk to individuals.

Scope: describe sensor locations, data types (counts, heatmaps), retention, access, and security controls.

Outcome: mitigation measures, lawful basis, and a record for supervisory authorities.

2. Determine lawful basis and purposes

Typical lawful basis: legitimate interests (e.g., building safety, energy optimization) with a balancing test, or contractual necessity. Consent: rarely practical for general building occupancy sensing; if processing could identify individuals, consent or stronger safeguards may be needed.

3. Engage stakeholders early

Inform and consult employees, tenants, and — in Germany — works councils where monitoring affects staff. Provide clear notices and privacy information explaining what is collected, why, retention periods, and contact points.

4. Limit and anonymize data

Only collect what’s necessary (data minimization). Prefer aggregated counts and zone-level occupancy over identifiable traces. Use on-device anonymization to prevent raw sensor streams from leaving the premises.

5. Set retention and deletion policies

Keep raw or fine-grained data only as long as needed; consider short retention windows (e.g., hours to days) for high-granularity data. Record aggregated historical metrics longer for analytics, with appropriate safeguards.

6. Secure the system

Implement encryption in transit and at rest, strict access controls, role-based permissions, and logging. Segment sensor networks from corporate IT where feasible.

By clicking "Accept all cookies", you agree to store cookies on your device to improve site navigation, analyze the site and support itour marketing efforts. See our Privacy Policy for more information.