Privacy policy

Last updated

This policy covers the Manhunt IRL iPhone app and App Clip, the Android app, the browser version at manhuntgame.com/play, the game server at api.manhuntgame.com, and this website. It describes what the software does today, checked against its code. It’s written in plain language, and it hasn’t yet been reviewed by a lawyer; we’ll update it after that review and change the date above.

Manhunt IRL is run by Aryan Agrawal. Questions or requests: privacy@manhuntgame.com.

The short version

  • No accounts. You play with a nickname. We never ask for your real name, email, phone number or birthday to play.
  • Location is for the game you host or join. A host’s location sets the play area. After that, phones send location only during the head start and the hunt, and it’s shared with other players only in the way the game rules allow.
  • Game data is deleted automatically, 24 hours after the game ends. Our host keeps backups that let deleted data be restored for up to 30 days, and then it’s gone for good.
  • No advertising and no data brokers. We don’t sell or share personal data, and no advertising company receives your location. The website sends crash reports to Sentry, and page views and a few named game steps to PostHog, without your GPS location or nickname, and with join codes removed (see “This website” for an earlier error-reporting bug). The map provider (OpenFreeMap in the browser, CARTO in the Android app) sees which map area is loaded (see “Service providers”).
  • You can delete your data from the iPhone app or the Android app, or by emailing us.
  • The idea box is optional. If you send an idea from manhuntgame.com/ideas, we keep its words (and a reply line, only if you add one) for up to 90 days, never show it on the site, and never store your IP address with it. See “The idea box”.

What we collect, and when

