Ledger 08 · Privacy

Privacy Policy

Last reviewed: 2026-09-19

Short version: this site does not collect personal data directly. There are no accounts, no forms that store personal identities, and no intrusive trackers.

What we collect

Nothing deliberately. There is no signup, no comment box, no newsletter and no contact form. The pages are static files served as they were built, so there is no server-side profile to assemble. The only text anyone can send us is the correction email at contact@tcgcardshopdb.wiki, and that is a mailbox, not a database.

What your browser stores locally

Two pages keep state on your own device and nowhere else:

The achievement checklist remembers which boxes you ticked, under a single localStorage key. It never leaves the device, is not readable by any other site on this domain, and is gone the moment you clear site data.
The tool pages (pack odds, worker payback, stock order, card binder) read your inputs from the address bar, so a set of numbers can be pasted to someone else. Those parameters live in the URL and in the page you chose to open, not in storage.

Third-party requests & analytics

Pages load typography from Google Fonts (fonts.googleapis.com). To understand overall reader interest and improve database coverage, aggregate traffic analytics (Google Analytics 4) is configured. No personal identities, advertising profiles, or intrusive tracking cookies are harvested. The site is hosted on Cloudflare Pages.

Advertising and monetisation

This is an independent community fan database. We do not run invasive popups, redirect ads, or unlabelled sponsored placements. Any future display sponsorships adhere strictly to non-intrusive standard banners.

Children, data sales and retention

There is no personal data to sell, share, retain or breach, because none is collected. No product or feature here targets children, and none asks a visitor to identify themselves.

Corrections to this policy

If you find a discrepancy between what this page claims and what the site actually does, that is a bug worth reporting to the address above. We would rather be told than be wrong about our own code.