MIRQ encrypts messages on the client and keeps private keys on your devices. The server stores only protected data, while your clients control access and decryption.
MIRQ blends post-quantum readiness with proven modern encryption so group chat stays fast, private, and future-proof without exposing sensitive implementation details.
Messages are protected with a layered approach that combines next-gen post-quantum safety with trusted modern crypto.
Channels and DMs use dedicated room keys so access is scoped and controllable for each space.
Messages are encrypted locally before they leave your device. The server never receives plaintext.
Encrypted messages stay compatible over time, with room to strengthen protections as standards evolve.
The design focuses on practical privacy for real communities: strong confidentiality, scalable access control, and crypto that will survive the next decade.
The server stores encrypted payloads and metadata only. Plaintext never touches server storage in guild channels or DMs.
CEKs allow fast group encryption while still enabling key rotation for access changes.
Hybrid post-quantum wrapping protects stored message archives against future decryption attacks.
Key distribution is role-checked. Only authorized users can grant or rotate CEKs.
MIRQ balances strong cryptography with the operational realities of group chat, keeping encryption practical for admins and reliable for members.
Most platforms stop at transport security or 1:1 encryption. MIRQ applies client-side protection to guilds and DMs with admin-friendly control.
Protection is designed to hold up as post-quantum standards mature, not retrofitted later.
Your private keys stay on your devices. The server only stores protected message data.
Client-side encryption extends to channels and DMs, not just direct 1:1 chats.
Room-level controls align with real community operations and access changes.
Encryption can evolve without breaking existing history or client compatibility.
What the server can and cannot see is explicit, so teams can govern with confidence.
The client owns the keys and the server stores only protected data. This is the high-level flow without revealing sensitive internals.
Strong encryption does not eliminate every risk. MIRQ is explicit about the trade-offs so teams can plan accordingly.
When membership changes, rotating room keys limits future access while preserving history as intended.
Admins decide how far back access should go for new members.
Access changes depend on admin actions to apply immediately.
Basic delivery metadata like timing and size remains visible for routing.
Strong local protection and device security are essential.
If a device is missing keys, it may need to re-sync before it can read older messages.