← back

privacy

last updated october 2, 2026

howlongistheberryline.com is a small student project that estimates the line at berryline in cambridge, ma. it's not affiliated with berryline or harvard. this page covers everything the site collects, why, and what you can do about it. we don't sell your data, show ads, or send marketing.

reporting the line

reports are anonymous. you don't need an account. when you send one, we store:

  • the headcount you picked and the time.
  • your location (from your browser, with your permission) at the moment you hit submit. we use it to check you're actually near berryline, and keep it to investigate fake reports. it's never shown publicly or included in the api or downloads.

the headcount and time are public: they power the estimate, charts, csv downloads, and api. we keep reports indefinitely, since past reports are what the “how it usually looks” history is built from.

photos

posting a photo requires signing in with a harvard google account. when you post, we store the photo, the thumbnail crop you chose, your caption, the time, and which account posted it.

  • the poster's account is only visible to the site admin, for handling abuse. it's never shown publicly.
  • we strip all metadata from photos when they're uploaded, including the gps location phones embed. we check your location to confirm you're at berryline but don't store it with the photo.
  • photos appear on the site for 3 days, but the files are kept after that and anyone with a photo's direct link can still open it. please only post people who agreed to be in it.
  • if you tick “keep it for daily highlights” when posting, your photo may come back for a day as the daily highlight after it leaves the feed, once we've reviewed it. you can ask us to take it out of highlights at any time.
  • anyone can report a photo, which hides it until it's reviewed, or like one, without signing in. both use an anonymous id cookie (see below) so each browser counts once. like counts are public; who liked or reported what isn't.

signing in

signing in (for photos or an api key) uses google. we store your harvard email address and an api key tied to it. google also shares your name and profile picture with the sign-in, but those stay in an encrypted cookie in your browser; our server doesn't save them. we can suspend accounts that break the rules.

feedback

the feedback form stores your message and, only if you give one, your email address. to stop spam, it also sets the same anonymous id cookie used for photo likes.

cookies and analytics

  • report cooldown: after you report, a cookie stops a second report from your device for 3 minutes, then expires.
  • anonymous id: the first time you like or report a photo, or send feedback, we set a cookie with a random id, so we can count you once and limit spam. it isn't tied to your name, account, or ip address, and lasts a year. we don't store ip addresses at all.
  • sign-in: if you sign in, a session cookie keeps you signed in for up to 30 days.
  • bot check: cloudflare turnstile looks at your browser and ip address to tell people from bots.
  • analytics: vercel web analytics counts page views without cookies and without tracking you across sites.

there are no ad or tracking cookies. our hosting providers also keep standard server logs (like ip addresses and request times) under their own policies.

who handles your data

the site runs on these services, which process data on our behalf:

  • cloudflare turnstile: the bot check on reports and feedback
  • cloudflare r2: stores and serves photos, and scans them for child sexual abuse material
  • google sign-in: harvard sign-in for posting photos and api keys
  • vercel: hosts the website and runs its cookie-free analytics
  • render: hosts the backend that receives everything you submit
  • supabase: the database everything is stored in

we'll only share data beyond that if the law requires it, or to deal with serious abuse of the site.

your choices

  • you can use the site, see the estimate, and report the line without an account.
  • you can deny location access, but then you can't send reports or photos.
  • you can ask us to delete your photos, your account and api key, or feedback you sent with your email. we can't find or delete individual reports, since they aren't linked to you.
  • you can ask what we have tied to your email.

changes and contact

if what the site collects changes, we'll update this page and the date at the top.

questions or requests: email igzcodes@gmail.com or use the feedback form (leave your email so we can reply).