Privacy.

Analytics.

We use Google Analytics 4 to see which guides and features people use. It loads only on glutenfreestadiumfood.com, not on preview copies, and not for automated browsers. It uses cookies to tell one visit from another.

It records page views and a few actions: searches (the words you typed and how many results came back), the filters you choose, whether Near me found a location, taps on a venue phone number or email, which map sections you select, whether you open or send a report or photo form, and whether the menu alert sign-up was on screen, opened from the guide header or the bar at the bottom of a phone screen, started (the first keystroke, not what you typed), left unsent, or sent, and on which kind of page, whether that bar showed or you closed it, whether you printed a game-day card, whether you ticked the tailgate checklist or printed it, and whether a game-day card kept on your phone, linked from an alert email or opened with Show my card opened, or you removed it. Each event carries the page you were on, and the sign-up, bar and card events say which of the two sign-up versions the guide had. It never receives what you type into a report, photo or sign-up form, and it never receives your coordinates.

We also use PostHog, in cookieless mode, to count page views and a few actions: menu alert sign-ups the server accepted, results from Find food near your seat, search and Near me, a game-day card opening (kept on your phone, linked from an alert email, or opened with Show my card), a first tick or a print of the tailgate checklist, and shares. For the menu alert sign-up it also counts when the form is on screen, a tap on the button or bar that brings it into view, whether that bar showed or you closed it, the first time you type in its email field, and, if you then leave the page without signing up, whether the field had anything in it and how many seconds had passed. Half the guides show the game-day card before the sign-up, and these counts say which of the two versions the page had. It never gets what you typed. It sets no cookies and keeps nothing on your device. When one of this site’s own scripts fails, it also gets the kind of error (such as TypeError) and the script file, function name and line where it happened, never the error’s text or anything you typed. When you press the button to confirm menu alerts, our server tells PostHog that a sign-up was confirmed and for which guide, with no email address and not your IP address. It never gets your search words, email address or coordinates. Page addresses are sent without the part after ? or #, and of the campaign tags in an address, only utm_source, utm_medium and utm_campaign are kept. PostHog receives your IP address only to make a daily cookieless hash and does not store it. A link you copy or share with a page’s Share button ends in utm_source=share, utm_medium=referral and the kind of page, so both tools can count visits from shared links; you can delete that part of a copied link before you paste it. It does not load at all if your browser asks not to be tracked (Do Not Track or Global Privacy Control), or for automated browsers.

Your location.

ZIP search runs in your browser. The page downloads a small public file for the first two digits of the ZIP, so our host can see those two digits but not the full ZIP or what else you typed. Near me asks your browser for your location and uses it on your device to sort venues by distance. We do not receive or store it.

If your device can’t share a location, the page asks GeoJS (get.geojs.io) for an approximate area based on your IP address. GeoJS sees that request. Your browser also remembers, on your device only, the map section you pick on a guide; each guide whose game-day card you opened or got after signing up (the page, the day and, for a guide, whether the card came with a sign-up, never your email) and a copy of that public guide page for use without signal, so the card opens again when you come back, until you tap Remove under the card; which items you ticked on the tailgate checklist, until you tap Clear ticks; and, until you close the tab, that you closed the card bar or signed up from a guide, so the bar stays away.

Reports and food finds.

A report records the guide, the item, the status you chose, an optional stand or section, an optional visit date, an optional email address, and the time. A food find adds the food name, how it was described, and an optional link and details. We store these in a Cloudflare database and check each one by hand before a guide changes. Please leave out personal information.

A report we approve appears on its guide as one line beside the item, such as “A fan found it on Oct 18, 2026,” and the guide shows the date of its latest fan report. It never shows your stand text, your email address, or anything else about you. If you add an email address, we use it once: when your report is on the guide, we email you a link to it and delete the address. We delete it sooner if we do not publish the report, and after 90 days in any case. It is never added to menu alerts. Cloudflare sends this email for us.

To limit abuse, each client gets an hourly cap on reports and food finds. The cap is counted against a one-way hash of your IP address and the hour. We do not store your IP address with a report.

Menu alerts.

If you sign up for menu alerts on a guide (the game-day card sign-up), on a venue’s vegan or peanut-allergy page, or pick a venue on a league or stands page, we store your email address, that venue’s guide or page, and the time in a Cloudflare database. The game-day card is built from the guide in your browser. Your browser keeps which guide it was for and a copy of that guide, so it opens again there (see Your location above); we store nothing about the card. We use your address only to email you about changes to the guides or pages you chose, at most once a week for each. Links in those emails carry utm_source=menu_alert so we can count the visits they bring; they carry nothing that identifies you. Right after you sign up, we send one email asking you to confirm. Alert emails go only to confirmed addresses. An unconfirmed sign-up is kept and gets no alert emails until it is confirmed. Every email has a link to stop. Cloudflare sends these emails for us.

Sign-ups have the same hourly cap per client as reports. We never share or sell your address. To delete every alert for your address now, enter it here.

Done. Alerts for that address are deleted.

Menu photos.

Your browser re-encodes a menu photo before upload, and our server rebuilds the file from its image data only. That removes EXIF data, including GPS location, camera details, and embedded thumbnails. The photo and your optional caption go into private Cloudflare storage and wait for review.

Approved photos appear on the guide with their caption, venue, and date. Rejected photos are deleted from storage. Photo uploads have a daily cap per client, counted against a one-way hash of your IP address and the day. Crop out faces, tickets, and anything personal before you send.

Hosting.

Cloudflare hosts and serves the site. Like any web host, it sees the technical details of each request, such as your IP address and browser.

This weekend's games come from ESPN's public scoreboard. Our server asks ESPN for the day's games; your browser never contacts ESPN, and ESPN receives nothing about you.

Restaurant maps.

The map of gluten-free restaurants near a venue loads only when you tap Show on map. Then your browser downloads map images from OpenStreetMap (tile.openstreetmap.org), which sees that request, including your IP address and the area on the map. Until you tap, the page sends nothing to OpenStreetMap.

What we don’t do.

No ads. No affiliate links. We do not sell or share your data for marketing. We do not ask you to make an account.

This site has no email address of its own. Menu alerts and the one thank-you for a published report are the only emails it sends. To correct a guide, use Report next to a listed item, or Share a food find or Add your menu photo on the venue guide.