Privacy policy

1. Controller

Email: kontakt@byterider.xyz

2. Bedrock Simple Voice in brief

Bedrock Simple Voice is a free connection service for the Bedrock Simple Voice plugin. The website accepts the voice connection in the browser. The relay associates it with the Minecraft server selected by a PIN and forwards control and voice data between the browser and game server.

Bedrock Simple Voice does not record voice packets and does not store them as audio files. There is no advertising, audience measurement or creation of user profiles.

3. Website access and infrastructure protection

Technically necessary connection data is processed when the website is accessed. This may include the IP address, time, requested address, transferred data volume, response status, browser and operating system information.

This processing is necessary to deliver the website, establish encrypted connections, defend against attacks and investigate errors. The legal basis is Art. 6(1)(b) GDPR for providing the requested service and Art. 6(1)(f) GDPR. The legitimate interest is the secure and reliable operation of the free service.

The relay process does not maintain its own HTTP access log. Technical logs produced by upstream network or reverse proxy services are deleted when they are no longer needed for delivery, security analysis or troubleshooting, unless statutory retention obligations apply.

Cloudflare

Cloudflare is used for encrypted delivery, DDoS protection and WebSocket security. Cloudflare processes IP addresses, technical request information and security events. The provider is Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA, including its European group companies.

Processing outside the European Union cannot be ruled out. Cloudflare states that it uses the EU Standard Contractual Clauses and additional safeguards. Further information: Cloudflare privacy policy and Cloudflare GDPR information.

Server location

The application server is hosted by Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. Further information: Hetzner privacy policy.

4. Connecting to a Minecraft server

When Bedrock Simple Voice is used with a PIN or saved device session, the following data may be processed depending on the functions used:

• IP address as a short-lived security key against abusive sign-in attempts,
• one-time connection code, server ID and connection token,
• Minecraft player name and player UUID,
• a freely chosen device name and technical client, browser and audio capabilities,
• connection status, latency and quality information,
• aggregate counts of active game servers and connected Bedrock and Java voice users,
• group, participant and volume information,
• chat messages when web chat is used, and
• microphone and voice packets during an active voice connection.

The data is processed to authenticate you, establish the requested voice connection, associate players and groups, transmit audio and perform the functions you select. The legal basis is Art. 6(1)(b) GDPR. Security and abuse prevention additionally rely on Art. 6(1)(f) GDPR.

Plugin update checks

The update checker is enabled by default and contacts the Modrinth API and the public Byterider version service at server startup or when an administrator explicitly requests a check. Only the server platform and Minecraft version are sent as filters. The providers necessarily receive the game server's IP address and standard HTTP connection metadata. No server names, player information, UUIDs or voice data are sent. Disable it with updatechecker.enable: false.

5. Forwarding to the selected game server

The Minecraft server selected by the PIN receives the connection data required for authentication and operation. This includes the identity, session, status, chat and voice data described above. The server processes this data under its own responsibility and uses Simple Voice Chat to determine which connected players receive voice packets.

Voice data is also forwarded to players who are allowed to hear you based on proximity, group and server rules. The privacy information of the respective server operator applies to further processing on that Minecraft server.

6. Relay retention periods

• Connection codes are held only in memory, are single-use and remain available for no more than five minutes.
• Active connection, control and voice data remains in memory only for the duration of the connection. Voice data is not recorded.
• When web chat is enabled, public chat messages are forwarded live to authorized browsers. Bedrock Simple Voice creates no permanent chat history; the browser displays no more than the latest 200 messages of the current page session.
• Public live counts are derived from active connections, contain no player names or UUIDs and are not stored as usage history.
• Server name, plugin version and server icon are stored only while the game server is connected to the relay.
• For registered game servers, a random server ID and SHA-256 hash of the relay access token remain stored while the registration exists. The relay does not store the token in plain text.

Saved device sessions are primarily stored by the selected game server and locally in the browser. The central relay does not maintain a permanent player database of its own.

Separately, the private admin panel stores aggregated daily Relay history for up to 90 days: active game servers, split into new and returning registrations, and the daily maximum of simultaneous voice users. A game server counts as active if it connected at least once on that UTC calendar day. A day-scoped hash of the Relay server ID is used only to deduplicate that day's count. The history contains no server names, addresses, player names, player UUIDs, or per-player timeline. Public live counts are still not stored as a history.

Optional status reports from independent installations

Self-hosted relays and direct-mode installations are not automatically visible in central counts. Server operators can therefore enable voluntary anonymous status reporting. This feature is disabled by default.

A report contains only a random installation ID, product version, platform category, relay mode, number of active servers, aggregate Bedrock and Java voice user counts, timestamp and random nonce. It never contains server name, server domain or server IP as payload, server icon, player names, player UUIDs, chat messages, audio or voice content, group information, pairing codes or session tokens.

