A small game with a small data footprint.

URBANTRACE uses browser local storage to remember language and puzzle preferences, tutorial status, guesses, practice and daily statistics, optional map calibration settings, and whether this device has visited on a previous day.

This information is stored on the device you use. You can remove it by clearing this site's browser data. If you do not sign in, these local records are not associated with an account.

If you choose Sign in with Google, Google provides URBANTRACE with a stable account identifier, your email address and display name. The stable identifier—not your email address—is used to link your URBANTRACE account. URBANTRACE does not request access to your Google Drive, contacts, mail, calendar or other Google services.

On the first sign-in, statistics already stored on that device can become the account's starting record. After that, completed-round identifiers, game mode, daily or practice mode, win or miss, guess count and streak data are stored so the same record can be used on other signed-in devices. For Daily games, recent guessed-city identifiers and the current day's collection-tour progress are also synchronized so an unfinished or completed puzzle can be resumed in another browser or installed web app. These recent Daily snapshots are retained for up to 45 days. Session cookies are used to keep you signed in and are not used for advertising. A player session may remain valid for up to one year and is renewed when an active signed-in player returns, unless you sign out, delete the account, or clear the browser cookie.

You can sign out without removing local browser records. The Delete Account control permanently removes the Google-linked URBANTRACE account, its server sessions and synchronized records; local records on the current device remain until you clear them in your browser.

To draw the puzzle, your browser requests map styles and tiles from OpenFreeMap and related map infrastructure. Those providers may receive standard request information such as an IP address, browser details and request time under their own policies.

The site's hosting provider may also process ordinary technical logs needed to deliver and protect the service.

URBANTRACE records first-party aggregate counters for page views, first guesses, completed games, wins, Reverse round outcomes and five-map scores, map loading success or failure, game mode, interface language, and broad viewport category. A failed map load is also grouped into a coarse stage such as timeout, style loading, renderer initialization, or runtime. Raw error text and failed resource URLs are not stored. Successful result-share actions are also counted. These counters do not include a player identifier, IP address, exact location, email address, or the cities you guessed.

For acquisition measurement, campaign links may include normalized UTM source, medium, campaign, and content labels. When those labels are absent, URBANTRACE records only a coarse category such as direct, search, social, or referral. Full referring URLs are not stored. Attribution remains in session storage for the current browser tab so aggregate visits, starts, and completions can be compared without creating a user profile.

Friend-challenge links also record aggregate counts for viewing the challenge page, accepting it, starting and completing the game, and sharing again. Map failures may be compared by broad device category—mobile, tablet, or desktop—to identify compatibility problems. These counters do not store a device identifier, raw browser error, or individual browsing history.

Aggregate interactions with the optional Add to Home Screen control may also be counted, including opening iOS instructions and accepting or dismissing a browser installation prompt. A signed-in test account explicitly configured by the operator can be discarded before these counters are updated. The account identifier and email address are not written to the analytics table.

URBANTRACE currently does not include third-party analytics or advertising code, use advertising cookies, or sell personal information. If advertising or third-party analytics is introduced, this policy will be updated and appropriate notices and consent controls will be added where required.

The Share Result button creates a text summary on your device. It uses your browser's sharing or clipboard feature and does not upload your result to an URBANTRACE account.

When you choose to submit a map report, URBANTRACE stores the city, puzzle collection, issue category, map center and zoom, result summary, interface language, and any note you write. It does not attach your name, email address, IP address, or full game history to the report.

When you send general feedback, URBANTRACE stores the category and message you submit, along with the current game mode, daily or practice mode, interface language, broad viewport category, and page path. It does not attach your name, email address, account, or precise location.

This page may change as the game gains new features. The date above will be updated when a material change is made.