Privacy · 1:1 chat

Buzzio 1:1 chat

Private messages designed so even we can’t read them — sealed on your devices, delivered as ciphertext, deleted after delivery. You control who can reach you. We never keep a lasting social graph of who you privately talk to.

On this page

Introduction

Private messages. Not a cloud inbox.

Buzzio 1:1 chat is built for people who want real privacy — not a server folder dressed up as a messenger. Your message is encrypted on your phone before it leaves. Our servers only move an encrypted envelope. Only the other person’s device can unlock it. After delivery, that server copy is deleted. Readable history lives in a locally encrypted database on your devices.

We do not sell your data. Never. Not messages. Not who you talk to. Not your Buzzio ID.

Why Buzzio is best for private 1:1

We can’t read your chats

End-to-end encryption on device — plaintext never lands with us.

No lasting social graph

When nothing is undelivered, we don’t keep “A talks to B” as a private-relationship database.

You control who reaches you

Gate messaging, calls, group adds, and online status — down to My contacts or Nobody.

Identity without your phone number

A random Buzzio ID and a 12-word phrase you control — not SMS OTP tied to your SIM.

Courier, not filing cabinet

Delete-on-delivery plus a short safety purge — not a permanent cloud inbox of private chat.

Honest about every surface

Sealed 1:1 stays sealed. Shared rooms that need storage say so — we never pretend otherwise.

What you get on the sealed surface

The same private lane includes encrypted voice and video calls, disappearing timers, once-view tools, and field-level privacy controls for who can reach you and what they can see.

  • End-to-end encryption
  • Delete-on-delivery
  • No durable social graph
  • Messaging gates
  • Smart Inbox
  • Restrict sharing
  • Disappearing & once-view
  • Block, report & lists
  • Encrypted calls

How it works

Encrypt on device

Keys are derived on your device from your 12-word recovery phrase. We never receive that phrase or your private messaging keys. Only public key material is published so others can encrypt to you. On first contact, devices run X3DH, then switch to the Double Ratchet for ongoing chat. Photos and files get their own encryption keys; those keys ride inside the already-E2E message.

  1. Create account

    Keys stay local. Your phrase never leaves your control.

  2. Publish public material

    Others can seal messages to you — we still can’t open them.

  3. Negotiate & ratchet

    X3DH starts the session; Double Ratchet keeps keys evolving.

Blind relay — courier, not filing cabinet

While a message is waiting to deliver, servers see an encrypted blob plus the minimum routing info needed to wake the right account. They never see readable text, photos, or voice content. You can verify safety numbers in-app when you want out-of-band confirmation that you’re talking to the right person.

Delete on delivery

Buzzio is not building a cloud folder of your private chats. While the other person is offline, an encrypted copy may sit briefly on the relay. When their device takes delivery — decrypts and stores it locally — that relay copy is removed. “Delivered” means the recipient’s device processed the message, not merely that they opened and read it. If someone never comes online, undelivered envelopes are safety-purged after about 3 days.

Multi-device note: delivery is to the account. The first device that successfully receives the message consumes the server copy. Readable history stays on each device unless you restore an optional encrypted backup you control.

How a message moves

1You encrypt on device
2Blind relay holds ciphertext briefly
3Their device unlocks & saves locally
4Relay copy deleted

Offline friend? The encrypted envelope waits (up to the ~3-day safety window), then is purged if never collected. When nothing is left undelivered, there is no who-you-talk-to graph for that chat on our servers.

Encrypted voice & video calls

Setup signaling is encrypted — not parked as a permanent call dossier. Audio and video use peer-to-peer WebRTC when possible (TURN only when networks need help). We do not record calls. The call list you see lives on your device. When nothing remains for setup, private calls are treated as a zero durable call-metadata surface. Read the full private calls story.

Privacy controls

Who can message you

Open Profile → Advanced security → Only contacts can message me. When this free toggle is on, people who are not in your opt-in synced contacts cannot send you 1:1. On their side the send fails with “You can’t message this contact.” You don’t get notified that they tried.

  • Synced contacts can still message you
  • People you Accept locally can message — without saving them as a contact
  • If you message someone first, they can reply
  • Turning it on does not announce the setting to others

Your inbox stays yours. Strangers don’t get a free seat at the table.

Smart Inbox

Smart Inbox is a Premium safety filter for 1:1. Unknown senders — people who are not saved contacts and not Accepted on this device — stay out of your main chat list until you choose Accept or Block. Open it from Advanced security → Smart Inbox.

