Private Messaging by Architecture: Server-Blind, End-to-End Encrypted
SANKET keeps communication private by design. Every message, file, call, reaction and encrypted broadcast is encrypted on the device with Signal's independently audited libsignal and AES-256, the server relays ciphertext without ever holding the keys, and no SANKET app or server contains third-party analytics.
Server-Blind
No keys to your content on the server
Post-Quantum Protection
PQXDH, SPQR and hybrid TLS
Forward Secrecy
A fresh key for every message
No Third-Party Analytics
In any SANKET app or server
Core Architecture
Server-Blind Architecture
A server-blind design relays and stores only ciphertext, and never holds the keys to read it. Anyone with access to the server, including its administrators, sees encrypted data, not your messages, files or calls.
Traditional server model
Alice types a message
Plaintext on device
Message sent over HTTPS
Encrypted in transit only
Server decrypts and stores
Server holds plaintext
Server re-encrypts for Bob
Server handles the keys
Server can read content
Operator holds the keys
Whoever controls the server can read the content, so a breach or insider threat on the server exposes communication.
SANKET server-blind model
Alice types a message
Plaintext on device
Message encrypted on device
With libsignal, once for each of Bob's devices
Ciphertext sent to server
Server receives encrypted data only
Server relays ciphertext
It holds no keys to the content
Bob's device decrypts locally
Plaintext only on the recipient's device
The server never holds the keys to message content, so a breach of the server or an insider on it yields ciphertext, not plaintext.
What server-blind architecture delivers
Content stays with the participants
Messages, files, calls, reactions and encrypted broadcasts are readable only on the participants' devices, never by the server or its operators.
A server breach yields ciphertext
An attacker who compromises the server obtains encrypted data and no keys to read it, and signed device lists stop the server adding a device to receive copies.
Keys generated and held on devices
Identity and session keys are generated on the device and protected by its secure hardware. The server never holds the private keys to content.
Past messages stay protected
Every message has a fresh key from the Double Ratchet with SPQR, so compromising a key later does not unlock earlier messages.
No content analysis
With no access to content, the server cannot scan, analyse or profile what people say. Routing information needed for delivery stays inside your own installation.
No master key
Groups use pairwise encryption to every member device, so there is no single group key or master key that unlocks all messages.
Double Ratchet with SPQR
Forward Secrecy and Post-Quantum Protection
libsignal's Double Ratchet gives every message a new key that is used once and discarded, so compromising a key today cannot decrypt messages sent in the past. SANKET sessions also run SPQR, a post-quantum ratchet alongside the Double Ratchet, and begin with PQXDH key agreement using a post-quantum Kyber prekey.
For organisations facing persistent adversaries, forward secrecy and post-quantum protection make the difference between a contained incident and the exposure of years of communication, including traffic recorded today for decryption tomorrow.
Session Start
PQXDHPQXDH key agreement establishes the session from identity keys, signed prekeys and a post-quantum Kyber prekey, with signatures verified by libsignal.
Each Message
Triple RatchetThe Double Ratchet advances with the conversation, and SPQR adds a post-quantum ratchet alongside it, so every message uses a unique key.
Key Derivation
HKDFEach ratchet step derives fresh encryption and authentication keys. Message keys are used once and then discarded.
Past Messages
Forward SecrecyDiscarded message keys cannot be regenerated, so an adversary who later compromises a device key still cannot decrypt earlier messages.
Cryptographic Specification
Encryption in SANKET: AES-256 Throughout
Every layer uses published, peer-reviewed standards, with messages encrypted by Signal's independently audited libsignal and everything else by AES-256-GCM. There are no proprietary algorithms and no weaker fallback.
| Layer | Algorithm | Standard | Key Size | What It Protects |
|---|---|---|---|---|
| Message Key Agreement | PQXDH with a post-quantum Kyber prekey | Signal Protocol (libsignal) | X25519 + ML-KEM family | Session establishment that resists harvest-now-decrypt-later collection |
| Message Ratchet | Double Ratchet with SPQR (Triple Ratchet) | Signal Protocol (libsignal) | A fresh key per message | Forward secrecy and recovery after compromise, with a post-quantum ratchet |
| Message Encryption | AES-256-CBC with HMAC-SHA256 | Signal Protocol (libsignal) | 256-bit | Confidentiality and integrity of messages, reactions and encrypted broadcasts |
| File Encryption | AES-256-GCM, one key per file | NIST SP 800-38D | 256-bit | Files, images, video and voice notes, with the key delivered inside the libsignal message |
| Call Encryption | AES-256-GCM frames plus SRTP AES-256-GCM | RFC 7714 | 256-bit | Voice and video media, with five new frame keys every second |
| Transport | TLS 1.3 preferred, AES-256-GCM-only suites | RFC 8446 | 256-bit | Every connection between the apps and the installation |
| Hybrid Post-Quantum TLS | X25519MLKEM768 offered first | IETF hybrid key exchange | X25519 + ML-KEM-768 | Transport key exchange protected against future quantum attack |
| Device Authentication | Device mutual TLS with on-device P-256 keys | RFC 8446 / X.509 | P-256 | Only approved devices with a valid client certificate can connect |
| Key Storage | Secure Enclave / StrongBox / TEE | Platform secure hardware | Hardware-bound | Device keys protected by the phone's secure hardware |
| Local Storage | SQLCipher database and AES-256-GCM file cache | AES-256 | 256-bit | Messages and files stored encrypted on mobile and desktop |
All algorithms are publicly specified standards. Message encryption uses Signal's official libsignal, and AES-256 is required everywhere, with no fallback to weaker ciphers.
Layered Controls
Privacy controls at every level
Administrator Controls
User provisioning and removal by administrators, SCIM 2.0 or single-use invitation
Device approval, revocation, lost mode, locate and server-confirmed remote wipe
Forced disappearing messages, from 30 seconds up to 90 days
Forwarding, clipboard, file download and screenshot policies
Customer-defined classification labels with handling rules
Retention windows for server-held data and a hash-chained audit log
User Controls
Disappearing messages per conversation
Safety-number verification and identity-change warnings
Read receipts and typing indicators
App passcode and biometric unlock
Generic lock-screen notifications that reveal no message content
Screenshot protection and in-chat screenshot alerts on supported platforms
Organisation Data Controls
A dedicated installation in the region, cloud or data centre you choose
Air-gapped operation with everything inside your enclave
First-party, content-free usage counts that the organisation can switch off and delete
No advertising, profiling or third-party analytics in any app or server
Audit records identify people by Sanket ID and never contain message content
Optional account self-deletion that revokes devices and removes the account from use
Regulatory Alignment
Built to Support India's DPDP Act and the GDPR
Data protection starts with architecture. SANKET's server-blind design, choice of where each installation runs and organisation-defined retention are built to support obligations under India's Digital Personal Data Protection Act 2023, the GDPR and similar laws.
Request a Data Protection BriefingIndia's Digital Personal Data Protection Act 2023
Designed to support DPDP obligations: content end-to-end encrypted, an installation that can run entirely in India or on your own infrastructure, organisation-defined retention and no third-party analytics.
Data Minimisation
Replies, locations, contact cards and link previews travel inside the encryption, delivered ciphertext is removed from the server, and retention windows prune what remains.
Privacy by Design and by Default
The server is blind to content by design: it relays ciphertext and never holds the keys to messages, files, calls, reactions or encrypted broadcasts.
Security of Processing
libsignal end-to-end encryption with post-quantum protection, AES-256 at rest and in transit, hardware-backed device keys and device mutual TLS.
Deletion and Retention
Disappearing messages expire on the server and the devices, retention windows are set by the organisation, and accounts can be removed from use.
EU General Data Protection Regulation
Designed to support GDPR principles for organisations that need them, with residency set by where you choose to run the installation.
Data Residency and Transfers
Each installation runs where the organisation chooses, from any region on any cloud to its own data centre or an air-gapped network.
Business Model
Your communication is not a product
Consumer messaging platforms often earn from advertising, which depends on understanding user behaviour. SANKET has no advertising model and no incentive to analyse or monetise your communication.
Consumer messaging platform
Advertising revenue depends on understanding user behaviour
Message metadata (who, when, how often) is commercially valuable
Contact graph analysis serves targeted advertising
Terms of service allow broad data use for 'improving services'
Free service means the user's attention and data is the product
SANKET
Revenue comes from organisational deployments, not data
No commercial incentive to analyse communication patterns
No advertising integrations in any app or server
No third-party analytics or crash-reporting SDK in any SANKET app
Customers own their installation and their data
Evaluate SANKET's privacy architecture for your organisation
Request a technical deep-dive with the Tosh Defence team. We cover server-blind architecture, the encryption specification, data protection and the deployment options that fit your requirements.