Privacy-first smart infrastructure

Why we put the intelligence in the fixture, and what that means for the people in the room

Most "smart building" products are built the same way: a sensor in the room streams data to a hub or a cloud service, and the intelligence lives somewhere else. That architecture is convenient for the vendor. It is a poor fit for a bedroom, a bathroom or a hotel room, where the data being streamed describes the most private moments of someone's day.

Arqaios made a different architectural choice from the start. The sensing, the interpretation and the first response all happen inside the fixture itself: the switch on the wall, the outlet by the bed, the vent in the ceiling. We call it fixture-native, and privacy is the reason it exists.

No cameras, by construction

There is no image sensor in an ALLIE fixture. Not a disabled one, not a low-resolution one, none. Presence, position, movement and posture are resolved from mmWave radar, which measures how radio waves reflect from people and objects in the room. It can tell that a person is standing by the bed, has walked into the bathroom, or has dropped to the floor and stopped moving. It cannot capture a face, a body or anything a human being could recognise.

Acoustic sensing follows the same principle. It recognises the signature of events, a fall, breaking glass, a call for help, and does not record or stream audio.

Processed in the room

Raw sensor signals are consumed by on-device models in the fixture. What leaves the room is an event or an aggregate: "occupied", "unoccupied since 14:10", "fall detected, bathroom, 02:14". There is no video to store, no audio archive, no stream to intercept.

That has practical consequences for operators:

• There is nothing for a family member, a regulator or an attorney to ask to see, because nothing was recorded.
• The data that does exist is small, structured and easy to govern with ordinary retention and access policies.
• Network and storage requirements are a fraction of what camera-based systems demand.

Presence, not identity

ALLIE's job is to know what is happening in a room and whether someone needs help. It does not need to know who they are to do that. Radar resolves people as moving point clouds, and the system is designed around presence, activity and distress rather than identification.

Encrypted, scoped, transparent

Traffic between fixtures and the operator dashboard is encrypted. Access is role-based, so a night-shift caregiver, a facilities lead and an administrator each see what their role requires. Retention is configurable per site. And every deployment includes transparency for the people who live or stay in the building: what is sensed, what is stored, who can see it.

Why it matters beyond compliance

Privacy is often discussed as a compliance obligation. In the places we serve, it is also the difference between a system that gets used and one that gets rejected. Residents refuse cameras. Families push back. Guests would never accept them. A safety and energy layer that everyone can live with has to be private by construction, not by policy.

That is the standard we built ALLIE to meet.