Privacy

Last updated 25 September 2026

This page explains what Eagler26 collects and why. The short version: while the client is in beta, each launch sends a technical diagnostics log to GoldHQ, labelled with your in-game name and a report number, so we can fix the bugs you run into. Passwords, chat and your network traffic are never collected.

Diagnostics (every launch)

When you launch Eagler26, the client creates a random session ID (like E26-7KQ2-M9XD-4TPA) and registers it with GoldHQ as soon as your in-game name is known. The server gives the session a report number (like #1042), shown on the in-game Diagnostics & Bug Reports screen and on this site's launch page. If you report a bug, send us that number.

The diagnostics log contains:

• Session: session ID, report number, start time, uptime, your in-game name.
• Build: Eagler26 version and build identifiers.
• Device and browser: browser name and version (user-agent string), operating system, language, screen and window size, pixel ratio, CPU thread count, approximate memory, graphics card model as reported by the browser, and which browser features are available.
• Game state: current menu, whether you're connected, the server address you joined (with any passwords or tokens in the address removed), dimension, approximate position (whole blocks), game mode, selected resource packs.
• Performance: frame rate, frame times, memory use and chunk-loading statistics, sampled every 5 seconds.
• Events: menu changes, connects and disconnects (including the kick or disconnect message shown to you), server switches, resource-pack download results, skin loading counts, sound start-up problems, graphics context loss, window focus changes.
• Errors: crashes, stalls and script errors with shortened technical stack traces.

Never collected

• Passwords, including anything typed after /login, /l, /register, /reg, /changepassword, /unregister and similar server login commands.
• Chat and private messages (/msg, /tell, /w, /r and others). The diagnostics code never reads chat.
• The content of your network traffic (only message types and sizes are counted), resource-pack files, skin or cape images, or any other file on your device.
• Other players' account IDs.

Everything is filtered on your device before it is sent, and filtered again when it arrives. The filters recognise known shapes of secrets (login commands, tokens, cookies, secrets in web addresses, e-mail addresses). A password typed somewhere unusual, such as pasted into the server address box, can't always be recognised, so please don't do that.

When it is sent

Once at launch, then about every 5 minutes, shortly after a crash, error or disconnect, when you switch away from the tab, and a final small upload when you close the page. At most 20 uploads per hour per page. If the upload fails, the game keeps working.

In-game, open Diagnostics & Bug Reports (click the version text on the title screen, or the bug icon in the pause menu) to see your report number and session ID, or to copy or save the full diagnostics yourself.

Who sees it and where it is stored

• Diagnostics are visible only to GoldHQ staff on an access-controlled page.
• They are stored with Supabase (our database provider; the project is hosted in the United States, us-west-2). The site is hosted on Vercel, which, like any web host, processes requests and may keep short-lived access logs including IP addresses. GoldHQ's diagnostics tables don't store IP addresses.
• To diagnose a bug, staff may give a session's filtered diagnostics to an AI coding assistant (see AI Disclosure).
• We don't sell diagnostics or use them for advertising.

How long it is kept

A session is deleted about 30 days after its last upload. Staff can delete a session sooner; to ask, send us its report number on Discord. Copies that staff exported while fixing a bug are handled as internal engineering material.

Stored in your browser

• The game keeps your settings, profile and skins in your browser's storage on your device. GoldHQ doesn't receive them.
• The client remembers your latest report number in this browser so the launch page can show it.
• No advertising or analytics cookies. Staff who sign in get login cookies from Supabase, plus a short-lived cookie that lets them launch while the client is locked.

Staff accounts

Staff sign in with an email link. Supabase Auth stores the staff member's email address and sign-in times. Players never need an account.

Questions and requests

Ask on the GoldHQ Discord. If you want a diagnostics session deleted, include its report number. We may update this page; the date above shows the latest version.