Privacy

Last updated 4 October 2026.

Eat Featured is a map of places featured on food TV and by food creators online. This page says what we collect when you use it, who else sees anything, and how to ask us to delete what we hold. It's written plainly on purpose.

The short version

Browsing the site is counted by a cookieless analytics tool — it tallies visits and which parts of the site people use, sets nothing on your device, and can't follow you across sites. What it records is aggregate: counts, not a profile of you. The times we store something you'd recognise as your own are when you send us a restaurant suggestion, when you join the early-access list for the app, and when you send us feedback through the contact form — in each case we keep only what you gave us, plus two small anti-spam details described below, and we delete the throwaway ones on a schedule.

When you browse

We use Plausible Analytics to see whether the site is useful: how many people visit, and which parts they use — opening a venue, building a road trip, running a search. It is cookieless. It sets nothing on your device, does not fingerprint you, and cannot follow you from this site to another. Everything it records is aggregate — counts, never a profile of you — and it never receives anything you typed; the only detail sent with an action is a public identifier the venue or show already has in its web address. We keep these aggregate figures for as long as we run the site, and because none of it is personal to you, there is nothing about you in it to hand back or delete. Plausible's own privacy policy is at plausible.io/privacy.

Loading a page also means your browser talks to a few other services, and like any web request that includes your IP address:

Netlify, which hosts the site.
Supabase, which serves the restaurant data.
Cloudflare, which runs our own map server and serves the map tiles you see. The map is drawn from OpenStreetMap data, but we keep our own copy, so your browser never contacts OpenStreetMap.
Plausible, which counts the aggregate usage described above.
Google Fonts, which serves the typefaces.
YouTube's image server, for the still picture on a venue that has a video (see below).

Each of those has its own privacy policy. We don't send them anything about you beyond the request itself. The code that draws the map comes from our own site, so no other service is asked for it.

Some venue locations come from the Overture Maps Foundation's open map data. We keep a copy of it on our side, so your browser never contacts Overture.

When you press play on a video

Some venues carry the video that featured them. Pressing play loads that video from YouTube (Google) in YouTube's privacy-enhanced mode, which YouTube says does not use its cookies to personalise what you see. Nothing plays until you press play: before that the page shows only a still picture of the video and a play button. That picture comes from YouTube's image server, so showing it is already a request to YouTube. Once you press play, your browser talks to YouTube directly, and that request — like any web request — includes your IP address; what YouTube does with it is governed by Google's privacy policy. We don't tell YouTube who you are, and we don't receive anything back about you from it.

When you save a place

Saving a place stores a short identifier for it in your own browser; it is not sent to us and is not shared. That identifier is all that is kept - the place itself is looked up fresh each time you open your Saved list.

When you plan a road trip

The route planner sends the start and the destinations you type (up to five), and the route between them, to a routing and geocoding service (openrouteservice, run by HeiGIT) through our own server — so that service sees our server, not you. Nothing about a route goes to any other third party. We don't store your route or your towns.

When you search by ZIP code

Searching by ZIP code reads a file from our own site (in the app, from your phone); the ZIP you type isn't sent anywhere.

In the iPhone app

The app shows the same places as the site and keeps a copy of the catalogue on your phone, which it refreshes from our site. It has no account. Near me asks for your location only when you tap it, uses it on your phone to sort places and move the map, and never sends it anywhere. Places you save and trips you save stay on your phone. Planning a trip sends the start and the destinations you type (up to five) to our server, which looks them up with openrouteservice, the same as on the site; we don't store them. Videos, map tiles and the pages the app opens (these terms, this page and the contact page) load from the same services this page names for the site.

When you suggest a restaurant

The suggestion form is paused right now, so there is nothing new to send. This section still describes what we hold from suggestions sent before the pause — that data is unchanged and governed exactly as below.

If you use the suggestion form, we store what you type: the restaurant, city, state, show, dish, a link if you gave one, and your message. If you give us an email address so we can reply, we store that too.

We also store two things you didn't type:

A hashed version of your IP address. Not the address itself — a one-way fingerprint of it, salted, that we can't reverse. We use it only to stop the form being flooded.
Your browser's user-agent string, for the same reason.

How long we keep it

The restaurant details — name, city, show, dish, link, message — we keep as part of our research record, since they may become a listing.
Your email, the IP hash, and the browser string are deleted 90 days after your suggestion is reviewed, or after 12 months if it's never reviewed. This happens automatically.

What we do with your email

Two things, and only these: an automatic note confirming we received your suggestion, and — if the place makes it onto the map — a message to tell you. We don't add you to a list. We don't share it.

When you join the early-access list

The iPhone app is free and needs no account. If you ask us to tell you when it launches — using Get early access on the home page, or the sign-up on a page for a place that has closed — we store your email address so we can do exactly that.

