Privacy policy

Last updated 4 November 2026. This describes FirePoop Journey at firepoop.com, run by Hagerling and hosted on Vercel.

The short version. Playing needs no account. Putting a score on the leaderboard needs no account: the server stores the nickname you pick and a hash of a random key your browser made, never anything about you. Signing in with Apple or Google is optional and keeps your nickname on other devices; it stores a hashed account identifier, never your email or name. Racing friends in a room sends your room nickname and your race progress through a short-lived relay that forgets the room within minutes. There is no third-party analytics and nothing sets a third-party cookie. The site keeps a daily count of page loads without any IP address, and rate limits keyed by a salted hash of your IP address. All of it is described below, in full.

What your browser stores

The game keeps your progress and settings in your own browser, using localStorage (one key uses sessionStorage). None of this leaves your device except where a key says so. Clearing site data for this domain deletes all of it, and the game then treats you as a new player.

The Journey game at /journey/

fp_journey_player_id
A random identifier generated in your browser the first time the leaderboard is used. It is sent with the request that starts a run, and the server does not store it.
fp_journey_lb_name
The nickname you typed for the leaderboard (up to 12 characters), kept so the form is pre-filled next time.
fpj_device_key
A random key made in your browser the first time you submit a score. It is sent with each submit so the server knows the nickname is yours; the server stores only a hash of it, never the key itself. Clearing site data loses it, and the nickname then needs a sign-in to get back.
fp_journey_mp_name
The nickname you last used in a multiplayer room, kept so the room form is pre-filled next time.
fp_journey_local_best, fp_journey_best_score, fp_journey_best_pct, fp_journey_best_organ, fp_journey_completions, fp_mouth_best, fp_mouth_attempt and similar fp_mouth_ keys
Your own best results, how far you got, how many runs you finished and your attempt count.
fp_journey_skins, fp_journey_ability_seen, fp_journey_flush_seen, fp_journey_hint_seen
Which skins you have unlocked, and which one time explanations you have already seen.
fp_journey_quality_choice, fp_journey_quality, fp_journey_quality_pref, fp_journey_beatring, fp_mouth_mute
Settings: graphics quality, the beat ring switch and the sound setting.
fpj_auth_ping
A short message the sign-in window leaves for the game tab, so the game knows the sign-in finished. It holds no account details.
fp_journey_pv (sessionStorage)
Marks that this tab already counted one page load, so the counter below is not bumped twice. It is gone when the tab closes.

The original game at /

firepoop_player_id, firepoop_player_name
A random identifier and the name you typed. On this host the original game's score, run and replay services are not served, so neither is sent anywhere.
firepoop_best, firepoop_attempts, firepoop_poophunt_best, firepoop_poophunt_scores
Your own results and attempt count.
firepoop_skin_active, firepoop_skins_morphed, firepoop_classic_handling, firepoop_metronome, firepoop_journey_practice, firepoop_launch_seen, firepoop_latest_replay_ext
Settings and unlocks: which skin is on, which morphs you have seen, the classic handling switch, audio preferences, practice mode, and whether the launch notice has been shown.

Cookies

The game sets no cookies. Signing in sets two cookies of this site's own, both HttpOnly and Secure: fpj_s keeps you signed in for 30 days (it holds the service name and the hashed identifier, signed by the server), and fpj_oa lives for at most ten minutes during a sign-in to protect it against forgery. Sign out in the leaderboard removes fpj_s.

What the server records

The server side runs on Vercel. Leaderboard data is kept in a private Vercel Blob store. Multiplayer rooms are kept in an Upstash Redis database. Nothing else is stored.

Run tokens

Every run asks the server for a signed token before it starts. The token is self-contained: nothing about you is written to storage to issue it. When a time is claimed, the server keeps a marker that the token has been used, holding only a hash of the token and the time it was issued, so the same run cannot be submitted twice.

Rate limits

