Bitebooker

Legal

How we handle your data

What we ask you, when, who receives it and what stays on your device. Written by reading the code, not a template.

Last updated
30 October 2026
Data controller
BITEBOOKER S.R.L.
Registered office
Via Vincenzo Nardi 101, 51100 Pistoia (PT), Italia
VAT number
IT02042780474
For your rights, write to
privacy@bitebooker.it
Certified mail (PEC)
posta@pec.bitebooker.it

This page describes the public Bitebooker site: the restaurant listings, the search, the forms to book or request a table, the reviews and your personal area. It does not describe the software restaurants use internally, which is a different thing with its own rules.

What we ask you, and only when it is needed

Browsing requires nothing. You can look at every listing, filter by city and cuisine and read the reviews without telling us who you are and without any account.

We ask for data at four moments, and at each one only what that thing needs:

  • Booking a table — name, phone, email, day and time, how many people (adults, children, pets), and any note you want to leave the restaurant. Consent to the processing is required: without it we cannot pass your name to the restaurant, so there is no booking. Consent to marketing messages is separate and optional, and is not needed to book.
  • Requesting a table at a place that does not use Bitebooker — name, one contact (phone or email), day, time and how many people. It lets us pass the request along and tell you how it went.
  • Reporting something wrong on a listing — the reason, and an optional note. We do not ask for any contact details: telling us a place has closed should not cost a sign-up.
  • Writing a review — the rating, the text, a title if you want one, and the name to sign it with. This needs an account, because a review is tied to a booking: that is why we can say every review is verified.

If you sign in with Loonar ID we receive your identifier, name and email address from the sign-in service. We never receive or store your password: that stays with Loonar.

If you search "near me"

There is a button that looks for restaurants around where you are, and it only works if you press it: the portal never asks for your location on its own, and does not ask at all unless that button is pressed. Permission is granted by your browser, and can be withdrawn from its settings.

What happens when you press it:

  • your browser gives us your coordinates, and we round them to three decimal places before using them — about 110 metres. That is enough to search within a kilometre and not enough to say which building you are in;
  • the rounded coordinates go into the page address, so the search can be shared and found again with the back button. That means they are also in your browser history and in our server logs, along with every other request;
  • we do not store them anywhere else: they go into no table, they are not attached to your account if you have one, and they do not outlive the page;
  • we do not ask anyone what place that is. We do not turn the coordinates into a street or a neighbourhood name: that would take an outside service, which we would be telling where you are — and that is exactly what this portal does not do.

To turn it off, use "Search everywhere" next to the filter.

Who receives your data

The restaurant. It is the most important line on this page, and it is the only recipient that makes sense: you book to have dinner somewhere, and that somewhere needs to know who is coming, how many of you and at what time.

From that moment the restaurant has your details in its own customer records and answers for what it does with them — its own messages, its own follow-ups, its own mailing list. Requests about that (removing you from its records, finding out what it holds) go to the restaurant, and we cannot make them on your behalf.

We do not sell your data and we do not pass it to anyone unrelated to your booking. If that ever changed, changing this page would not be enough: the product would have changed.

If you link a booking to your account

Linking a booking to your account does not move it and does not change who answers for it: the record stays in the restaurant's files, exactly as if you had never signed in. The link is ours, kept separately, and it does one thing: it lets you find that booking again from another phone.

Three consequences, and they are the reason it is built this way:

  • the restaurant does not see the link. To it you are the name you typed when booking, no more and no less. It does not know whether you have an account, nor whether you have booked elsewhere;
  • you link one booking at a time, and you choose. We link nothing automatically even where we could: the list this browser remembers may hold bookings made by someone else who used the same device;
  • unlinking or deleting your account removes the link, not the booking. That stays with the restaurant, which needs it: it is its evening, its books, its dining room.

It is also why “my bookings” is a *view*, not an archive. We keep the thread; the data stays where it has always been.

If you write down your preferences

In your personal area you can state a few preferences — vegetarian, vegan, gluten free, whether you often go out with children or with a pet, a preferred province. They are closed choices, with no free text, and they exist only if you tick them and press "Save": we do not derive them from your bookings.

  • only Hoomer, the site's assistant, reads them, and only when you are signed in, to choose which places to suggest; when it takes them into account it tells you;
  • the restaurant does not see them, not even when you book;
  • you delete them from your personal area with "Delete all", and it takes effect at once. Turning them all off and saving does the same.

A preference such as "gluten free" may say something about your health: that is why it stays a box you tick and untick yourself, and we use it for nothing else.

What stays on your device

