Encrypted Communication Built to Support GDPR and India's DPDP Act
SANKET is a privacy-by-design communication platform built to support data protection obligations under the GDPR and India's Digital Personal Data Protection Act 2023. Content is end-to-end encrypted, the installation is dedicated to your organisation and runs where you choose, and administrators control identities, devices and retention.
Privacy by design: content end-to-end encrypted
Dedicated installation where you choose
Organisation-defined retention
No advertising or third-party analytics
The shift
Before SANKET vs. After SANKET
Before - current state risks
Staff conversations full of personal data on consumer apps the organisation does not control
No clear answer to where communication data is held and who can reach it
No organisational control of retention or access
End-to-end encryption, so message content is never readable by the server or its operator
After - with SANKET
A dedicated installation in the region and on the infrastructure you choose
Retention windows for server-held data, and disappearing messages from 30 seconds to 90 days that the organisation can enforce
First-party, content-free usage counts that the organisation can switch off, and no third-party analytics
Built for this
The architecture behind the solution
SANKET minimises what the server can ever see: content is end-to-end encrypted, replies, locations, contact cards and link previews travel inside the ciphertext, delivered ciphertext is removed from the server, and retention windows prune what remains.
Server-Blind Architecture
End-to-end encryption, AES-256 at rest and in transit, hardware-backed device keys and a hash-chained audit log support the security-of-processing and privacy-by-design expectations of modern data protection law.
Signal Protocol via libsignal
Built on Signal's independently audited libsignal, with post-quantum PQXDH key agreement and the Double Ratchet with SPQR, so every message has a fresh key.
Administrator Control
Administrators control identities, groups, devices, policies and retention, with FIDO2 security keys protecting the console itself.
Sovereign Deployment
Sanket.Work runs as a dedicated installation in any region on any cloud you choose, operated under contract. Sanket.Enterprise keeps everything on your own infrastructure.
The result
What organisations achieve
Replace consumer messaging with a platform where residency, access and retention are under your control
Demonstrate privacy by design with content that the server cannot read
Reduce the personal data your communication platform holds
Evaluation guide
Questions every buyer should ask
Is message content end-to-end encrypted and never readable by the operator?
Can we choose where the installation and its data reside?
Can administrators enforce retention and disappearing messages?
Is the platform free of advertising and third-party analytics?
Is there an audit trail of administrative actions?
Can the installation run entirely on our own infrastructure if required?
FAQ
Frequently asked questions
Does SANKET help with GDPR and DPDP obligations?
SANKET is designed to support them: content is end-to-end encrypted, the installation runs where you choose, administrators control identities, devices and retention, and there is no advertising or third-party analytics. Your data protection team should assess your specific obligations.
Where is Sanket.Work data held?
In the region and on the cloud you choose, in a dedicated installation for your organisation. Sanket.Enterprise keeps everything on your own servers.
Can SANKET enforce retention automatically?
Yes. Retention windows prune server-held data, delivered ciphertext is removed from the server, and the organisation can enforce disappearing messages, from 30 seconds up to 90 days.
How does SANKET handle data subject requests?
Account records and audit events are held by your installation and can be exported. Message content stays end-to-end encrypted on the participants' devices.
Ready to solve this with SANKET?
Talk to the Tosh Defence team. We start with your threat model and deployment constraints - not a product pitch.