Skip to content
Trust

The security model, in plain terms

Most shared-screen dashboards are a website with your household's calendar on it. Denframe is a service on a computer you own, and every choice below follows from that.

01

Four roles, four amounts of trust.

Owner

Sets the household password (or explicitly opts out), configures every connector, and can recover access.

Member

A paired household device with a restricted view — posts notes and completes tasks, never sees owner credentials.

Guest

Reads notes and the guest card already scoped to them; can't pair further devices or change settings.

Kiosk

A shared display or receiver — shows scenes and household information, accepts no household changes at all.

Security facts

Network posture

Binds to loopback (127.0.0.1) until you deliberately choose a LAN or reverse-proxy binding. Remote management requires HTTPS from a configured origin; plain HTTP credential requests are rejected even on a trusted LAN.

Passwords and sessions

The household password is hashed with PBKDF2-SHA256 on the device and never transmitted. Signing in exchanges it for a revocable 12-hour session token; repeated wrong attempts are throttled.

Pairing

A pairing QR carries a random, five-minute, one-time exchange offer — never the durable grant itself, which returns only after exchange and is scoped to a role and explicit permissions.

Connectors

A Home Assistant token or calendar credential lives only on the backend, in the secret store. It's excluded from provider metadata, scene payloads, receiver messages, and logs. Disconnecting deletes it.

Home controls (experimental)

Owners approve each device and operation through Home Assistant; locks, doors, heating and water are never offered. What Denframe shares with Apple Home goes through Home Assistant's HomeKit Bridge, and everyone in that Apple home can use it.

Backups and recovery

Backups are files you keep, verified before restore, with a rollback copy of prior data. Owner recovery revokes every existing browser and paired-device grant at once.

Diagnostics

Local, content-free metrics and a redacted diagnostics export are available on the device. Nothing in either leaves it.

Report a vulnerability

For supported Denframe app releases, we aim to acknowledge reports within three business days and provide an initial assessment within seven calendar days. Confirmed critical issues target mitigation within 72 hours and a fix within 14 days; high-severity fixes target 30 days and medium-severity fixes 90 days. We coordinate advisory publication with reporters and communicate revised dates when a target cannot be met.

Security support for Denframe 0.2 beta builds ends March 31, 2028, and for 0.x desktop pilot builds September 7, 2027. The published panel build, 0.1.0-pilot.5, records its own date: 30 September 2027. Each release records its support end date in its component SBOM and release notes. Android OS, WebView and radio firmware support require a separate supplier commitment; no supplier hardware support period is announced here.

Found a security issue? Email support@nannertech.com with details and reproduction steps. Please don’t test against a household that isn’t yours.