YOUR GAME. YOUR CHOICES.

Privacy policy

Last updated:

This policy describes the independent Fireboy and Watergirl game at fireboy-watergirl-game.web.app, developed and maintained by AppsOverFlow. You can play without entering a name, email address, or password.

What to know before you play

  • Progress, personal bests, and sound settings are saved on your device.
  • Online rooms send the information needed to keep both players in the same game to Google Firebase.
  • Measurement starts by default without analytics cookies. Optional analytics cookies need your choice in Cookie settings.
  • Advertising placements are currently disabled. The game works with optional cookies off.

What stays on your device

  • Progress and records. Browser local storage holds played and completed levels, the last started level, best completion times, diamond records, and perfect clears. These saved records are not an account backup and do not automatically transfer to another browser or device. Gameplay events may still be measured as described below.
  • Sound preferences. Your music and effects choices and volume levels are stored locally. The game creates its music and sounds on your device.
  • Controls, display and replay. Touch-control placement and response, visibility preferences, drawing mode and the optional best-run ghost setting stay on this device. Completed local runs can retain up to eight room records with position samples taken eight times per second, for runs no longer than ten minutes, within a two-million-character storage limit. These traces are not uploaded.
  • Progress transfers. Saved progress lets you download a file containing compatible completed levels, personal bests and your place on the map. Importing a file is a local action with a preview before applying it. It does not upload the file or transfer room codes, reconnect tokens, preferences or ghost traces.
  • Problem reports and performance exports. The pause menu can prepare a local file with the selected problem category, your optional description, level identity, limited player positions and mechanism counts, and recent aggregate performance measurements. You can review these details before downloading. The report does not include room codes, reconnect tokens, raw controls or browser identity. It is not sent to the developer automatically; you decide whether and where to share the file.
  • Cookie choices. Your optional-cookie choice is stored locally and is treated as valid for up to 180 days. After that, the game asks again.
  • Room reconnection. A room code and reconnect token are kept in browser session storage. Firebase also saves an anonymous sign-in session for that browser tab so you can reconnect without an account form.

Your browser may cache public website files such as images and fonts to speed up visits. The game does not create a separate downloadable copy. Previously saved game downloads are removed automatically on a connected visit, without removing progress or preferences.

Local progress and preferences have no automatic expiry in the game. They remain until you or your browser clear them. Closing a tab ends its normal session storage; restoring a browser session may restore it. Clearing site data does not delete information already held by a service provider.

Online rooms

Online play uses Google Firebase Authentication and Realtime Database. An anonymous Firebase identity is created or reused when you connect. Firebase receives the room code, player identifiers and roles, connection timestamps, controls such as movement and fairy dragging, and the current game state. The room creator’s browser runs the shared simulation and sends updates to the other device.

Room information is available to your teammate and can be accessed by someone who has the room code. Treat an invite link as access to that room. There is no free-text chat, public player profile, or name-entry field. Four preset co-op signals can send a short instruction and an in-game position to your teammate. They disappear from the screen after eight seconds; their last stored values remain part of the room until replaced or the room is deleted. Firebase connection and authentication data are needed for online play regardless of optional-cookie choices.

How long room data remains: choosing to leave as room creator deletes the hosted room. A disconnected guest’s seat can be reclaimed after two minutes. If someone tries to join a room inactive for more than 24 hours, the game attempts to delete it. Abandoned rooms are not removed by a scheduled background cleanup, so they may remain until that check or administrative deletion.

Ending a browser session or leaving a room does not itself delete the anonymous Firebase Authentication account. Provider authentication records are separate from room data.

Game measurement and analytics

Google Tag Manager and Google Analytics load by default on the game and public guide pages, including this policy. Before analytics cookies are allowed, the game sets analytics storage to denied and uses Google’s Advanced Consent Mode. Google can still receive cookieless measurement requests. “Reject optional” does not turn off all measurement. Google explains this behavior in its Consent Mode documentation.

Measurement covers page visits and engagement, campaign and level choices, starts and finishes, collected diamonds, restarts, pauses, active play time, interface use, frame rate, connection quality, and page performance. Requests can also include basic browser, device, and network information processed by Google. The game can temporarily queue analytics events in page memory and deliver them when Google’s measurement script becomes available, including after connectivity returns. These queued events are not saved to device storage.

The game’s analytics events do not include your name, email address, room code, reconnect token, pointer coordinates, or the contents of keyboard input. Page and link URLs supplied by the game omit query strings and fragments. This is separate from the controls and positions transmitted to your teammate during online play.

Downloading a problem report can record its selected category, drawing mode and standard game context only when analytics cookies are allowed. The written description, report file and player positions are never included in that analytics event.

If you allow analytics cookies, Google can use cookie identifiers to recognize repeat visits and sessions. The game disables Google Signals and advertising personalization in its tag settings. Google’s retention and processing rules apply to data it receives; deleting browser data does not erase those service-side records.

Advertising

Advertising is not currently displayed by the game: its optional AdSense placement is disabled. When no placement is enabled, the game does not load its AdSense advertisement script or offer an advertising choice.

If a placement is enabled in a future update, the game is designed to load it only after you allow optional advertising. It requests non-personalized ads. Google may then use cookies and process device, network, and page information to deliver and measure ads and prevent fraud. Non-personalized advertising can still use cookies. Availability also depends on Google’s approval and applicable consent requirements.

Manage your choices

  1. Change optional cookies: use Cookie settings in the footer of the game or a guide page. Choose Reject optional to deny analytics and advertising storage while retaining cookieless measurement.
  2. Withdraw a previous choice: turn off the relevant option and save. The game attempts to remove accessible Google analytics and advertising cookies, then reloads the page. A local game restarts. This cannot remove cookies on Google’s own domains or data already received by Google.
  3. Remove local saves: clear site data for this address in your browser’s privacy or storage settings. Your progress, personal bests, sound settings, cookie choice, and reconnect session may be removed.
  4. Limit network measurement: browser content-blocking controls can prevent analytics requests. Same-device play does not require optional analytics or advertising cookies; online rooms still need their Firebase connection.

Services and questions

Google Firebase hosts the public site and supports online rooms. Hosting and connection providers may process IP addresses and request logs to deliver and protect their services. Fonts and game artwork are served from this site. This game does not request access to your camera, microphone, or precise location.

For provider details, read Google’s privacy policy, how Google uses information from partner sites, and Firebase’s privacy information.

This game is developed and maintained by AppsOverFlow. Visit the About page to learn more about the game and this independent adaptation.

When the game’s data practices change, this page will be updated and the date above will change.

Back to the game →