← Back to Pixoot

Privacy Policy

Last updated: 8 November 2026

Pixoot ("we", "us", "the game") is a browser-based pixel-art co-op RPG operated from pixoot.com. This privacy policy explains what data we collect, why we collect it (our legal basis under the GDPR), how long we keep it, and your rights. It covers the game, your account and the in-game chat.

We are the data controller for the data described here. We have not appointed a Data Protection Officer — our processing does not meet the legal threshold for one. Privacy questions: privacy@pixoot.com.

1. Data We Collect

1.1 Account Information

When you sign up with email and password, we store:

When you sign up with Google Sign-In, we store:

We also store a nickname (display name) of 1-16 characters. This is the name shown beside your messages in chat; you can change it in Account Settings, and if you never set one we generate a unique Nick#1234567 for you. We never collect your real name, date of birth, phone number, or any other personally identifiable information beyond what is listed above.

We also record which Terms & Privacy Policy versions you accepted, and when — so we can prove which text applied to your account, and ask you to confirm a new version if the policy changes (see §11).

1.2 Game Data

We store your game progress server-side, including:

This data is linked to your account and is deleted when you delete your account.

1.3 Chat

The game includes public chat channels (Global, LFG, Single player, Builds), staff-run read-only channels (FAQ, News) and a chat for your current co-op room. To keep chat usable and attributable:

Moderation records. Every message the filters touch — obvious spam (blocked), banned-word hits, and borderline messages (rejected and flagged for review) — is recorded in a moderation log with the message text, the rules it matched, a spam score, your nickname and account ID, the action taken, and a truncated hash of your IP address (never the raw address, and only for linking related abuse from the same source). This log powers the admin "Spam" review view; it is pruned to keep approximately the newest 2,000 entries and rows older than 90 days are deleted automatically.

1.4 Local Storage (on your device)

Your browser stores game save data locally using localStorage. This includes:

Two values are kept in sessionStorage (cleared when the browser tab closes) instead of localStorage:

This data is strictly necessary to run the session you requested and never leaves your device unless you are connected to the game server. The three things on this device that need your consent — Google's sign-in script, Google's ad script, and the 30-day persistence of a referral link — are described in §1.6.

1.5 IP Addresses

We do not store raw IP addresses anywhere. They are hashed (SHA-256, truncated) before any storage and used only for:

Hashed IPs are automatically deleted after 90 days by the same clean-up job. A hash is still personal data — we treat it as such; it exists only to stop abuse.

What the audit log actually contains: the event name (for example login, nickname_set), a timestamp, that truncated 16-hex-character hashed IP, the account's internal id, occasionally small non-identifying details of the action (such as the nickname you just chose), and — for sign-ups only — a 16-hex-character hash of your e-mail address (so the same address registering twice can be linked without ever storing the address itself). Raw IP addresses and raw e-mail addresses are never written to it.

1.6 Cookies, Ads and Analytics — and a consent choice

Pixoot sets no cookies of its own, uses no tracking pixels, and runs no analytics services — no Google Analytics, no Facebook Pixel, no similar tool. It does show Google AdSense ads on the game menu, and those are served entirely by Google. There are exactly three consent-relevant extras on this site, and all three are off until you allow them in the cookie banner (or, for Google sign-in, until you explicitly continue in the small on-page prompt after clicking "Sign in with Google"):

Everything else on this device — game save, login, settings, bot protection — is strictly necessary and never gated. You can change or withdraw your choice at any time through the "Cookie settings" link in the footer of the game page: refusing (or withdrawing) is as easy as accepting, and your choice is remembered on your device for up to 13 months (after that we ask again).

1.7 Payment Information

Optional cosmetics are paid for through Stripe Checkout. Stripe collects and stores your card details; Pixoot never receives or stores your full card number, CVC, or expiry date. We only keep:

Purchases require a verified email address and are recorded against your account. Nothing you buy is linked to a card number on our side.

1.8 Leaderboards (Hall of Fame)

The Hall of Fame is a public leaderboard. Appearing on it requires a verified email address or a Google sign-in — guests and anonymous players never appear. For each hero that places, we store and publish:

