Your game, your location.
Updated October 26, 2026. This page describes Scatter's current private-group implementation. Ask your game host who operates the deployment before sharing location.
Your device profile
You choose a username and avatar without email or password. A device-bound credential lets the backend authorize your profile. Native apps keep it in secure device storage; the web app keeps it in this browser's local storage. Clearing app or website data can permanently remove profile access.
Game and location data
Scatter stores game rules, roster, roles, messages, tag events, results and profile preferences in its Convex backend. During consented active play it receives coordinates, accuracy and timestamps. Teammates, hunters and spectators receive only the views permitted by the game rules. Full personal trails are available to their owner.
Host setup can use a device fix to select a game-zone center. That approved center becomes part of the room's shared rules. Searching places sends the search text to the configured search provider; map providers receive viewport requests and ordinary network information.
Retention and your controls
Live positions clear when a round ends. Room, chat and recorded audio state is scheduled for cleanup after seven days. Personal results and trails remain until you delete the round or profile. Reports are retained for up to 180 days. Profile settings provide export and deletion controls. Device/browser settings let you revoke location or notification permissions.
Services and access
Convex processes profile, game and location data. OpenFreeMap supplies maps based on OpenStreetMap/OpenMapTiles data. The website host handles normal web requests. Optional notification services process delivery details when configured. No advertising or analytics SDK is included in the game.
The deployment operator can access the underlying database. Private-room authorization is not a substitute for choosing a trusted host. Cached app assets can be stored on your device; private messages, audio and GPS responses should not be stored in the service-worker cache.
Questions
Contact your game host for deployment ownership or data questions. Use Support for troubleshooting details. Do not send passwords, device credentials or precise location in a public support report.