Shared site policy
Privacy policy
Last updated: September 17, 2026
About this site
This site hosts Snap Dragon and may host other small browser projects. Unless a project clearly says otherwise, the practices below apply across the site. The policy will be updated before a project begins collecting information not described here.
Information processed to provide and protect the site
Like any web service, the server and its delivery provider receive ordinary connection information such as IP addresses, request routes, timestamps, and browser headers. This information is used to deliver pages, enforce rate limits, diagnose failures, and prevent abuse—not for advertising or cross-site tracking.
Suspicious or abusive requests may create security records containing a keyed one-way hash of the IP address, a timestamp, event type, sanitized request route, and response status. Raw IP addresses are not written to these application security records. Automatic bans normally last one hour, and security event logs are normally retained for 30 days.
Snap Dragon gameplay
Snap Dragon does not require a player account. While you play, the server temporarily processes the player name you enter, selected deck and card identifiers, room information, game actions, match state, a random browser-session identifier, and an IP-address-derived connection hash. This is used to run and reconnect matches, prevent duplicate rooms, count active players, enforce rate limits, and protect the service.
Match state is held in server memory rather than retained as match history. Finished or abandoned rooms are normally removed within one hour; other inactive rooms are normally removed within twelve hours. A server restart also clears this temporary state.
A random presence identifier is held in memory for about 45 seconds so one active browser is counted once. The server retains only aggregate active-player samples in five-minute time buckets and daily peak counts for up to 365 days. These statistics do not contain player names, browser identifiers, decks, game actions, or match results.
Optional progress and deck cookies
The age screen offers two optional choices. Basic site access, multiplayer matches, computer matches, and campaign play remain available when both are off. The site does not use advertising or analytics cookies.
After you confirm that you are at least 13, the site remembers that confirmation in first-party local browser storage for up to one year so the age screen is not shown on every visit. The record contains only a version and expiration time, not your birth date or exact age. Clearing this site's browser data or using private browsing may cause the age screen to appear again.
If you allow campaign progress, Snap Dragon uses a first-party, HttpOnly cookie containing a random browser identifier. The server hashes that identifier and stores only the campaign battle numbers completed by that browser. The cookie may remain for up to one year. If you do not allow it, campaign battles remain playable but completed battles are not saved after the current game.
If you allow deck storage, an active-deck cookie stores the selected deck for the current browser session. Player Decks uses a separate random, HttpOnly browser-library cookie that may remain for up to one year. The server stores the corresponding deck names and card lists under a hashed identifier until they are deleted or removed during storage maintenance. If you turn deck storage off, the active-deck cookie is cleared and Player Decks is unavailable.
Your two choices are remembered in first-party local browser storage so they can be applied on later visits. That preference record is used only to honor your choices and is not sent as a browser identifier. You can revisit Cookie choices from the Snap Dragon menu.
If you share a deck, its name, card list, sharing time, and any optional username you provide are stored and displayed publicly so other players can view and use it. Shared decks may remain until the server operator removes them.
Battle Chess
Battle Chess runs its training matches in your browser. It stores the training rating and sound preference locally in your browser so they remain available on later visits. Those preferences are not sent to this server. Remote multiplayer is currently disabled, so the site does not create online Battle Chess rooms or transmit match commands to a multiplayer service.
Planet Station
Planet Station processes simulation commands and the current station state in temporary server memory. The simulation state is shared by visitors to the hosted station and is cleared when its service restarts. The game stores manual saves, automatic recovery saves, display theme, text size, and alarm preference locally in your browser. Local saves are sent back to Planet Station only when you choose to load or restore them.
Planet Station 2 developer preview
Planet Station 2 is an openly accessible Stage 2 developer preview. It stores the callsign you enter, a random session credential, your console assignment, shared recovery priorities, crew signals, station state, and recent event history in its PostgreSQL database so the shared station and testing identity can survive reconnects and service restarts. Callsigns are testing identities, not verified accounts, and the current preview has no login or access gate.
Everyone using the preview joins the same shared station and can see its crew callsigns, priorities, signals, and event history. Do not enter sensitive or private information as a callsign or into shared controls. A random session credential is kept in the browser tab session and sent back only to authenticate that testing identity.
Particle Evolution
Particle Evolution runs its simulation entirely in your browser. The server delivers static game files and does not receive simulation settings or state. The current release uses no accounts, cookies, analytics, local database, or persistent browser or server storage.
Evolution Sim 2
Evolution Sim 2 is an openly accessible, shared persistent simulation. The server stores the generated world identifier and seed, terrain version, simulation tick and tuning values, organism bodies, energy, damage, movement, brain programs, and versioned checkpoints so the same world can survive service restarts. This generated gameplay data is not linked to a visitor account.
Visitors can view the shared world and use its run, pause, step, speed, and brain-editing controls. The hosted simulation does not expose the world-reset control. It uses no accounts, advertising, analytics, or application cookies, and does not store browser data. The site's general connection-processing practices above still apply.
Sub Game
Sub Game processes the callsign you enter, a four-character room code, a random player identifier, station assignments, mission commands, crew status, and shared expedition state in temporary server memory so connected players can operate the same submarine. The browser keeps the current room and player identifier in session storage and the selected console color in local storage.
Sub Game has no accounts or durable database. Destroyed expeditions close immediately, inactive rooms without connected event streams normally expire after twelve hours, and a service restart clears all rooms.
Batball
Batball stores your club name, generated players and statistics, lineup, defensive assignments, colors, scouting offers, currency and campaign results on your device. It saves local match checkpoints every five seconds while play is active and when you select Save. Checkpoints contain rosters, positions, scores, stamina, orders, already completed random outcomes and recent play events. Future random rolls are not stored. Restoring a local match starts it paused.
The Godot browser game stores these files and preceding recovery copies in first-party browser storage (IndexedDB). A desktop build uses its local Batball application-data folder. Club and match imports and exports are processed on your device. The Godot cutover clears the retired game's browser saves and resets earlier preview profiles once. A local version marker prevents resetting new progress on later visits. Local clubs and matches are not uploaded automatically. Records remain until replaced, reset or removed through your device or browser's storage controls. Browser storage can also be evicted by the browser.
Creating or joining an online room uploads the selected club name and generated playing roster. The other manager and anyone who knows the room code can view those teams, players, match events and results. Online exhibitions are unranked and do not award local currency. A private reconnect credential is kept in device storage, including a recovery copy, and sent only to this site's game service to authorize your team controls. It is never placed in a link. The server stores its hash, not the original credential. Losing the credential loses access to that manager seat.
The online service retains room rosters, credential hashes, command receipts and current match state on disk. Active rooms expire after 24 hours without authenticated activity. Matches continue when browsers disconnect, following the managers' current instructions. Autonomous state is checkpointed every five seconds, accepted orders are saved before acknowledgement, and shutdown saves progress. Downtime pauses match clocks; an unexpected interruption can lose progress since the last checkpoint.
Private recovery and migration copies can retain previous room information, including expired rooms, after it leaves the active service. Preceding data generations and migration snapshots are retained for rollback until separately removed during operator maintenance; there is no automatic deletion schedule for these copies. Server-side removal and retention maintenance must include them. They are not publicly accessible. Reset profile removes current device saves and their recovery copies; it does not delete shared server records.
The shared tournament stores its generated player catalog, teams, schedules, active games, standings and career totals. Completed tournament standings are public and retained without automatic deletion. Tournaments run without viewers and restart after completion. Opening Batball's home screen or tournament view reads public match snapshots and standings without uploading your club or credential. Spectators cannot direct play or change its speed.
Rate-limit counters remain in server memory for up to one minute and are not written to Batball application logs. Batball adds no verified user accounts, chat, analytics or advertising trackers. The site's general connection-processing practices also apply.
Dinosaur Colony private playtest
Dinosaur Colony is a downloadable Windows game. The playtest password unlocks downloads and online lobbies. The service stores a salted password hash. Successful sign-in creates a random, signed access token valid for 30 days: the website keeps it in a secure first-party cookie scoped to this game, and the Windows launcher protects its local copy with your Windows account. The launcher checks for updates when opened.
The relay temporarily processes lobby names, room codes, player counts, connection addresses, and gameplay packets to connect players to the hosting PC. Lobby listings are visible to signed-in playtesters. Lobby state is kept in memory and removed when the host leaves or the relay restarts. The host processes player names and shared game state; settings and installed game versions stay on your PC. This playtest has no advertising or analytics tracking.
Feedback and external services
Issue and suggestion reports store the report type, title, details, submission time, and server type. The report itself does not store a player name, browser identifier, IP address, or user-agent string. Reports may remain until reviewed or deleted.
The public site is delivered through Cloudflare, which processes ordinary connection information under its own policies. Snap Dragon may load fonts from Google Fonts. If you open its tutorial video, the Rules page loads it from YouTube’s privacy-enhanced youtube-nocookie.com service.
Your choices and contact
This site does not sell personal information and does not use its cookies or server records for advertising, cross-site tracking, or individual gameplay analytics. By using the site, you represent that you are at least 13 years old or have a guardian’s consent.
To ask a privacy question or request review or removal of a stored submission or shared deck, email [email protected].