The technical client IP is present for the HTTP connection but is used only for rate limits and abuse prevention and is not stored in the status record. Only a hash of the status token is stored server-side. HMAC signatures, timestamps and one-time nonces protect against manipulation and replay.

A report is considered offline after 150 seconds without a heartbeat. Nonces are removed after five minutes and reporting identities without a successful report after 30 days. The public status API only returns totals. Operators can stop reporting with status-reporting.enabled: false and, while the server is stopped, delete data/status-reporting.json to reset the local ID and token.

Pseudonymous plugin diagnostics

Separately, diagnostics is enabled by default, including after a plugin upgrade. It can be disabled with diagnostics.enabled: false in config.yml. Every 60 seconds the plugin reports a random installation and process ID, plugin version, platform category, relay mode, Relay version/build, the random Relay server ID used to match it in the private admin panel, and aggregate totals for all players, Bedrock players, Bedrock voice users, all browser voice users, and their respective high-water peaks. Bedrock counts are marked unavailable when Geyser/Floodgate cannot be queried on the plugin platform. A timestamp and nonce protect against modification and replay.

It also reports up to 20 aggregated error fingerprints. Each contains only a plugin component and operation, exception class name, derived SHA-256 fingerprint, occurrence count and last-seen time. Error text and stack traces are not sent. Server names, domains and IPs as payload, icons, player names and UUIDs, chat, groups, pairing codes, session tokens, and voice or audio data are also excluded.

The technical source IP at the diagnostic endpoint is used only for rate limits and abuse protection and is not stored in diagnostic records. Aggregate counters and error categories are stored under a random pseudonymous installation ID, along with only a hash of the reporting token. Player peaks are cumulative maximum values without a timeline or timestamp. Error events are deleted 30 days after their last occurrence; the latest installation snapshot is removed 30 days after its last heartbeat. The local data/diagnostics-reporting.json file contains the random ID and secret reporting token; stop the server and delete this file to remove both.

The overview at /admin/ is protected by a dedicated relay admin account configured locally through the server console. There is no default password. Installations use random IDs. The separate Relay-server view may show a display name already supplied over that server's authenticated Relay connection; diagnostic reports do not collect that name.

Private operational monitoring stores minute-level aggregate measurements of servers, browser/Voice connections, payload throughput, CPU, memory, outgoing queues and event counters. Hourly records per random Relay-server ID contain observed Voice peaks and traffic deltas, without player identifiers. Retention defaults to 30 days and can be configured to 1–90 days. The private admin audit log contains time, action, pseudonymous target and outcome, not credentials or IPs; it is additionally limited to 2,000 entries. Received positive error-counter increases are kept for 30 days for time-window queries. None of these private operational records are exposed through the public status API.

The Relay operator may optionally set BSV_RELAY_DISCORD_WEBHOOK_URL. Then one Discord alert is sent after the first accepted heartbeat for a new diagnostic installation. It contains only random installation and Relay IDs, plugin version, platform and Relay mode—not names, addresses, player counts, errors, tokens, chat or audio. Failed deliveries are retried; existing installations are not reported retroactively. Discord processes the alert under its own terms and retention rules. Alerts are disabled when the environment variable is unset.

7. Local browser storage

Bedrock Simple Voice does not use advertising or analytics cookies. Only technically necessary browser storage is used for settings and optional saved connections:

• IndexedDB for the session token, device identifier, player and server association,
• Local Storage for language, theme, microphone, volume, device and participant settings,
• Cache Storage used by the service worker so the web app can load and update reliably.

This data is stored only on your device. It is technically necessary for the service expressly requested under Section 25(2) TDDDG. You can remove the saved voice session in the settings. Other local data can be deleted through the website or browser data controls.

8. Microphone and device features

The browser requests microphone permission before use. Without permission, Bedrock Simple Voice can operate in listen-only mode. Microphone audio is processed only while a voice connection exists and transmission is active according to the selected settings.

Wake Lock, Media Session and web-app installation are used only to improve control and recovery on mobile devices. They do not create additional user profiles.

9. Contact

If you contact us by email, the sender address, content, time and technically necessary metadata are processed to answer the request. Depending on the subject, the legal basis is Art. 6(1)(b) or (f) GDPR. The data is deleted once the request has been fully handled and no statutory retention obligation applies.

10. Your rights

Subject to the statutory requirements, you have the right to access, rectification, erasure, restriction of processing, data portability and objection. An email to kontakt@byterider.xyz is sufficient to exercise these rights.

You also have the right to lodge a complaint with a data protection supervisory authority. The competent authority is in particular:

11. Automated decisions, changes and language

There is no automated decision-making within the meaning of Art. 22 GDPR. Automatic limits on failed sign-in attempts are used exclusively to protect the service.

This privacy policy is updated when features, providers or legal requirements change.

This English translation is provided for convenience. The German privacy policy remains the authoritative version.

Last updated: 16 October 2026