Who sees it: anyone who opens the Hall of Fame. Board pages are served uncached to everyone, so removing something removes it at once for every visitor. Your rows are profanity-filtered before display, and an account whose appear on leaderboards setting is off is rendered under a stable pseudonym (Adventurer#…) instead of its nickname — rank and score are unaffected by that setting. The board also remembers your own rank on your device (pixoot_lb_last_v1 in localStorage) to show rank-change arrows.

Deleting a character does not remove a placement you already earned. The row and its snapshot belong to your account's record and stay published, exactly as captured — deleting the hero never erases your score. Deleting your account does remove every placement: scores, snapshots, names, evidence and moderation flags are erased from the boards, the placement popups and every other public read at that moment (a Hall window someone else already has open refreshes within one poll cycle, at most 60 seconds).

1.9 Page Views — our own visitor counter

To count page loads and classify them as human or machine, each page load sends us one first-party request. It sets no cookies, runs no third-party analytics (§1.6), and is never used to follow you across sites. It stores only:

Rows are deleted after 90 days by the same clean-up job as the audit log. The totals appear only in the operator console — they are never published, never used to identify anyone, and never affect gameplay, matchmaking or your account. Note that this counter only sees browsers that execute JavaScript: ad blockers, privacy browsers and non-JavaScript clients never send it, so the count always reads lower than a CDN's own request count. You can switch it off on your own device by setting localStorage.pixoot_pv to "0" and reloading.

2. How We Use Your Data — and Our Legal Basis

Under the GDPR we must name a lawful basis for each purpose:

PurposeLegal basis
Creating your account, saving game progress, enabling co-op playPerformance of a contract — Art. 6(1)(b)
Hosting and delivering chat messages you send (the chat feature you asked to use)Contract — Art. 6(1)(b), plus our legitimate interest in keeping channel history working — Art. 6(1)(f)
Spam and bot filtering, proof-of-work checks, moderation logs, hiding messages, temporary mutes and bans, protecting players and the service from abuseOur legitimate interests — Art. 6(1)(f): keeping chat usable and safe, preventing fraud and attacks
Transactional emails (verification, password reset, security notifications)Contract — Art. 6(1)(b)
Processing purchases and keeping purchase records for tax and consumer-protection lawContract and legal obligation — Art. 6(1)(b) and 6(1)(c)
Publishing a Hall of Fame placement (nickname, title, hero name, score and placement snapshot) to other players, and keeping the server-observed evidence behind each scoreOur legitimate interests — Art. 6(1)(f): players expect a public ranking of scores the server itself observed. Participation requires a verified account, public reads never expose your email address, and you can erase every placement at once by deleting your account (see §1.8 and §7)
Showing Google AdSense ads on the game menu — including contacting Google to request one at allConsent — Art. 6(1)(a): the ad script is loaded only after you allow the "Google services" category in the cookie banner, and withdrawing that choice stops it (see §1.6)
Answering support, privacy and legal requests; defending legal claimsLegitimate interests / legal obligation — Art. 6(1)(f), 6(1)(c)

Our legitimate interests are: other players expect a usable, moderated chat; we do not process sensitive data through chat by design; chat is optional; and our safeguards are minimisation, hashed IPs, short retention, transparency, the right to object, and human appeal on moderation decisions.

What we do not do: no marketing emails, no profiling for advertising by us, no selling or renting data, and no sharing of chat content with other players' third-party services. The only advertising on the site is Google AdSense, which runs entirely on Google's side and only after you allow it (§1.6) — we never receive, keep or inspect which ads you were shown, or the data Google used to choose them.

3. Automated Checks and What They Decide

Messages pass through automated checks before delivery. We tell you this here, as the GDPR requires for decisions with legal or similarly significant effects (Art. 22) and for meaningful information about the logic involved:

4. Chat Moderation

5. Third-Party Services

Your data is processed by the following services:

Each third-party service has its own privacy policy. We only share the minimum data necessary for each service to function. We do not sell or rent personal data, and we do not share your chat content with advertisers.

6. Data Retention

DataHow long
Registered account (email, nickname, game data)Until you delete your account
Chat messagesRolling 90 days, then deleted automatically
Chat moderation log (blocked / flagged messages, IP hash)Newest 2,000 entries; rows also deleted after 90 days
Guest accountsSoft-deleted after 90 days of inactivity, permanently removed 30 days later
SessionsExpire after 30 days; rows deleted 7 days after expiry
Auth tokens (verify/reset)Deleted 7 days after use or expiry
Hashed-IP rate-limit windowsDeleted after 90 days
Audit logsDeleted after 90 days
Purchase recordsKept for as long as your account exists, plus any period required by tax or consumer-protection law
Hall of Fame placements (scores, ranks, names, placement snapshots)Until you delete your account — deletion removes them from public reads at once (a Hall window open elsewhere refreshes within 60 seconds); deleting a single character does not remove a placement
Hall of Fame anti-cheat evidence (server-observed events per score)Rolling 90 days, and deleted with the account

All automatic deletions run in a clean-up job every 6 hours.

7. Your Rights (GDPR)

If you are in the European Economic Area (EEA) or United Kingdom, you have the following rights under GDPR:

We answer data requests within one month. We only ask for the minimum information needed to confirm the request comes from you — never identity documents for routine requests.

8. Children's Privacy

Pixoot is designed for a general audience. We do not knowingly collect personal information from children under 13. If you are under 13, do not create an account. In the EEA/UK, the required age for agreeing to this policy yourself ranges from 13 to 16 depending on your country — if you are below the age that applies where you live, a parent or guardian must agree for you. We rely on self-declaration and do not ask for age documents; if we become aware that a child below the applicable age has provided personal information, we will delete it promptly.

9. Data Security

10. International Transfers

Your data may be processed in countries outside the EEA (e.g., United States) by our hosting providers (Cloudflare, Hugging Face, Neon, Brevo, Stripe) and, when you have allowed ads, by Google (AdSense — see §1.6 and §5). Where data leaves the EEA/UK we rely on an adequacy decision where one exists (e.g., the EU-US Data Privacy Framework for certified providers), and otherwise on the EU Standard Contractual Clauses (Commission Decision 2021/914, with the UK Addendum where UK law applies) together with our providers' security measures. A copy of the applicable safeguards can be requested from privacy@pixoot.com.

11. Changes to This Policy

We may update this policy from time to time. Significant changes will be communicated via the game or email before they take effect. The "Last updated" date at the top will always reflect the most recent revision. We keep a record of which version you accepted and when; when a new version takes effect we will ask you to confirm it again in the game.

12. Contact Us

For privacy-related questions or requests (including access, erasure and portability), contact us at:

privacy@pixoot.com

To report a security vulnerability (not a chat report), contact security@pixoot.com — this is also the address in .well-known/security.txt.

To report chat messages, players or illegal content, and for legal notices, see legal@pixoot.com (see Terms & Conditions).

This privacy policy is effective as of 22 September 2026, with payment processing added 27 September 2026, chat, moderation, legal bases, retention schedules and data-export rights added 27 September 2026, and the third-party script (Google Sign-In), Network Error Logging and local-storage inventory disclosures added 3 October 2026. Consent-version recording, the audit-log contents disclosure, the security contact address, password-change notification emails and the backup-residue note were added 3 October 2026, and the Hall of Fame leaderboard disclosure (§1.8, its legal basis, its retention rows, and leaderboard coverage of erasure, access and portability) was added 25 October 2026, and Google AdSense advertising (§1.6's third consent-relevant extra, the AdSense entry in §5, its consent legal basis in §2 and the international-transfer note in §10 — plus the cookie banner's matching copy) was added 2 November 2026, and a first-party page-view counter (new §1.9, the matching hashed-IP use bullet in §1.5, and its User-Agent disclosure) was added 8 November 2026. That last revision did not raise the consent version: the counter sets no cookies, runs no third-party analytics and can be switched off on the device, so nothing new needs a consent decision. The same section now also discloses the 2-letter country code our CDN derives from the visitor's IP address at the edge and forwards with the beacon (stored next to the hash, never the raw address, and never editable from the browser) and the fact that the referring hostname is grouped into a named source in the operator panel — both added 8 November 2026 as disclosure of how that same counter's data is used, so they raised no consent version either.