Security
Built to be verified.
How Naad Secure protects every message, file and call.

Read this first. Each principle maps to a mechanism in the code. Certifications are not claimed; the platform is open to independent evaluation.
Design principles
Six principles, each with a mechanism.
Text, files, voice and video alike.

- 01
A person is a key
Identity is a hash of three public keys and can be recomputed from those keys.
- 02
Nothing in the middle is trusted
Seeds can withhold, never forge. Relays splice ciphertext only.
- 03
Bind the session to the wire
The initiator signs a value unique to the connection. A relay that terminates the transport is refused.
- 04
Post-quantum at every step
Every ratchet step uses a post-quantum hybrid key exchange. There is no classical-only path.
- 05
The cheapest honest path
A direct path is tried first. Every route is cryptographically identical.
- 06
Sealed at rest, guarded on screen
Identity is PIN-sealed and history encrypted. The window resists screen capture.
Collaboration safeguards
Protection that extends to groups, calls and files.
Members, devices and forwarders get nothing they can read.
Group keys
Group keys are protected by post-quantum hybrid sessions and rotated on every join or leave.
Membership changes
Removing a member rotates the group keys; the removed member does not receive the new seed.
Calls
Three nested layers per frame; the call key travels inside the ratchet.
Files
Chunked and encrypted; received files land in a confined folder.
Offline delivery
Sealed sender hides the sender from the store; the recipient stays visible.
Devices
Device certificates are signed by the person’s key and can be revoked. Recovery uses k-of-n shares of an encrypted vault.
On the wire
Post-quantum keys are larger. The design budgets for it.
Standard sizes from the NIST FIPS documents and RFCs.
Trust by deployment type
What each deployment type removes from the trust path.
These properties belong to the deployment type, not to every installation.
| Identity | Servers in the path | Cloud and internet | |
|---|---|---|---|
| Self-hosted, including air-gapped | A key only. No phone number, SIM or e-mail address. | Seed, relay and store run by the customer. No central server in the trust path. | Air-gapped: no internet dependency and no foreign push or cloud service in the trust path. |
| Tenant-hosted | Key-based identity. | Operated by Knowlcom for one organisation. Relays splice ciphertext only. | Depends on placement. Private infrastructure is available. |
| Public infrastructure | Key-based identity. | Public relay and store carry ciphertext only. | Not a no-cloud deployment. |
Stated plainly
Known limits and work ahead.
- Independent cryptanalysis by a third-party laboratory is on the roadmap.
- Hardware key custody and signed distribution are work ahead.
- Relays can still observe message size and timing.