PLAYER INFORMATION

Privacy, terms of play, and community rules for the game as it works today.

Effective October 21, 2026

Privacy

What SPADEFALL stores

SPADEFALL does not require an account. The game stores your callsign, settings, local statistics, mastery progress, and preferences in your browser. This information stays in that browser unless you clear site data. It is not a secure account or cloud backup.

Multiplayer data

Matches are peer-to-peer. The browser elected as host runs the match. Players in your room receive the gameplay state needed to play, including callsigns, teams, movement, actions, scores, team chat, and active vote-kick information. SPADEFALL does not operate a central match-history, report, ban, or chat database.

Room-wide public chat is disabled by default. Team chat is temporary and is not intentionally retained by SPADEFALL after a session. Other players can still record or capture what appears on their devices, so do not share private information in a callsign or message.

Services involved

The site is hosted on Cloudflare Pages. Cloudflare may process ordinary web-server data such as IP address, device or browser information, referring pages, and requests under its own privacy statement. PeerJS Cloud helps browsers find each other, and WebRTC connection services may process network metadata needed to establish a peer connection. A peer-to-peer connection can expose network information to participating services or peers as permitted by the browser and WebRTC.

SPADEFALL has no advertising tracker and does not build player or device profiles. It sends a small sample of anonymous operational diagnostics to its Cloudflare edge service: game version, graphics tier, coarse frame-budget results, connection or host-migration outcomes, match-abandonment time ranges, and non-readable crash fingerprints. These reports contain no callsign, peer or persistent identifier, chat, room code, precise position, complete URL, or raw error message. Source network addresses may be processed transiently by Cloudflare for delivery and abuse rate limiting, but SPADEFALL does not write them into its game-health dataset.

The production game also sends an anonymous summary of each human player's completed or abandoned round to the same service. It includes map and mode, active visible play time, weapon-use time, kills and deaths, deaths within three seconds of spawning, successful digging and building actions, objective contribution, and whether the round finished or the player left. Bot actions are excluded. Round summaries contain no name, persistent player or device identifier, chat, room code, or exact position. They are used for aggregate gameplay reports. A person playing several rounds contributes several summaries.

To estimate how many browsers actually play and return, the game separately creates a random analytics identifier when you enter a match. It is stored in this browser under tos.analytics-player and replaced after 90 days. Each newly entered round sends only that identifier and the counter version; the service records when it arrived. The identifier is not attached to round summaries, callsigns, accounts, chat, or precise locations, and is not derived from an IP address or browser fingerprint. Reports show aggregate browser counts, not individual identifiers or verified people. Different devices, clearing site data, and identifier replacement can count one person more than once; shared browsers can count several people together. If browser storage is unavailable, this counter is skipped.

Links to GitHub and Ko-fi take you to third-party sites with their own policies.

Your choices

You can disable gameplay summaries and the browser counter in the menu under display & accessibility → anonymous gameplay stats. The game also honors browser Do Not Track and Global Privacy Control signals for both. Disabling collection deletes the locally stored analytics identifier and stops new reports; it does not remove previously received records or aggregate counts.

You can reset locally stored progress and preferences by clearing site data for spadefall.io in your browser. You can leave any peer-hosted room at any time. Questions or privacy requests can be opened through the project’s GitHub issue tracker.

Terms of play

By playing SPADEFALL, you agree to use it lawfully and follow the community rules below. Do not modify clients, automate input, exploit bugs, disrupt connections, impersonate others, or interfere with another player’s ability to use the game.

SPADEFALL is provided as available, without a promise that a room, browser session, local record, or peer-hosted match will be uninterrupted or preserved. The elected host is authoritative for its room. Host migration and integrity checks reduce failures and cheating but cannot make an untrusted peer-hosted room equivalent to a centrally moderated server.

Local mastery and statistics have no cash value and may be reset or changed as the game develops. Game code and assets remain subject to the license and notices in the project repository. These terms may change when the game’s services or business model change.

Community rules

• Play fair. No cheats, patched clients, deliberate exploits, or network attacks.
• Play the objective. Do not sabotage teammates, trap spawns, or destroy the battlefield only to prevent others from playing.
• Keep callsigns and team chat free of slurs, threats, targeted harassment, and personal information.
• Use vote-kick for active cheating or serious disruption, not retaliation, skill, or ordinary disagreements.
• If a host is abusive or a room feels unsafe, leave it. A decentralized room cannot force its host to remove itself.

Callsign filtering and vote-kick are practical safeguards, not perfect moderation. Repeated misuse may lead to stronger safeguards as the game evolves.