Privacy

Privacy policy.

What MAP.RACING collects in your browser and in the iOS and Android apps, why, and for how long. Only what the game really does.

Updated: 20 November 2026

In short.

  • No account, no email address, no real name.
  • No ads, no advertising ID, no tracking. The game, the app and these pages set no cookies.
  • Your location is used only when you tap “My location”. The game then asks only for an approximate location, rounds it on your device to about a kilometre, and it stays on your device. On beta.map.racing the home page picks three places from the broad location of your connection; we do not keep it.
  • Anonymous performance data is on by default; you or a parent can switch it off.

This policy covers the game (in the browser and in the iOS and Android apps) and this website. Businesses that become a sponsor have a separate privacy notice (in Dutch): privacy notice for sponsors.

Who is responsible.

Responsible for the data of MAP.RACING (the controller) is webRidge (sole proprietorship), Kreeftenstraat 36, 4691 KR Tholen, the Netherlands. Chamber of Commerce (KvK) 56845367. Email: support@webridge.nl.

What the game collects.

Do I need an account or email address?

No. You play without an account, without an email address and without a real name. In the game you drive under a made-up name.

What data does the game collect?

When you press Drive, we count that a game is being played. For that we keep one row per session in our database: a random session number, the day, the build number, the region, phone or desktop, the start time and the play time (updated every minute). The session number is not tied to an account or a name, but it is stored. We delete those rows after 400 days. To counter abuse we also count how many sessions start per day from one internet connection. For that we do not store your IP address itself, but a secret, hashed shorthand of it (an HMAC of the IP address, for IPv6 of the whole /64 block). We keep that counter for a few days. No cookie and no user agent. Browsers with Do Not Track are not counted. Unexpected errors go to our server log in a fixed format: source file with line number, build, region, vehicle and play time, without free text, link or name. For the sentence on the home page, beta uses only a broad location from the request to choose three Dutch places; we do not store that location or log an IP address or city.

Does the game send performance data?

The game (on the website and in the app) measures how smoothly it runs, so we can get it running well on phones. Every 30 seconds of play one block is sent, at most 20 per session. It holds: a random session number that only stays in memory, the platform, the model family of your device (for example iPhone15,2), in the app the major version of the operating system, a rough screen class, the build, how often and how fast frames are drawn, simulation and render time, number of draw calls and triangles, heat and battery saver state, the chosen quality level, the region, whether you are roaming, racing or being chased, and memory use. It holds no name, account, device or advertising ID, IP address, location or free text. We use the IP address only briefly in the server’s memory to apply a limit. With each block we keep 4 bits of a daily changing, hashed shorthand of it, so we can see that data does not come from one connection (16 possible values, so not an ID). We keep the blocks for 90 days. Sharing is on by default for all ages, players under 13 included. You switch it off in Settings under “Prestatiegegevens delen” (share performance data), and a parent can switch it off in the parental settings (“Performance data off”, behind the PIN when one is set). With the same switch, anonymous play data is sent too: per 500 m square we count driving time, distance, standing still, stuck cars and error counts, without an ID, IP address or route. If you start at “Mijn locatie” (my location) or “Rij naar je huis” (drive to your home), the game counts nothing within 2 km of that point. We only show a square once at least 5 different sessions were there, and we keep the daily totals for 180 days.

Does this website use cookies or tracking?

No. The game, the app and these pages set no cookies and use no analytics or ad networks. The fonts of these pages are on our own server. More in the privacy policy.

What happens when driving together?

Your age setting stays on your device. Others see your made-up name and the quick phrases you pick. We keep a report from a player for 90 days to counter abuse.

Can I have my data deleted?

We do not know you by name and have no account or email address of yours. The session numbers and performance data cannot be tied to you personally, which also means we cannot look up which rows are yours. They disappear on their own: session rows after 400 days, performance data after 90 days, play data after 180 days (then only totals per square), player reports after 90 days, weekly leaderboards 2 years after the week ends. Companies that sponsor can ask about their data via the sponsor page. This is a summary; everything is in the privacy policy.

Performance data and play data.

