Privacy & security

What the relay sees. And what it never can.

Privacy claims are easy to make. Here is exactly how Kant handles your data — stated plainly, including the parts that are still in progress.

Never stored or readable by the relay
  • Your messages
  • Your message history
  • Your contact list
  • Your identity keys
  • Your photos, files and other private data
What the relay does handle
  • •Signed, public addresses so devices can find each other
  • •Connection and reservation details
  • •Health, readiness and metrics data
  • •TLS certificate data where the relay is served over HTTPS

Who connects when is still visible to a relay operator. If that matters to you, turn on onion routing — or run your own relay.

Threat model

What we planned for, and how.

Scoped to what ships today: the relay, address publishing, identity and session handling on your device, and the HTTPS layer in front of public relays.

Someone intercepts a message

Messages are encrypted end to end on the device. The relay only ever forwards encrypted frames it can't decrypt.

Someone impersonates you

Address records are signed with the owner's identity key, so nobody can publish an address on someone else's behalf.

Someone replays old requests

Every /register and /lookup call carries a one-time nonce. Duplicates are rejected outright.

Someone floods the relay

Address records expire on a timer and are removed on disconnect, which limits how much a flood of reservations can pile up.

The relay host is compromised

The relay's identity can be restored through an authenticated backup flow, so a lost host doesn't mean a lost relay identity.

Admin tools are exposed

Admin endpoints require a configured bearer token and aren't reachable at all without one.

Honest by default

This is an engineering threat model, not an audit badge.

It’s written for deployment and review. It doesn’t replace a formal red-team or an independent audit — and Kant hasn’t had one yet. A production release is gated on a tested public deployment, a backup and restore plan for the relay seed, a secrets rotation plan, a current threat-model review, and an independent security audit or penetration test.

We’d rather tell you exactly what has been checked than round up. Likewise, this privacy summary is a practical baseline — not a legal opinion or a compliance certification.