As of November 2026. This policy covers real-world-games.com, the games on real-world-games.com (web app) and our apps for iOS and Android.
1. Controller
Real World Games GbR
Rosa-Kempf-Str. 19
81248 München
Germany
Email: hello@real-world-games.com. We are not required to appoint a data protection officer; write to us directly with any question.
2. Visiting the website
When you open a page, our hosting provider Cloudflare processes the technically necessary data (IP address, time, page, browser) to deliver the page and protect it from attacks. The legal basis is our legitimate interest in running the site securely (Art. 6 (1) (f) GDPR). Cloudflare keeps these logs only as long as delivery and security require. We serve fonts and scripts ourselves; visiting the website loads nothing from third parties. We set no cookies for analytics or advertising.
Reach and error analysis with PostHog. To understand how the website and the games are used and to find errors, we use PostHog (PostHog Inc., data processed in the EU, Frankfurt) without cookies and without storing anything on your device. The data passes through our own server. PostHog derives a daily-rotating, irreversible hash from your IP address and browser details to count visits, and a rough country and city; the IP address itself is not stored. We record pages viewed (without access codes in links), clicks on "Play", that a form was sent (not what was in it), and technical errors. There is no session recording (except in research games you agreed to, section 4) and no profile across days. The legal basis is our legitimate interest in a working, improving service (Art. 6 (1) (f) GDPR); you can object at any time (see below), for example by email, by turning on "Do Not Track" in your browser, or by blocking trackers.
Whether you dismissed the "also available in …" notice is stored only in your browser's local storage.
Status page. Our status page shows whether our games and website are running. It is a page of this website like any other, run by us: it loads nothing from third parties and sets no cookies. What it shows comes from Better Stack, which checks from outside every few minutes that our pages and servers answer; the monitoring carries no personal data. Our server fetches the results from Better Stack, so opening the page sends Better Stack nothing about you.
3. Requests and waitlists
When you write to us through a form or by email, we store your details (such as name, company, email, city, date, group size, message) to answer your request and prepare a quote (Art. 6 (1) (b) GDPR). When you join a waitlist, we store your email address to tell you about the game (Art. 6 (1) (a) GDPR); you can leave at any time. We delete requests and waitlist entries after twelve months at most, or earlier on request; you can leave a waitlist at any time.
4. Playing
- No account: to play you only need a nickname and a figure. We store a random player id so you can rejoin after losing the connection.
- Team names: your team can give itself a name (at most 24 characters, checked against a list of words we do not allow). It shows wherever teams appear: in the lobby, the feed, the ranking, on the big screen, in the recap, in the organizer's summary and on public share links. A team name is text you write, so please do not use anyone's real name. It is kept with the game's data and in the archive record (see "How long"); analytics never receive it.
- Location: during a game your device sends your position once you allow it. It only goes to your team, to everyone during certain game events (such as a rally), and to the organizer view. For the replay at the end, the game keeps a point of your route about every 20 seconds; after the game all players can see the routes, and we delete them seven days after it ended. No positions are kept for longer, unless you choose to keep your own routes in your account (section 5).
- Buried treasure: in this task your team photographs a spot for the other teams to find. The photo is shown to them as the hunt's clue. Where you stood when you sent it is kept as the hidden spot: the game tells the hunting teams only how far away and in which direction it lies, never the spot itself. It stays with the game's data and is deleted with it.
- Sprints: in races and sprint duels your device also counts your steps with its motion sensor, to measure the distance you covered together with GPS. Where the device requires it, you are asked for motion access first. The step counts stay with the game's data and are deleted with it.
- Age bracket (optional): for fair races you can give an age bracket (under 14, 14–17, 18–39, 40–59, 60+), when joining or later in the game, or skip it. We do not check it; it only adjusts your own sprint target, so younger and older players get a slightly shorter one. Only you see it; others see only your target. It stays with the game's data, is deleted with it, and never goes into our database, the game log, the archive, analytics, research recording or a rematch. Legal basis: your choice (consent, Art. 6 (1) (a) GDPR); choosing "Skip" withdraws it at any time.
- Photos, audio and video: what you record for challenges is stored so your team and the game can see and check it, and the other players of the game where the game shows it (another team's review, the awards vote, the feed, a buried treasure's hunt). We delete it when the game ends, except the winning pictures of teams that agreed to the recap, which we delete after seven days.
- AI checks: to judge challenges we send recordings (photos, audio, video), typed answers (such as words or riddle solutions) and the text of an appeal to AI services: Anthropic (Claude) for the verdict, Cloudflare Workers AI for speech recognition. Under their contracts the providers do not use the data for training.
- No automated decision-making under Art. 22 GDPR: the AI check only decides game results such as Credits, and your team can appeal a result. It has no legal or similarly significant effect.
- Game analytics: we analyse game events (such as a game started, a challenge solved, a field claimed, the stars of a rating) with the random player id through PostHog to improve rules and challenges. Names, positions, texts and media are never included. A challenge's result also carries short codes for its situation (daylight or dark, the kind of weather, the kind of place, the team's size, a working day or a day off), and we count how many open tasks the weather or the time of day moved; none of this carries a position, a field or a place. For AI checks of a submission we record only the model, duration and size of the request, not its content (research games below are the exception). AI calls that involve no person (building boards, place texts, city packs) are logged in full. Events our servers send carry no location; for events from your browser PostHog derives a rough country and city, as in section 2.
- Keep playing: near the end the players can vote on more time. The game keeps each answer until it erases itself. Everyone, the organizer included, sees only the count, never who answered what; analytics receive only the totals.
- Feedback: ratings are stored with the random player id and no name; optional free text is deleted after 180 days.
- Push notifications: if you allow them, we store your device's push token to notify you about your game (through your browser's push service, Apple or Google).
The legal basis is running the game you take part in (Art. 6 (1) (b) GDPR); for location, motion and push also your consent in your device's permission prompt, which you can withdraw in its settings at any time.
How long: all of a game's data (nicknames, team names, player ids, positions and routes, push tokens, typed text, the game's feed and its media) is deleted automatically at most three weeks after the game ends, or 30 days after it was created for a game that never started. For the organizers' game history we keep each ended game's final ranking with the team names and nicknames (for team events also the summary's per-team figures) for twelve months at most, shorter on request. A log of how games went (Credits, fields, challenges), the game's directory entry and the rating stars are kept for 24 months at most, to improve the rules; they hold only random ids and team numbers, no names, player positions or texts. The log names where a task's pin stood (a sight, or a square of about 100 metres), never where a player was. From it we count, per place and kind of task, how tasks went there, without any player, team, game or time, so that tasks go to places where they work.
You are not obliged to give us any data. Without a nickname you cannot play, without location access location-based tasks do not work, and without an email address we cannot answer a request.
Team events
- Branding: the organizer can add a company logo and an accent colour. The logo is stored with the game, stripped of embedded metadata, and erased with the game's data. It appears in the lobby, on the big screen, in the recap, the summary and the game's share cards.
- Own tasks: the tasks an organizer writes (title, text, kind, difficulty, a place picked on the map) are stored with the game and deleted with it. The AI checks read them together with the teams' submissions (section 4, AI checks). Please do not put personal details into a task.
- Task sets: a signed-in organizer can save own tasks to the account. We keep them until the set or the account is deleted.
- Big screen: the organizer's link opens a screen for the venue with the ranking, the clock and public highlights. It shows a team's winning photo only if every member of that team agreed to the recap; otherwise text only.
- Summary: after the game the organizer gets a printable summary about the teams (ranking, points, fields, tasks solved, distance walked, number of photos, teamwork, highlights). Apart from the names the teams chose for themselves it names no one, gives no figure for a single person, and shows no position, photo, recording or typed answer. For it we keep per-team figures (team, kind of task, time, task title; no player) in the game's archive record for twelve months at most.
The legal basis is the contract with the organizer and running the game (Art. 6 (1) (b) GDPR); for photos on the big screen, the team's agreement to the recap (Art. 6 (1) (a) GDPR).
Sharing
- Share links (
/s/…): you can make a public link to a game's result or to a challenge your team won or lost. It shows game facts only: each team's colour and the name the team chose for itself, the ranking, fields, the distance all players walked together, the city, the game's name and a task's title, and for a team event the company's logo and accent colour. Never players' nicknames. We keep a share link for twelve months after it was first shared, and delete it sooner on request. If you are signed in, the link carries your account's invitation code (section 5). - Picture cards: a member of a team that agreed to the recap can make a public card of one of the team's kept pictures. It asks search engines not to index it and is deleted with the recap, seven days after the game.
- Pictures shared as files leave from your own device through its share menu; we do not host them.
- Counting: share pages count views and clicks on "Play your own game" through PostHog, with only the card type and language (as in section 2, without cookies). Visits by crawlers are not counted.
- In the apps, saving a picture asks for permission to add it to your photo library; the app only adds, it does not read your library.
The legal basis is the sharing you ask for (Art. 6 (1) (b) GDPR); for picture cards also your team's agreement to the recap (Art. 6 (1) (a) GDPR), which each member can switch off in the lobby until the game ends, and afterwards withdraw by writing to us; we then delete the game's cards at once. For counting, our legitimate interest (Art. 6 (1) (f) GDPR).
Research games (beta)
An organizer can create a game as a research game (beta) to help us improve the game. You can join one only if you agree before joining; every normal game is the alternative, and records none of the following. Research games are for players aged 16 or older, and the organizer confirms that the game is not an event of an employer.
If you agree, we record for research on the game: (1) analytics under a lasting pseudonymous research id, never your name, including a session replay in which inputs, texts, pictures and the map are masked; (2) the AI's prompts and answers about your own submissions (typed answers and appeal texts in full, photos and recordings only by reference); (3) your routes and race tracks during the game. This goes to PostHog (EU, Frankfurt) and is kept for twelve months at most; session replays for 90 days at most where our plan allows, never longer than twelve months.
On your device we store the research id in the browser (rwg.researchId), plus PostHog's own storage while a research game is on screen; both only after you agreed. You withdraw by leaving the game: recording stops at once and PostHog's storage is cleared. To have your research data deleted, write to us with the game code and your nickname, or your research id. No advertising, no sale of data, no marketing use. Legal basis: your consent (Art. 6 (1) (a) GDPR, § 25 (1) TDDDG).
Internal test games of our own team run under an internal agreement and record more (full AI traces, session replay, positions); their media and game data are kept for 90 days at most. From them we also keep the AI check's cases (the task, typed answers, the transcript, the verdict and our team's label; photos only by reference) for twelve months, to test changes to the AI check; they are deleted with the game. Only our own team plays these games.
5. Account, saved games and emails
Account (optional): you never need an account to play. If you make one, we store your email address and send you sign-in links by email (through Resend). We log the emails we send with recipient and subject for 30 days at most, their content for a day at most. Legal basis: Art. 6 (1) (b) GDPR.
Signing in with Apple, Google or Microsoft (optional): instead of the email link you can sign in with your Apple ID, your Google account or your Microsoft account (personal, work or school). You then sign in on that provider's page, and it tells us your account's email address, whether it has confirmed that address, and a lasting id of your account with it (Microsoft also the id of your organisation's directory). We ask for nothing else: no name, no picture, no contacts. We store the provider's id with your account, so that your next sign-in finds it. With Apple you can hide your address: we then get an address at Apple's relay service, which forwards our emails to you. For Apple we also keep the token Apple issues for the sign-in, encrypted, only to withdraw our access at Apple when you disconnect Apple or delete the account. If a provider does not confirm the address, we first send a link to it and connect the provider only once you open it. You can disconnect a provider on /account at any time; the email link keeps working. Each provider is responsible for its own sign-in under its own privacy policy. Legal basis: Art. 6 (1) (b) GDPR.
Saved games: when you save a game to your account, we keep the game code, your random player id from that game, your team and the time. While both exist, this links that game's pseudonymous log and your rating to your account. Saved games stay until you delete the account, twelve months at most.
Three optional settings: all start off, none is a condition for anything, and none is rewarded. (1) Analytics under a lasting pseudonymous id: a keyed hash of your account id, not your email address. Your events in the games you saved and on your account's pages are then counted under this id with a profile in PostHog, so we can see how people play across games; nothing more, no session recording. On our account pages your browser then keeps PostHog's own storage; switching the setting off clears it. (2) "Help improve the game with my routes": for each game you saved we keep your own route from its replay (a point about every 20 seconds, your team, the start and end of the game; nobody else's route) for twelve months after the game, linked to your account, to tune step counting, distances and boards. Switching it off deletes the routes it kept, and so do removing the game from your account, deleting the account, or the game being erased. (3) Newsletter by email. We log every change with its time, where it was made and the version of the wording, as proof of your consent, until you delete the account. Legal basis: your consent (Art. 6 (1) (a) GDPR; for the storage on your device also § 25 (1) TDDDG), which you can withdraw at any time in your account settings.
Newsletter: you can subscribe in your account or, without an account, in the footer of our website. Either way we send it only after you confirm (double opt-in; the confirmation link is valid for seven days), and every email has a one-click unsubscribe link. Without an account we store your email address, its language, where and with which wording you subscribed, and when you confirmed, as proof of your consent; a request you do not confirm is deleted after seven days, and if you later make an account with the same address, the subscription moves to it. Resend keeps the recipient list for us (processor; mail is sent from Ireland, the list is stored in the USA, see transfers below). When you unsubscribe we delete your entry there, and without an account also our record of your address. Legal basis: your consent (Art. 6 (1) (a) GDPR).
Closed Beta sign-up: on /beta you can ask us to contact you about the Closed Beta and invite you to test rounds. This is a list of its own: it does not sign you up for the newsletter. We store your email address, its language, your first name, your city, who you would play with, the size of your group, an Instagram or TikTok handle if you give one, where and with which wording you signed up, and when you confirmed (double opt-in as above, as proof of your consent). We use these details only to plan rounds that suit you. Once you confirm, Resend keeps you on our beta list with the same details (processor, as above), where our team reads them and writes to you; we may also note there where you stand (invited, date set, played). We delete everything twelve months after your confirmation at the latest, a request you do not confirm after seven days, and at once when you unsubscribe from any of our emails or delete an account with the same address. Legal basis: your consent (Art. 6 (1) (a) GDPR).
Invitations: if you arrive through an invitation link (/r/…), we carry the invitation code in the address until you sign up or buy a game; we do not store it on your device. Then we store the code and who invited whom. Legal basis: Art. 6 (1) (b) GDPR.
Codes and trophies: discounts your account earns or is granted (a reward for an invitation, a rematch voucher, a loyalty code, a code for your own game after playing in someone else's, an education or reseller grant) are promotion codes at Stripe, linked to your account's random id. We keep each code, its kind, what earned it (a game code or a count) and when it expires, was used or withdrawn, until you delete the account, and at most a year after the code ended. If you have never bought anything, the code is made without a Stripe customer, so none of your details go to Stripe. Trophies are counted from your saved games and carry no money value; nothing else is stored for them. Legal basis: Art. 6 (1) (b) GDPR.
Buying: when you buy a game, Stripe handles the payment; we never receive full card details. You name the country where the game will be played, which decides its price. The purchase keeps that country, the price, the kind of discount used and, if you came through a partner's link or code (such as a hotel or an agency), that code, so that we can pay the partner a commission; partners receive no personal data from us. When a company pays by invoice, it enters its company name, billing email, address and VAT id if any on the buy page; these go straight to Stripe and we do not store them. Stripe issues and sends the invoice with any reminders and receipts, and offers bank transfer. Stripe's customer portal (linked on /account) shows your invoices and lets you change those details and a kept card. Billing data (name, billing address, VAT id if any, invoices) is kept by Stripe and by us as long as commercial and tax law requires (up to ten years), also after the account is deleted; our purchase and charge records then no longer name your account. Legal bases: Art. 6 (1) (b) and (c) GDPR.
Paying at the start and extras: a game that costs money is paid when its organizer starts it. Stripe keeps the card used at checkout for later charges on your games (the checkout page says so): the start, extra time you approve, and, once after the game, the difference if more people played at once than you paid for. Each of these charges is an invoice at Stripe, which Stripe or we email to you; we record per account which game was charged, for what, how much and whether it is paid. With a kept card, or as a company whose VAT id Stripe has verified, you can also start at once and pay the invoice within two days, and such a company can instead get one invoice after the game. Someone else can pay a game's start through a QR code: Stripe then keeps no card and links the payment to nobody's account. The game notes which account pays until it erases itself; players never see it. Legal bases: Art. 6 (1) (b) and (c) GDPR.
Gift vouchers: you can buy a game as a gift voucher on our website, without an account. Stripe Checkout asks for your email address and billing address and handles the payment; Stripe issues the invoice and the receipt. After payment we email you the voucher code (through Resend, logged as above). We keep no other record of the purchase; Stripe keeps the voucher code and its records, with the billing details, for the period commercial and tax law requires. Legal bases: Art. 6 (1) (b) and (c) GDPR.
Deleting your account: you can delete your account at any time on /account. We then delete your email address, sign-ins, the connections to Apple, Google or Microsoft (and withdraw Sign in with Apple at Apple), saved games and the routes kept from them, settings with their proof, invitations, your codes, the link to Stripe, a newsletter entry and a Closed Beta sign-up for your address, and your entry at Resend.
We use no advertising or retargeting pixels.
6. Maps, place data, weather and surroundings
Your device loads the in-game maps from OpenFreeMap (tiles.openfreemap.org), which sees your IP address. Everything else in this section runs on our servers and sends no player's position, no identifier and no other personal data:
- Boards and challenges are built from open data (OpenStreetMap, Wikipedia, Wikidata, Wikimedia Commons, Wikivoyage, Overture Maps), and the terrain's heights from the Terrain Tiles on AWS Open Data (we ask only for a map tile's number or an area).
- Town and region: we send the centre of the board the organizer chose to Nominatim (OpenStreetMap) to learn the town, the country and the state or region. The game keeps the region to know its public holidays.
- Weather: for a game's forecast we send the point the organizer chose on the map, rounded to about one kilometre, to the Norwegian Meteorological Institute (MET Norway), and for official weather warnings to the country's weather service: the Deutscher Wetterdienst through Bright Sky in Germany, the National Weather Service in the USA, MET Norway in Norway. The game's log and archive keep a weather class (sky, temperature range) that relates to no one.
- What is going on nearby: to keep tasks away from closures, events and races on the day, a game can have Anthropic's web search look for news around its board. The search receives the town and country, the board's point rounded to about one kilometre, the date and the game's hours, and the names of places on the board from OpenStreetMap. The result is kept for an hour per area and day and shared by games in the same place.
- Air, pollen and UV: the Umweltbundesamt and the Deutscher Wetterdienst give us files for the whole country (we send nothing). Copernicus CAMS, through ECMWF's Atmosphere Data Store, receives a box of about 25 kilometres around the board; AirNow the board's point rounded to about one kilometre; the US EPA the town and state.
- Road safety: to keep sprints away from dangerous crossings we use accident counts from the Unfallatlas (read ahead, nothing sent) and, in New York, from NYC Open Data, which receives a box of a few kilometres around the board. We keep counts per place, never single accidents.
- Public transport: stops and lines come from the transport associations' timetable files (MVV, VBB, the MTA) and OpenStreetMap, read ahead; games send nothing.
- Closures and events: Munich and Berlin give us the whole city's building sites and closures. In New York, NYC Open Data receives a box around the board and the date, and 511NY gives us the state's list.
- Street pictures: Mapillary receives a map tile's number, and Mapillary and Panoramax a box of about 90 metres around a sight, to learn about street furniture and to find street pictures of the sight. To check that a sight still stands, Anthropic's model looks at up to three of these pictures; we keep only its verdict with the picture's id and date, never the picture.
The sources and their licences are listed in the legal notice.
7. Recipients and third countries
We use these processors: Cloudflare (hosting, database, storage, AI), Anthropic (AI checks, and web search for what is going on near a board), PostHog (analytics and error tracking, and in research games session replay and AI traces; data processed in the EU), Resend (email), Stripe (payments), Better Stack (uptime monitoring), Apple and Google (push notifications in the apps). When you sign in with Apple, Google or Microsoft, that provider acts for its sign-in as a controller of its own (section 5). Some are based in the USA. Transfers rely on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses.
8. Your rights
You have the right of access, rectification, erasure, restriction of processing, data portability, and to object to processing based on legitimate interests. You can withdraw any consent at any time with effect for the future. Write to us at hello@real-world-games.com. How to have your data deleted is explained at real-world-games.com/account/delete. You can also complain to a data protection authority, for example the one responsible for us: Bayerisches Landesamt für Datenschutzaufsicht (BayLDA).
Right to object (Art. 21 GDPR)
Where we process data on the basis of our legitimate interest (Art. 6 (1) (f) GDPR), you may object at any time on grounds relating to your particular situation. We then stop processing it unless we can show compelling legitimate grounds that override your interests, or the processing serves to establish, exercise or defend legal claims.
9. Children
Children under 16 may only play with their parents' consent, for example in a game a school or their parents set up.