We also record, and neither of these is personal to you: which of those two places you signed up from, and — if it was a closed venue's page — that venue's public web-address name, so we can learn which places make people want the app.

To stop the form being flooded we store the same two throwaway things as the suggestion form: a salted, one-way hash of your IP address (not the address itself) and your browser's user-agent string.

How long we keep it

Your email we keep until the app launches and we've told you, or until you ask us to remove it — whichever comes first. It is used for one thing only: telling you the app is ready. We don't add you to any other list.
The IP hash and browser string are deleted 90 days after you sign up. This happens automatically.

What we do with your email

Only this: a single message when the app launches. We don't sell it, rent it, or share it, and we won't email you about anything else.

When you send feedback

There's a contact form — reached from the footer, or from a "Something wrong here?" link on a venue's page — for telling us something's off, asking a question, or letting us know when a place closed. We store your message, and — only if you fill it in — the email address you give so we can reply. There's no name field and no subject box.

If you sent it from a specific venue's page, we also store that venue's public web-address name, so we know which place your note is about. If that link was out of date and the venue isn't one we recognise, we simply drop the reference and keep your message.

To stop the form being flooded we store the same two throwaway things as the other forms: a salted, one-way hash of your IP address (not the address itself) and your browser's user-agent string. We don't use a captcha, so nothing about you is sent to a third party to prove you're human.

How long we keep it

The IP hash and browser string are deleted 90 days after you send the message. This happens automatically.
Your message and email stay while we're still dealing with it — you can't reply to a thread that's been erased. Once it's resolved, or if you ask, we remove them.

What we do with your email

Only this: a reply to what you sent, if you left an address. We don't add you to any list and we don't share it.

When a creator sends us their places

Some food creators we work with send us the places from their videos through a private link we give them, with no account and no sign-in. For each place we store what they type: the video link, the restaurant's name, its town, and an optional dish and note, filed under the creator the link belongs to. We keep the video links as links: we don't download or read anything from them.

To stop the form being flooded we store the same throwaway things as the other forms: a salted, one-way hash of the IP address (not the address itself) and the browser's user-agent string.

How long we keep it

The IP hash and browser string are deleted 90 days after the list is sent. This happens automatically.
The places are kept: a person checks each one before anything reaches the map, the same way as every other place on the site.

Who we share with

Nobody. We don't sell, rent, or share what we hold. The services named above receive only what's needed to serve the page or plan a route.

Your rights

You can ask us at any time to tell you what we hold about you, or to delete it. Email support@eatfeatured.com and say which suggestion it was (the restaurant name and roughly when you sent it is enough). We'll do it and confirm.

If you're in the EU, UK, or California, you have specific rights under GDPR, UK GDPR, or the CCPA. The paragraph above is how you exercise them; the answer is the same for everyone.

Backups

Each night we save a copy of our database in case something goes wrong. The times on this page are when we delete things from the database itself. Copies made before then stay in our past backups, which are kept privately and are not used for anything else.

Children

The site isn't aimed at children under 13 and we don't knowingly collect anything from them. If you think a child has sent us a suggestion with their email, tell us at the address above and we'll delete it.

Changes

If this page changes in a way that matters — new data collected, a new service that sees your requests — we'll change the date at the top and say what changed. We won't quietly widen what we collect. On 7 September 2026 we added cookieless, aggregate analytics (Plausible) and named it above, and added the early-access sign-up list for the app, described under "When you join the early-access list." On 8 September 2026 we added a contact and feedback form, described under "When you send feedback." On 10 September 2026 we said what happens when you press play on a video, under "When you press play on a video". Later the same day we added saved places, under "When you save a place" — the list lives in your browser and never reaches us. On 22 September 2026 we named the Overture Maps Foundation as a source of venue locations; your browser never contacts it, so nothing about you changed. On 24 September 2026 we corrected this page in two places. The map tiles come from our own map server, run on Cloudflare, not from OpenStreetMap, and the code that draws the map now comes from our own site rather than from another site. And the still picture shown before you press play on a video comes from YouTube's image server: we had said nothing loads from YouTube until you press play, and that was wrong. On 30 September 2026 we added "In the iPhone app", which says what the app keeps on your phone and what it sends, and corrected the early-access section: the app is free and needs no account, where we had said it would be a paid product. On 1 October 2026 we added "When a creator sends us their places", for the private link some creators use to send us places. On 3 October 2026 we said that a road trip sends the start and up to five destinations you type, where we had said the start and end, on the site and in the app, and added "When you search by ZIP code". On 4 October 2026 we added "Backups", under "Your rights": the times on this page are when we delete things from our database, and copies made before then stay in our past backups.

Contact

support@eatfeatured.com

This notice is written in plain language rather than legal language. It is not a substitute for legal advice; if the site's data handling grows beyond what's described here, it should be reviewed by someone qualified.