Secure Comms

Encrypted voice and text, with proof of every step.

Pair two devices by comparing a short code. Press to talk, check what the transcript says, then send. Each stage comes back as a signed receipt.

Not launchedWorks locallyTwo-device test not yet verified

Screenshots

Real screenshots of the Secure Comms app, taken 2026-10-08. Two test devices ("alpha-demo", "bravo-demo") ran as two separate processes on one BB2G machine, talking over loopback. The messages are made up for the demo.

Secure Comms conversation: a received text message, then a sent voice message with its reviewed transcript and receipt stages from Queued to Acknowledged by person. — Demo data Test instance running in mode B over loopback; LAN mode is off on the installed service. Sender's view. The voice message shows each receipt stage: queued, sent to transport, received by device, verified, playback completed, acknowledged by person.

Secure Comms receiver view: the voice message marked untrusted content with Listen, Acknowledge and Receipt buttons. — Demo data Receiver's view. Received content is marked untrusted, and nothing in it runs automatically.

Secure Comms on a phone-width screen. — Demo data The same app at phone width.

What works today

Shown on BB2G's machine with automated tests and an independent code review (final verdict: ACCEPT).

Pairing with a QR or text code, plus a 3-number verification code that both people compare
End-to-end encryption with Olm (vodozemac: triple Diffie-Hellman key agreement plus the Double Ratchet)
Voice messages carry the original audio. The transcript is made on the device, and the sender reviews it before sending
Signed receipts for each stage, which you can check offline
Tampered, replayed, misaddressed, expired and forged messages are refused
Store-and-forward with retries; a message sent while the other device is off arrives when it comes back
Starts offline with no network listener. Network modes need an explicit choice, and gateway mode needs a typed confirmation and switches off at restart

Not verified or not available

Two physical devices: not verified yet. Every test so far ran two processes on one machine
Local network (LAN) mode, relay and tailnet access: built and tested, but switched off by the owner for now
LoRa radio, satellite and acoustic modem: no hardware attached, so not available
Downloads: not available. There's nothing to install yet

We don't call this "unhackable", "untraceable" or "production-ready". The claims on this page are the only ones we make, and each has test evidence.

Availability list

Tell me when it's available

Leave an email and we'll send one note when a product opens to customers. That's the only thing we'll use it for. There's no newsletter and no sales sequence. Today nothing is sent: emails are stored until launch.

What we store: your email, the product you picked (optional) and the date. We don't store your IP address, browser details or a name.

Why: only to tell you when the product becomes available.

Where: a private storage area in BB2G's hosting account (Vercel Blob, private access). It isn't publicly readable. The BB2G owner reads it; Vercel, our host, processes it on our behalf.

How long: 12 months from your last request, then it's deleted automatically.

Deletion: use the "Remove my email" button at any time, or ask BB2G. Full privacy notice.