Privacy policies

Overview

AE2 Web Integration collects limited telemetry to understand which Minecraft versions are used, whether the mod is used in singleplayer, and to estimate overall activity.

Telemetry is enabled by default when running a packaged mod outside a development environment, including custom builds. The game server periodically sends telemetry reports, including when running in singleplayer. Players connected to a multiplayer server do not send separate reports.

What is reported?

• Mod build verification: a randomized cryptographic proof derived from the mod's JAR file, used to recognize known official releases. The original file hash is not transmitted.
• Minecraft version: the version running the game server.
• Public mode: whether the mod's public mode is enabled.
• Singleplayer: whether the game is running in singleplayer.
• Session identifier: a temporary random identifier used to associate reports within a single session.
• Approximate country: the telemetry service derives a country code from the network information associated with the incoming request. Only the country code is stored in telemetry records, not the originating IP address. This information is used for aggregated geographic statistics. The country reflects the origin of the server's network connection and may represent a hosting provider's location rather than the players' actual location.

View the telemetry source code (opens in a new tab).

Reports do not include player counts, usernames, player UUIDs, network identifiers, stored resources, inventories, crafting history, world files or coordinates.

Sessions and retention

A new random session identifier is generated each time the server starts and renewed with the first report of each new UTC day. Session identifiers are not preserved across restarts or daily renewals, and we do not link separate session records together.

The service records when each session was first and last observed to estimate overall activity. The website displays only aggregated statistics and activity estimates. Individual session records are never publicly displayed.

Inactive session records are removed during scheduled cleanup after seven days without a report. No permanent history of individual server sessions is maintained; the published counts are recalculated on website visits, at most once per five-minute interval, from the records that remain.

How is the data used?

Telemetry helps us estimate overall activity and understand the distribution of Minecraft versions, recognized mod releases, public-mode settings, singleplayer usage and approximate geographic distribution. The website publishes only aggregated estimates of the number of active game servers, including singleplayer worlds, and how that number changes over time.

Telemetry is not used for advertising, tracking individual players or individual profiling.

Legal basis for processing

Where telemetry data constitutes personal data, we rely on our legitimate interest under Article 6(1)(f) of the GDPR to estimate overall activity and understand the distribution of Minecraft versions, recognized mod releases, public-mode settings, singleplayer usage and approximate geographic distribution.

Deriving an approximate country from connection information is part of this statistical analysis. The separate purpose of securing the endpoint is described under Network security.

We minimize the information collected through temporary session identifiers, limited data retention and the exclusion of player-specific information.

Disabling telemetry

The server or world owner can disable telemetry in the mod's configuration. In multiplayer, reporting is controlled by the server's setting. Changing a connected player's local configuration does not disable the server's reports. Telemetry is optional and is not required for the mod's core functionality.

Turn off telemetry in Server Settings, set enabled = false in the [telemetry] configuration section and reload the configuration, or run /ae2webintegration telemetry off. Use telemetry on to enable reporting or telemetry status to check the setting. The singleplayer owner can use these commands without cheats; on a dedicated server they require permission level 4.

Disabling telemetry stops further reports. Previously received session records are removed according to the retention period above.

Network security

To protect the telemetry service against abuse and DDoS attacks, IP addresses may be processed by Cloudflare and our own server-side rate limiter.

IP-based rate-limiting records are kept only in memory and expire within 60 minutes.

The hosting infrastructure maintains HTTP access and security logs, which may contain IP addresses and technical request metadata. These logs are used for security, abuse prevention and troubleshooting. They are separate from telemetry records and are not used for community statistics.

HTTP access and security logs stored on our own hosting infrastructure are retained for up to 91 days. Cloudflare may independently process connection information according to its own data retention practices.

IP addresses are used for rate limiting and to derive an approximate country code. Only the country code is stored in telemetry records for aggregated geographic statistics; the originating IP address is not stored in those records or used to track individual players.

Rate limiting and the use of access and security logs are based on our legitimate interest in maintaining the security and availability of the service, under Article 6(1)(f) of the GDPR.

For more information about Cloudflare's data handling, see Cloudflare's Privacy Policy (opens in a new tab).

Third-party services and data transfers

Telemetry requests pass through Cloudflare for network security and DDoS protection. Telemetry records are stored on self-hosted infrastructure in Poland.

Cloudflare may process connection information outside the European Economic Area. Its Data Processing Addendum (opens in a new tab) sets out the applicable transfer safeguards, including European Commission Standard Contractual Clauses where required.

Your rights

Where the GDPR applies, you may have the right to access, rectify or erase your personal data, restrict processing, object to processing and, where applicable, request data portability. To exercise your rights, contact ae2web@kuba6000.pl.

Telemetry sessions are not associated with player accounts or identities, so we may be unable to identify records relating to a particular individual. We do not collect additional personal information solely to identify telemetry users. If you provide information that enables us to identify the relevant records, we will take it into account when handling your request.

You also have the right to lodge a complaint with a data protection authority, including the Polish Personal Data Protection Office (UODO) (opens in a new tab).

Contact

AE2 Web Integration is maintained by kuba6000. For questions about telemetry or privacy, contact ae2web@kuba6000.pl.

Overview

This notice describes how information is processed when visiting the AE2 Web Integration website, independently of the mod's telemetry.

The website is informational and does not require user accounts or collect information through registration forms. We do not use visitor analytics or advertising trackers.

Interactive demo and browser storage

The website provides an interactive demonstration of the AE2 Web Integration web interface.

The demo uses browser local storage and session storage to support its functionality and maintain interface state and preferences. The website also uses local storage to remember your light or dark appearance preference. These storage mechanisms are separate from mod telemetry.

You can remove stored browser data through your browser settings. Removing it may reset the demo's saved state and preferences and the website's appearance preference.

Connection data

When visiting the website, our hosting infrastructure and Cloudflare may process technical connection information, including IP addresses, request timestamps, requested URLs and browser information.

This information is used to deliver the website, maintain its security, prevent abuse and troubleshoot technical issues. Processing is based on our legitimate interest under Article 6(1)(f) of the GDPR.

HTTP access and error logs stored on our own infrastructure are retained for up to 91 days. Cloudflare may independently process connection information according to its own privacy and retention practices.

For more information, see Cloudflare's Privacy Policy (opens in a new tab).

Mod telemetry

Simply visiting this website does not trigger the mod telemetry described above. Telemetry reports are sent by Minecraft servers running AE2 Web Integration, not by website visitors.

Contact and your rights

The contact information and applicable data protection rights described in the policy above also apply to website-related data processing.

For privacy inquiries, contact ae2web@kuba6000.pl.