Privacy Model Overview
Buzzio is built with two honest modes:
- Sealed conversations — encrypted on your device, relayed briefly, then readable history stays on your phones.
- Shared rooms and feeds — store more on purpose so history, roles, discovery, and moderation can work.
Either way, Buzzio does not sell your messages, metadata, Buzzio IDs, community posts, Whisper content, backups, or wallet activity.
Get started
- Read the comparison table below once.
- Pick the feature that matches the job (private chat vs shared room vs public feed).
- Open that feature’s page in Help if you need step-by-step controls.
Quick comparison
| Feature | What it’s for | Can Buzzio read the content as part of the product? | History model (plain language) |
|---|---|---|---|
| 1-to-1 chat | Private two-person messaging | No | End-to-end encrypted · delete after delivery · history on your devices |
| Encrypted calls | Voice / video with a private chat partner | No call recordings | Encrypted setup · peer-to-peer media when possible · local call list only |
| Whisper private chat | Time-limited QR anonymous chat | No | End-to-end session · deleted after expiry |
| E2E groups | Private group chat with sealed history | No readable transcript | End-to-end · short catch-up relay · new joiners do not get a full open archive |
| Open-history groups | Groups that need shared backscroll | Shared history is required for the feature | Server-managed encryption · durable history for members |
| Communities | Discord-style spaces with roles and channels | Shared history is required for the feature | Server-held keys so history, roles, and moderation work |
| Broadcast channels | One-to-many announcements | Feed is operated as a channel product | Server-managed encryption · posts kept for the retention window (~30 days) |
| Stories | 24-hour status posts | Media is sealed for delivery; audience / views need product data | Expires about 24 hours · not a permanent private chat archive |
| Whisper Questions | Anonymous ask links | Yes — so you can read answers | Stored for the link owner · not the Whisper private-chat model |
| Contact sync | Optional saved-contact map | Contact IDs / nicknames map (not chat bodies) | Opt-in · off by default |
| Encrypted backup | Optional restore copy you control | Encrypted blobs only; unlock needs your recovery key | Off unless you enable it |
How to choose
Use 1-to-1, Whisper private chat, E2E groups, and private calls when you want a sealed conversation and minimal durable “who talked to whom” archive on sealed surfaces.
Use open-history groups, Communities, and Broadcast when shared continuity, roles, discovery, or one-to-many publishing matter more than operator-blind history.
Use Stories for short social updates, and Whisper Questions when you want anonymous answers you can read later.
What “zero metadata” means here
On private sealed surfaces — especially 1-to-1 after delivery when nothing remains undelivered — Buzzio aims not to keep a durable server archive of who privately talked to whom and what they said.
That does not mean Buzzio stores nothing at all. Account records, safety tools (blocks and reports), push delivery, and shared-history features still need operational data.
What never changes
- We do not sell your data.
- Features that need more storage say so honestly in this overview.
- Maximum secrecy where the product is a sealed conversation; transparent extra storage where the product is a shared room or public feed.
Tips and limits
- “Encrypted” does not always mean “Buzzio cannot operate the feature.” Shared rooms need server-managed keys on purpose.
- Whisper Questions is intentionally readable by the link owner — do not confuse it with Whisper private chat.
- Optional contact sync and optional backup are opt-in — leave them off if you do not need them.
- Retention windows differ by feature (for example Stories ~24 hours, broadcast posts ~30 days, community history on a longer schedule).
Related features
- Security overview — keys, local encrypted database, delete-on-delivery.
- Account and Buzzio ID — identity without a phone number.
- Backup and recovery — optional encrypted restore path.