To stop the leaderboard being flooded, the server counts recent requests per address: starting a run (60 an hour), claiming a time (30 an hour) and the page counter (30 a minute). Each count is a short list of request times stored under a salted hash of your IP address. The raw address is never stored. Reading the leaderboard is limited in memory only and nothing is written for it.

Page counter

Loading /journey/ sends one beacon per browser tab. The server adds one to a daily counter for that page, and one to a daily counter for the hostname of the site that linked you there, if any (only the hostname, at most 50 different ones a day, the rest counted as "other"). No IP address, identifier, language or time of day is kept: only the totals per day.

The leaderboard

Playing and submitting a score need no account. When you submit, the server stores your nickname with a SHA-256 hash of your browser's random key (fpj_device_key above), so only this browser can use that nickname. Signing in with Apple or Google is optional: it links the nickname to your account so you can use it on other devices. It asks the service for the least it allows: Apple no name or email; Google the openid scope only. The game does not read or post anything on either service.

For your account the server stores which service you signed in with, a keyed hash (HMAC) of that service's account identifier, the nickname you use now, every nickname the account holds (so nobody else can take one of them), and the date the account was first used. It does not store or show your email address, your name, your profile picture or the raw account identifier.

The public entry for a claimed time is your nickname, your score, your Poop Hunt score, the total, your elapsed time, the distance, the skin in use and the date in UTC. Each entry also records, on the server only, which account or which hashed browser key submitted it. The nickname is public on the board; the account behind it is not. No replay video is uploaded.

Multiplayer rooms

Racing friends uses a room of up to 4 players, joined with a four letter code. The room service is a relay: it passes messages between the players and keeps the room in Upstash Redis only while it is in use. For each room it holds:

A room is deleted 10 minutes after the last player stops polling it, and no room can be used for more than 3 hours. The room service sees no account, no email and no leaderboard data, and nothing from a room is ever written to the leaderboard. Its own rate limits count requests under a salted hash of your IP address and of the client identifier, and those counters expire within two minutes.

An invite link looks like ?room=ABCD&as=Name. The as part is the name the host typed for you: anyone you send the link to can read it, and it stays in your browser history like any link. The server only reads the room code from that link, to show the invite preview.

Third parties

There is no third-party analytics on this site and no third-party cookie is set by anything on it. Google Analytics used to run on the production domain and has been removed: no script from googletagmanager.com, or from any other analytics vendor, is loaded.

Every file the page loads comes from this domain. There are no trackers, no advertising, no social media widgets and no embedded third-party frames. The fonts are self-hosted .woff2 files served from /fonts/. The links in the game to GitHub, Instagram, dev.to and Buy Me a Coffee are ordinary links: nothing is loaded from those sites until you choose to follow one. Signing in takes you to the sign-in page of the service you pick, under that service's own privacy policy.

How long things are kept

Who the data goes to

Nothing is sold, rented or handed to advertisers, and no analytics vendor receives anything. The site is hosted on Vercel, which as the hosting provider necessarily processes traffic to the site, including your IP address in its own short-lived request logs, and stores the leaderboard in Vercel Blob. Multiplayer rooms run on Upstash Redis, which processes the room data described above. Both act as service providers for this site.

Your choices

You can play without submitting a score, in which case nothing bearing a name of yours is stored on the server. You can play alone without ever opening a room. You can clear your browser storage to reset the game. If you want a leaderboard entry or your account and its nicknames removed, ask and it will be removed: tell us the nickname and, if you signed in, the service you used.

Children

The game is silly, but it is not built for or aimed at children under 13, and it deliberately collects nothing that would identify one.

Getting in touch

FirePoop Journey is made by Hagerling. For anything about this policy, a removal request, or a question about what is stored, use the contact details at hagerling.se.

Changes

If what the site collects changes, this page changes with it and the date at the top is updated. It is written from the actual endpoint code rather than from a template, and a test checks it against that code.