Privacy
Last updated 2026-09-15
Solace Buzz is a client for a Buzz relay. Messages and attachments go to the
relay you paired with; when an AI worker invokes a remote model, relevant
task and context data is sent through the configured model-service route. This
policy describes who runs that relay, what leaves your device, and what we do
not do. For a paid hosted community, the owner can export metadata while the
subscription is active and for 30 days after paid_through; after
that grace an operator may decommission the host.
No third-party trackers. Neither the app nor this website contains any third-party analytics SDK, crash-reporting SDK, or advertising SDK. We do not track you across other companies' apps or websites, there is no advertising identifier, and we sell nothing to anyone.
Who holds your data
A relay is the server your workspace lives on. There are two cases and they have genuinely different answers:
- A relay you or your company operates. Your messages, attachments and workspace records are stored on your infrastructure. We do not receive them and cannot read them.
- A relay we host (a
*.communities.solacebuzz.comaddress). Your messages and attachments are stored on our servers so we can deliver them to your workspace. We use them to run the service and for nothing else — not to train models, not to advertise, not to sell.
The app tells you which relay you are paired with. If you are unsure, that screen is the authority.
What the app puts on the wire
| Data | Why | Where it goes |
|---|---|---|
| Messages and threads | To deliver them | Your relay |
| Images you attach | To deliver them | Your relay |
| Display name and profile | So colleagues know who is speaking | Your relay |
| Public key (your user ID) | It is your identity — every message is signed with it | Your relay |
| Model prompts and task context | To execute worker actions when an AI worker invokes a remote model | Configured model-service route |
All workspace content is linked to your identity, because a workspace in which messages were unattributable would not be a workspace. None of it is used for third-party tracking.
What stays on your device
Your private key is generated on the device and stored in the system keychain. It is strictly device-local, is never transmitted, and we never hold a copy — so we cannot recover it for you, and we cannot impersonate you. Losing the device without a backup means losing the identity.
Permissions the app asks for
- Camera — to scan a pairing QR code and to take a photo to attach to a message.
- Photo library — to attach an image, and to save one.
- Microphone (desktop) — voice huddles.
- Local network (desktop) — optional local relay and shared compute. Remote messaging does not need it.
Each is asked for at the moment it is used, and declining it only disables that feature.
AI workers
Solace Buzz workspaces can contain AI workers. When a worker acts, the message and relevant task context it was responding to is sent to the language-model provider configured for your workspace, through the configured provider route your administrator controls. Which provider that is, and what it retains, is your administrator's decision and is governed by their agreement with that provider. The app records what each worker did so a human can audit it later; that record lives on your relay alongside everything else.
Children
Solace Buzz is a workplace product and is not directed at children. We do not knowingly collect data from anyone under 13. If you believe a child has used the product, email us and we will remove the account.
Your rights
You can ask for a copy of your data, correct it, or have it deleted. On a relay you operate, your administrator does this directly. On a relay we host, email support@solacebuzz.com and we will act within 30 days.
Changes
If this policy changes materially we will say so in the app before the change takes effect, and the date at the top will move. Old versions stay in the public repository's history — a policy that can be rewritten silently is not a policy.