1. Who operates VEYRA
VEYRA is a Minecraft server management service operated by its owner. For privacy questions or data requests, use the account help page to open a private support request. The service is hosted through Cloudflare Pages and Cloudflare D1.
For account and server information described below, VEYRA decides why and how that information is used. When a server owner connects a Minecraft server, the owner chooses what server data is sent to VEYRA and who on their team can see it.
2. Information we collect
Account and security information
When you register or sign in, VEYRA stores your email address as an account identifier, your chosen username, and a password hash. New accounts must confirm their email address using a one-time link before sign-in. The service also creates a signed, 14-day session cookie when you sign in. Passwords are not stored in plain text.
To limit abuse, requests use the IP address supplied by Cloudflare for rate limiting. Rate-limit counters are stored with their time-window keys. Cloudflare may also process network and request metadata when delivering the site.
Server and player information
If a server owner installs and pairs the VEYRA plugin, it sends server software and Minecraft version, online player count, server health metrics, player UUID and username, online state, health, world, coordinates, and an inventory summary. It also sends sampled terrain, biome names, and player join/leave events. Player snapshots are refreshed by server heartbeats, which default to every 10 seconds.
Moderation, commands, and anti-cheat review
VEYRA stores staff actions, queued Minecraft commands and their delivery results, anti-cheat signals, review decisions, and audit events. Signal records may include a player UUID and username, check name, score, world, coordinates, and detector details. VEYRA does not use these signals to automatically ban players.
Support and server settings
Support requests include their contact handle, subject, category, message, status, staff reply, and creation time. People who cannot sign in can open an account support request without email verification. The page gives them a private status link; VEYRA stores only a hash of that link, and the requester is responsible for keeping the link private. Authenticated support tickets include their subject, category, messages, status, assignment, and attached files. A ticket can contain up to five attachments, each up to 256 KB. Server settings may include a server name, logo, platform, team membership, and role. Support staff may see tickets to answer them; server collaborators may see information allowed by their role.
3. How we use information
- To create accounts, authenticate users, and protect account access.
- To connect a server, display its status, and deliver actions requested by authorized staff.
- To show player snapshots, map locations, server events, and anti-cheat review context to authorized server collaborators.
- To answer support tickets, prevent abuse, troubleshoot failures, and protect the service.
Where applicable law requires a legal basis, processing is based on providing the service you request, legitimate interests in operating and protecting VEYRA, legal obligations, or consent where required.
VEYRA does not currently run advertising or sell personal information. The current site does not load a third-party advertising or analytics script. When anti-cheat alerts display a Minecraft player head, your browser requests that image from MCHeads using the player UUID; MCHeads may receive your IP address and standard request metadata. If the image is unavailable, VEYRA shows an initial instead.
6. Retention and deletion
Account, support, audit, moderation, and server records are retained in the service database. The current application does not have a self-service account deletion control or a general automatic retention schedule. Current player snapshots are overwritten as new heartbeats arrive; offline player records, server events, anti-cheat signals, command history, and tickets may remain until removed by an owner or staff member, or until the related server or ticket is deleted. Expired invitation and password-reset token hashes, and rate-limit records, are not currently covered by a general automatic cleanup schedule.
You can remove a server from its settings, which deletes its associated telemetry and server data. Staff can delete a support ticket, which also deletes its messages and attachments. These actions do not delete your VEYRA account or every audit record. To request access, correction, or deletion of account data, open a private support request through the account help page and describe your request. We may ask for information needed to verify the request and may retain records where the law permits or requires it.
7. Your choices and privacy rights
Depending on where you live, you may have rights to access, correct, delete, restrict, receive, or object to certain uses of your personal information, or withdraw consent where processing relies on consent. You may also complain to your local privacy regulator. Contact VEYRA through the account help page to make a request. We will respond as required by applicable law. There is no account self-service export or deletion flow at this time.
You can change your username and password in account settings, sign out to clear the current session cookie, and ask a server owner to remove your collaborator access. If you do not want your Minecraft player data sent to VEYRA, ask the server owner to disable or uninstall the VEYRA plugin. VEYRA does not make player bans solely by automated processing.
8. Children and server player data
VEYRA is a server administration tool and is not designed to collect information directly from children. Server owners are responsible for deciding whether to install VEYRA, for providing any notices required to their players, and for having a lawful basis to send player information to the service. If you believe a child’s personal information was submitted improperly, contact VEYRA so it can be reviewed.
9. Changes to this policy
This policy may be updated as VEYRA’s features or data practices change. The current version and its effective date will be posted on this page. If you keep using VEYRA after an update, the new policy applies to future use, subject to rights that cannot be waived under applicable law.
VEYRA