Privacy notice

Scope of this notice

This notice describes the current Puffer Party browser game and its game server, operated by the Puffer Party team and hosted on Railway, and website analytics on the game and public information pages. It covers browser storage, anonymous daily participation, request data and the owner's self-hosted Plausible analytics.

What stays in your browser

The game uses localStorage under the key pufferparty:v1. It stores a randomly generated anonymous player ID, your selected language, sound and music preferences, tutorial completion, daily attempts, completion status and best results. It also stores daily revive state and supported in-progress runs, including run IDs, elapsed time and the tile/action history used to restore progress.

This storage is associated with the browser and site, not a named account. It is not an account login or a cross-device backup. A different browser, profile or device may have a different ID and separate local progress. The game does not ask for your name, password, payment details or account registration.

What the game server receives and records

Starting a daily challenge sends the anonymous browser ID and daily date so the server can record participation. To verify a completed daily run, the browser submits its date, anonymous ID, attempts and timestamped actions, including selected tiles and tools. The server replays those actions against the official board instead of trusting a submitted score alone.

The gameplay database records daily participants and first-seen timestamps; verified results including completion time, attempts, tile selections and tool counts; result timestamps; and daily revive grants including the anonymous ID, date, run ID and grant timestamp. The action history is processed for verification; the result tables store the verified result fields rather than a full replay log.

Player-state requests check whether a revive has already been granted. A revive request records the daily grant so that another attempt or browser navigation with the same ID cannot grant a second revive that day. Daily statistics and relative rankings are produced from anonymous participation and verified results, not a list of named accounts.

Hosting and request metadata

Railway handles normal web requests as the hosting provider. Network requests expose technical metadata needed to deliver the site, which can include an IP address, requested URL and browser request headers. Hosting infrastructure may process request or operational logs as part of running the service.

The application uses IP-based counters in server memory to limit abusive requests to daily write endpoints and player-state reads. Counters are grouped into minute-long windows and may remain until cleanup or a server restart. They are not an account identifier or part of the gameplay result tables. We do not promise a fixed hosting-log retention period or a precise IP-counter deletion deadline.

Why these data are used

Browser storage preserves your settings, tutorial state and progress. Anonymous server records support daily participation counts, result verification, comparisons and the once-daily revive rule. Request handling and rate limits help operate the game and reduce automated abuse. This version does not provide account-based synchronisation, data export or a self-service server-record deletion tool.

Self-hosted Plausible website analytics

We use the owner's self-hosted Plausible instance at analytics.agentx.love on the game and all public information pages to understand aggregate website usage. It measures page visits and visited page URLs, referring sites and supported campaign parameters, browser and device types, approximate geographic location, time spent on a page and scroll depth.

The currently configured script also measures outbound link clicks, file downloads and form submissions. These events record the event and relevant URL, not form-field contents. The website currently has no on-site forms. Our integration does not send gameplay tile selections, action logs, the game's clientId or runId, saved progress or custom properties to analytics.

Plausible does not set tracking cookies or create a persistent browser identifier. Its daily, site-specific visitor counts are derived from request metadata; individual events and sessions are processed to produce aggregate reports, not to track identity across devices or websites. Analytics HTTP requests still expose normal network metadata, such as an IP address and browser request headers. This is separate from the game's localStorage player ID and progress. The tracker may read an optional plausible_ignore localStorage flag to exclude visits.

Plausible's official data policy describes its privacy design. That reference is not a statement that this owner-operated instance uses Plausible Cloud hosting or that Cloud-specific hosting details apply here. We do not promise a fixed analytics retention period or automatic deletion of analytics records when you clear game storage.

Advertising, cookies and optional tracking

The current game does not integrate advertising tags, AdSense or Google advertising cookies. Plausible is the only website analytics integration in this version. Promoting the game through Google Ads does not itself mean that the game sets Google advertising cookies. Essential game progress uses localStorage as described above.

If Google Ads conversion tracking, remarketing, optional advertising measurement or other analytics tools are introduced later, their providers, purposes and storage practices must be disclosed before activation, with consent obtained where required. This notice is not a guarantee of legal compliance or an unconditional claim that consent is unnecessary. It is not a claim that those future tools are already installed or that an advertising platform has approved the site.

Your storage choices and deletion limits

You can clear this site's browser data using your browser settings. This removes the locally saved ID, preferences and progress and can cause a new anonymous ID to be generated on your next game visit. Clearing local data does not automatically delete participation, results or revive records already held on the server.

Blocking localStorage can prevent saving. The game attempts to handle storage errors, but cannot guarantee progress recovery across reloads or navigation when storage is blocked or unavailable. We do not promise an exact server-data retention duration, automatic expiry of every record, or deletion merely because you stop playing. Local housekeeping of old daily entries is not a server-data deletion policy.

Privacy questions

Contact the Puffer Party team at support@pufferparty.io. The contact page explains what to include. Please do not email passwords or other sensitive information.