DataWhenWhyKept for
A random player ID and a device secret (the ID also encodes when it was created)The first time you host or joinTo reconnect you to your game if your connection dropsOn your device until you delete it (see “Your choices”). On iPhone it’s kept in this device’s Keychain (not carried to a new phone by a backup), which iOS keeps even if you delete the app. On Android it’s kept encrypted with a key held in the phone’s Android Keystore, in the app’s private storage (not carried to a new phone by a backup), and Android removes it when you uninstall the app. On our server, only inside the records below.
A per-install id (random bits, not an Apple or Google advertising id)Minted once on first useSo several phones on one Wi-Fi count as separate devices for the referee rule and for keeping a removed player outOn iPhone: 64 random bits in this device’s Keychain, sent only as part of the app’s User-Agent (ManhuntInstall/…). Kept through Delete my data and through deleting and reinstalling the app, so a host’s removal still sticks after a fresh install. On Android: 64 bits made by hashing the Android app’s own device id (ANDROID_ID, a value Android makes per app and device that is not an advertising id; the raw value never leaves the phone), sent only as part of the app’s User-Agent. It is kept through Delete my data and through deleting and reinstalling the app, like the iPhone’s. On the browser: a random id in that browser’s local storage (mh.install), sent only in the join or host request body. Clearing the site’s data mints a new one. The server never stores the raw id: it only folds it into the device fingerprint below.
Nickname and emojiWhen you host or joinTo show you in the lobby, on the map and in the recapWith the game record
Precise location (latitude and longitude to about 1 meter, plus GPS accuracy, speed, heading and the time of each reading)When you set up a game as host, and during the head start and the hunt (details below)To run the game: boundaries, pings, the heartbeat, tags, jail, jailbreaks and the end-of-game replayWith the game record. We don’t store heading.
Your route (one point every 10 seconds, thinned to half that on long games)During the head start and the huntFor the end-of-game replayWith the game record
Battery level (iPhone app only; the Android app doesn’t send it)Every few minutes while you’re in a gameSo nobody’s phone dies unnoticedWith the game record
Game events (tags, disputes, jailbreaks, pauses, awards, names of people asking to join, and any player report: the host and referee see who was reported and why, never who reported; the game record keeps who reported whom, only to allow one report per person; and, only if the host turns Dares on, the dares the host chose or typed, and who claimed a dare, who judged it and the result: nothing is filmed or uploaded, and a dare claim carries no location)During the gameTo run and referee the game, and for the recapWith the game record
Status shown to other players (online or last seen, whether your location is currently marked unverified, and whether you’re using the iPhone app, the App Clip, the Android app or a browser)During the gameSo the group knows who’s connectedWith the game record
A device fingerprint: a keyed, one-way hash of your IP address, your app’s or browser’s user-agent, and (when present) the per-install id aboveWhen you host, join or ask to join a gameSo a host can keep a removed player out of their game, and so several sessions on one device count as one player for the referee ruleWith the game record. It can’t be reversed without our server’s secret key. While you’re waiting to be let into a game, the game also keeps a keyed hash of your network alone (for IPv6, your /64), so one device can’t take every waiting place; it goes when you’re let in, turned away, or stop waiting.
Which games your player ID joinedWhen you host or joinSo “Delete my data” can find and clean every game you were inEntries expire after 7 days and are deleted within about 6 hours after that, or right away when you delete your data
That your player ID finished a game (the ID and an expiry date, nothing about the game)When a game you played in (not practice) ends after at least 5 minutes, with 3 or more devices sharing locationSo people who already play can still host new games if someone floods the server with fake ones90 days, then deleted within about 6 hours, or right away when you delete your data
Daily game totals (counts by app type, host/player history bucket, link or code join, approval outcome, round size and mode, duration bucket, winning team, and zone choice)When a game is created, joined, started, rematched or finishedTo understand whether groups can start, play and bring in friends across platforms400 UTC calendar days. These are daily totals only: no player, game or device IDs, codes, names, locations, IP addresses or event timestamps are stored in the counter data.
A keyed hash of your IP address, as a rate-limit counter (for IPv6, of your /64 network; when you host, also of your wider /56 and /48 network, or /24 and /16 for IPv4, and a counter per network operator (its public ASN number, which names your internet provider, not you); your player ID is used the same way for some limits). The address itself isn’t stored.When you start a session, host, join, delete or send an ideaTo stop abuse, such as someone guessing join codes or flooding the server with fake games or ideasThe counters reset after 1 minute, 1 hour or (for the idea box) 1 day, and expired counters are deleted within about an hour.
Server diagnostic logsWhen our server logs an error or eventTo find and fix problemsUp to 7 days, at Cloudflare. Query strings are removed from logged URLs.
Player reports (the game id, the reported player’s id and a fixed reason such as “name” or “unsafe”; never who reported, and never names or locations)When someone taps Report on a playerSo we can review abuse reports (App Store guideline 1.2)90 days in our reports store, or until you ask us to delete earlier. A copy may also be sent to an owner-only webhook if one is configured.
An idea you send (its words; a reply line, only if you add one; and one of four words for your kind of device: iPhone, Android, browser or other)Only if you send one from manhuntgame.com/ideasTo read it and decide what to build; the reply line only so the owner can write backIn the idea box for up to 90 days, then deleted by the system. The words may also be copied, never with the reply line, into our private product notes. Never your IP address, device id or any other identifier. See “The idea box”.
Your emailOnly if you email usTo replyAs long as needed to answer, then deleted

How long a game record lasts. A game’s whole record (every item marked “with the game record”) is deleted 24 hours after the game ends. A lobby that never starts is deleted 12 hours after it was created. A game that is still running after 4 hours is ended automatically, and deleted 24 hours later. Starting a rematch keeps the record going as a new game. Our host, Cloudflare, keeps point-in-time recovery backups of this storage, which could be used to restore deleted data for up to 30 days; after that it’s permanently gone. We only use these backups to recover from an outage or a bug.

Join codes are 4 letters and point to a game for up to 48 hours. After that, the same code can be reused by a different game.

