Privacy

Advertising, profiling and analytics

This site carries no advertising networks, no social media pixels, no fingerprinting and no cross-site tracking. We do not build profiles of visitors, and we never sell, rent or share personal data with anyone.

We do measure how the site is used, with a single privacy-preserving tool: Umami, which we run ourselves on the same self-hosted server as the site, so these figures are never sent to an analytics company. It sets no cookies and assigns you no persistent identifier; visits are grouped by a hash derived from your IP address and your browser, which cannot be turned back into a name or an account, and which is not shared with any other website. What we see is aggregate only — page views, referring sites, countries and browsers — never one person's browsing history. Alongside those page views we count a small number of named actions, so that we can tell which pages are worth expanding and which links people actually use: a search that returned no results, together with the search text you typed, so that we can find the cards and filters our data is missing; a page that could not be found; which rules section or keyword was opened; and whether you reached a card from a search engine or from a link elsewhere on this site. We also count the start and the completion of a sign-in, which provider you chose, and — when a sign-in invitation was shown to you — from which feature it appeared. These actions carry no account identifier and no deck, collection or wishlist content, and they are counted the same way as page views — as totals, not as one person's trail.

We also never ask for your email address, never send marketing messages, and never require a sign-up, survey or mailing-list opt-in as a condition of viewing cards or rules.

Browsing without an account

If you browse without signing in, no account is created and we assign you no identifier. The only trace your visit leaves is a per-deck view counter, incremented when you open a public deck: it records that a view happened, never who made it or when.

What we store when you sign in

Signing in with Discord or Google stores only what is needed to recognise you on your next visit: which provider you used, the account identifier that provider gave us, a display name and an avatar image URL, plus the date your account was created. We never receive or store your password. We do not request your email address from Discord. Google includes an email address in its sign-in response, which we use only as a fallback display name when your Google account has no name set.

We also store the content you create: your decks and their cards, maybeboards, tags, primers and video links, your collection and wishlist quantities, the decks you have favourited, your display-name and collection-warning preferences. We process all of this to provide the deck-saving features you asked for, on the basis of the consent you give by choosing to sign in. If you create an API token or authorize an app to access your account, we additionally store the token's name, its permissions, a hashed form of the secret (never the secret itself) and when it was last used; you can revoke either at any time in your settings.

Cookies and browser storage

We use a small number of cookies and browser-storage entries, none of them for tracking or advertising. A session cookie holds your encrypted sign-in state and is only set once you sign in. When you start a sign-in, a second short-lived cookie remembers the address of the page you were on, so that we can return you to it afterwards; it holds nothing else and expires after ten minutes. Three preference cookies remember whether you prefer card results and deck lists as a grid or as text, and whether the card search opens in simple or advanced mode; they last a year and are written only when you change those settings. Your light or dark theme choice is stored in your browser so it survives a reload, and the same local storage keeps a few more entries if you use those features: the completion goal you pick per set in your collection, the draft deck you can build before signing in, and a small counter of viewed card pages that decides when to show a one-time note about supporting the site — dismissing that note is remembered the same way. These stay on your device and are never sent to us — with one exception you choose yourself: when you save a draft deck by signing in, that draft becomes a deck in your account. We deliberately set no language cookie — your language lives in the page address instead. If you install the app, your browser may also cache card images on your device so they load faster; that cache is local and we cannot read it.

Third parties

When you choose to sign in, your browser communicates directly with Discord or Google, and their own privacy policies govern that exchange. The site runs on self-hosted hardware, but Cloudflare sits in front of it as a proxy and cache: your connection reaches Cloudflare first, so it sees your IP address and which pages you request, under its own privacy terms. Our anonymous usage figures are counted by analytics software we run on that same hardware, reached through the same Cloudflare proxy, so no analytics company receives them. We keep backups of the database so that it can be restored after a hardware failure, and those backups are stored on Google Cloud Storage. Google therefore holds a copy of the same data, including your decks, collection and wishlist, encrypted at rest and governed by its own privacy terms; each backup is deleted automatically 30 days after it is made. Apart from the services named on this page, no other third party is involved.

Card images and set logos are copied onto our own servers. We fetch each one from Ravensburger's public Disney Lorcana TCG image servers a single time, then keep that copy and serve it to you ourselves — so displaying a card no longer makes your browser contact Ravensburger, and Ravensburger no longer receives your IP address when you browse. The images are served unaltered, exactly as Ravensburger published them.

Public decks

Decks are private by default. If you switch a deck to public, its name, format, card list, tags, primer and video link become visible to anyone with the link, together with the display name on your account. Switching it back to private removes it from public view.

Public decks keep a counter of how many times they have been opened. It is an aggregate number only: we do not record who viewed a deck, or when.

Deleting your data

You can delete your account at any time from the settings page. Deletion is immediate and permanent: your account record, decks, maybeboards, tags, primers, collection, wishlist, favourites and preferences are all removed from the database and your session is cleared. Routine database backups may still contain your data for up to 30 days after deletion: each backup is erased automatically once it reaches that age, and we never alter the contents of a backup.

Changes to this policy

If this policy changes, we will update the date shown at the top of this page.