Buzzio documentation
Site: doc.buzzio.dev · Product: buzzio.dev · Open-source crypto: github.com/ve-21/buzzio-crypto-open-source · Forum: forum.buzzio.dev
Buzzio is a privacy-first messenger with two product lanes: a Privacy section (sealed — 1-to-1, E2E groups, Whisper private chat) that aims to be a blind relay, and a Feature mode (shared — open-history groups, Communities, Broadcast) that stores more by design — and says so. Data is never sold.
Who this site is for
| Audience | Start here |
|---|---|
| New users | Quickstart → FAQ |
| Privacy-focused readers | Privacy guarantees → Threat model |
| Developers / researchers | How to verify → Crypto → Open-source repo |
| Press / auditors | Privacy guarantees → Protocol one-pager → How to verify → Security disclosure |
Start here
- Quickstart — install, create identity, send a first sealed chat
- Download and requirements — platforms and age rules
- Protocol one-pager — sealed-path diagram + Privacy vs Features · PDF download
- Glossary — Buzzio ID, sealed, sealed sender, Whisper, Secure View, and more
- Sealed vs shared — which features are operator-blind
- Privacy guarantees — promises, ceilings, and product refusals
- Why Buzzio ranks in privacy — mechanisms behind the claims
Browse by topic
| Topic | Pages |
|---|---|
| Privacy | Guarantees · Why privacy · Sealed vs shared · Why not unidentified delivery · Zero metadata |
| Architecture | System · Delivery path · One-pager + PDF · Shared media dedup (planned) |
| Cryptography | Overview · How to verify · Open-source repo · X3DH / Double Ratchet · Sealed sender · Groups |
| Features | 1-to-1 · Calls · Whisper · Groups · Communities · Broadcast · Stories |
| Trust | Privacy guarantees · Why not unidentified delivery · Threat model · vs Signal / WA / Telegram · Security disclosure |
| Reference | Retention · Premium and quotas · Subprocessors · Changelog |
| Help | FAQ · Troubleshooting · Security disclosure · Forum · Contact |
Honest ceilings (read once)
- Buzzio does not claim Tor-grade network anonymity.
- “Zero metadata” is scoped — see definition.
- Sealed sender write cutover is complete on 1:1 (legacy plaintext-
fromwrites off). - Shared rooms use server-held or server-managed keys for text; shared-room media dedup is planned.
- Full promise / refusal table: Privacy guarantees.
Full reading order: INDEX