Privacy

How privacy works around these menu pages, in plain words

Last updated

A site has to move a small amount of information about before it can do anything at all. Some of it arrives on its own the moment a browser asks for a page, and some of it exists only because you decided to write to us and put it there yourself. This page sets out in general terms what those two piles are, what they get used for, and where the using stops.

It is written the way the rest of this site is written: the same plain wording we use for cravings and menus, and roughly the same length. No column of defined terms, no sentence built to be read twice, nothing dressed up to sound weightier than it is. If you can read a menu you can read this, and that is deliberate.

Three piles, no more

What information may sit around when you use this site

Three broad sorts of thing turn up around a guide like this one: what a browser hands over by itself when it asks for a page, what you choose to type into a message if you write in, and the public detail already printed on the venue listings you came here to read.

What a browser hands over by itself

Asking for a page is a request, and a request carries ordinary technical detail with it: which page was wanted, roughly when it was wanted, and enough about the browser and the screen for the right version of the page to come back. You do not type any of that, and nothing here asks you to.

What you choose to put in a message

Write in and the note holds whatever you decided to put in it. The form on the page for venue teams asks for a venue name, a link to the menu and an address to reply to; a plain email holds only what you typed. Either way the contents are your call, line by line.

What is already public on a listing

Venue names, the kind of room, addresses and the menu wording itself are public facts, published by the places that cook the food. They sit here so a craving has somewhere to land, and they describe kitchens rather than the people reading about them.

None of it is gathered to assemble a picture of you for advertising somewhere else, and none of it is stitched into a profile that follows you off this site. The work here is keeping menus readable and answering the people who write in, and the information involved is not asked to do anything beyond those two jobs.

Two jobs only

What this site does with information and what it refuses to do

The second half of that heading is the half worth reading twice.

Everything described above is put to two uses, and both of them are the dull kind.

Keeping the pages upright

Technical detail is what keeps a site standing: pages that load, images that arrive at the size their frame expects, and enough of a trail to spot a broken route or somebody hammering the server before too many readers walk into it. Read in that spirit it is maintenance, not watching.

Reading what you actually wrote

A message gets opened, read and, where it needs one, answered. The address you wrote from is used to write back to you and for nothing else. A note about one menu is not treated as a standing invitation to send you anything later on.

What it is never treated as is stock. Nothing that passes through here is sold, rented, traded away or handed to anyone running a marketing campaign of their own, and no part of it is priced up as a product. That is a flat refusal rather than a setting, so there is nothing here for you to go and switch off.

If something worries you

How to raise a privacy question that can actually be acted on

There is no separate channel for this and no hidden form to hunt down. Anything you want to ask about how information is handled travels the same route as everything else: the address printed at the foot of every page here, and set out again on the page for venue teams.

Write to cravings@wheretomenu.com and say plainly what is on your mind. A question about how something works is as welcome as a complaint, and neither needs a formal opening to be taken seriously.

Worth putting in the note

  • What you were doing at the time

    The page you were on, roughly when, and what you had just clicked or typed. A concern anchored to one moment can be traced; the same concern described in general terms usually cannot.

  • What it was that worried you

    Name the thing itself rather than the feeling around it: something that looked like it had been kept, something that turned up where you did not expect it, a message you thought had gone nowhere. The specific version is the one that can be answered.

  • What you would like to happen

    An explanation, a correction, or a message removed from the pile. Saying which of those you are after saves a round of asking and gets you to the answer a good deal faster.

You will get a reply from a person who has read the whole note, not a receipt. If the answer is that something needs fixing, the fixing happens first and the reply says what changed.