When location is collected

  • Hosting. When you set up a game (in the iPhone app or in the browser at /play), your device reads your location and sends it to our server to set the center of the play area and the jail. In the browser version, and in app versions that offer it, a host can instead pick the center on a map, anywhere (up to 3,000 meters from the middle to the edge); the server stores a picked spot as the play area’s center and treats it exactly like a spot from the host’s GPS in this policy, and it never compares it with the host’s own location. In the lobby, only the player who set that spot (normally the host) sees it exactly; everyone else, referees included, sees it only roughly (to within about a kilometer). If the host role passes to someone else, they also see it only roughly unless they move the play area. A host can move the play area in the lobby with Center the zone on me, which sends their current location once to set the new center (the jail moves with it). If the player who set that spot leaves the lobby or deletes their data before the game starts, the server keeps only the rough area, and the game can’t start until the new host sets a new center. Someone who joins after a game has ended sees the play area only roughly. Once the game starts, every player sees the play area and the jail.
  • iPhone app and App Clip. After you allow location access, the app starts reading your location when you’re in a game lobby, so it has a GPS fix ready and the game works with your phone in your pocket. If the lobby hasn’t started after 20 minutes, the app stops reading your location while it’s in the background, until you open it again. It sends your location to our server only during the head start and the hunt, and stops when the game ends or you leave. It also sends your battery level every few minutes from the lobby on.
  • Android app. After you allow precise location, the app reads your location while you’re in a game lobby or a game, so it has a fix ready. While you’re in a game, a notification is shown (Android requires it), and it keeps the game running when you lock your phone. The app asks for location only while its screen is open, and it never asks for location in the background when you’re not in a game. It sends your location to our server during the head start and the hunt. In the lobby it also sends your location so the host can see who has location on (“I’m in”); the server uses it only for that, and no player sees where you are. It stops sending when the game ends or you leave, and the notification and the location reading stop when you leave the game. If you allow only approximate location, the game can’t tell where you are and asks you to turn precise location on.
  • Browser version. Your browser starts reading your location when you tap Join, Host a game, or Practice with bots (or, if you reopen the page within 6 hours of joining a game, when it reconnects you), and sends it to our server every few seconds only during the head start and the hunt, never in the lobby or after the game ends (except the one reading used to set the zone when you host or practice). While it’s sharing, the page shows “Sharing location with N players”. Your browser stops reading your location when the game ends (it starts again if the group plays a rematch), when you leave, or when you close the page.
  • Referees: our server doesn’t accept or store a referee’s location.
  • Walking away. A location more than about 150 meters past the edge of the play area is never shown to anyone. If you stay that far out for a minute of play (with a good GPS signal, even if your phone then goes quiet), you’re taken out of the round and the server ignores those far locations, so where you go isn’t shared with anyone, even if you forgot to tap Leave. Coming back inside the play area (with a good GPS signal) puts you back in as a hunter, unless you tapped Leave; while you’re out this way you don’t see the other players.
  • Not between games. Nothing tracks you between games, and nothing runs in the background when you’re not in one.

Who can see your location

