Privacy & Telemetry Policy

Who is responsible?

GTNH Extra Nerf is maintained by kuba6000, the controller responsible for the processing described here. For privacy questions or to exercise your rights, contact extranerf@kuba6000.pl.

Mod telemetry

In versions with the reporting choice, telemetry is opt-in: an undecided world sends no statistics or team reports until the world or server owner chooses a reporting mode. An existing team opt-in or telemetry refusal is carried over during migration. Older versions may enable basic statistics by default. Reports are sent periodically by the game server, including when running in singleplayer. Players connected to a multiplayer server do not send separate reports.

Telemetry is optional and is not required to play or use the mod. The server or world owner controls reporting. We use it to estimate community activity and world progression, understand release usage, and produce internal approximate geographic statistics.

What the mod sends

• Session identifier: a temporary random identifier used to associate reports within a single server session.
• Player count: the number of players currently connected to that game server.
• Progression tier: one highest currently available world progression tier, calculated locally. Individual certificate records and exam answers are not sent.
• Server mode: whether the game runs on an integrated singleplayer server, including worlds opened to LAN, or a dedicated server.
• Build information: an optional randomized value derived from the mod file, used to recognize published builds. The mod file and its unmodified fingerprint are not sent.

Basic statistics reports do not contain player names, player UUIDs, chat messages, inventories, stored resources, world names, world files, coordinates or individual gameplay records. Team reports contain player identities as described below.

Team tracking (optional)

Team tracking is an alternative to basic statistics, selected by the world or server owner. Versions with the reporting choice send one mode at a time. A team report includes a permanent team ID, the Minecraft UUID and name of the leader, the progression tier, server mode, up to 256 online players' UUIDs and names, and an optional build proof. Some releases also send a temporary server-run ID and a separate player count in team reports; the service now ignores those two fields, while records saved before this change follow the session retention rules below. Team reports can also supply community statistics. In versions with the updated notices, players online when tracking is enabled and players who join while it is on receive chat notices linking to the policy and explaining their right to object. Older versions may not notify players already online when tracking is enabled and may not mention the right to object.

This website may publicly show the team name, its tier and players' names for recognized official builds. Other teams are stored but are not publicly listed; their valid reports can also contribute to aggregate statistics. Some older team reports rely on a separate basic telemetry report to appear in those statistics. UUIDs and the team ID are not published. The purposes, legal basis, retention, how to turn it off and how to have data removed are described in the Team Tracking Policy. To confirm an eligible team leader's name, our server also sends the leader's Minecraft UUID to Mojang's public profile service, which is operated by Microsoft.

Information added by the service

The service records when each session was first and last observed to estimate overall activity. It uses the build information to recognize published mod releases and stores the recognized version and a build classification, but does not retain the submitted build proof.

Approximate country: the service derives a country code from the network information associated with the incoming request. The country code is stored with session and team records, not the originating IP address. The mod does not obtain or send the country.

The country describes the game server's network connection. It can be the location of a hosting provider, proxy or VPN rather than the players' location. No city, coordinates or originating IP address is stored in telemetry records.

Country information is for internal analysis only. Neither individual countries nor country breakdowns are included in the public statistics API or shown on the website.

Sessions and retention

For basic statistics, a new random session identifier is generated each time the server starts. A statistics session record does not store the team ID or player identities. We do not link separate session records together.

For each session, we retain its latest reported values, country, recognized mod version and build classification, and when it was first and last observed. We do not retain a per-session history of reports or earlier values.

Only recent server sessions that pass our validation checks contribute to public activity estimates. These statistics are approximate and do not represent a guaranteed count of unique servers or players.

Inactive session records are removed during scheduled cleanup after seven days without an accepted report. Active sessions can remain longer. No permanent history of individual server sessions is maintained.

We also retain historical activity data for internal trend analysis, including aggregate statistics and limited server-level observations such as player counts, progression tiers, approximate countries, server modes and build classifications. These records do not contain session identifiers, are not publicly displayed and are deleted after one year.

Only current aggregate active-server counts, reported online-player totals and progression-tier distributions are public. Individual session records, server mode, build classification and mod-version data are not publicly exposed. The website does not publish country statistics.

Purposes and legal basis

Where the information constitutes personal data, the stated basis for processing limited telemetry is our legitimate interest under Article 6(1)(f) GDPR: understanding use of the mod, maintaining community activity and progression statistics, and internally understanding approximate geographic distribution. Security processing has the separate purpose described below.

We reduce the information collected through temporary session identifiers, limited retention, exclusion of individual gameplay records, and aggregate public results. These measures do not mean that all connection information is anonymous.

Telemetry is not used for advertising, tracking individual players, or individual profiling. We do not make automated decisions about people that produce legal or similarly significant effects. Providing telemetry is not a statutory or contractual requirement; turning it off does not restrict gameplay.

