Security
End-to-End Encryption on the Signal Protocol, With Post-Quantum Protection
SANKET encrypts every message, reaction and encrypted broadcast with Signal's independently audited libsignal library, using PQXDH key agreement with a post-quantum Kyber prekey and the Double Ratchet with its SPQR post-quantum companion (the Triple Ratchet). Files and calls use AES-256-GCM, transport uses AES-256-GCM-only TLS with hybrid post-quantum key exchange, and the server stays blind to content throughout.
What this means
The platform, in plain terms
Messages, reactions and encrypted broadcasts: libsignal PQXDH plus the Double Ratchet with SPQR, one ciphertext for every recipient device
Files: a fresh AES-256-GCM key for every file, delivered inside the libsignal message
Voice and video calls: AES-256-GCM frame encryption plus SRTP AES-256-GCM, with five new frame keys every second and a fresh key whenever someone joins or leaves
Transport: TLS 1.3 preferred with AES-256-GCM-only suites, and hybrid post-quantum X25519MLKEM768 key exchange offered first
Hardware-backed keys: Secure Enclave on iOS, StrongBox or the trusted execution environment on Android
Signed device lists, identity pinning and safety numbers, so a new device or key never slips in unnoticed
Device mutual TLS: every approved phone and desktop presents its own client certificate issued under your certificate authority
Server-blind by design
Privacy architecture
SANKET is server-blind: the server relays ciphertext and never holds the keys to messages, files, calls, reactions or encrypted broadcasts. Replies, locations, contact cards, link previews and forwards travel inside the encrypted message, and the routing information needed to deliver messages stays inside the customer's own installation.
libsignal · Post-quantum · AES-256
Security model
Defence in depth runs from the device to the release pipeline: hardware-backed device keys, device client certificates checked at the edge, administrator FIDO2 security keys, a SHA-256 hash-chained audit log, and Ed25519-signed releases that an installation refuses if they are unsigned, expired or older than the one it runs.
Hosted · On-premise · Air-gapped
Deployment control
The same cryptography protects every edition. In Sanket.Enterprise the whole system, including the certificate authority, push for Android, licensing and updates, runs inside your own network, connected or fully air-gapped.
No third-party analytics
No advertising model
SANKET has no advertising business model and no user profiling. No SANKET app or server contains a third-party analytics, advertising or crash-reporting SDK, and first-party usage counts stay inside the installation, where the organisation can switch them off.
Built on Signal's independently audited libsignal
Post-quantum PQXDH, SPQR and hybrid TLS
AES-256 for files, calls, storage and transport
Server-blind: no keys to your content
Deployment path
Choose the right tier for your organisation
Sanket.Chat
IndividualThe free private messaging app for iOS and Android, built in India and operated by Tosh Defence on Indian infrastructure.
Sanket.Work
OrganisationA dedicated, whitelabel installation hosted in any region on any cloud you choose, operated for you under contract.
Sanket.Enterprise
Defence and GovernmentA customer-operated installation for defence, government and critical infrastructure, on-premise or fully air-gapped.
Protect content against network interception, server compromise and harvest-now-decrypt-later collection with post-quantum key agreement
Contain lost or seized devices with hardware-backed keys, device certificates, revocation and server-confirmed remote wipe
Give evaluators a documented architecture, set out in full in the public SANKET whitepaper
Frequently asked questions
What encryption protocol does SANKET use?
SANKET uses the Signal Protocol through Signal's official libsignal library: PQXDH key agreement with a post-quantum Kyber prekey and the Double Ratchet with the SPQR post-quantum ratchet. Inside libsignal each message is encrypted with AES-256-CBC and authenticated with HMAC-SHA256.
Is SANKET post-quantum?
SANKET adds post-quantum protection at two layers. Message sessions use PQXDH with a Kyber prekey and the SPQR ratchet, and the edge offers hybrid X25519MLKEM768 key exchange first to every client whose TLS stack supports it.
What does server-blind mean?
The server relays and stores ciphertext and never holds the keys to read messages, files, calls, reactions or encrypted broadcasts. Decryption happens only on the participants' devices.
How are calls protected?
Calls run through a self-hosted media server. Every frame is encrypted with AES-256-GCM using per-sender keys delivered over libsignal, the media is also protected by SRTP with AES-256-GCM, and keys renew five times a second and whenever a participant joins or leaves.
How are encryption keys protected on devices?
Keys are generated on the device and protected by a hardware key: the Secure Enclave on iOS, and StrongBox or the trusted execution environment on Android. The protection level is recorded for each device and policy can require a minimum level.
Has SANKET been independently audited?
SANKET is built on Signal's libsignal, which has been independently audited and analysed. SANKET's own code has been through structured internal security reviews, and independent assessment, including a CERT-In empanelled audit and national evaluation, is part of the SANKET certification pathway.
Explore the security design
Each part of the SANKET security design has its own page, and the public whitepaper documents it chapter by chapter.
Start with a conversation, not a commitment
Tosh Defence works with security-conscious organisations through a structured evaluation. Tell us about your threat model and we will show you the right deployment path.