During a game, the server decides what each player receives. Other players can see:

  • Teammates: each other’s live position during the hunt, while they’re free. (In Infection mode, humans don’t see each other.)
  • Hunters: a runner as a fuzzy circle at each ping, which the runner is somewhere inside (not necessarily near the middle). Circles are usually tens of meters wide and get smaller late in the round. In Classic mode, if nobody has been caught for 6 minutes, circles tighten to within a few meters (about 8 meters, more if GPS is poor) until the next catch. Hunters also see a runner’s exact position while that runner is outside the boundary.
  • Runners: a vibration when a hunter is within about 80, 50 or 25 meters (not which hunter, or which direction), and a hunter’s exact position while that hunter is outside the boundary, standing near jail, or left jail early during the head start.
  • Everyone: a caught runner walking to jail; the last known position, once, of a player whose GPS has been weak or silent for a while; the position, once, of a player who calls a safety pause, so they can be found; and, when a paused game resumes, the position of whoever called the safety pause and of anyone who moved more than about 20 meters (beyond GPS error and where they were already running) while the game was paused, or of a player whose location was off during a longer pause, at their first reading afterwards if they’re further from where they stood than they could have run since the game resumed (counting at most 90 seconds of running; a pause is a freeze).
  • A disputed tag: the two players and the referee see how close the two were in the 30 seconds before the tag (distances only, never positions).
  • Players in jail: everyone’s position with a 90-second delay, as spectators. Players who are out of the round (they left the area, or their location was off for 5 minutes) get no spectator view, only the one-off positions everyone gets (listed above).
  • The referee, if a leader takes that role: every player’s live position, but only while at least four other players are in the game on their own phones (so a referee can’t be used to watch one or two people). Every player can see who the referee is.
  • The play area: every player sees the boundary and the jail once the game starts. By default, the host’s app centers them on where the host was standing when they set up the game.
  • The host and the referee can see every player’s battery level; other players see their own team’s.
  • After the game: every player in that round receives everyone’s route from that round for the replay, trimmed to the play area plus a 50-meter margin, and the recap shows each player’s closest call (how near a hunter came). It stays in memory on their device; we don’t keep a replay library. Share cards made from a recap draw the round’s routes as abstract lines, with no map, street names or join code.

Nobody outside the game can see players’ positions through our service.

Service providers

We use a small number of companies to run the service. None of them may use your data for their own advertising.

ProviderWhat they doWhat they see
Cloudflare, Inc.Hosts this website and the game server, stores game records and daily aggregate counters, and keeps server logsEverything our server stores, as described above, as our processor. The daily counters contain only the fixed dimensions and daily totals described above; they do not contain identifiers or event timestamps.
OpenFreeMapSupplies the map in the browser version (map tiles and map-label fonts, drawn from OpenStreetMap data)When the map loads, your browser asks OpenFreeMap’s servers for map tiles and fonts around the game area, so OpenFreeMap sees your IP address, which area of the map is shown (roughly where the game is) and your browser type. The page asks your browser to send no cookies and not to tell OpenFreeMap which page you’re on. OpenFreeMap says it uses no cookies or tracking, that its normal access logs don’t record IP addresses, that error logs that may include one are deleted after 7 days, and that it may log IP addresses for up to 30 days if it detects misuse. It serves maps through Cloudflare (OpenFreeMap privacy policy).
CARTOSupplies the map images in the Android appWhen the map loads, the Android app asks CARTO’s servers for map tiles around the game area, so CARTO sees your IP address, which area of the map is shown (roughly where the game is) and the type of app or device making the request. CARTO says it shortens IP addresses and keeps these logs for 30 days (CARTO basemap terms).
AppleDistributes the iPhone app and App Clip, and supplies the maps inside the iPhone app (MapKit)What Apple’s own privacy policy describes. The iPhone app’s alerts are generated on your phone; we don’t use push notifications.
GoogleDistributes the Android app through Google Play, and supplies the location service the Android app uses to read your position (Google Play services, when your phone has it)What Google’s own privacy policy describes. The Android app’s alerts are generated on your phone; we don’t use push notifications, and the app has no Google analytics, advertising or sign-in.
Sentry (Functional Software, Inc.)Receives crash reports from this website, on Sentry’s free planThe page address with the join code, query string and anything after # removed, the browser error, the browser type, and the IP address of the browser that sent the report (Sentry uses that to guess a city). Not your GPS location or nickname. Join codes are removed; an earlier stack-trace bug is described under “This website”. Sentry’s privacy policy.
Anthropic, PBCIts AI assistant (Claude) helps us read and sort the ideas sent through the website’s idea boxThe words of an idea, without the reply line. Nothing from the apps, no game data and no location.
PostHog, Inc.Counts page views and game steps on this website (not the iPhone app), on PostHog’s free planThe page views and named events listed under “This website”, with a random ID for your browser (not your player ID, and not linked to it); the page address with the join code, query string and anything after # removed; your browser and its user-agent string, operating system, device type, screen and window size, language, time zone and in-app browser name; and the IP address your browser connects from, which the site asks PostHog not to turn into a location. Not your GPS location, nickname, emoji, player ID, game code or invite link, and no screen recording. Our PostHog plan shows us the last year of events. PostHog’s privacy policy.

