Privacy Policy

Last updated: October 15, 2026

Deutsche Fassung

1. Controller

The controller for Voxinity (website, dashboard and Discord bot) is:

2. Summary

Voxinity is a Discord bot that moves players of an ER:LC private server into shared Discord voice channels based on their in-game position. We only process what is needed for this:

• Discord IDs and names, and the voice channels members are in,
• your Roblox user ID and Roblox name if you link your account,
• player names, Roblox IDs and positions from the ER:LC server – briefly, in memory only.

The bot does not record conversations, does not join voice channels and does not read messages. There is no advertising, no tracking and no analytics.

3. This website

This website is served as a static site. It sets no cookies and loads no third-party content (fonts and images are hosted on our server). To deliver the pages, the server necessarily processes your IP address; we do not keep access logs containing IP addresses. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in operating a working website).

4. Dashboard and Discord login

You sign in to the dashboard (https://dashboard.voxinity.xyz) with Discord (OAuth2, scopes “identify” and “guilds”). Discord provides us with:

• your Discord user ID, name and avatar,
• the list of your Discord servers with your permissions there (to show which servers you can manage),
• an access token used to fetch that list.

Name, avatar and token are stored encrypted in a cookie in your browser (session cookie, valid for up to 12 hours or until you sign out). We keep the server list in memory for at most one minute. During sign-in we also set short-lived cookies (10 minutes) that protect against forged sign-in attempts. All cookies are strictly necessary; there are no tracking cookies.

When you set up a server, we store its ER:LC private server key encrypted, the server’s settings, and your Discord ID as the person who set it up. Legal basis: Art. 6(1)(b) GDPR (providing the service you use).

5. Discord bot

On Discord servers the bot has been added to, it processes:

• the IDs of the server, the channels it created and the configured staff roles (stored),
• who is in which voice channel of the server and the display names of these members (in memory only, to decide whom to move and to show it to the server’s admins in the dashboard),
• the moves it performs and the commands you send it.

The bot only changes members in its waiting room and its group channels. Server admins can see in the dashboard who is in these channels and where linked players are in the game. Legal basis: Art. 6(1)(b) GDPR; for members of servers who did not add the bot themselves, Art. 6(1)(f) GDPR (the server operator’s legitimate interest in proximity voice). You can object at any time by leaving the bot’s channels or using /proxvoice optout.

6. Roblox account linking (/verify)

So the bot can recognise you in the game, you link your Discord account to your Roblox account by signing in with Roblox (OAuth 2.0 / OpenID Connect, scopes “openid” and “profile”). Roblox shares your Roblox user ID and name with us. We never receive your password. We use Roblox’s access token once for this request and do not store it.

We store: Roblox user ID, Roblox user name and display name, Discord user ID, the time of verification and whether you opted out of proximity voice. The link applies to all servers using Voxinity. You can delete it at any time in the dashboard under “Roblox account”. Legal basis: Art. 6(1)(b) GDPR.

Verification roles: servers can use Voxinity like a verification bot. On those servers the bot gives verified members the roles the server chose, can set their nickname (e.g. to the Roblox name) and posts a short note in the server’s log channel (your Discord mention and Roblox name). This happens when you verify, remove your link, use “Update roles” or /verify there, or join the server. The roles and nickname are stored by Discord as part of your membership on that server; we only store the server’s settings (role and channel IDs, nickname template). Legal basis: Art. 6(1)(b) GDPR, for the log note Art. 6(1)(f) GDPR (the server operator’s legitimate interest in knowing who verified).

7. Position data from ER:LC

For configured servers, the bot queries the ER:LC API (Police Roleplay Community) every few seconds using that server’s key. It receives the names, Roblox IDs and positions (coordinates, street, postal code) of the players on that server.

This data is kept in memory only: the current and the previous snapshot (for movement prediction). It is discarded or overwritten after a few seconds. No position history is stored. Legal basis: Art. 6(1)(f) GDPR (the server operator’s legitimate interest in proximity voice), or Art. 6(1)(b) for linked players.

8. Logs and error reports

For operation and troubleshooting the bot writes technical logs, e.g. “member moved” or “account verified”. These may contain Discord and Roblox IDs but never tokens or keys (these are redacted automatically). Logs are size-limited and overwritten automatically. Server admins can see the logs of their own server in the dashboard. Legal basis: Art. 6(1)(f) GDPR (security and stability of the service).

Error reports: warnings and errors are additionally kept as error reports so that we can fix problems, including after a restart. The same problem on the same server is stored once, with a counter and the time it first and last occurred. An error report contains the message, the affected Discord server ID and technical details, which may include Discord and Roblox IDs. Error reports are deleted automatically 30 days after the problem last occurred, and at most 500 are kept (the oldest, resolved ones first, are deleted beyond that). Only the operators of Voxinity can see them.

Notifications to the operators: new errors and important events (for example the bot being added to or removed from a server, a server being set up, a restart) are sent to a private channel of the operators via a Discord webhook. These messages contain the same information as the error report, such as the Discord server ID and name, and are stored by Discord as part of that channel. Legal basis for both: Art. 6(1)(f) GDPR (security and stability of the service).

9. Recipients and third parties

• Hosting: Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen. The server is located in Germany. A data processing agreement is in place with the host.
• Discord (Discord Inc., USA): sign-in, bot and voice channels run on Discord, and notifications to the operators are delivered through a Discord webhook. Discord’s privacy policy applies.
• Roblox (Roblox Corporation, USA): sign-in for account linking. Roblox’s privacy policy applies.
• ER:LC API (Police Roleplay Community): source of the position data of the respective private server.

Discord and Roblox also process data in the USA. We do not share data with other third parties and we do not sell data.

10. Retention

11. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). Contact us at contact@nuvon.xyz and include your Discord ID so we can find your data.

You also have the right to lodge a complaint with a data protection supervisory authority.

12. Other

The minimum age of Discord and Roblox applies. We update this policy when the service changes; the version published here applies.