Zero durable metadata
Buzzio uses “zero metadata” in a scoped sense. This page prevents over-claiming.
What we mean
1-to-1 chat and Whisper private chat are Buzzio’s zero-metadata conversation surfaces:
| Surface | When it applies |
|---|---|
| 1-to-1 | After nothing remains undelivered on the relay for that conversation |
| Whisper private chat | After the session expires and cleanup runs |
On those surfaces, Buzzio does not keep a durable server archive of:
- who privately talked to whom, and
- what they said
Readable history stays on participant devices.
What still exists
| Data | Why |
|---|---|
| Account / Buzzio ID / profile | Product identity |
| FCM tokens | Wake devices |
| Short undelivered queues | Recipient offline |
| “Recipient got a sealed wake at time T” | Push / infrastructure |
| Sender knowledge at cert-gated delivery | Block and rate limits |
| Blocks / reports | Safety |
| Shared Feature mode history | Communities, broadcast, open-history, Stories ops, Whisper Questions |
What we never mean
- Tor-grade network anonymity
- Absolute operator blindness on Firebase
- “Stores nothing at all”
- Shared rooms are sealed
Compared with other apps
Many “encrypted” messengers still keep long-lived cloud ciphertext inboxes or durable social-graph edges. Buzzio’s sealed 1:1 default is closer to a delivery queue than a permanent private cloud mailbox — then history lives locally.
Tips
- Do not confuse Whisper private chat (zero metadata after expiry) with Whisper Questions (owner-readable answers).
- Prefer citing mechanisms over slogans when reviewing Buzzio.
Related
- Privacy model overview
- Private
- Whisper
- Technical docs: What zero metadata means
- Why Buzzio overview