The iPhone app, the App Clip and the Android app don’t include analytics SDKs or crash reporting. The game server separately keeps the daily aggregate totals described above. The iPhone app keeps the crash and battery summaries iOS gives it on the phone (they hold no location or identity) and sends them nowhere; Settings lets you share them yourself if you choose. This website reports crashes to Sentry and sends analytics to PostHog, as described under “This website”. We don’t use advertising software, and we don’t sell data.

What we don’t do

  • We don’t sell or rent personal data, or share it for advertising.
  • We don’t build advertising profiles. Our game server doesn’t keep a history of your games; the website’s analytics keeps only the game steps listed under “This website”, under a random ID that isn’t linked to your player ID or your games. The server also keeps daily game totals without identifiers, codes, names, locations, IP addresses or event timestamps for 400 UTC calendar days.
  • We don’t track your location outside a game you’ve joined.
  • We don’t let other players see your exact position except in the situations listed above.
  • We don’t use cookies. The browser version stores a few items in your browser’s local storage (your player ID and secret, nickname, emoji, per-install id, the last game you joined, that you’ve seen the intro cards, and your answer to the “Are you 13 or older?” question with the time you gave it) so it can reconnect you, not show the cards again and not ask the question again. It also keeps up to 600 map tiles and map fonts in your browser’s cache storage for up to 30 days so the map loads faster; they show roughly where games were played, and Forget this device clears them. The website’s analytics (PostHog) keeps its random ID and settings in local storage too.
  • We don’t dial emergency services from the app or the browser. The Safety sheet shows your coordinates and how to pause; calling for help is done with your phone’s usual dialer.

Your choices

  • Leave a game at any time. Your phone stops sending location.
  • Delete my data (iPhone app): Settings → Delete my data. It removes you from every game you’re in or were in during the past week (your name becomes “Deleted player”, and your location, route, battery level and fingerprint are removed, including from recaps that haven’t been sent yet), permanently retires your player ID, and erases your ID and profile from your phone. We keep only your random player ID and the time you deleted it, so that ID can never be used again. The per-install id in the Keychain is not rotated (see the table above). If you had been removed from a game, the fingerprint on that game’s removed-players list stays until the game record is deleted. Server-side deletion was added on September 27, 2026. If your phone can’t reach our server at that moment, it still erases your ID from the phone, and your game records are deleted on the normal schedule; email us if you want us to check.
  • Delete my data (Android app): Settings → Delete my data. It does the same on our server as the iPhone app’s Delete my data (above), and erases your ID, secret, nickname, emoji, block list and the note that you’ve seen the intro cards from your phone. The per-install id is not rotated. If your phone can’t reach our server at that moment, it still erases your ID from the phone and your game records are deleted on the normal schedule; email us if you want us to check.
  • Browser version: tap Forget this device (on the join screen, or in the lobby) to leave the game, delete your data on our server the same way as the iPhone app’s Delete my data, and erase your player ID, secret, nickname, emoji, per-install id, last game, the note that you’ve seen the intro cards and the saved map tiles from that browser (the next person to open the page sees the cards again). It also gives the website’s analytics a new random ID. Events already sent to PostHog stay there under the old random ID, which isn’t linked to your player ID, nickname or games. If our server can’t be reached at that moment, the browser still forgets you and says so, and your game records are deleted on the normal schedule; email us if you want us to check. Clearing this website’s data only erases the browser’s copy. A “No” answer to the age question is kept even after Forget this device; clearing this website’s data in your browser erases it.
  • Website analytics: if your browser sends Do Not Track or Global Privacy Control, this website sends nothing to PostHog. Safari, and so every browser on iPhone, sends neither signal. If you answer “No, I’m under 13” to the age question in the browser version, this website sends nothing to PostHog or Sentry from that browser, on any page, for as long as that answer stands (24 hours, then the question is asked again).
  • Location and notification permission: you can turn them off at any time in your phone’s settings. You can’t play without location, because the game depends on it.
  • Requests: to ask what we hold about you, to correct it, or to delete it, email privacy@manhuntgame.com. Because we don’t have accounts, tell us your nickname, the game code if you remember it, and roughly when and where you played. Depending on where you live, you may have further rights under local law; we’ll honor them.

