Privacy information

This Privacy page explains how spacebarclickergame.org handles information when you use the Spacebar Clicker game, the Spacebar Counter tools, the leaderboard pages, and the related guide and support content. The site is designed to work without a traditional account system, so the privacy model is intentionally narrower than the model used by social platforms, large games with logins, or services that build long-term advertising profiles.

That difference matters. We do not ask users to register for an account before they can play the game, run a timed spacebar test, or read the public site records. At the same time, some information is still processed because the site needs to save progress locally, accept leaderboard submissions, reduce abuse, and render public records pages accurately. This page is meant to explain that boundary clearly instead of hiding the product behavior behind vague language.

A substantial part of the Spacebar Clicker experience is intentionally stored on your own device. Local game progress, upgrade state, exported save data, language preference, low-bandwidth preference, and the locally generated user identifier are kept in browser storage so the site can reopen in a familiar state without forcing account creation. That local identifier may also be written to the sb_uid cookie so the same browser can reuse it across pages.

When information stays local, it is not automatically turned into a public profile. If you never submit a timed result or a clicker session to a leaderboard endpoint, your local save and most of your play behavior remain in your own browser context. You can usually clear that data by removing site storage in your browser or by using the reset and import/export tools that the site provides for the clicker game.

Some site features do require a server request. When you submit a leaderboard result, the request may include the locally generated user ID, an optional nickname, the chosen mode or duration, result values such as clicks or score, proof-related timing data or timing digests, device type, and the client time reported by the browser. The server may also derive technical context such as country from the request environment when that data is available through the hosting platform.

That submission data is used for a limited product purpose: accepting runs, running anti-cheat checks, writing audit records, and updating public leaderboard caches. Public leaderboard pages may display accepted fields such as nickname, country, device type, clicks, score, CPS, and record timestamps. Because public records are part of the site feature set, users should avoid submitting information they do not want displayed on a public page.

The site uses submitted and technical data to operate the product rather than to create a traditional customer identity system. In practical terms, that means data may be processed to keep leaderboard pages working, evaluate suspicious submissions, detect repeated abuse patterns, maintain service integrity, and understand whether core site features are functioning. If analytics or infrastructure monitoring are enabled, they are used to understand performance, availability, and aggregate usage rather than to offer a user account dashboard.

The product does not promise invasive tracking, fingerprint-based identity building, or a hidden profile that follows you across unrelated websites. That said, no internet-facing service can honestly claim to process zero technical metadata. Basic request information, abuse prevention signals, and infrastructure logs may exist for operational, security, or hosting reasons. This page should therefore be read as a description of product intent and actual feature behavior, not as a claim that online requests happen in a total vacuum.

You can control a meaningful part of your privacy exposure by choosing whether to submit runs, whether to attach a nickname, whether to keep a local save, and whether to clear browser storage after use. If you only browse guides or support pages, or if you practice locally without submitting, your exposure is different from the exposure of a user who chooses to push runs to a public leaderboard page. That distinction is central to how this site works.

Because the product may evolve, this Privacy page can be updated when the feature set, hosting configuration, or public record behavior changes. Users should review this page from time to time if they rely on the site regularly. Continued use of server-backed features after changes are published generally means you are using the product under the updated explanation. If a future update affects only some pages or tools, those pages may be revised individually rather than all at once.