Buzzz is the operating system for local commerce and digital storefronts — and chat is built right into it. Current personal text-message bodies are encrypted separately for participant devices using Matrix Olm. Calls use WebRTC transport encryption. Metadata, service content, decrypted device caches or backups, commerce records and media are outside the text-message encryption guarantee.
Supported personal text is encrypted on the sender's device separately for every participant device using Matrix Olm. Buzzz stores ciphertext for those message bodies.
Talk it through when typing isn't enough. Voice and video calls use WebRTC DTLS-SRTP to encrypt media in transit between participants or a relay. Buzzz does not yet claim a separate, independently authenticated app-level E2EE layer for calls.
Temporary-message settings ask supported clients to remove eligible messages after the selected interval. Recipients can still copy, capture, forward or retain content, and deletion is not guaranteed on every device or backup.
Personal-chat media sends are temporarily paused while client-side file encryption and per-device media-key wrapping are completed. Supported personal text can still be sent with Matrix Olm encryption; structured or service content has different protections.
Message-history backups are encrypted on the client with an account-bound recovery key before upload. Buzzz cloud storage receives ciphertext rather than the cached plaintext history.
Chat is built into Buzzz commerce. Message a seller, agree on the details, and check out right there in the conversation. No links, no leaving the app.
One chat space for the people and businesses you talk to — built into the app you already use to discover, shop and sell.
Supported personal text-message bodies are encrypted per participant device.
WebRTC encrypts call media in transit; calls do not add a separate app-level E2EE protocol.
Supported clients remove eligible messages on schedule; recipients may retain copies.
Media is paused until end-to-end file encryption is complete.
Backups are client-encrypted before upload; restore requires the recovery key.
Our policy prohibits using private chat content to train AI.
Current personal text-message bodies are encrypted separately for participant devices using Matrix Olm. We don't use private chat content to train AI, sell your data or build cross-app ad-targeting profiles. Metadata and decrypted copies remain outside the message-content encryption boundary. Other limits are described above and in our policy. Read our privacy promise →