Five things, and none of them reaches us by itself.

  • The «My dinners» list — it lives in your browser's storage, under the key bb:portale:mie-prenotazioni. It holds only what is needed to reopen a page: the type, the booking code, the place, the day and the time. It does not hold your name, phone, email or how many of you were coming. It keeps at most twenty entries and each one disappears by itself sixty days after the booked day. You can empty it at any time from the page itself, and on a shared device you probably should.
  • Two cookies, only if you sign in — bb_sessione holds the session (up to thirty days) and bb_giro lasts ten minutes and exists only to complete the sign-in safely. Both are technical, readable only by our server, and without an account they are never even written.
  • The conversation with Hoomer — it lives in the storage of this browser tab, under the key bb_hoomer_v1, and disappears when you close the tab. It holds what you wrote and the answers, so reloading the page does not lose the conversation, and which of the two ways of suggesting places it is using (see «What we count»). Your messages reach us only when you send them, so that Hoomer can answer.
  • Celebrations already shown — when the table is confirmed the page celebrates only once: to remember it, the browser keeps, under the key bb_feste_v1, the codes of the last twenty bookings or requests already celebrated. Nothing else: no names, no days, no places.
  • Only if you use the app — installed on your phone or downloaded from the stores, the site keeps in a cache on your device the «You are offline» page, the graphic files and a copy of «My dinners» with no personal data (downloaded without signing in), so they open without a connection. Account and booking pages are never stored. In the browser this does not happen.
  • Notices, if you ask for them — only in the app, and only if you tap «Notify me» after a booking, your phone gives us an address to send two notices for that dinner: the table confirmation and the morning reminder. Our server keeps that address with the restaurant, the day and the time of the dinner — not your name, phone or email — and deletes it the day after the dinner, or straight away if the phone says you no longer want notices. The message travels through the phone system's notification service (Apple, Google or the browser's), encrypted: whoever carries it cannot read it. You can turn them off in the phone settings.

There are no profiling cookies, no advertising and no banner to accept, because there is nothing to accept.

What we count

To understand whether the site really helps people find a table, our server keeps a few counters per day and per portal: how many conversations with Hoomer start, how often the page of a place suggested by Hoomer is opened, how many booking or request forms are opened and how many table requests are sent. The bookings made here are already known to the restaurant, which receives them.

  • A counter is just a number that goes up by one. We do not write who you are, which IP address you come from, or any code that would recognise you from one visit to the next: that data is never written, so what one person did cannot be reconstructed.
  • No cookies and no analytics service: the counters are kept by our server, like the rest of the site.
  • Hoomer is trying two ways of suggesting places. At the start of each conversation one is chosen at random; it stays for that conversation and lives only in its memory in this browser tab. We count how many conversations each way had and how many place pages were opened from it, to keep the one that helps more. A new conversation may get the other way.

No third party receives your visit

Measured across ten pages of the site, including the ones where you book and sign in: the browser made 218 requests and every one of them to our own address. None to an analytics service, an ad network, a map, a font archive or a social button. The fonts are served by us, the images are ours.

It means that opening this page tells nobody else that you opened it.

Reviews are public, and can be withdrawn

A published review shows the rating, the text, the title if there is one, the first name only and the date. It does not show the surname, the email, the phone, or which booking made it possible. If you leave the signature empty it appears as «a guest».

You can withdraw it whenever you like from your personal area: from that moment it no longer shows on the listing.

If the published details are yours, and you never gave them to us

We do not write the restaurant listings: name, address and contact details come from public OpenStreetMap map data, where somebody put them. We publish them because this site is a catalogue of businesses open to the public, and a catalogue that only holds whoever signed up is no use to somebody looking for dinner.

On almost every listing those details belong to a business. On some they do not: the number is sometimes the mobile of whoever works there, or the personal mailbox of whoever opened the place. That is a person's data, on a page built to be found by a search engine.

If it is yours, you can ask for it not to be here: at the foot of every listing there is the link «ask us to take them down». You can ask us to remove the whole listing, or the contact details only.

⚠️ The request does not remove anything by itself: that form is open to anyone, and automatic removal would be the quickest way to make a competitor disappear. A person reads it, checks it and replies to the address you left — including when the answer is no, and in that case we say why.

And the fix that lasts is at the source. The map data belongs to OpenStreetMap: corrected there it counts for every site that uses it, not just this one, and it does not come back with the next update of our catalogue.

Your rights

You can ask what data we hold, have it corrected or deleted, restrict its use, receive it in a readable format and object to a given use. You can withdraw a consent at any time, and withdrawing it does not make what happened before unlawful.

You can also complain to the Italian data protection authority (Garante per la protezione dei dati personali).

For requests about what the restaurant did with your data after the booking — its records, its messages — the recipient is the restaurant: we cannot reach into its customer database.

How long

What stays on your device lasts as long as written above: sixty days from the booked day for the list, thirty days for the session cookie, ten minutes for the other one.

On our server there is no automatic deletion. A booking, a table request, a review and the link between a booking and your account stay until somebody deletes them: there is no expiry that removes them by itself. We write it because that is how it is.

Four things are yours to do, and they take effect at once:

  • withdraw a review from your personal area: it disappears from the restaurant's page;
  • unlink a booking from your account: the booking stays, the link goes;
  • delete your preferences from your personal area, with "Delete all";
  • empty the list this device remembers, from its own page.

Cancelling a booking is not deleting it: the table is freed and the restaurant sees the cancellation, but the booking stays on record — the restaurant needs it to know what happened that evening.

Deleting your account is done from your personal area, «Profile» tab: you confirm by typing a word, and for thirty days you can change your mind. After thirty days we delete the links to your dinners, your preferences, the name your friends see and the reviews you wrote, and we close the account. Bookings stay with the restaurants.

To have us delete your data in another way, write to the address at the top of this page. The copy the restaurant holds in its own records is theirs, and has to be asked of them.

If this page changes

The date at the top says when the text you are reading is from. If anything changes that concerns your data — a new recipient, an analytics tool, one more cookie — this page changes first.