Small games. Clear privacy.

Last updated: 12 September 2026

Who is responsible?

Puffer AB, Swedish company registration 556850-9144, is the controller of personal data processed for Zubboo. Our postal address is Flaggan 1338, 116 74 Stockholm, Sweden. Contact us at privacy@zubboo.com.

Playing as a guest

The games run in your browser. When browser storage is available, we save game progress, best scores, unlocked cosmetics, preferences, favourites, recent games and your chosen character on this device. These saves remain until you clear them or your browser removes them. They are not uploaded as cloud saves while you are signed out.

Your browser still sends normal connection information, including your IP address, browser details and requested page, to our hosting provider to deliver and protect the website. Guest play is not the same as an anonymous network connection.

The recent-games list holds up to ten game names, their modes and last-played times on this device. It updates after a gameplay action, not from viewing a page. Related-game suggestions are chosen from our own catalog; this history is not uploaded to your account or an advertising service. You can switch off or clear the list in recent-games controls.

Optional accounts and cloud saves

Accounts are available to players aged 16 or over. We ask for an age band before registration, not your date of birth. If you are younger, you can keep playing and customising your character locally.

For an account, we store a random account identifier, creation time, the public part of your passkey, related technical verification details, session records, a hashed recovery code, and the versioned game and wardrobe data you choose to save. We do not receive your fingerprint, face scan or device unlock code. Those checks happen through your device’s passkey system.

Your account saves are private. We do not turn them into a public leaderboard or share them with other players. Games and cosmetics currently sync as personal progress; a saved score is not a verified competition result.

Optional play stats

With your permission, we use first-party play stats to learn which pages and games work well. Events contain a known page or game name, mode, broad traffic source (such as Google or a social site), country, device category and whether this browser returns after its first opted-in day. On game pages we count the first accepted play action and first result in each mode. The elapsed time to that result is capped at one hour and can include pauses. Completed account registrations are counted by the server separately.

Stats do not contain account IDs, passkeys, recovery codes, saved game content, names, free-text searches, exact referrer URLs or an analytics visitor ID. They do not create a profile across devices. Country comes from the hosting connection; IP addresses and full browser details are not written into the play-stats dataset. Short-lived network rate limits help protect the collection endpoint.

Cloudflare Analytics Engine stores these events for three months. We use grouped reports to improve the site. Stats are a sample of consenting browsers, not a count of unique people or verified competition scores. Because events have no visitor identifier, we cannot retrieve one person's previous stats from that dataset.

Your play-stats choice and first opted-in day are kept in local storage for up to 180 days. When enabled, a first-party zubboo_stats cookie remembers permission for up to 180 days; it contains no visitor ID. A broad acquisition-source category is kept in session storage, reused for at most 30 minutes between pages and removed when stats are switched off. No stats are sent before permission. “No thanks” and browser Do Not Track or Global Privacy Control preferences keep them off.

You can withdraw permission at any time in play stats controls. This stops future collection and removes the stats cookie and source category; previously collected events expire with retention. All games and account features work without stats.

Cookies and browser storage

Signing in uses a secure, first-party session cookie that expires after 30 days. A separate sign-in challenge cookie lasts up to five minutes. They support authentication, not advertising. Local storage holds game saves, your wardrobe, favourites, recent games and sync checkpoints so we can detect conflicting versions safely.

You can play without these account cookies. Blocking browser storage can prevent progress from lasting beyond your current visit. Device data controls explain how to clear local saves separately from your account.

Why we process data

• Optional play stats: your consent lets us measure use and improve the games. You can withdraw it without affecting play or your account.
• Provide the service you request: authentication, recovery and cloud saving are needed to provide your optional account under our terms.
• Keep the service working safely: limited technical logs and short-lived rate limits support our legitimate interests in preventing abuse and fixing faults.
• Answer messages: when you email us, we use your address and message to handle your question, request or complaint. Depending on the request, this supports the service, our legitimate interests in providing support, or a legal obligation.

We do not use your data to make automated decisions with legal or similarly significant effects.

Service providers and international processing

Cloudflare provides our hosting, content delivery, security, account database and inbound email routing. Our account database is configured for the European Union. Website delivery and related technical processing may take place in other countries through Cloudflare’s global network; an EU database does not mean every network operation stays in the EU.

Support messages are forwarded to our business email service for a reply. Service providers may process data only as needed for their services and applicable legal requirements. Where international-transfer safeguards are required, we rely on the applicable contractual safeguards, including standard contractual clauses. Contact us for information about safeguards relevant to your request.

How long information stays

• Device saves: until you clear them or the browser removes them.
• Account and cloud saves: while your account exists. Account deletion removes them from the live account database.
• Sessions and challenges: no longer accepted after their 30-day and five-minute expiry periods. Expired database entries are removed during housekeeping requests.
• Abuse-prevention counters: short-lived, hashed buckets with ten-minute expiry periods, removed during housekeeping.
• Worker diagnostic logs: retained by the hosting platform for up to seven days. Our application does not deliberately log recovery codes or passkey responses.
• Database recovery copies: historical copies may remain in Cloudflare’s restricted recovery system for up to 30 days. They are not used for ordinary gameplay after deletion.
• Support messages: for handling the request and any necessary follow-up or legal record. You can ask us to delete messages that we no longer need.

Your choices and rights

You can access and export account data, correct your saved character through the wardrobe, sign out individual or all sessions, remove a passkey, and delete the account in account controls. Local saves need to be cleared separately on each device.

Depending on the processing and applicable law, you may also request access, correction, erasure, restriction or portability, and object to processing based on legitimate interests. Email privacy@zubboo.com. We may need to verify that the request concerns your account; we will not ask for your recovery code by email.

You can complain to your local data protection authority. In Sweden, that is Integritetsskyddsmyndigheten (IMY).

Young players and families

All games can be played as a guest. We do not offer accounts to under-16s, a parent-consent service, public chat or behavioural advertising. If you believe a child has created an account contrary to these rules, contact us so we can investigate and remove account data where appropriate.

Changes

We will update this page when the service or its data practices change. Material changes will be explained on the site before any new use that needs a choice from you.