Cookies & device-storage policy

Launch draft · 23 September 2026. Publisher identity, postal address, support/privacy contact and hosting/retention details must be completed and verified before commercial release. This preview is not a completed production notice.

The current SMASHBIKES web game does not set HTTP cookies or use advertising cookies, analytics cookies or tracking pixels. It uses browser storage to remember your rider name and bike choice, and caches game files for offline play. Browser storage can be covered by privacy rules even when it is not called a cookie.

Scope and operator

Last updated: 23 September 2026. This policy describes the official web game, including its installed web-app version. Publisher: [PUBLISHER LEGAL NAME], [POSTAL ADDRESS]. Privacy contact: [PRIVACY EMAIL], [PUBLIC CONTACT TELEPHONE]. Future native app packages must be checked separately before this notice is used for their store release.

What is stored

Rider name — dl_name (local storage)
A player-chosen nickname, used for your next session and sent to the game server when you play online. It is not a login or a unique identity. Remains until changed or cleared; the browser may also remove it.
Bike choice — smashbikes-bike (local storage)
Your selected visual bike type. Sent during online play so others see your choice. Remains until changed or cleared.
Connection settings — dl_server and dl_pub (session storage)
Existing server/invite overrides, written when the corresponding URL options are used. Normally last for the tab session; browser session restoration can extend this. A custom server has a separate operator. Do not enter personal information in URLs or use unknown server links.
Update marker — dl_reloaded (session storage)
Prevents repeated automatic reload attempts during version changes. Normally lasts for the tab session.
Offline game cache — exploline-* (Cache Storage and service worker)
Downloaded game files and pages for faster loading and offline play. This is separate from cookies and contains no analytics identifier. The service worker removes older game cache versions when an update activates. Current caches remain until replaced, evicted by the browser or cleared in site-data settings. Online room lists, game connections and analytics endpoints are not deliberately stored in this offline cache.
Legacy identifier — dl_uid
Earlier builds created this identifier. The current build removes it on game load and does not create or transmit it. The clear-preferences control also removes it if present.

Advertising and third parties

No advertising or analytics SDK is included in this build. The planned model permits static sponsorship plus reviewed Google or similar publisher advertising services. Static images delivered with game files have no advertiser tracking requests. Network advertising is different: an enabled service may use cookies, local storage, consent records, SDK storage and permitted identifiers for delivery, frequency control, measurement and fraud prevention. Even non-personalized ads may use these technologies.

Before network advertising is activated, an actual storage inventory must identify provider, key/cookie or identifier, purpose, lifetime, recipient and applicable consent requirement for the precise integration. We will not present speculative cookie names or durations as if they were already installed. Google's general explanation is at Google partner-site information. This is not a substitute for the game’s own inventory.

No ad script, SDK or non-essential advertising storage may run before its required legal and consent conditions are met. Required consent choices must be available again through the privacy menu; clearing only the rider name is not withdrawal of advertising consent or deletion of provider records. Such an advertising-choice interface is not implemented in the current build.

Choices and consent

There is no “accept advertising cookies” banner because no advertising-cookie service is active. This does not mean that all possible browser storage is automatically exempt from consent rules. Functional-storage purposes, persistence and any applicable consent exemption must be reviewed for the launch countries before commercial release. If a use requires consent, it must be prevented until valid consent is obtained, with an equally accessible refusal and withdrawal option. Children’s consent requirements must also be addressed. These policy words do not implement a consent system.

Any future optional analytics, ad tracking or other non-essential storage will require an updated policy and the necessary controls before activation. Clicking Play or accepting game terms will not be used as blanket consent to such processing.

Clear or block storage

Use Clear saved name & bike after closing other game tabs. This clears this device’s named game preferences and the current tab’s listed session keys. It does not delete server logs, close other tabs, unregister the service worker or remove cached game files. To remove all game storage, use your browser’s site-data controls for the game’s address; installed web apps may share storage with the browser. Other open tabs can save settings again.

You can block or clear storage in browser settings. The game may no longer remember your selections, and offline play may become unavailable if caches are blocked or removed. Removing storage on one device does not remove it from another.

Changes and questions

We will update this notice when storage behavior changes. Privacy and parental requests go to [PRIVACY EMAIL] or [PUBLIC CONTACT TELEPHONE]. The privacy policy explains data rights and hosting.