Encrypted calls
Private voice and video calls on the 1-to-1 sealed surface. Setup is encrypted; media prefers device-to-device; Buzzio does not keep a server recording you can play back later.
Privacy properties
| Property | Status |
|---|---|
| Call content archive on Buzzio servers | No — we do not record calls |
| Signaling | Encrypted; not kept as a permanent call dossier |
| Media path | WebRTC peer-to-peer when networks allow; TURN/relay only when needed to connect |
| Call history list | Local on device (Call tab hides older records after about 24 hours) |
| Durable “who called whom” archive when idle | Treated like other sealed surfaces — no lasting browsable server file |
How to place a call
- Open a 1-to-1 chat.
- Tap voice or video.
- Or open the Call tab for recent local history and return to people you have called.
In-call controls: mute, speaker, camera on/off, flip camera, end. Screen share is not offered in current controls.
Technical notes
- Calls inherit the same trust boundary as sealed 1:1 messaging: content is not a Buzzio-readable cloud product.
- Signaling uses the sealed call invite path for 1:1 and conference (
deliverSealedCallInvite): no plaintextsender_id_hinton the incoming node; FCM/VoIP wakes omitcaller_id(generic “Incoming call” until the app opens the envelope). Conference flag lives inside the sealed envelope (is_conference). - Conference / multi-party calling may exist in code or roadmap; this page documents the 1:1 product surface.
Limits
- Requires a private 1:1 relationship path in the app.
- Blocks generally prevent continued calling through that relationship.
- Network quality dominates voice/video experience; P2P may fall back to relay for connectivity only — not for Buzzio recording.