Loading
Effective date: 2026-06-22 · Last updated: 2026-06-22
Data controller: MineStar Network , contacto@minestar.me
StarAC is a Minecraft server anti-cheat plugin. We never collect player names, IP addresses, chat messages, or any personally identifying information. By default StarAC sends two things, both anonymous: (1) operational data that identifies a server (a random server UUID) and never a person, and (2) anti-cheat improvement datain which every player's identity is pseudonymizedon the server before it ever leaves (HMAC of the UUID under a secret salt that never leaves the administrator's machine , see section 3c). This improvement data is part of how StarAC works and is always on , it cannot be turned off, because the plugin relies on this shared, non-identifying data to keep cheat detection accurate for every server. The data we receive is anonymous or pseudonymized and is used only to keep the plugin compatible and to improve cheat detection. (A third channel, bStats, is bundled but inactive , it ships disabled and sends nothing unless a future build registers a bStats id.)
This policy is for the server administrators who install StarAC. Individual players do not interact with us; StarACruns inside the administrator's own server. Administrators are responsible for their own players' data and for their own privacy obligations.
a) bStats (anonymous usage statistics). StarAC bundles bStats, the standard open-source metrics service for Minecraft plugins. When enabled it reports anonymous, aggregate figures: server software/platform, Minecraft version, plugin version, Java version, OS, core/RAM bucket, online-player count, and which checks are active. No identifiers that point to a person. bStats can be disabled globally in /plugins/bStats/config.yml.
b) StarAC operational data (anonymous). StarAC sends an anonymous operational payload identified only by a randomly generated server UUID (not tied to any identity): Minecraft/plugin/Java/OS versions, hardware buckets, the server MOTD, aggregate violation counts, and live operational metrics (flags by check type, sanctions applied, server TPS, online-player count). It contains no player names, no IP addresses, no chat, and no per-player data , it identifies a server, never a person , so it carries no personal data.
c) Anti-cheat improvement data (pseudonymized , always on). To improve detection for everyone, StarACalso ships per-session training records: the anti-cheat's own state for that session (per-check violation levels and the action taken), the numeric movement/combat feature vectors, and a label (a clean session, or a session ended by a staff ban). These are numeric features, stripped of player names, IPs and any personal identifiers before leaving the server.
To link a player's own sessions for training without ever shipping their identity, the player's Minecraft UUID is pseudonymized: it is run through HMAC-SHA256 with a secret salt that is generated on, and never leaves, the administrator's own server. The result is a stable but non-reversible token , the same player maps to the same token on that server (so sessions can be grouped for training), but the token cannot be traced back to the UUID or the person without the secret salt, and the same player produces a different token on a different server. The raw UUID is never transmitted. This collection is part of StarAC's core anti-cheat function and is always active , it cannot be disabled, because the plugin depends on this pooled, non-identifying data to keep detection accurate and false positives low for every server that runs it.
We never collect: player usernames, raw UUIDs, IP addresses, chat content, locations, payment data, or any special-category personal data.
Where the GDPR or similar laws apply, our basis is our legitimate interest in maintaining compatibility and improving detection accuracy, and the necessity of this pooled, non-identifying data for providing the anti-cheat service itself (the plugin's core function depends on it). The improvement data is pseudonymized on the server before it ever leaves. The telemetry (3b) is anonymous. The anti-cheat improvement data (3c) is pseudonymized(HMAC of the UUID under a server-held salt, never the raw identifier); pseudonymized data is treated as a privacy-protecting measure under the GDPR, and because the linking salt never leaves the administrator's server, we cannot re-identify anyone from what we receive. The administrator, as the controller for their own players, enables this and informs their players where their local law requires it.
We use this data only to: keep StarAC compatible across Minecraft versions and platforms, understand adoption, fix bugs, and improve detection accuracy (fewer false positives, better cheat coverage). We do not sell data, and we do not use it for advertising.
We do not share data with any other third party.
Anonymous aggregate data is retained only as long as useful for the purposes above and may be stored in aggregated form indefinitely. As it contains no personal data, it cannot be linked back to an individual.
/plugins/bStats/config.yml. (bStats ships inactive in the current build, so there is nothing to disable yet; this applies if a future build enables it.)StarAC is a server tool for administrators, not directed at children, and collects no personal data from anyone.
Questions about this policy: contacto@minestar.me (MineStar Network).
We may update this policy; the effective date above reflects the latest version, and material changes will be noted in the changelog.
See also the StarACTerms & Conditions.