Effective September 16, 2026 · V2

Privacy promise

ArcadeBench is a free, non-commercial, open-source arcade. We are here to make games—not to turn players into a dataset.

What stays on your device

Ordinary gameplay and replay inspection run in your browser. Loading a replay file does not upload it. Your downloads and your browser's local preview data remain under your control.

When a replay is uploaded

A complete replay reaches ArcadeBench only when you submit a ranked score for verification or explicitly choose Share for 5 days. The server replays its inputs through the open-source game engine to verify the result.

Shared replay links and ordinary score proofs expire after five days. Submissions made under the earlier five-day policy keep that deadline. After deletion, we retain the replay’s SHA-256 hash and public leaderboard summary; a hash cannot play the game back.

Top 50 replay archive

If a score submitted through a current ArcadeBench game score form reaches the Top 50 on its specific leaderboard, we keep its full replay without a scheduled expiration, even if later scores overtake it. Each game has its own leaderboards, separated by game version, season, and game-specific modes or settings. Other submitted replays expire after five days.

Submissions made through older compatibility clients and routes keep their five-day replay deadline, even when submitted after this policy took effect.

Saved replay files are private and are not available for public playback on ArcadeBench. The public recent-scores feed may show your callsign, game, leaderboard, placement when submitted, and submission time.

Historical leaderboards

When scoring or gameplay changes make old and new scores incomparable, we close that leaderboard to new entries and start a new version. We preserve the completed leaderboard as a read-only historical record with its final standings, including callsigns, score summaries, and submission dates. We do not merge or rescale scores across versions.

This public score history is separate from replay retention. A score summary can remain after its full replay expires.

Optional social-media use

You can separately allow ArcadeBench to share your saved replay or clips from it on social media. This checkbox starts unchecked for each run. Leaving it unchecked does not affect your score, ranking, or Top 50 replay retention. We record your choice, the permission version, and when you submitted it. We do not publish saved replays on social media without this permission.

Social-media permission does not authorize AI training. We do not use your gameplay or replays to train AI.

What a leaderboard keeps

  • The callsign you submit, score, game and level, difficulty, timing, partition count, game version, and submission date.
  • The replay hash and verification status after the replay itself is deleted.
  • Anonymous game and level votes.

Votes and private feedback

You can vote up or down on supported game items and optionally leave a private note for ArcadeBench’s maintainers. Notes are not public comments, do not appear in activity feeds or vote totals, and are not sent to AI models.

Notes expire 90 days after their latest explicit update. Voting again does not extend that deadline. You can clear a note separately from your vote while your anonymous browser session remains available. Losing the session cookie loses access to its editing controls.

Accountless play and safety

There are no player accounts. A signed anonymous cookie lasts up to 30 days so voting, private feedback editing, one-time score challenges, and rate limits work. ArcadeBench does not write IP addresses into its application database.

To keep public callsigns suitable for everyone, only the proposed callsign—not gameplay, replay data, prompts, or controller code—is sent to Cloudflare Workers AI for one safety classification. Approved names appear on leaderboards. Rejected raw names are not stored; the moderation cache keeps a hash.

Infrastructure

Cloudflare delivers the site and may process ordinary network and security metadata needed to operate and protect it. ArcadeBench uses Cloudflare D1 for leaderboard and social records and R2 for temporary replay objects and saved Top 50 replays.

Open code, honest changes

The games, replay verifier, retention job, and this promise are public in the ArcadeBench repository. If our practices change, we will change the code and this page together—not quietly reinterpret the words.