F1bonacci has no user accounts, no passwords, and asks for no personal information. There's one optional exception — a nickname for the leaderboard — and it's spelled out below.
The game runs entirely in your browser. Your progress — best tile, best time, undo allowance, last theme played, and your chosen nickname — is saved only to your device via localStorage. None of that is shared unless you submit a score, described next.
F1bonacci has a global leaderboard. When you finish a game (win or lose), the result is sent to our server so it can be ranked. To keep this honest about what leaves your device, here is exactly what is sent and stored:
If you haven't chosen a nickname, your runs are filed under an anonymous handle (like anon_3f9c1a2b) rather than your name. We never ask for, and never store, your real name, email, or any account details.
So that nobody else can claim or overwrite a nickname you've picked, your browser generates a random ownership token once and keeps it in localStorage. The server only ever stores a one-way hash of it — never the token itself.
This data is held in a hosted key-value database (Upstash Redis). Scores are validated and ranked on the server, never trusted blindly from the browser.
When a score is submitted, the server briefly uses your IP address to rate-limit submissions (a guard against spam and fake scores). For anonymous runs, it also derives the anonymous handle above from a hash of your IP and browser user-agent. These signals are used only to keep the leaderboard fair — not to identify or profile you.
We use two analytics tools to understand how the game is used:
GoatCounter — privacy-friendly, anonymous page view counts. No cookies, no cross-site tracking, GDPR-compliant. See goatcounter.com.
Google Analytics 4 (property G-WJD7H0GWQQ) — page views plus a small set of custom gameplay events. GA4 sets cookies in your browser and sends data to Google; it may also collect an approximate location (derived from IP) and basic device/browser info. Google's handling is covered by the Google Privacy Policy.
The custom events we send to GA4 are:
theme_selected — which theme you picked from the menugame_start — a new game begins (with theme)milestone_reached — first time you reach tile 5 or tile 8 in a gamegame_win / game_over — highest tile reached and elapsed timeinsight_view — you opened a tile's fact card (theme and tile)undo_modal_open / undo_used — you opened the Undo panel / spent an Undo (with theme)share_open / share_complete — you opened the share sheet / a share went out (with the channel, e.g. WhatsApp or copy)referral_prompt_shown / referral_share_open / referral_share / referral_reward — the invite-a-friend prompt and its free-Undo rewardNo account info, names, or emails are sent to analytics. We use these signals purely to see which themes are popular and how far players get.
If you'd rather not be measured, browser-level controls such as "Do Not Track," content blockers (e.g. uBlock Origin), or Google's GA opt-out add-on will stop GA4 from loading.
The game itself is static HTML and JavaScript with no build step — most of what you interact with runs entirely in your browser. The one server-side piece is a small serverless API that powers the leaderboard (submitting a run, picking a nickname, reading the rankings), backed by the hosted database mentioned above.
External resources loaded by the pages: the Inter font from Google Fonts (typography), Phosphor Icons (UI icons), Google Analytics, and a lightweight GoatCounter script (anonymous page view counting).
We store no passwords and no sensitive personal data, all score logic is checked server-side, and submissions are rate-limited. The attack surface is deliberately small.
We don't know who you are, and we're fine with that.