Privacy Policy

Effective date: May 13, 2026

The short version

SemaBuzz collects no personal data from the app. There are no accounts, no server storing your messages or identity. This website uses Google Analytics to understand traffic patterns — no personal information from the app is involved.

1. What we collect

Nothing. SemaBuzz does not collect, transmit, or store any personally identifiable information. Specifically:

2. How messages are handled

All messages are encrypted on your device using ECDH P-256 key exchange and AES-256-GCM before they leave your machine. The relay server forwards only encrypted bytes. The relay holds no encryption keys and cannot read the contents of any message, file, or whiteboard stroke.

When a session ends, no record of the conversation is retained anywhere by SemaBuzz or its relay.

3. The relay server

SemaBuzz requires a relay server to connect two peers. You must self-host the open-source SemaBuzz Relay software. The privacy practices of any relay are the sole responsibility of whoever operates it.

4. Local data

The application stores only your preferences (theme, relay address, indicator settings) and profile data (handle, avatar) locally on your device. This data never leaves your machine unless you explicitly share it with a peer during a session handshake.

5. Third-party services

This website uses Google Analytics (gtag.js) to collect anonymised page-view and traffic data. Google may set cookies and log your IP address per Google's Privacy Policy. This data is used only to understand how visitors find and use the site; it is not linked to any identity or app usage.

This website also uses Google Fonts, which may log your IP address per Google's privacy policy.

6. Children

SemaBuzz is not directed at children under 13. We do not knowingly collect any information from children.

7. Changes to this policy

If this policy changes, the updated version will be posted here with a new effective date. Continued use of the software after changes are posted constitutes acceptance of the revised policy.

8. Contact

Questions about this policy can be raised via GitHub Issues.