Play data. With the same switch ("Prestatiegegevens delen", share performance data) the game also sends anonymous play data, so we can see where the world needs more detail and where players get stuck. The game divides the map into squares of 500 by 500 metres and counts, per square, how long people drive there, how many kilometres, how long someone stands still or drives slowly, and whether a drive starts there; with the kind of vehicle (car, bike, boat, ...) and what you are doing (free roam, race, chase, mission). If the car gets stuck, sinks into the ground or the water, or the game puts it back on the road, that is sent with the square, the surface, the kind of road and a rough frame rate. We also count errors: an error code of the game (with no data in it), a file that did not load (the path only), stutters and memory warnings. No name, account, device ID, session number, IP address, exact position or route is sent, and nothing with a time finer than the day. If you start at "Mijn locatie" (my location) or "Rij naar je huis" (drive to your home), the game counts nothing within 2 kilometres of that point. In our overview a square only shows once at least 5 different play sessions were there. We use the IP address only briefly in the server's memory against abuse (a key that changes every hour). We keep the daily totals for 180 days; after that we keep only summed totals per square without a date. You switch it off in Settings ("Prestatiegegevens delen"), a parent in the parental settings.

Start problems and stability. With the same switch, if the game cannot start, it also sends why (for example no suitable graphics card or a download that got stuck), the kind of browser with its major version, the operating system and the make of the graphics card. It also counts per day, without an ID, how often the game gets stuck, stutters or hits an error and how far starting gets (opened, ready, driving, 5 minutes). No name, account, device ID, session number, IP address, error message or browser string (user agent) is sent. We keep this for 90 days.

Loading time on the website. With the same switch the website sends, once per start after loading, how long each loading step took (for example preparing the graphics), the longest time the page stood still, and whether loading succeeded. It comes with the same coarse details as start problems: the kind of browser with its major version, the operating system, the make of the graphics card and whether it is the processor's built-in graphics or a separate card (not the model), with the chosen graphics quality and the region. No name, account, device ID, session number, IP address or error message is sent; the server only notes the minute it arrived. We keep this for 90 days.

Pick your spot and My location.

You pick where you start on a map of the Netherlands. The map loads map tiles (streets, buildings and names from OpenStreetMap) from our server for the area you look at, like any online map; we do not keep track of who loads which tiles. On the website a spot you tap on the map goes into the page address, so a reload continues there.

If you tap “My location”, the game asks for your location: once, only an approximate location (not a precise one), and only while you use the game (never in the background). Your phone or browser asks for permission first. The Android app asks permission for your approximate location only; the iPhone app asks for an accuracy of one kilometre. On your device the location is immediately rounded to about a kilometre; the map goes to that area and puts a pin on the nearest road, which you can move yourself.

We do not store that location, not even on your device, and we do not send it to our server: not in a request, not in the page address, not in “Continue” and not in the play data. The same goes for a spot you then tap on the map within 2 kilometres of that location. Without permission you simply pick your spot on the map yourself.

Broad location on the home page.

On beta.map.racing, where we try out new versions of the website first, the home page picks three Dutch places for its opening sentence. For that the server uses the broad location (country, region, city) that our hosting provider derives from your connection. This happens only at the moment of the request: we do not store that location and do not log an IP address or city. Nothing asks for permission for this and nothing is taken from your device.

Weekly leaderboards.

If you set a time or score in a minigame, it goes to the weekly leaderboard: a random player number that your device makes and keeps itself, the region, the minigame and your time or score. Your nickname is not sent to this leaderboard; the list shows a made-up driver name.

There is also a sponsor leaderboard per minigame. An earlier version of the game in the browser sent your time or score there after a minigame, together with the name of your driver (your nickname, at most 24 characters, filtered for inappropriate words) and a random player number. The server keeps that nickname, a hashed shorthand of the player number, the region, the minigame, the week and your time or score. The current game, in the browser and in the apps, no longer sends anything to this leaderboard; stored rows are deleted 2 years after the week ends.

The server knows four other weekly lists, with the same player number and a made-up driver name: the weekly challenge per municipality (your time), the speed cameras (your speed), Dé Lijst (your place on the list) and the drive of the number one of a weekly challenge (a recording of the drive in the game of at most about 90 kB: positions, heading and steering of the car in the game world, not your real location). The current version of the game sends only the minigame leaderboard.

Against abuse we count how many new player numbers come from one connection per week, with a hashed shorthand of the IP address, not the address itself. We keep that counter for up to 14 days. We keep the weekly lists themselves for 2 years after the week ends; after that they are deleted automatically. A recording of a drive is also kept for 2 years if it is among the top ten of its list that week, otherwise for 6 months after the week ends.

Driving together.

When you drive together with a group, our server passes your made-up name, your car and where your car is in the game to the others in the group. The server does not keep it; when the group ends, it is gone. Only a report about a player is kept, for 90 days.

In-game feedback.

With “Wat kan er beter?” (what could be better?) you pick a topic and, if you like, write a short text (at most 280 characters). Only the kind of device (iOS, Android or web), the version, the quality setting, the screen and the in-game region go with it: no account, no device ID, no IP address. We remove email addresses, phone numbers, websites and @names from the text, and we do not keep a text with inappropriate words. We keep feedback for 1 year.

