This policy explains how Run With Zombies handles your data. We are designed to keep your location private: your route stays on your device, while spot discovery uses your current game location as described below.
Your route and generated zombie replay positions are processed in your browser only and are never uploaded to our servers. Your current game coordinates are sent for spot discovery and visits, including mock play. Location access drives the game — your real-world position decides where you are on the map.
During play, spot discovery sends the player coordinates drawn on the map to our server, including when logged out or using mock movement without GPS. If no spot exists within 1 km, the server queries OpenStreetMap/Overpass for nearby public places. Guest visits are saved as signed receipts in this browser for up to 24 hours; after the game, the existing login button saves your score, badges and visited spots together. Choosing not to log in leaves ownership unchanged. Coordinates are processed but not retained as check-ins by this endpoint. Spot locations, the current owner’s display name, and ownership time are public. A later visit takes priority over an earlier deferred claim.
Recovery Spot placement may query OpenStreetMap/Overpass with nearby coordinates to find walkable roads or paths. These queries are made to locate a safe target on the map and do not store your location.
Finished runs are saved in this browser's local storage so you can review and visualize them on this device. If you clear browser data, switch devices, or use another browser, those local runs may not be available.
If you log in and choose to save scores, we transmit non-location score metadata (for example score, survival time, and horde settings) to power the public leaderboard. Your GPS location and route are never part of score submissions.
Guest badge progress is stored locally in this browser using IndexedDB. Signing in submits pending session summaries so eligible badges can be registered to your account. These summaries contain session identifiers, dates, durations, distances, outcomes, difficulty settings, and gameplay achievement counters. We store badge progress, your badge calendar timezone, earned badges, and award dates. GPS coordinates, routes, and zombie replay positions are not included in badge submissions.
Selected earned badges are displayed publicly on the leaderboard. Detailed progress and activity calendars are private to your account. Account badge records are removed when the account is deleted. Guest records remain in browser storage until it is cleared. Failed uploads remain queued for retry; a local badge is not saved to your account until registration is confirmed.
When you are logged in, unused freeze and gun charges are saved privately to your account across games and devices, with no expiry until used. We store weapon balances and pickup and use records linked to your account, without GPS coordinates or routes. Unused guest charges transfer to your account when you sign in before starting another game.
This browser caches account weapon balances and pending changes in local storage. Offline pickups and uses are queued for sync when your connection returns. Clearing browser data before sync can remove pending changes. Signing out hides your saved weapons without deleting account records; signing back in restores them. Weapon account records are removed when the account is deleted.
We use anonymous analytics (Google Analytics) to understand how the game is used. No personally identifiable information is collected.
The homepage uses a locally hosted video thumbnail. The embedded YouTube player loads only after you press play, using YouTube’s privacy-enhanced embed domain. Playing the video connects your browser to YouTube. Links to full missions open on YouTube.
You must be at least 13 years old to use this service.
Questions about this policy? Join our Discord channel.
Last updated: October 6, 2026