Accept

Moves the chat into your main 1:1 list. Does not save them as a contact, does not sync, and does not notify them. Accept is device-local.

Block or report

Leaves Smart Inbox. They can’t message or call you. Report also sends a reason plus recent messages for review, then blocks.

3-message limit

An unknown sender can send up to 3 messages. The 4th is blocked until you Accept — on both client and server.

Not a social graph

Accept is permission to talk on this device — not a Buzzio address book of who you know.

Advanced security

Profile → Advanced security is the control room for tighter messaging and inbox gates — separate from everyday Privacy fields like last seen or group-add.

Only contacts can message me

Hard gate: unsynced people can’t start a 1:1 to you.

Smart Inbox

Premium filter that parks unknown chats until you decide.

Auto-archive unknown contacts

Premium: first chats from unsynced people wait in Advanced security until Accept or Block.

Silent call for unknowns

Unsynced callers can still show Accept/Decline — without a ringtone blast. Off by default.

Stealth Stories

Premium: view stories without appearing on the author’s who-viewed list.

Two-factor authentication

Optional TOTP for stronger account sign-in protection.

App lock and recover hidden chats live under Profile → Privacy. Hide or lock a single chat from that contact’s info.

Who can add you to groups

Under Privacy → Groups, choose who may add you: Everyone, My contacts, My contacts except…, or Nobody. The default when unset is My contacts — so random people can’t drag you into rooms you never asked for. Contact-based options need optional contact sync turned on.

Who can call you

Under Privacy → Calls, set who can place a voice or video call to you — same audience choices, default My contacts. Pair it with Silent call for unknown contacts in Advanced security if you want surprise callers quiet.

Online status & last seen

Under Privacy → Last seen and online, choose who can see when you’re online or last active — Everyone, My contacts, My contacts except…, or Nobody. Default is My contacts. You can also hide online status for a single contact from their contact info. Stale presence is cleaned after about 24 hours. Read receipts and typing indicators are separate toggles under Messaging privacy.

Restrict sharing

On a 1:1 contact’s info, turn on Restrict sharing under message security. While it’s on, new messages in that chat can’t be forwarded, shared out, saved to Saved Messages, or saved to the gallery. Messages sent before you turned it on stay unrestricted. Use it when the thread itself should stay inside the chat — not wander into screenshots folders and forwards.

Disappearing messages

Open contact info → Disappearing messages, or set a default for new chats under Privacy. Timers: Off · 24 hours · 7 days · 90 days. Either person in the chat can change it. Countdown starts when you send — not when they read. Applies to text and media. Kept messages let you exempt specific bubbles until you unkeep them — without creating a Buzzio-readable cloud transcript.

Once-view messages

Once-view mode

Swipe up in a 1:1 chat to turn it on (swipe again to turn off). New messages leave after they’re seen — timer from about 5 seconds up to 5 minutes. Built for chats that shouldn’t linger on screen.

View-once media

Send a photo, video, or voice as view-once. It opens once in a secure viewer, then is removed from the experience. Send it once — don’t leave it sitting in the thread.

Chat tools

How block & report work

Block

From contact info, chat actions, or Privacy → Blocked contacts. Blocked people can no longer send you messages or call you. Profile and presence stay closed; they shouldn’t be able to add you to groups either. Manage the list anytime.

Report

Choose a reason (spam, harassment, scam, and more). Report blocks them and can attach the last few messages from your device as evidence for review. Safety evidence is not sold and is kept only as long as needed for review.

Add to favorites

On contact info, tap Add to Favorites. Those chats show up under the Favorites filter on the Chat tab and in Profile → Lists. Favorites are a free, local shortcut for people you talk to most — separate from Premium custom lists.

Clear chat

From the chat More menu, choose Clear chat. Clear all messages, or media files only — and optionally clear starred items too. This wipes the local history on this device. It does not delete the other person’s copy. Media you already saved to your gallery stays on your phone.

Add to list

From contact info or multi-select on the Chat tab, add chats to a list. Favorites and unread filters are free. Custom lists are a Premium perk — create a named list, pick chats, and use it as a Chat tab filter so big inboxes stay organized without changing privacy.

Contacts & identity

How contact sync works

Contact sync is optional and off by default. Buzzio does not import your phone address book as identity — you add people by Buzzio ID, QR, or invite. When you opt in, we store a map of the Buzzio IDs and nicknames you saved — not your chat history — so contact-based privacy and story audiences can work across devices and reinstalls.

