Privacy Policy

FanumStudios determines the purposes of account administration and platform security. A Minecraft server operator determines why gameplay is collected on their server and which moderation settings to enable. The operator must inform its players and establish an appropriate lawful basis.

Responsibilities for hosted gameplay processing depend on the actual service arrangement and applicable data-protection rules. Contact us if you need the processing terms or information about the party responsible for your records.

• Account name, password hash and authentication/security records.
• Minecraft name and optional linked Discord account information.
• Server identifiers, licence entitlement and account/staff access records.
• Connection and security information used to protect access and investigate abuse.
• Support correspondence and any purchase information you provide.

Account information is used to provide and manage the service. Security processing supports the legitimate interest in protecting accounts and infrastructure, subject to the applicable requirements and your rights. Legal obligations can require some records to be retained.

Depending on enabled features, the plugin and Cloud workspace can process player names/UUIDs, movement and combat observations, interaction timing, connection information, flags, available replay details and moderation history. Optional chat or voice moderation can process the content submitted to those tools.

Evidence may be accessible to authorised server staff and platform personnel with a relevant administrative purpose. Gameplay identifiers are personal data when they relate to an identifiable person. Hashing an identifier does not automatically make it anonymous.

Behaviour analysis uses observations to build statistical baselines. Shared combat learning pools numeric summaries of accepted crystal placement, crystal damage, the time between matching placement and damage, direct melee timing and supported Java aim alignment timing from participating servers. Reviewed snapshots can include derived timing spread and rhythm descriptors, such as changes between successive observations and regularity at the declared resolution. These are descriptive measurements, not a claim to read a player’s mouse cursor or measure human reaction time. Native Bedrock aim observations are currently unsupported.

Its bounded reference snapshots retain player UUIDs, source server and staff review provenance to prevent duplicate contributions and support revocation. Other server customers receive aggregate numeric statistics, without foreign player identities, server identifiers, review details or raw timing sequences. Participation is enabled by default when Cloud analysis and AI detection are enabled, and a server owner can disable that server’s contribution and scoring in the dashboard. References stop contributing after 90 days, and old review governance is removed by periodic expiry. Up to eight historical checkpoint versions are retained and can contain older numeric summaries and provenance until those versions are replaced. Recent live timing windows are not saved across restarts. Timing and rhythm summaries are processed on Fanum Cloud infrastructure and are not sent to a language model API.

Only legitimate review snapshots approved by a founder become shared scoring references. Rhythm regularity or fast play alone does not produce a shared alert. An anomaly percentile is not the probability of cheating and does not trigger an automatic punishment. A score is not conclusive proof of cheating, and server operators remain responsible for moderation and any applicable requirements concerning automated decisions.

If you use PvP Forensics, the recording and information visible or audible in it can be personal data. Submit only evidence you are authorised to process and minimise unrelated usernames, conversations or private material. Video AI is currently paused for validation. Where the local provider is selected, processing runs on FanumStudios infrastructure. Where Groq is selected, sampled recording frames are sent to Groq for analysis; the full video file, audio, account credentials and optional player identifiers are not sent. The upload screen identifies the selected processing method before submission.

Groq may process data in the United States and retain submitted frames and outputs for up to 30 days for reliability or abuse monitoring unless its zero data retention setting is enabled. FanumStudios has not verified that setting for the current account. See Groq’s data controls. Findings and derived frames remain evidence for staff review. Video findings do not trigger automatic punishments and submitted recordings are not used to train the model. Analysis may be limited by the recording’s quality and context.

Uploaded videos and derived frames have a default 7-day retention period. Reports and their review records have a default 30-day retention period. Contact us or the relevant server operator about a recording that concerns you.

The hosted service relies on infrastructure providers. Optional Discord linking and Discord interactions involve Discord under its own privacy terms. Minecraft avatar requests can transmit the requested username to the avatar provider.

Access to the service from another country does not, by itself, describe where stored information is hosted. Contact us for the applicable hosting locations, recipients and international-transfer information. Any restricted international transfer must satisfy the applicable data-protection requirements.

The current Cloud cleanup removes ordinary flags after 90 days and resolved staff-review records after 60 days. Flags associated with punishment timing can be retained longer. Expired session records are eligible for cleanup.

Punishment records, audit records and some other evidence currently have no automatic age-based expiry. Retention must still be justified by its purpose and any legal obligations. Contact us or your server operator about deletion or the retention of a particular record; do not assume that closing an account immediately erases all evidence and backups.

Passwords are stored as salted hashes. The public website uses HTTPS, and account and server permissions restrict access to evidence. Authentication and selected-workspace information are stored in your browser so you can use the signed-in service. Logging out clears the local session information.

Keep credentials and authentication codes private. No security measure can eliminate every risk; report a suspected account compromise to contact.fanumstudios@gmail.com.

Where the GDPR applies, you may have rights to access, correction, deletion, restriction, objection and, where applicable, portability. These rights have conditions and exceptions. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing.

Email contact.fanumstudios@gmail.com for account or platform records. For server gameplay evidence, identify the server and relevant player account so the responsible operator can be involved. We may need proportionate information to verify a request. Do not send your password.

You can complain to the Danish supervisory authority, Datatilsynet, or another competent data-protection authority.

Minecraft servers may have younger players. Operators must consider their players’ age, provide suitable information and comply with any applicable requirements for children. A player’s presence on a server is not blanket consent to unrelated data collection.

The update date identifies this notice. Material changes to how personal data is handled should be communicated appropriately. Ask FanumStudios at contact.fanumstudios@gmail.com about a data practice, request or concern.