Drive to your house.

When you type your postcode and house number, the game looks them up in an address list that is entirely on your device. Your address never reaches us: not while searching, not in the statistics and not in a shared link. If you choose “Remember my address”, it stays only on your device; “Forget my address” removes it.

Shared links and challenges.

When you share a place, a clip or a challenge, we keep only the place in the game (with the place name) or the recording of your drive, under a short code. No name, no account, no device ID. Near your saved house we never share the exact place but the centre of your town, and we do not share a drive past your house. Your device makes the clip itself; it does not reach us. We keep place links for 1 year and challenges for 6 months.

We count per day how often a shared link is opened and how often “Drive to your house”, a clip or a challenge is used: only the number and the kind of device, without an ID or a place. This is off when you switch off the performance data.

Excluding an address.

Do you want an address to be out of the smash effects and not choosable as a start? Ask at map.racing/en/address-opt-out. We keep the request only to handle it, never publish it and delete it afterwards (after 1 year at the latest).

The iOS and Android apps.

The apps only use the internet, vibration and (after your tap) your approximate location. No camera, no microphone, no contacts, no photos. There is no advertising, analytics or crash-reporting package from other companies in them. What we know about crashes and errors comes from the performance and play data above: an error code of the game with no data in it, and how often it happens.

App Store. The App Store privacy details list: Diagnostics (Crash Data, Performance Data and Other Diagnostic Data), Usage Data (Product Interaction: that a game is played, for how long, and the daily counters above), Gameplay Content (your times, scores and drive recordings on the leaderboards and in shared challenges) and Identifiers (User ID: the random player number of the weekly leaderboards). None of this data is linked to you, and none of it is used to track you.

Google Play. The Google Play data safety section lists: crash logs, diagnostics, app interactions, other user-generated content (the text you write yourself in “Wat kan er beter?”) and device or other IDs (the random player number of the weekly leaderboards, not an ID of your device). This data is collected, not shared with other parties, and encrypted in transit.

Windows. The Windows version checks for a new version when it starts. It sends no ID, no player number and no details about your computer: it only fetches the public version file from map.racing.

Your progress, garage, settings and parental settings are on your device. A transfer code is made by the game on your device; it is not sent to us.

Other parties.

The website, the game and the database run on Cloudflare. The game in the browser loads its fonts from Google Fonts, so Google sees your IP address. This site itself does not. We fetch the in-game weather from Open-Meteo for the centre of the region; nothing about you is sent. We do not sell data and do not share it with advertisers.

Why we may do this (legal basis).

Legitimate interest (running, securing and improving the game): the session rows and abuse counters, the error reports, the performance data (which you or a parent can switch off), the feedback you send yourself, the weekly leaderboards, reports about players, the broad location on the home page of beta.map.racing, the fonts and the weather in the game.

Consent: your approximate location for “My location” (you tap it and your phone or browser asks for permission; you can withdraw it at any time in the settings of your device or browser).

Performing what you ask for (contract): driving together with your group.

Data outside the EU.

Cloudflare (hosting and database) and Google (fonts in the game) are US companies, so data may also be processed outside the European Union. Such transfers rely on the safeguards the GDPR provides for them, such as the EU-US Data Privacy Framework or the standard contractual clauses of the European Commission.

Your rights.

You have the right to ask which data we hold about you, to have it corrected or deleted, and to object to what we do on the basis of legitimate interest. Because we do not know who you are, we usually cannot see which rows are yours; they disappear on their own after the periods above. What is on your device you can delete yourself: remove the app, or clear the site data of map.racing in your browser. If you disagree with how we handle data, get in touch. You can also complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

Email questions or requests about your data to support@webridge.nl.

How long we keep what.

Session row of a game
400 days
Abuse counters (hashed IP)
up to 14 days
Performance data
90 days
Play data
180 days, then only totals per square
Report about a player
90 days
In-game feedback
1 year
Weekly leaderboards
2 years after the week ends
Recording of a drive (top ten of a weekly list)
2 years after the week ends
Recording of a drive (others)
6 months after the week ends
Shared place link
1 year
Shared challenge (recording of a drive)
6 months
Daily counters (link opened, clip shared …)
2 years
Request to exclude an address
until handled, 1 year at most
Your address for “Drive to your house”
not with us (only on your device)
Your location for “My location”
not kept
Broad location on the home page (beta.map.racing)
not kept

Questions.

Questions or requests about privacy: see the contact page. If anything changes in what the game collects, we update this page first.