Children

Manhunt IRL is for people 13 and older. The app and the browser version aren’t intended for children under 13, and we don’t knowingly collect personal information from them. The browser version asks “Are you 13 or older?” before it loads the game. Your answer (“yes” or “no” and when you gave it) stays in your browser; it is never sent to our server or to any analytics service, and nothing else is collected from someone who answers no. A “no” is remembered for 24 hours, so a mistaken tap does not lock anyone out for good; after that the question is asked again. The iPhone and Android apps ask the same question and keep the answer the same way, on your device only. Younger kids can still play Manhunt the traditional way, with no phones, using our printable rules with an adult running the game. If you believe a child under 13 has used the service, email privacy@manhuntgame.com and we’ll delete their data. The idea box is the same: it is for people 13 and older, a browser that answered “No, I’m under 13” gets no form on that page, and a younger player can ask a parent or guardian to send an idea.

Security

Everything travels over encrypted connections (HTTPS and secure WebSockets). The server, not the players’ phones, decides what each player can see, so a modified app can’t pull other players’ exact positions. Game records are deleted on the schedule above, which keeps what could ever be exposed small.

We would respond to valid legal process. Because game records are deleted within about a day of a game ending, we usually have nothing to provide.

Where data is processed

Our operator is in the United States. Cloudflare runs our server on its global network, so game data may be processed in data centers in other countries, close to where the game is played.

The idea box

The page at manhuntgame.com/ideas is a form where anyone can tell us what to build, fix or change. It is optional, there is no account, and it is the only form on this site that takes free text.

  • What you send. The words of your idea (10 to 1,000 characters), a reply line only if you choose to add one (an email or an Instagram name, up to 120 characters), and one of four words for your kind of device (iPhone, Android, browser or other), which the page works out from your browser’s own name for itself. Nothing else goes with it: no location, nickname, player id, game code or anything from the apps.
  • What we store. One record with those three things and the UTC time you sent it. No IP address, device id, user agent or player id is stored with it. Your network’s address is turned into a keyed one-way hash only to count how many ideas one network sends (5 an hour and 20 a day, and 300 a day in total), the same kind of rate-limit counter as in the table above; that hash is not in the record and not linked to it.
  • How long. The system deletes the record 90 days after you sent it, at the latest. We usually delete it sooner: when we have read the idea and written it down, we delete the stored copy, and with it the reply line.
  • Who sees it, and what we do. The owner, and the tools the owner uses to read and sort ideas: an AI assistant (Claude, by Anthropic) gets the words of an idea, never the reply line, and writes the idea down in our private product notes so we remember what people asked for. Those notes are private, they are kept as long as they help us plan the game, and they never hold the reply line. We read ideas as text only: we do not open links in them and we do not follow instructions in them. If you gave a reply line, only the owner sees it, and only to write back; we never share it and no assistant is given it.
  • What we never do. We never show what people type on this site or anywhere public, never share it, never use it for advertising, and never sell it. The idea page loads no analytics and no error reporting, sets no cookies and saves nothing in your browser.
  • Taking it back. Email privacy@manhuntgame.com with the words of the idea and roughly when you sent it, and we will delete the stored copy and remove the words from our private notes. The notes keep an edit history, so an older version of the notes can still hold a removed idea; it stays private.
  • Age. The page is for people 13 and older (see “Children”).
  • Not for emergencies. Nobody watches this box around the clock. If anyone is in danger, leave the game, tell an adult and call your local emergency number. To report a player, use Report in the game or email support@manhuntgame.com.

