Plain terms
What Where2Resto does with information while it settles a night out
This site does one narrow job: turn an unresolved argument about dinner into a single name worth proposing, with a second held in reserve behind it. A tool that small moves far less information than a booking platform or a delivery app, and the paragraphs below set out what there is.
Being small is not a reason to say nothing. Someone reading a shortlist on a phone with the group waiting, and someone who runs a room that turns up on one of those shortlists, should both be able to find out in a couple of minutes what is involved when this site gets used.
What follows is an explanation, not a contract. It does not replace the law that applies where you live, and where a statute is more precise than a sentence here, the statute is the one that governs. The whole aim of the page is that an ordinary visitor can read it to the end and know where they stand.
Last updated , and that stamp only moves when the wording underneath it does.
Three kinds
What kinds of information may show up when you use this site
Broadly three kinds, set down in ordinary words rather than in the vocabulary of a technical document. Saying there is none at all would be the comfortable answer and also a false one.
- What arrives with the request itself. A browser states a few plain facts about itself in the act of fetching a page, here and on whatever you were reading a minute ago. None of it waits on you tapping a control; it has already happened by the time this paragraph is on screen.
- What you type in to describe a situation. The pages that narrow a night down ask you to write the evening out: roughly how many are coming, what the occasion has to protect, the line somebody keeps repeating in the group chat. Write in about a plan instead and the message carries whatever you chose to put into it, and nothing else.
- What is already public about a venue. A room's name, where its door is, what it cooks and the score diners have left it sit on the public record long before any of that reaches a shortlist here. Being listed makes a restaurant no more private than it was, and nothing personal about you is fastened to it.
The site does not ask for more personal detail than it needs to run those flows and to answer a message where an answer is possible. Describing a Friday for eight people does not require you to say who you are, and nothing on a decision page asks for anything the decision does not actually turn on.
The purposes
What the information is actually used for
Four uses, written out so nobody has to imagine a fifth one waiting quietly behind them.
- Running the site. Pages have to load, a shortlist has to come back while the group is still arguing about it, and the link through to a venue has to arrive where it says it will.
- Answering people who write in. A note about a plan that fits none of the main flows, or about something wrong on a listing, only gets a reply because a person can read it and respond.
- Keeping the place safe to use. Abuse, floods of junk and attempts to break something get noticed here the way they get noticed anywhere: the traffic stops looking like people trying to settle dinner.
- Seeing which pages help. Knowing that one route ends with a group walking somewhere and another ends with a closed tab is how the questions on these pages get sharper.
Descriptions of an evening and notes about what worked are read for the pattern, not for the person. They change which questions a decision page asks and how it words them. They are not gathered into a profile of any individual diner, and no shortlist on this site is assembled out of something it thinks it knows about you personally.
Care and change
What keeps information safe here, and when this wording changes
Reasonable care, scaled to what this service honestly is, plus a straight note about the fact that these sentences are not permanent.
Protection starts by asking for less. What is never collected cannot be lost, so the flows stay short and the questions stay about the meal rather than about you. Whatever does exist stays with the people who operate the service and is reachable by those who need it to do that work, rather than sitting open to anyone who happens to be around.
No particular tool or supplier is named on this page. Naming one would be out of date the week it changed, and it would tell you less than the principle does: hold a small amount, keep the reach around it narrow, and treat anything a visitor typed in as theirs rather than ours.
These sentences can change. Sites get rebuilt, a flow gets reworked, and the description has to move with it. Whatever is published here at the moment of your visit governs that visit. No earlier draft survives somewhere else with the power to override it, and the stamp at the top marks the last time any of this was edited.
If privacy is something you weigh carefully, read this page again before your next visit rather than trusting the version you read once.
Ask a person
If you need to ask about how information is handled
One route in, the same route every other page here sends you down. No separate privacy channel gets stood up beside it, because a single address is the one people actually remember.
Go in through Tell us about a tricky plan, the page where anything the main flows do not cover already ends up, or write directly to [email protected]. Open with the words that this concerns privacy. Flagged that way, a note is handled as a privacy matter rather than sorted in with suggestions about rooms that belong on a shortlist.
Then keep the note to what the question needs. You do not have to attach documents, account details or anything sensitive to ask how information is treated here, and a message about privacy should never be the reason more of it arrives.
