Shared rooms now use TLS-only transport
Open-history groups, Communities, and Broadcast are not E2E. Traffic uses TLS, while text and media are stored without at-rest encryption so Buzzio can operate those spaces.
We have updated Buzzio's shared-room architecture and every public privacy label that describes it.
Open-history groups, Communities, and Broadcast channels are not end-to-end encrypted. Their network traffic uses TLS in transit, but new text, captions, and media are stored without at-rest encryption. Buzzio can read that content to provide history, mentions, search, moderation, roles, and feeds.
There is no server-held DEK privacy model for these surfaces. Legacy encrypted media may remain readable through compatibility code until normal retention removes it.
What changed in the app
Each shared surface now shows an in-chat notice:
- Open-history groups: TLS in transit, plaintext shared backscroll
- Communities: TLS in transit, plaintext history for mentions and moderation
- Broadcast: TLS in transit, plaintext posts
Use 1-to-1 chat, Whisper private chat, or an E2E group when content secrecy from Buzzio is required.