Privacy & Cookies

The short version

EggLedger reads your mission history from the Egg, Inc. API. There is no advertising and no third-party tracking. The hosted web app counts visits anonymously, as described below. What is stored, and where, depends on which build you use. The desktop app keeps your mission data on your own machine. The hosted web app decodes it on the server and keeps it under your account until it is deleted. Payment data is never handled here.

You are using the hosted web app, so the Web app section below applies to you.

Signing in

Sign-in is handled by EggIdentity, a separate federated authentication service run by the same operator. You pick a sign-in source: Discord, Google, Microsoft, or GitHub. Your password is never seen or stored by EggLedger.

EggLedger receives only the basic identity needed to recognise you again, such as an account identifier, a display name, and an avatar. It does not read your email, messages, or server list. EggIdentity has its own terms and privacy policy covering the login itself.

Desktop app

The desktop build stores all config, mission data, and exports in the same directory as the EggLedger binary, in a local SQLite database and on-disk files. Nothing is uploaded anywhere. The only outbound network calls are to the Egg, Inc. API itself and an occasional update check against github.com, which carries no personal data. Unless you contact the operator directly or turn on Settings Sync, there is no way to know you are even using this tool.

Web app

The hosted instance runs as a Blazor Server app. Your browser holds a live connection to the server while you use it, and your Egg, Inc. backup is decoded server-side. The result is stored in a Postgres database, tied to your account. What is stored is:

• Mission history. The spaceship missions your fetches return.
• Drops. The loot recorded against each mission.
• Backups. The decoded account snapshot each fetch is built from.
• Settings. The interface and export preferences you have chosen.
• Reports. The report definitions and groups you have built.

That data is yours. It is not sold, shared, or used for advertising, and it is not profiled. It is kept until it is deleted, as described below. If you would rather nothing was stored server-side, use the desktop app instead.

Separately from your account, the server logs API requests that it rejects, recording the IP address, path, and user agent, so that abuse can be blocked. Those rows carry no account identifier and are not joined to your data.

The hosted web app also counts page visits. Counting is anonymous and cookieless: a per-day hash of your address and browser is kept in memory only and discarded at midnight, and only daily totals per page are stored. No visitor can be identified or followed across days. Browsers sending Do Not Track or Global Privacy Control are not counted, and declining analytics in the cookie banner stops counting too.

Settings Sync (optional)

Settings Sync lets you carry your settings between devices. On desktop it is off unless you turn it on, and turning it on requires signing in. If you never use it, nothing about you leaves your machine beyond the Egg, Inc. API calls and the update check described above.

Synced settings are encrypted before upload and stored encrypted at rest. The key is generated per account by the sync service and handed to your devices when you sign in, so this is not a zero-knowledge design: the operator's infrastructure holds the key and can technically read what you sync. The web app uses that same key to restore your settings on your first sign-in. No settings data passes through the sign-in source you picked.

Cookies

The web app uses strictly-necessary cookies, plus one consent cookie that records your choice. A small banner asks once; the choice applies across every EggIdentity-backed site and is remembered on your account when you are signed in. The cookies used are:

• Session cookie. Keeps your Blazor Server circuit and your sign-in connected across page loads. Removed when you log out or close the session.
• Antiforgery token cookie. A security cookie that protects form submissions against cross-site request forgery. It does not identify you.
• Consent cookie. Records whether you allowed optional functional and analytics cookies. Set on the shared parent domain so you decide once for every site. Kept for one year.

The web app does not keep your preferences in the browser. They are saved server-side in your account's settings, along with the rest of your stored data. The desktop app uses no cookies; its settings live in the on-disk config described above.

Payments

Donations are processed entirely by third-party platforms (GitHub Sponsors, Patreon, and Buy Me a Coffee). This application never sees, processes, or stores your payment card data. Anything to do with billing is held by those platforms under their own privacy policies.

Data retention

Desktop data is retained for as long as you keep it on disk. Deleting the app's directory removes it completely, with no system-level traces left behind. Web app data is retained until it is deleted, either by you through the options below or by the operator on request; there is no scheduled purge, and no history of your activity is built for profiling purposes. Synced settings are kept only while your account exists. The rejected-request log described above is kept for abuse protection and is not tied to any account.

Removing your data

To remove the data stored about you:

• Desktop. Delete the EggLedger install directory to remove all local data. Use Delete Remote Data in the cloud sync settings to remove the synced settings held for you on the server.
• Web. Use Disconnect in the cloud sync settings to delete your synced settings and sign out. This does not remove the mission data stored under your account.
• Your whole account. There is no self-service button for this yet. Ask the operator and the account is deleted along with everything stored under it: mission history, drops, backups, settings, and reports.
• Revoke EggLedger's access from your sign-in source, such as your Discord, Google, Microsoft, or GitHub account settings.
• Clear your browser's cookies for the web app to remove the session and antiforgery items.
• Reach the operator through the GitHub repository or the project Discord server.

Changes

This policy may change as the project evolves. The date at the top reflects the latest version. For the terms that govern use of the service, see the Terms of Service page.