1-to-1 chat
Who this is for: anyone using private two-party messaging — Buzzio’s flagship sealed surface.
What it is
Private chat between two Buzzio IDs. Messages are end-to-end encrypted on devices, relayed briefly, then deleted from the server after delivery. Readable history stays in SQLCipher on your phones.
How to use
- Open Chat and start or open a 1-to-1 conversation (Buzzio ID,
@username, or invite flow in the app). - Send text, media, or replies as usual.
- Optional: enable Secure View, disappearing messages, once-view, or view-once media from chat settings / message actions.
- Place a voice or video call from the same chat — see Encrypted calls.
- Block or report from contact info if needed — Safety.
Privacy strip
| Property | Status |
|---|---|
| Content E2EE | Yes — X3DH + Double Ratchet + AES-GCM |
| Zero durable chat metadata | Yes after nothing remains undelivered |
| Delete-on-delivery relay | Yes |
| Undelivered purge | ~3 days |
| Local history | SQLCipher on device |
| Sealed-sender preferred path | Yes — write cutover complete |
| Operator-readable transcript | No |
Scoped definition: What zero metadata means.
Verify: Verify zero metadata.
In-chat privacy tools
| Tool | Behavior |
|---|---|
| Secure View | Mutual screenshot/recording hardening; pending requests ~2h |
| Disappearing messages | Chat-level 24h / 7d / 90d |
| Once-view messages | ~5s after seen + stronger screenshot protection |
| View-once media | Open once, then leave the thread experience |
| Kept messages | Exempt selected messages from disappearing timers |
These reduce device residue after decrypt — they are not Tor anonymity. Glossary: In-chat privacy tools.
Limits
- Free accounts: unlimited messages; Premium raises file size and create slots — Premium and quotas.
- Very late online recipients may miss undelivered envelopes after ~3 days.
- Blocks stop delivery by design.
Troubleshooting
Troubleshooting · FAQ · Delivery path: Message delivery