Coming Soon

Not Your Keys. Not Your Messages. Council

The first messaging app where you control the encryption keys. Create them. Share them. Burn them. Your conversations, your rules.

User-Controlled Keys
Quantum-Resilient
Burn When Done

Every encrypted messaging app you use today has a security design problem.

Your messages are protected by encryption that can be compelled, will eventually be broken, and is already being extracted by forensic tools. The industry calls it secure. We built something better.

01 No social graph. No contact list. No way to map your connections.
02 A compromised passphrase doesn't break encryption.
03 Quantum-resilient today. Not on a roadmap.
04 The server is excluded by math, not by policy.
05 Burn means gone. Forensics-safe deletion.

Resource-exhaustive security by design

01

Passphrase is membership.

Other messaging apps build a social graph from your phone number and contact list. Council doesn't. Your phone or email is only used for account security -- it's never shared, never linked to others, and never used to build a map of who you know. Networks are joined by passphrase. You know the phrase, you're in. The server cannot answer "who is in this group?" -- and that's by design.

02

Defense in depth that actually works.

Every passphrase-based system has the same fatal flaw: leak the password, lose everything. Council's layered architecture breaks this pattern. An adversary with the passphrase still needs your device secret and cycle secret -- both of which require physical device access or breaking ML-KEM-768. This is the defense-in-depth that the industry claims but doesn't deliver.

03

Zero quantum-vulnerable primitives.

The competition has bolted on partial quantum resistance as a hybrid afterthought. Most have none at all. Council's entire stack is post-quantum. No ECDH, no RSA, no Ed25519 -- nothing a quantum computer can break. Every key exchange is ML-KEM-768, every symmetric operation is AES-256 or SHA-512. For "harvest now, decrypt later" threats, there is nothing to harvest.

04

The server never touches key material.

Most encrypted messaging servers could theoretically intercept key exchanges. They promise not to, but the architecture permits it. Council's server is cryptographically excluded. Keys are derived on-device via Argon2id. Cycle secrets are sealed via ML-KEM to device keys. There is no key exchange the server mediates, no trust required.

05

Hard delete. Cascade delete. Gone.

When you burn your data, the server executes a cascade delete. Not a soft delete. Not "flagged for deletion in 30 days." The encryption key is destroyed. What remains is cryptographic noise that no tool can reconstruct. Your private conversations stay private -- permanently.

Protecting the people who do the right thing

Teams in the Field

When your mission depends on secure communication. Quantum-resilient messaging that keeps your team connected and protected.

Organizations & Leadership

Protect board discussions, strategy, and privileged communications. Keep sensitive decisions between the people in the room.

Journalists & Sources

Protect the people who trust you. No phone numbers to trace. No contact lists to expose. No server that knows who talked to whom.

Anyone Who Values Privacy

You shouldn't need a reason to want a private conversation. Innocence deserves protection. Council provides it.

Take control of your messages

Comprehensive security design that meets 2025 government encryption requirements -- available to everyone.