Privacy

The short version

Undercut stores what it needs to run your account and nothing else. There are no analytics scripts, no ad trackers, and no third-party cookies on this site. The four cookies it sets are the ones that make it work. You can export everything I hold about you as JSON, or delete the account and all of it, from your account page.

What gets stored

Account. An email address and a password hash (argon2id; I could not read your password if I wanted to), or your Discord user id and display name if you sign in through Discord. Discord sign-in uses the "identify" scope only: no email, no guilds, no friends.

Things you create. Watchlist items, saved presets, price alerts, and hand-logged portfolio trades. They exist so the site can show them back to you.

Character profile. If you're signed in, you can save your in-game premium status and your crafting, refining, farming and gathering specialization levels to your character sheet, so the craft, refine and farm calculators open already set to your numbers. It's data you type in yourself, and it goes when your account does.

Companion. A connected app has a label, a hashed and revocable token, and timestamps for creation, last use, revocation, and Bank snapshot rate limits. Market observations join the shared price feed. Bank Overview syncing is not enabled in this release. Raw game packets stay on your computer; the Companion never uploads them.

Billing. When paid subscriptions go live they run on Stripe. Undercut stores the Stripe customer reference, never card numbers. During the beta nothing is charged and no billing data exists.

Server logs. The web server keeps short-lived request logs (route, timestamp, status, plus the IP and, on an error, the email involved) for debugging and abuse handling. They are not fed into any analytics product. Requests are also counted, hourly and daily, per page, to see how the site is used; each visitor is folded into that count using a same-day hash of IP and browser that changes every 24 hours and is never stored on its own — only the totals are kept. When you arrive from another site, the domain of that site (for example a search engine, or a link someone shared) is recorded as a daily total, so we can see where visitors come from. The full address is never read, only the domain, and clicks between our own pages are left out. Automated crawlers — search-engine bots such as Googlebot, not people — are counted the same way: a daily total of how many times each crawler fetched each page, so we can tell whether search engines are indexing the site. That is a count of the bot software, never a visitor. How long a visit lasts and which pages it moves between are measured only in aggregate, from that same rotating same-day hash. No individual visit or path is ever stored, and none of this uses a cookie. Downloads of the desktop Companion are counted the same cookieless way: a total count plus a unique count from that same rotating same-day hash, never stored on its own.

Why we're allowed to. Account data is processed to provide the service you asked for (contract); server logs and visit counts rest on our legitimate interest in keeping the site up, unabused, and understood. No processing relies on consent, because there are no trackers to consent to.

Cookies

Four, all strictly necessary, which is why there is no cookie banner:

The session cookie is signed and keeps you logged in. It is set on login and cleared on logout.
The region cookie remembers which game server you were looking at.
A short-lived message cookie carries a one-time confirmation or error (like “password changed”) across the next page load, then clears itself.
A short-lived sign-in cookie is set only when you start a Discord sign-in — it ties that attempt to your browser for up to ten minutes and is deleted the moment sign-in finishes. It is never set just from browsing.

What leaves the site

Item images load from Albion Online's official render service, so your browser sends that server the same basic request data it sends any image host. Market data flows the other way: the site reads public data from the Albion Online Data Project; nothing about you is sent there.

The Companion sends decoded market observations to Undercut's shared feed. Npcap is a separate prerequisite from its official site. Undercut does not download or redistribute it.

Your data is not sold, shared, or handed to advertisers. It sits in a PostgreSQL database I run, with encrypted backups retained for up to 14 days.

Your rights

GDPR gives you access, correction, portability, and erasure. On this site those are buttons you press yourself. Export your data as JSON any time; delete your account and every row that belongs to it goes with it, immediately from the live database; encrypted backups age out within 14 days. Device rows are removed and quarantine evidence is de-linked; shared market observations remain non-account data. If you think I am mishandling your data you can complain to the Dutch DPA, the Autoriteit Persoonsgegevens. But write me first, I fix things faster than they do.