Plain-language policy

Privacy

Last updated July 31, 2026.

Every Silverweb Games title works without an account. Cloudflare hosts and protects the site and necessarily processes ordinary request information. Cloudflare Web Analytics is a separately configured traffic/performance service, but its automatic browser beacon is currently disabled. If enabled after privacy review, the beacon would report to Cloudflare's same-origin /cdn-cgi/rum endpoint and would not be joined to an account. Discovery and game pages load Google AdSense. The site requests nonpersonalized delivery and applies the under-age treatment marker. Root, Arcade, Casino, and individual game pages contain ads; legal, safety, profile, account, contact, analytics, guide, and error pages do not. No page carries more than two ad units, and every unit sits below the primary content. Google receives the normal network, device, page, publisher, and ad-slot information needed to return an ad. Silverweb Games does not send favorites, scores, practice balances, exact game actions, support messages, or account records to AdSense.

A first-party analytics collector records a small, fixed set of page views and real game-state actions. It uses random pseudonymous visitor and rolling 30-minute session identifiers in Secure, HttpOnly first-party cookies shared across Silver Web Games subdomains. Events can include the page path, game, coarse device and country, referrer hostname, release, and sanitized UTM attribution. It does not store arbitrary query strings, exact gameplay inputs, raw IP addresses, full user-agent strings, or browser fingerprints. The visitor cookie can renew for up to 180 days; the rolling session expires after 30 inactive minutes.

Games use your browser's local storage only to remember high scores, Table Games personal bests and recent play, and non-sensitive control, audio, and accessibility preferences. Casino simulations also store one versioned, device-only practice-credit balance and optional Blackjack learning totals. Practice credits are never synchronized to an account or server. Account credentials and reusable bearer tokens are never stored there. Retired racing games may have left best times, compact ghosts, and settings in older browsers; the clear-data control below removes those legacy keys too. Device-only game information stays on your device and can be removed by clearing site data.

Casino analytics uses only the same universal route view, committed-round start, and resolved-round completion events as the rest of the catalog, with coarse result and duration buckets. It does not collect exact wagers, cards, dice, roulette pockets, slot symbols or stops, balances, card counts, true counts, Table Heat, or refill amounts. Casino game logic does not send this information to account, payment, advertising, or leaderboard APIs. The surrounding page may load the labeled AdSense placements described above.

Silverline Racing was retired from the public catalog on July 16, 2026. Historical account records can include the account link, public display name, issued race sessions, completion proofs and anomaly flags, best times, achievements, cosmetic ownership, and a compatibility ledger linked to the canonical account ledger. Those retained records and the narrow legacy service boundary remain available only for operational integrity, account export, confirmed deletion, and audit reconciliation; the website no longer offers new racing play. Race proofs contain course and timing metadata, checkpoint splits, assists, reset and penalty counts, a compact input digest, and build versions—not raw steering history. Account racing records remain until the associated account is deleted; expired guest sessions remain eligible for routine cleanup.

Table Games can optionally request a server game session lasting up to two hours. The server stores an opaque guest or account key, game, mode and exact format, difficulty, assist category, server seed, rule version, challenge date, proof limits, issue and expiry times, a server-issued completion ID, and one accepted completion. Tournament play also stores an opaque run ID, current stage, exact rules format, and assist category so every computer-opponent stage can be verified and advanced without changing categories mid-run; only the final-stage win can create progression, leaderboard, achievement, or point effects. A completion record contains its random ID, score, outcome, duration, action count and digest, compact game statistics, and version fields. The Worker may inspect a bounded action list while checking a proof. Every game is deterministically replayed from its server seed and ordered actions; those action lists are not stored in the completion table. Signed-in records can also create a public display-name score, achievement, cosmetic state, and an immutable canonical point-ledger entry through an authenticated service-to-service bridge. Guests receive a random opaque swg_bar_guest cookie and receive no named score or points. Signed-in play uses a separate host-only, HttpOnly swg_bar_player cookie scoped to the Table Games API for at most 15 minutes; the API confirms its referenced account session on each authenticated request, and account credentials are not exposed to game JavaScript.

Historical account-linked racing records and current Table Games records are included in account export and are removed in dependency order during confirmed account deletion. Clearing browser data removes guest and short-lived game cookies, but it does not itself delete an account or an already accepted server completion. Account, points, named leaderboard, and game-bridge features fail closed when their feature flags, service secrets, or dedicated database are unavailable; anonymous gameplay remains available.

The support form stores the selected category, reply email, message, ticket status, response target, and an audited history of authorized staff actions. It is used only to answer and operate the request. Resolved tickets are removed after about 90 days and every ticket is removed after about 180 days. Do not send passwords, exact locations, or school details.

Account registration records the version of the Terms and Privacy Notice accepted and a confirmation that the player meets the published 13+ rule. It does not request a full birth date. Optional shared profiles are unguessable-link-only and are excluded from search.

Validated raw analytics events are retained for approximately 30 days; sanitized daily counts may be kept long-term. A minimal first/last-seen visitor registry expires after about 180 days without activity. Historical racing and current Table Games point-ledger entries are retained as audit records for an active account. Data is not sold. This first-party analytics and account data is not sent to AdSense by the Silverweb Games application.

A signed-in first-party analytics opt-out is account-wide: in production, saving it sets a preference cookie shared by trusted Silver Web Games origins, and both Silver Web Games browser clients and the D1 collector enforce it. The ?swg_analytics=off query and local-storage value swg_analytics_opt_out=1 affect only the current origin, so they must be repeated on other hostnames when the account setting is not used. Either control stops the affected first-party client and clears its retry and attribution data. The separate Cloudflare Web Analytics beacon is currently disabled and cannot be re-enabled until an edge rule binds it to the shared opt-out/GPC. Clearing site data removes local preferences and pseudonymous identifiers but does not stop Cloudflare's necessary hosting and security processing.