Privacy policy

Effective September 18, 2026.

Who we are and what this covers

Banquette (“Banquette”, “we”, “us”) makes software that restaurants, private clubs and event venues use to run their private events. This policy covers this website, banquette.events; the Banquette console that restaurant staff sign into; and the private pages that a restaurant’s clients and guests open from a link the restaurant sends them — to sign a contract, manage a party, or answer an invitation.

Two roles

For this website and for staff accounts, Banquette decides how personal information is used, and this policy describes it.

For the event records a restaurant keeps in Banquette — its clients, hosts, guests and vendors — the restaurant decides. We store and process that information on the restaurant’s behalf and only to provide the service to it. If you are a guest or a host of a restaurant that uses Banquette, the restaurant’s own privacy practices apply to you as well, and it is the first place to take a question about your booking. You can also write to us, and we will pass your request to the restaurant and help it answer.

This website

banquette.events does not ask for, collect or store information about its visitors. It sets no cookies and runs no analytics, advertising or tracking scripts, and its fonts are served from our own domain. The “Book a tour” form does not send anything to us: it opens a message in your own email program, and nothing reaches Banquette unless you choose to send it. If you do write to us, we keep your email so that we can reply.

Like every website, this one is served by a hosting provider (Vercel), whose systems necessarily handle technical details of each request — such as your IP address and browser type — in order to deliver the page.

What the Banquette console holds

Staff accounts

Restaurant staff sign in with Google. We receive your name, email address, Google account identifier and a link to your Google profile picture. We never see your Google password, and the sign-in token Google issues is checked and then discarded, not stored. Your account also records the restaurant you work for and your role there. We keep a record of administrative changes to accounts — for example, who was given which role, and when.

Event records a restaurant keeps

Depending on how a restaurant uses Banquette, its book can include:

• Clients and contacts — names, email addresses, phone numbers and the staff’s notes on an inquiry or booking.
• Events — dates, times, rooms, guest counts, menus, notes, and the contact the event is booked under.
• Contracts — the host’s name and email address, the terms and the amounts.
• Guests — a guest’s name, email address, number of seats, reply to the invitation, and any dietary or allergy note.
• Vendors — contact names, email addresses, phone numbers and insurance expiry dates.
• Payments — amounts, methods and status, as staff record them. Banquette does not currently process card payments and does not store card numbers.
• Documents — photos, scans and PDFs a restaurant uploads, such as event orders.
• Imports — when a restaurant brings its existing events book into Banquette, the records it imports.

Dietary and allergy notes

A dietary or allergy note can reveal something about your health. It is collected so the kitchen can serve you safely, and it is shown to the restaurant’s staff for that purpose. When a host manages their guest list, Banquette shows the host only that a guest has left a note — never what the note says.

Contract signatures

When a host signs a contract on their private page, we record the name they type, their email address, the date and time, the IP address and browser details of the device used to sign, and a fingerprint of the exact terms signed. This is the record that shows who agreed to what, and when.

Calendar subscriptions

Staff can subscribe their calendar app to the restaurant’s upcoming events through a private link. We record the name they give the device and when the link was last used.

Private links

Signing a contract, managing a party and answering an invitation all happen on private pages reached by a link, without an account. Anyone who has the link can open the page, so please treat it like a key. We store only a one-way fingerprint of each link, never the link itself, so a copy of our database could not be used to open your page. Links expire — a signing link 30 days after it was last sent; a host’s or guest’s link 30 days after the event (a host’s link stays open while a balance or a credit stands, up to a year after the event, and past that year only while money is still moving: each recorded payment, or an installment still to come, holds it open another 30 days); a calendar link after 90 days unused, or 400 days at most — and the restaurant can revoke any of them at any time.

Cookies and your browser

The console uses a single cookie, banquette_session, to keep a session — a staff sign-in, or the anonymous walkthrough the public demo offers, which identifies no one. It lasts 12 hours, cannot be read by scripts on the page, and is used for nothing else. The console also remembers a few conveniences in your browser’s own storage, such as the restaurant and role you last chose. The private signing, host and invitation pages set no cookies. Banquette uses no advertising or tracking cookies anywhere, so there is nothing for a “Do Not Track” or Global Privacy Control signal to switch off.

How we use information

• To provide the service: to keep a restaurant’s book and show it to its staff.
• To send the emails a restaurant asks us to send — a contract to sign, a host’s link, a guest’s invitation.
• To sign staff in securely, and to keep a record of signatures and of changes to accounts.
• To answer you when you write to us.
• To keep the service secure and working.

We do not sell or rent personal information, share it for advertising, or pass it to data brokers, and we do not use it to train artificial intelligence models.

Who we share it with

We use a small number of service providers, each only to run Banquette:

• Vercel hosts this website, the console and our servers.
• Neon hosts our database.
• Google provides staff sign-in.
• Resend delivers the emails a restaurant sends through Banquette, using Amazon Web Services. It receives the recipient’s address and the message, which carries the recipient’s private link. These emails come from the restaurant, and replies go to the restaurant staff member who sent them.

Within a restaurant, its staff see its records according to their role, and no restaurant can see another’s. We will disclose information beyond this only if the law requires it.

How long we keep it

Event history — bookings, contracts, signatures and payments — is a business record, so Banquette keeps a restaurant’s records for as long as the restaurant uses Banquette. In everyday use, records are retired rather than erased, so the history stays honest: a guest removed from a list, or a contract that was voided, stays on file marked as such. When a restaurant removes an uploaded document, the file itself is destroyed at once; a note that it existed — its name, size, and who removed it — remains.

We do not yet delete records automatically after a fixed period. When a restaurant stops using Banquette, or when we receive a verified request, we will delete or de-identify the personal information concerned, except what we must keep to meet a legal obligation — a signed contract, for example. Copies can remain in our database provider’s short-term backups for a limited time before they are overwritten. Private links and sign-ins expire as described above.

How we protect it

• Every connection to Banquette, and to our database, is encrypted in transit.
• Each restaurant’s records are separated from every other’s by the database itself, not only by the application.
• Private links are stored only as one-way fingerprints, and they expire.
• Staff sign in through Google; Banquette keeps no passwords.
• Our software keeps no request logs; our hosting provider retains short-lived technical logs of requests in order to run the service.

No system can be perfectly secure. If we learn of a breach affecting your information, we will tell the restaurants concerned, and you where the law requires, without undue delay.

Your choices and rights

You can ask us for a copy of the personal information we hold about you, ask us to correct or delete it, or object to how it is used. Write to hello@banquette.events and we will answer within 30 days. If your information is part of a restaurant’s records, we will work with that restaurant on your request, since it decides how its records are used. For staff accounts the same right applies with one limit: on a verified request we de-identify a staff member’s account records, except where the append-only history of administrative changes, or a legal obligation, requires the record to stand — and the part of our software that does this is still being built. Depending on where you live, laws such as the GDPR or California’s privacy law may give you further rights; we will honour them, and we will never treat you differently for using them.

Where information is stored

Banquette is operated from the United States, and the information we hold is stored and processed in the United States.

Children

Banquette is software for businesses and is not directed at children. We do not knowingly collect personal information from children under 13 through this website.

Changes to this policy

When we change how we handle personal information, we will update this page and its effective date, and we will tell the restaurants that use Banquette about any significant change before it takes effect.

Contact

Questions, requests and concerns: hello@banquette.events.