Disabling telemetry

The world or server owner controls the selected mode. On a multiplayer server, changing a connected player's local configuration does not disable the server's reports.

Administrative command

On a dedicated server, use administrator permissions (operator level 4). In singleplayer, the world owner can use the command without cheats; guests of a world opened to LAN still need operator permissions:

/extranerftelemetry off

In the server console, omit the leading slash. Use /extranerfteam off to stop team reporting. In versions with the reporting choice, the world keeps that choice across restarts; /extranerftelemetry on selects basic statistics and turns team tracking off, while /extranerfteam on selects team reporting and turns basic statistics off. The legacy configuration setting is only used when first migrating a world.

Disabling stops future reports, although a request already in progress may finish. Previously received data follows the retention rules above. Your applicable rights, including the right to object, are described below.

Update checks

Release builds of the mod check for a newer version when the game server starts and every twelve hours afterwards by downloading a small public file from this website. The request contains no telemetry data or game information, only the connection details any web request exposes, which are handled as described below. It is separate from telemetry and continues when telemetry is disabled.

Connection information and network security

Our hosting infrastructure and Cloudflare process connection information, including IP addresses and technical request metadata, to deliver and protect the service against abuse and DDoS attacks. This security-related processing is based on our legitimate interest under Article 6(1)(f) GDPR.

IP addresses are used for abuse prevention and to derive an approximate country, but are not stored in telemetry records. Limited security-related information is temporarily processed for abuse prevention and normally removed within two hours. These records are separate from telemetry data and are not used for community statistics.

Our own infrastructure's HTTP access and security/error logs may contain IP addresses, request times, URLs and client information, and are retained for up to 91 days. These logs support security and troubleshooting, not community statistics. Cloudflare has its own retention practices. The application does not intentionally log telemetry request bodies.

Recipients, storage and international transfers

Telemetry records are stored on self-hosted infrastructure in Poland and are accessible to the project maintainer and those administering the service as needed for its operation. Requests pass through Cloudflare, which processes connection information to deliver and protect the service.

Cloudflare may process connection information outside the European Economic Area. Its Data Processing Addendum describes applicable transfer mechanisms and safeguards, including adequacy arrangements or European Commission Standard Contractual Clauses where applicable. Information about those safeguards is available through that document or by contacting us.

See also Cloudflare's Privacy Policy. External services linked from this website, such as GitHub or Discord, apply their own policies when you visit them.

Your rights

Where the GDPR applies, you may request access to your personal data, rectification, erasure or restriction of processing, subject to the conditions in the GDPR.

You have the right to object, on grounds relating to your particular situation, to processing based on legitimate interests. We must stop that processing unless an applicable exception permits it, such as compelling legitimate grounds overriding your interests, rights and freedoms, or the establishment, exercise or defence of legal claims. The server or world owner can also switch off future telemetry at any time as described above.

Data portability applies where its legal conditions are met, in particular to eligible automated processing based on consent or contract; it does not automatically apply to processing based on legitimate interests. If any separate processing is based on your consent, you may withdraw that consent without affecting the lawfulness of processing before withdrawal.

Contact extranerf@kuba6000.pl. We respond without undue delay and normally within one month. If an extension is permitted because of complexity or the number of requests, we will explain it within that first month.

Statistics session records do not store player accounts or team IDs, so we may be unable to identify a session record relating to you. Team records are handled as described in the team policy. We do not collect additional information solely to identify telemetry users. If you provide information enabling us to identify the relevant records, we will take it into account; we may request proportionate information when necessary to verify a request.

You may complain to a competent data protection authority, including the Polish Personal Data Protection Office (UODO), or the authority in the place of your habitual residence, work or the alleged infringement.

Website privacy

The website provides information, downloads and aggregate mod statistics. It does not require visitor accounts or registration forms, and visiting it does not trigger game-server telemetry.

The website's own code does not use visitor analytics, advertising trackers, cookies or browser storage. Depending on the enabled protection features, Cloudflare may use necessary security cookies or challenges; these are separate from mod telemetry.

Website requests, including download requests, expose connection details such as IP addresses, timestamps, requested URLs and browser information to the hosting infrastructure and Cloudflare. They are used to deliver the site, secure it and troubleshoot problems under Article 6(1)(f) GDPR. The infrastructure, transfer arrangements and up-to-91-day local log retention described above also apply to website visitors.

If you contact us, we process the contact details and information you provide to respond and handle your request. Correspondence is retained only as necessary to deal with the matter, document compliance with applicable obligations or handle legal claims. The relevant basis is our legitimate interest in responding and, where applicable, compliance with legal obligations under Article 6(1)(c) GDPR.

The contact details and applicable data protection rights above also apply to website-related processing.

Changes to this notice

We update this notice when processing practices change and show the latest revision date at the top. A change of wording does not itself constitute consent to a new processing purpose.