What stays in your browser
The game uses browser storage for your current shift, personal best, sound settings, phone layout, motion preference and cached weather. It also keeps a queue of results waiting to sync after a connection problem.
Your full save includes the state of the game, such as accepted jobs and progress at a stop. Clearing this site’s browser data can remove that save and its pending uploads. Another browser or device does not automatically receive the full saved shift.
What the online leaderboard stores
Starting a shift registers a run automatically. During play and when you finish, the game sends summary fields: a run identifier, mode, vehicle, game time, earnings, cost categories, completed and cancelled job counts, late jobs, distance, service rating, apps used and the run’s outcome. The server stores timestamps and ranking eligibility with those fields.
The online profile has a generated player identifier and public nickname. The leaderboard upload does not include full saves, customer names, delivery addresses, route coordinates, job notes, game seeds or delivery photos.
Live and ranked boards can show your nickname and summary results to other people who can access the game. Your own history includes additional nonqualifying shifts. On a public deployment, these leaderboard results are public. A private deployment limits access through its host’s access controls.
Your profile and browser cookie
A private browser cookie identifies the profile that owns your results and may edit its name. The cookie is configured for up to 180 days, uses HttpOnly and SameSite protections, and is marked Secure on HTTPS. The server stores a hashed version of its credential.
An independent deployment uses the guest browser cookie and does not require a login. A deployment behind an explicitly trusted sign-in gateway may also use a hash of a verified user identifier to establish ownership. It does not store your platform email or account name in the leaderboard profile. An existing verified browser credential keeps its profile when platform sign-in changes.
Clearing cookies can lose access to a guest profile. Saves and profile cookies belong to this web address; they do not automatically move to a different domain. A public nickname is not a password and cannot recover or claim another profile.
What you can change
Open Leaderboards → Edit name to update your public nickname. Your permanent short player code stays attached, and earlier results use the updated name. Choose a nickname without your real name, contact details or another person’s private information.
Browser settings can clear local saves and cookies. That does not delete results already stored online. The current game has no in-game deletion or export control for online profiles and results. Starting a new shift also does not erase earlier online results.
Automatic leaderboard syncing is part of play. Going offline inside an app stops its new job offers; it does not switch off leaderboard uploads.
Connections and abuse prevention
The site host handles page requests and storage. Map, route and weather features can also contact external services. Those connections expose ordinary connection information, such as an IP address, to the service receiving them. Their handling of that information is separate from the leaderboard.
The leaderboard uses request limits to reduce abuse. For request and new-profile limits, an IP address supplied by the trusted hosting platform can be hashed with the date into an expiring rate-limit record. That record is not attached to a public score. This is not a statement about what the hosting platform records in its own logs.
Delivery photos capture the rendered game scene. The delivery-photo feature does not connect to a device camera or a real delivery platform.
Before you share
A challenge link shares a game setup. Screenshots can show your public nickname, earnings and other visible game details, so review them before sending. Learn how saving and scoring work, or return to SHIFT.