Sanket.Chat
The Problem

Encrypted One-to-Many Broadcast Communication

SANKET's encrypted priority broadcast delivers critical instructions to everyone, a role or a custom list, end-to-end encrypted for every recipient device. Four priority levels, full-screen alerts for urgent messages and acknowledgement tracking show command exactly who has received and acknowledged each broadcast.

The SANKET Answer

End-to-end encrypted priority broadcast

Four priority levels with full-screen alerts

Acknowledgement tracking and re-notification

Audience controlled by administrators

See It In Action

The shift

Before SANKET vs. After SANKET

Before - current state risks

Critical instructions lost in busy group chats

No way to confirm who has read an urgent order

Broadcast lists that anyone can be added to

End-to-end encrypted broadcasts, encrypted separately for every recipient device with libsignal

After - with SANKET

Four priority levels (normal, important, urgent and critical), with full-screen alerts on mobile

Acknowledgement tracking, with re-notification and an administrator alert for urgent broadcasts not acknowledged in time

Priority, deadline and expiry carried inside the encryption, so the server cannot downgrade, delay or replay a broadcast

Built for this

The architecture behind the solution

Broadcasts often carry locations, personnel instructions and response plans. SANKET encrypts each broadcast for every recipient device, and lock-screen text stays generic, so the content is readable only inside the app on the intended devices.

Server-Blind Architecture

Encrypted broadcasts are sent from a dedicated broadcast-sender account on its single approved desktop, and recipients pin the sending device and identity. Because priority, deadline and expiry travel inside the encryption, the server cannot downgrade, move or replay them.

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

Broadcast audiences and sender accounts are managed by administrators in the console. For routine, non-sensitive announcements, administrators can also schedule notice broadcasts, which are clearly labelled as notices that are not end-to-end encrypted.

The result

What organisations achieve

Deliver critical instructions to every intended recipient with acknowledgement confirmation

Keep broadcast content end-to-end encrypted and the audience under administrator control

Give command a clear view of who has acknowledged, with automatic follow-up for urgent messages

Evaluation guide

Questions every buyer should ask

Is broadcast content end-to-end encrypted for every recipient device?

Can we confirm who has acknowledged a critical message?

Is the audience controlled only by administrators?

Can the server downgrade or replay a broadcast?

Do urgent broadcasts follow up automatically when unacknowledged?

Are broadcast senders limited to approved accounts and devices?

FAQ

Frequently asked questions

How does acknowledgement tracking work?

Each broadcast records delivery and acknowledgement per recipient. An urgent or critical broadcast still unacknowledged at its deadline is re-notified to those recipients and raises an administrator alert.

Who can send encrypted broadcasts?

Encrypted broadcasts are sent from dedicated broadcast-sender accounts that administrators create, assign to named administrators and can suspend, each from a single approved desktop.

Is broadcast content encrypted for large audiences?

Yes. Each broadcast is encrypted for every recipient device with libsignal, and attachments are encrypted once with a per-file key carried inside each copy.

Can broadcasts be scheduled?

Encrypted broadcasts are sent immediately. Routine announcements can be scheduled as notice broadcasts from the administration console, labelled as not end-to-end encrypted, for non-sensitive content.

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.