This website

manhuntgame.com has no advertising and no cookies. It sends crash reports to Sentry so we can fix broken pages. A report includes the page address (with the join code, the query string and anything after # removed), the error, the browser type, and the IP address of the browser that sent it. It does not include GPS location, a nickname, or a game code, and the site does not record your screen. Cloudflare, which hosts the site, processes standard request information (like IP addresses) to deliver pages and protect against attacks.

Earlier crash reports: on October 19, 2026, we found that an error report could still include a join code in a stack trace (the script address attached to an error), even though the main page address was cleaned. The October 19 fix also removes join codes, query strings and fragments from those stack addresses before new reports are sent. Older reports may still contain a join code; this change does not erase reports already stored.

It also sends analytics to PostHog, so we can see how many people visit and how many games get started and finished. That’s a page view for each page you open, plus these steps in the browser version: joining a game (and whether from an invite link, the join form or the demo), hosting a game, starting a practice game, starting a game, starting a rematch, leaving a game, a game ending (and which team won), claiming a tag, reporting yourself caught, using an ability (scan or ghost), choosing where a game’s zone goes (on a map or on your own spot, and whether it is over one kilometer, never where or how big), choosing a ping circle size (tight, standard, wide or custom, never the number), choosing a ping rhythm, how often pings come (fast, standard, slow or custom, never the number of seconds), turning Dares on or off, claiming a dare, answering a dare (approved or rejected, never which dare or by whom), starting a jailbreak, a join that didn’t work (and which kind of problem it was: no such game, game full, removed, too many tries, no connection, or something else), your phone’s location getting in the way (blocked, off, no reading yet or lost, and whether it happened before the game or in it, never where you are), choosing to host a game or try the demo after a typed code did not match an active game, and tapping “Host the next one” or “Host a game” after a game or on an invite link whose game is over (and whether it was the browser button or the App Store link), and sharing or copying an invite link or showing its QR code (and whether you’re the host, and whether by share, copy or QR), and sharing or saving a recap card (and whether by file, link, copy or save, and whether you won and got an award). Some steps also say whether it was the demo game, or whether your connection was up at the time. Each comes with a random ID PostHog makes for your browser. It isn’t your player ID or your nickname, and the site never links it to them or to your games. Page addresses, including the address of the site that linked you here, are sent with the join code, the query string and anything after # (where an invite link keeps its token) removed. PostHog also gets your browser and its full user-agent string, operating system, device type, screen and window size, language and time zone, the name of the app if you opened the link inside one (such as Instagram), and which search engine sent you, if one did (not what you searched for). Events never include your GPS location, nickname, emoji, player ID, the join code or an invite link. PostHog receives the IP address your browser connects from, as any server does, and the site asks PostHog not to work out a location from it. Nothing is captured automatically beyond page views: no screen recording, clicks, typing, errors or console messages. PostHog’s random ID is kept in your browser’s local storage (or, if the site can’t use local storage, only in memory until you leave the page), never in a cookie. From October 17 until the October 18, 2026 analytics update, the site also tagged these events with the browser’s player ID; it no longer does, and you can email us to have events from that period deleted. If your browser sends Do Not Track or Global Privacy Control, the site sends PostHog nothing (Safari, and so every browser on iPhone, sends neither). The iPhone app, the App Clip and the Android app don’t use PostHog. Separately, the game server keeps the daily aggregate game totals described under “What we collect” for 400 UTC calendar days; these counters contain only fixed categories and do not include IDs, codes, names, locations, IP addresses or event timestamps.

Changes

If we change how we handle data, we’ll update this page and the date at the top before the change takes effect, and say what changed.

Contact

Manhunt IRL, run by Aryan Agrawal · privacy@manhuntgame.com · General questions: hello@manhuntgame.com