Privacy

Last updated November 18, 2026

BruinGuessr is a free student project, not affiliated with UCLA. It keeps as little about you as it can to run the game. There are no ads, no analytics and no tracking, and nothing is sold or shared for marketing.

If you sign in

Sign in is with Google only. When you sign in, Google tells us:

  • your email address,
  • your name and profile photo,
  • an ID for your Google account.

We never see your Google password. Your email is shown only to you, on your Settings page. Your Google photo is shown only to you, in the menu at the top right; your public profile shows the first letter of your username instead.

What the game keeps

  • Your username, which you choose, and when you joined.
  • Your games: where you dropped each pin, how far it was from the answer, your points, and when you played. For versus games, the room you played in and who else was in it.
  • Photo reports you file, so that one person cannot hide a photo by reporting it many times.

What is public: your username, your profile (join date, best game, games played, average score, bullseyes, versus results and your recent games’ distances and points), and your place on the leaderboard. Players in a versus room see your username and your pins for that game. If you contribute photos, your username is shown as the credit on them (see below).

If you contribute photos

The Contribute page uses your phone’s camera and location, and only after you press Start and your browser asks. The camera runs inside the page; nothing from it is kept or sent until you press Submit. Your location is read while the page is open so it can show how accurate it is; only the reading at the moment you take the photo is sent. If your phone has a compass, which way you were facing is recorded too (an iPhone asks you first).

Before anything is sent, your browser looks for faces in the photo and marks where it finds them. This runs on your phone; the photo is not sent anywhere for it. Nothing is blurred on your phone: the photo is sent as you took it, faces included, together with the marks.

When you submit a photo, we store, linked to your account:

  • the photo as you took it (not blurred), saved again without its embedded data (camera, date, location),
  • where you were (latitude and longitude), how accurate your phone said that was, and which way you faced if the compass was on,
  • when your location was read, when the photo was taken and when it arrived,
  • the size of your camera’s picture, your answer to “Are there people in this photo?”, and where in the photo your browser found faces (boxes, not pictures of them),
  • when you accepted the license (CC BY-SA 4.0).

Who sees it and for how long: a waiting photo is kept unblurred in private storage that only the site’s reviewers (admins) can open; it and its details are seen only by them, and the photo by you in your list. A reviewer checks it for faces: the marks from your browser show as suggested blur boxes, which the reviewer keeps, removes or adds to. If it is not accepted, the photo is deleted at once; the record without the photo stays so you can see the reason, and it counts toward the limit of 10 photos a day. If it is accepted, the server blurs the boxes the reviewer confirmed and makes a copy (at most 1,600 pixels across, no embedded data) that joins the game; the unblurred waiting file is then deleted, and the position becomes that photo’s answer. Only the blurred copy is ever shown in a game. Like every photo in the game, its position is never shown before a guess. After a guess, players see your username as the credit. The photo stays in the game until it is removed or you delete your account. Reviewers’ decisions (approved, rejected, pin moved, areas blurred) are logged.

Your list of photos on the Contribute page is shown only to you.

If you play as a guest

Solo play works without an account. Your browser gets a random guest code in a cookie (bg_guest, for 7 days) so the game knows your games are yours. We store only a scrambled form of the code, never the code itself.

To stop one person from creating endless guest games, we also keep a scrambled form of your network address (IP address). It cannot be turned back into the address. The records of when guest games started are deleted after a day.

Guest games never appear on the leaderboard and are never attached to an account. A guest and its games are deleted after 7 days without a visit, and signing in forgets the guest straight away.

Cookies and your browser

  • Sign-in cookies, which keep you signed in. They are needed for the site to work.
  • The guest cookie above, only if you play as a guest.
  • Your sound on/off choice, saved in your browser and never sent to us.

There are no advertising or analytics cookies.

Services the site runs on

  • Supabase stores the database, the photos and the sign-in accounts.
  • Vercel hosts the site. Like any web host, it handles your network address when your browser asks for a page.
  • Google handles sign in.
  • OpenFreeMap serves the map. Your browser loads map pieces straight from its servers.
  • The face check on the Contribute page is Google’s MediaPipe, served from this site and run in your browser. It sends nothing to Google.

Each handles data under its own privacy policy. We share nothing with them beyond what running the site needs.

Deleting your account

Go to Settings and choose Delete account. It removes your profile, username, solo games, photo reports and leaderboard entry at once. Photos you contributed are deleted with it, live and waiting: they leave the game, their files are deleted and your credit is removed. Rounds already played on them keep their scores. Versus games stay for the other players in them, with you removed. If you are signed in on another device, that device may show you as signed in for up to an hour, but it can no longer reach your account.

Children

BruinGuessr is meant for university students and is not directed at children under 13.

Changes and contact

If this policy changes, this page will show the new date at the top.

Questions, or a request about your data: contact Daniel Xing on LinkedIn.