Privacy Policy

1. What this policy covers

This site is a small history-battle card game built and run by one developer. It is not an official product of Wikipedia, the Wikimedia Foundation or any affiliate.

The developer decides what is collected and why, and is the contact point for everything in this policy. The policy covers this site only: once you follow a link to Wikipedia or post a poster on another platform, that platform's own rules apply.

2. What the site stores

A small part of your data is kept on the server so your record survives a device change. The rest stays in your own browser.

• Anonymous identifier (cookie): a cookie named battle-player holding a random 64-character hex string generated by the server. It is HttpOnly, SameSite=Lax, marked Secure over HTTPS, and expires after one year. It carries no name, email or phone number and is tied to no account.
• Server-side record: battles drawn, figures revealed, win or loss, difficulty, win rate and score, archive entries, unopened packs, pity counters, and the start and settle time of each round.
• Browser storage: battle-sound keeps your sound preference; battle-draw:v2 keeps a progress copy for fast loading and for the upgrade path from the previous version. Neither is uploaded by default.
• Legacy import: if an older local save still exists in your browser, it is imported into the server record once on first load and not imported again.
• Abuse counters: each draw increments a counter per anonymous identity and per egress address. In the cloud setup they live in a temporary table and normally expire with the window within two minutes. They are used only to decide whether a rate limit was exceeded, never to identify you.

3. What the site does not collect

• No accounts: no sign-up, no login, no email, phone number, real name, address, identity document or payment detail.
• No ads or tracking: no ad slots, no third-party analytics, pixels, heatmaps or A/B tools, no cross-site tracking and no third-party cookies.
• No device permissions: no location, contacts, photo library, microphone or clipboard access. Share posters are drawn on a local canvas and the images are never uploaded.
• No language guessing: the page language comes from the URL, not from your browser preference, and sets no cookie.

4. What the data is used for

Three purposes only: showing you your own record and archive, deciding whether you are hammering the draw endpoint, and diagnosing a failure.

• Draw results come from fixed server-side rules and the pity counter. There is no profiling, scoring or automated decision about you as a person.
• Data is never sold, rented or traded, is not used for advertising, and is not used to train models.
• Records are not exported in bulk to third parties for product improvement.

5. The ranking and what is public

The ranking compares you with fictional opponents built into the site. Those names and records are hard-coded sample entries, not real players, and they are not drawn from other visitors.

• There is no cross-user leaderboard. Other visitors cannot see your score, battle count, win rate or archive.
• Your record can only be read through the anonymous cookie in your own browser. The server exposes no way to look a record up by user.
• The one exception is sharing you start yourself: a share link carries only a battle identifier and a figure identifier, the poster is drawn in your browser, and once you post it elsewhere the audience is decided by that platform.

6. Where it lives and how long it stays

In the cloud setup the record lives in a Cloudflare D1 database while the app runs on Cloudflare Workers; in a self-hosted setup it is a SQLite file on the operator's own server. Access is controlled by the operator in both cases.

• Records stay until you clear them or the service stops. Clearing is a hard delete: it cannot be undone and cannot be recovered by support.
• Rate-limit counters roll off with the window and are normally gone within two minutes.
• Model verdicts are cached by battle, model and prompt version. That cache is tied to no player and holds no personal data.

7. Interactions with third parties

The server calls Wikimedia endpoints and your browser loads Wikimedia images. Neither carries your anonymous identifier.

• On a draw the server asks Wikipedia and Wikidata for article summaries, portraits and basic metadata. Your cookie and anonymous identifier are not part of that request.
• Which side a figure fought on is decided by server-side rules, a hand-maintained result table, or an optional model pass that sends only battle and figure names. The model may be self-hosted or a third-party OpenAI-compatible endpoint; the latter sees those names but none of your identifiers.
• Illustrations load straight from Wikimedia domains such as upload.wikimedia.org, so Wikimedia sees your address and browser string. That part is governed by the Wikimedia Foundation privacy practices.
• The hosting provider (for example Cloudflare) handles requests and storage as an infrastructure provider and does not use this data for its own marketing.

8. How the data is protected

• Everything travels over HTTPS, and the anonymous cookie is HttpOnly with SameSite=Lax, so page scripts cannot read it.
• Every write checks the request origin; cross-site forged requests are rejected.
• Draws are rate limited per anonymous identity and per egress address, which stops scripted farming.
• The database holds an anonymous identifier and game progress only, with no email, phone number or other field pointing back to you.
• No system is perfectly secure. If an incident could affect you, we will post a notice on the site describing the scope and what was done.

9. Your options and rights

You can do any of the following at any time without asking us first.

• Clear now: the Clear my record button on the ranking page deletes the server-side record, archive, packs and rounds and resets the counters. It cannot be undone.
• Unlink: deleting this site's cookie gives you a new anonymous identifier. The old record stops being linked to this browser and cannot be recovered.
• Refuse cookies: your browser can block them, at the cost of the record, archive and draws not working.
• Export or exercise a statutory right: write to Contact. Where your local law (for example in the EEA or the UK) gives you rights of access, correction, erasure, restriction, objection, portability or complaint to a regulator, we reply within 30 days; an erasure request is equivalent to Clear my record.

10. International transfers

In the cloud setup requests and data pass through Cloudflare's global network and may be processed or stored outside your country or region. In a self-hosted setup the location is chosen by the operator. Only necessary fields are transmitted, and we rely on the provider's encryption in transit and access controls.

11. Children

This site is not directed at children under 13 and does not knowingly collect their data. If you are a guardian and believe a child used the site without consent, write to Contact and we will delete the record.

12. Changes and earlier versions

Revisions update the date at the top of this page, and material changes to what is collected or why are announced on the home screen. Continued use means you accept the updated policy. Earlier versions are available on request through Contact.