Public website privacy

The public site does not need access to your live home.

kems.uk is deliberately separated from KEMS property appliances and Home Assistant. Public marketing, delayed demonstration data and private property access each have a different boundary.

No Home Assistant credentials

The public site does not request, store or transmit Home Assistant URLs, access tokens or KEMS property credentials.

Delayed demo only

The demo reads sanitised daily totals and half-hour KEMS routing evidence delayed by at least seven days. Precise live power, entity IDs and device identifiers are excluded.

No KEMS password database

Private property sign-in is handled by Cloudflare Access rather than a separate public KEMS username/password store.

No public control path

The public site cannot call Home Assistant services or issue commands to an inverter, charger, ESP32 panel or other property device.

Authenticated property access

A separate boundary for private dashboards.

When a user signs in, Cloudflare Access decides which protected KEMS property applications that identity may open. The property is reached through its outbound tunnel; local Pi maintenance, Home Assistant and hardware-control surfaces remain outside the public route.

Public websiteMarketing and delayed demo evidence.

Cloudflare AccessIdentity and per-property authorisation.

Property PiRead-only dashboard backed by local KEMS/Home Assistant.

Hosting and security providers may retain ordinary delivery and security logs. KEMS itself adds no advertising trackers on the public website in this release.

Back to KEMS home