Privacy policy
Last updated 10 November 2026
PlayedHere is a daily game. You can play the whole thing without an account and without telling us your name. This page says exactly what is stored when you do.
What we store if you just play
- A device id. A cookie called
ph_didholds a random identifier. It is how your score, your streak and your place on a leaderboard are remembered without an account. It is not linked to your name or your email unless you sign in. - The level you chose. If you pick Easy or Expert, a cookie called
ph_levelholds that one word, so the next page is drawn at your level. It is only written once you have picked one of those two, it is removed when you go back to Standard, and it says nothing about who you are. - Your rounds. For each round you play we keep the guess, the distance, the score and the time, against that device id. That is what the archive, the streak and the leaderboards are built from.
- Nothing precise about where you are. The game never asks for your location. Taps happen on a globe, and a tap is a point on a map, not a reading from your device.
What we store if you sign in
- Signing in is optional and does one thing: it carries your streak between devices. You can sign in with Google, with Apple, or with a one-time link sent to your email address.
- We keep your email address, the sign-in provider, and a session cookie. If you signed in with Google or Apple we receive the email address on your account from them; we do not receive or store a password.
- If you ask for daily reminders we store a push subscription for that browser. Reminders are currently switched off, and an existing subscription is not used until they are on.
Who else processes it
- Vercel β hosting. Serves every page and sees the usual request logs.
- Vercel Web Analytics β how many people visit, where they arrive from, and when an Off the Map climb is started, finished or shared. It sets no cookie and keeps no identifier from one day to the next.
- Upstash β the database holding game results, streaks, leaderboards and accounts.
- Google Analytics β how many people play and which pages they arrive on. It sets its own cookies.
- Google and Apple β only if you use their sign-in buttons.
- Resend β sends the one-time sign-in link, when email sign-in is available.
- Loops β holds the email list. If you have an account, your address is there.
- OpenStreetMap β supplies the map tiles the globe is drawn from.
- Google AdSense β if and when ads are switched on. They are not running today; this page will not need changing when they are, because the row is already here.
Signing in puts your email address on our list, and we may send you occasional email about the game β a new edition, a change worth knowing about. We are telling you here rather than in a line of small print under a button, because you signed in to carry a streak between devices and a mailing list is not what you came for.
Every email has a one-click unsubscribe and it works immediately. Unsubscribing does not touch your account, your streak or anything you have played. If you would rather not be on the list at all, email hello@playedhere.app and we will remove you.
Advertising
No ads are served at the moment. When they are, they come from Google AdSense, which uses cookies to serve and measure them. You can control personalised advertising in Googleβs own ad settings, and opt out of personalisation by vendors at aboutads.info.
Children
The game is not aimed at children under 13 and we do not knowingly keep an account for one. If you believe a child has signed in, email us and we will delete it.
Getting rid of it
- Clearing your cookies for this site drops the device id. Your past rounds stop being connected to you, and a new device id is issued the next time you play.
- To delete an account and the email address attached to it, email hello@playedhere.app from that address and say so. There is no form for this yet; a person reads it.
- We do not sell personal information, and we do not share it with anyone beyond the processors listed above.
Changes
If what we store changes, this page changes in the same release rather than afterwards. The date at the top is the date of the last change.