The short version

Privacy stays close.

Quiet Dictation Bridge has no account system, analytics, advertising, or cloud relay. Its working data stays on your devices or travels directly between the two devices you pair.

What stays on your device

Received transcripts are stored in your computer browser’s IndexedDB. License tokens and their last verification result are stored in localStorage. Pairing codes are kept only in page memory and disappear when you reload. You can export transcripts as JSON or clear them at any time.

Speech recognition

The microphone control is enabled only when the browser exposes an on-device recognition mode. Quiet Bridge requests that mode and does not deliberately fall back to cloud transcription. Your browser or operating system supplies the speech engine and its installed language pack, so review its privacy settings as well. You can always use typed text to test the bridge.

What crosses the network

Pairing uses WebRTC without configured STUN, TURN, or application relay servers. The invitation and answer contain short-lived local connection metadata and are exchanged by you. Confirmed text travels over the resulting DTLS-encrypted peer connection. Only the device you pair can receive it.

Licenses and checkout

If you buy or verify Quiet Kit, your browser contacts the Sociobot billing API. The API receives the license token, product slug, and ordinary request metadata such as IP address. Checkout is hosted by Sociobot/Dodo, the merchant of record; their policies apply to payment details. Quiet Bridge never receives card details.

Contact and changes

This policy is effective 28 August 2026. Material changes will be reflected here. Questions can be raised through the project’s public source repository.