Security

On the hub, in your home. Measurements, the device registry and your floor plan are kept on its memory card, not on our servers.

The interface you use is served by the hub itself, so looking at your own home does not send a request anywhere.

Each hub is registered during manufacturing and receives an identity document signed by us. It carries that document and checks it when it starts.

The identity is bound to the chip on the board, not to the memory card. Replacing the card does not make it a different device, and copying the card does not produce a second one.

A hub does not run unattended upgrades. No blanket package updates that nobody tested together.

An update is one release: the application, its dependencies and the runtime, tested as a set. Every file in it is identified by its SHA-256 hash, so a modified file is simply a different file.

Delivery of updates to customers is still being built. Today it is a controlled process on our side, not an automatic one on yours.

There is no support tunnel, no always-on connection for us to reach into your home, and no shared key that would open every hub in the field. This is not a promise for later — none of it is built.

Remote support is being designed. When it exists, we will describe exactly how it works before anyone uses it.

The configurator reads your plan inside your browser. The file is never uploaded: we do not receive it, we do not store it, and there is nothing for us to lose.

A floor plan says a great deal about a home — its layout, its size, sometimes its address. Not holding it is simpler than guarding it.

• no analytics, no advertising trackers, no third-party scripts
• no cookie banner, because there are no cookies that would need your consent
• fonts are served from this domain, so your browser does not tell anyone else that you were here