Benefit: restore contacts

New phone or reinstall — your saved Buzzio contacts and nicknames come back with you.

Benefit: “My contacts” rules

Group-add, calls, last seen, and messaging gates can use your synced contact set.

Benefit: Stories audiences

Contact-style story audiences need sync so the right people see what you share.

You stay in control

Turn sync off anytime. Leaving it off keeps nicknames device-local. Turning it off stops server sync and removes the synced map.

Why “My contacts only” works

Most privacy fields share the same audience model: Everyone, My contacts, My contacts except…, or Nobody. “My contacts” means people in your opt-in synced contact list — mutual trust you chose, not a graph Buzzio invents from chat traffic. That is how messaging gates, call allow-lists, group-add, username findability, and online status stay consistent without turning private chats into a server address book of who talks to whom.

Tip: enable contact sync if you want My contacts rules. Without sync, contact-based audiences can’t see who you saved.

How your identity is protected

Your account is a randomly generated 12-digit Buzzio ID — not your phone number, not SMS OTP, not a personal email inbox. Messaging keys are derived on-device from your 12-word recovery phrase. We never receive that phrase or your private keys. Optional @username is separate and gated by who can find you by username (default My contacts). Who can find you by Buzzio ID is also a field-level setting you can tighten to Nobody.

  • No phone number required to create a private identity
  • Buzzio ID is random — not derived from your real-world contacts
  • Recovery phrase and private keys stay on devices you control
  • Profile fields (photo, description, ID, username) each have their own audience
  • Losing devices + phrase with no unlockable backup means we cannot recover that identity — by design

Why it’s secure

The crypto stack — safe to say publicly

Serious private messengers advertise their crypto model. Naming X3DH, Double Ratchet, per-message keys, and forward secrecy builds trust. It does not hand attackers your keys.

X3DH

Devices agree on secrets without shipping a password.

Double Ratchet

Keys keep evolving as you chat.

Per-message keys

Each message gets its own derived key.

Forward secrecy

One exposed key doesn’t unlock the whole history.

AES-GCM

Authenticated encryption for message and media blobs.

secp256k1 + HKDF

Elliptic-curve and key-derivation foundation.

Why we have so little metadata

Most messengers keep a permanent cloud folder: who you talk to, when, how often, and a searchable inbox. Buzzio 1:1 is built the opposite way. We move sealed envelopes long enough to deliver them, then delete them. Readable history stays on your devices. That design is why private 1:1 produces very little lasting server metadata — there is nothing left to file once delivery is done.

While undelivered

  • Encrypted blob
  • Minimum routing to wake the account
  • Timing & delivery flags

Never

  • Readable text
  • Photos or voice content
  • A plaintext transcript we can open later

We never store who you privately talk to

If there are no undelivered messages left on our relay for that private conversation, we do not have a server-side social graph of who you privately talk to for that chat. We don’t keep a lasting record of “User A chats with User B.” Your conversation list and message contents stay on your devices — not in a Buzzio address book of your private relationships.

  • No durable “who talks to whom” graph for that private chat
  • No searchable archive of what you said
  • No way for us to open your private transcript later
  • Your chat list lives on your devices

How metadata clears when nothing is undelivered

  1. Message waits as ciphertext

    Only a sealed envelope and minimal routing sit on the relay.

  2. Recipient device takes delivery

    They decrypt and store locally. The relay copy is deleted.

  3. Queue empties for that chat

    When nothing remains undelivered, temporary routing metadata for that hop is gone.

  4. No lasting social graph

    We don’t keep “A talks to B” as a private-relationship database for that chat.

Undelivered envelopes that are never collected are safety-purged after about 3 days. Stale presence is cleaned after about 24 hours. Optional contact sync is separate and only exists if you turn it on — it is not a sealed-chat social graph.

What “zero metadata” does not mean

It does not mean Buzzio stores zero bytes anywhere. Accounts need an ID, public keys so encryption can start, push tokens so notifications work, and safety tools (blocks, reports) so abuse can be handled. Those are operational and safety — never sold — and they are not a private chat social graph.

Other Buzzio surfaces (Communities, Broadcast, open-history groups) store more by design because those products need shared rooms and discovery. Private 1:1 is the sealed lane.

Ready to use sealed 1:1?

Download Buzzio and start a private chat — encrypted on your devices, controlled by your privacy settings, not stored as our inbox.