Privacy notice

Information the game uses

We store a pseudonymous player identifier, display name, card inventory, earned coins, pack history, favorites, quiz progress, battle results and social actions to provide the game. Friend requests, card offers, auction bids, guild membership and messages are stored on the server.

If you sign in, we store your email address, sign-in times and session records, plus your Google account ID when you continue with Google (Google sends us a signed token with your account ID, email and name; we never receive your Google password). Emailed sign-in codes are kept only as keyed hashes and expire after 10 minutes. For purchases we store the offer, price, currency, status, payment channel and the payment provider’s order reference.

Your display name, collector code and collection and win counts can appear to other players. Trade counterparties see their offers, guild members see guild chat, and direct messages are returned only to their participants by the game API. Messages are not end-to-end encrypted. Avoid putting sensitive personal information in names or messages.

Invite links contain your 12-character collector code. When someone joins through your link, we record that link between the two accounts so invite rewards can be granted, and you see how many invited collectors joined and qualified, not who they are. Share buttons open the chosen service or your device’s share sheet; we count that you tapped share and which channel, not whether or what you posted. That service’s own privacy terms apply to anything you publish there.

Source feedback and corrections

If you submit a report, we store your player identifier, the selected card and its Wikipedia revision, issue type, explanation, optional supporting URL, submission time and review status. Reports are private to you and the Wiki Battle operators. They are retained until the report and any related follow-up are resolved or you request deletion; there is no automatic report expiry in this edition. We do not submit your report to Wikipedia or automatically fetch links you supply. Avoid including private information. Contact support for access or deletion requests.

Cookies and preferences

The essential HttpOnly cookie wb_session identifies a guest and can remain for up to one year. If you sign in, the essential HttpOnly cookie wb_account keeps you signed in for up to one year; signing out deletes it. The Google button loads Google Identity Services from accounts.google.com, which may use Google’s own cookies when you choose it. Browser storage also keeps preferences such as sound and AI invitation settings. Blocking or clearing essential storage can prevent progress from being retained. Hosting and sign-in providers may use their own security and authentication cookies. We use Umami, hosted at umami.teamaiservices.com, to measure page visits, referral sources and technical information such as screen size and browser language. The analytics service receives the network requests needed for these measurements. We do not send private messages, card inventories or payment details as analytics event data. We also use sampled heatmaps to understand click positions and scroll depth, together with page URLs and viewport dimensions. Session replay is currently disabled, so this setup does not record page text, messages or form contents. We do not add advertising trackers.

Optional nearby players

Nearby discovery is off until you choose it and permit browser geolocation. The client rounds the coordinates to one decimal place before submitting them; the server also rounds them. This is approximate area data, not an exact address. Only people who also enable nearby discovery can find each other, within about 100 km. Other players receive broad distance bands rather than coordinates.

The area setting expires after 24 hours and is removed during server housekeeping on the next request. You can turn it off earlier in the battle lobby. We use it only to offer nearby challenges. A browser’s permission and our nearby setting are separate controls.

Hosting and external sources

The service runs on OpenAI Sites and Cloudflare, including Cloudflare database storage and a realtime connection service. These providers process requests and technical information such as IP addresses and device or connection details to deliver and secure the service. Sign-in codes are emailed through Cloudflare Email Service. Data may be processed outside your country. Realtime messages carry channel membership, connection presence and revision notifications; unrevealed card choices are not broadcast.

Links to Wikipedia and Wikimedia sources open third-party services with their own policies. If your browser requests an externally hosted image, that host receives the network request.

Payments run through our payment gateway (pay.teamaiservices.com) and Waffo Pancake or Creem. Checkout is provided by Waffo Pancake or Creem, each the merchant of record for purchases made through it, and payment card data is processed by a PCI-DSS certified payment processor and never stored on our servers. The provider you pay through receives the name, email, billing country or address and payment details you enter at its checkout; we receive the order reference, amount, currency, payment status and the checkout email.

Retention and your choices

Progress, account and social records are retained to keep your game available; purchase records are kept as long as needed for accounting, tax and dispute handling; there is currently no automatic whole-account expiry. Some histories have rolling limits, such as the latest 20 fusions and 100 guild messages. Closing the browser or clearing a cookie does not delete server records.

For access, correction or deletion requests, contact support@wiki-battle.com and provide your collector code, or write from your account’s email address. We may ask for proportionate verification to protect another player’s records. Do not send passwords, session cookies or identity documents in an initial email. Applicable privacy rights depend on your location. You can withdraw nearby discovery at any time without losing access to the rest of the game.

Questions and updates

For privacy concerns or reports involving a child’s data, contact support@wiki-battle.com. Material changes to how the game handles data will be reflected here. The support page identifies the service operator.