a436ee77b9
Co-authored-by: npub1ux8n2yfs8qfvgd75s7kyhar2mztac355v6vmrz4juc9l3msw4pgstums9e <e18f3511303812c437d487ac4bf46ad897dc46946699b18ab2e60bf8ee0ea851@sprout-oss.stage.blox.sqprod.co> Signed-off-by: npub1ux8n2yfs8qfvgd75s7kyhar2mztac355v6vmrz4juc9l3msw4pgstums9e <e18f3511303812c437d487ac4bf46ad897dc46946699b18ab2e60bf8ee0ea851@sprout-oss.stage.blox.sqprod.co>
1.6 KiB
title
| title |
|---|
| Buzz Support |
Buzz support
Get help with the Buzz mobile and desktop applications.
Home · Privacy policy · Source code
Get help or report a bug
Use the public Buzz issue tracker to report a reproducible problem or request a feature. Before opening a new issue, search existing issues for a solution.
Include your Buzz version, device and operating-system version, what you expected, what happened, and steps that reproduce the problem.
Do not include private keys, access tokens, passwords, private messages, personal information, or other sensitive data in a public issue.
Workspace and account access
Buzz connects to a workspace through a relay. If you cannot pair, connect, access a channel, or manage workspace-hosted data, contact the administrator or relay operator that provided your workspace. The open-source maintainers cannot restore a lost Nostr private key or change permissions on a relay they do not operate.
Security vulnerabilities
Do not disclose a suspected security vulnerability in a public issue. Follow the private reporting instructions in the repository's security policy.
Privacy questions
For questions about the Buzz privacy policy, open a public support issue only if the question contains no sensitive information. For data stored by your workspace or relay, contact that workspace's administrator or relay operator directly.