Watch a sentence become ciphertext
This runs the actual production encryption code tebDictate ships (e2ee-live-cursor.js) —
right here, in this page. No phone, no account, nothing sent anywhere.
Prove it on the real thing — 60 seconds
Verify the live service, end to end, with your phone and a laptop.
- On a laptop, open tebchart.com/dictate. A QR code appears.
- Press F12 (or right-click → Inspect) → click the Network tab → type
streamin the filter box. - Scan the QR with your phone's camera and dictate a sentence out loud.
- Back on the laptop, click the
streamrequest → open the EventStream tab (in Firefox, the Response tab). - Read the data arriving from our server. Every frame looks like:
Your words are nowhere in it — only{"v":2,"iv":"9Xk2…","ct":"Qz7Rf1p…","n":3}
ct, the ciphertext. The readable text appears only on your screen, after your browser decrypts it.
Bonus — try to break it: attempt to send unencrypted text to the relay and it refuses with
HTTP 400 — end-to-end encryption required. The server is physically unable to store your words in the clear.
Why this is real, not a marketing word
The design, in four facts anyone can check.
Keys meet through your camera
The pairing key travels inside the QR code, scanned camera-to-screen — never through our servers. So we can't sit in the middle.
Standard, audited crypto
X25519 key agreement → AES-256-GCM, the same primitives that protect Signal and TLS. No home-grown ciphers.
Nothing is stored
No account, no database of notes. The relay holds only ciphertext under a key that expires in minutes — undecryptable the moment your session ends.
The code is open to read
The entire client is plain, un-minified source you can inspect line by line.
Read the source yourself: dictate.html · e2ee-live-cursor.js · dictate-phone.html