Your guest list is yours. Here is exactly what that means.
Including the parts we have not built. A data page that only lists what works is the one you cannot check.
True today
Each of these is true in the product today.
Export your book as a spreadsheet, whenever you like — n8rhood's bookings, your walk-ins and the bookings you recorded from phone, WhatsApp or Instagram, each marked with where it came from, with its date and time and who took it — with your guest book, each guest's visits split between n8rhood's bookings and your own, the history of changes n8rhood has recorded to each booking, the fees we charged you, and your menu costing, stock and sales if you keep them in n8rhood.
Bookings are matched to your venue by its id. An older booking that carries only a venue name is included only when no other venue on n8rhood has that name: the export refuses to guess rather than put someone else's guests and phone numbers in your file. Whenever that leaves a booking out, each sheet says how many and why.
An owner only ever reaches their own venue's data — every read and write is checked against a real ownership row, never a display-name guess. The n8rhood team can reach every venue's data; that we use it only for support you ask for is a promise, not a control, because the team's access is not logged yet.
Guest contact details are never shown to another venue. A booking is scoped by venue id; an older one that carries only a venue name is matched by that name only while no other venue shares it.
Every change to a booking's status, table, note or headcount is recorded, wherever in n8rhood it was made, and so is every walk-in seated on Tonight or from the waitlist — including a change a colleague's newer one overruled. Not in that log yet: a party added to the waitlist, or taken off it without a table.
Not built yet
Named here rather than discovered during an audit. None of these is written in the present tense anywhere on this site.
- A consent log — recording which guest agreed to what, and whenOn the roadmap
- A self-serve deletion endpoint for a guest recordOn the roadmap
- Regional data residency — choosing which country your data sits inNot built
- A read log showing who on your team opened which guest profileNot built
- A signed Data Processing AgreementOn the roadmap
What the biggest competitor's contract says
Worth reading before you sign anyone's, including ours. SevenRooms assigns ownership of Client Information to the client — and carves out an exception where the venue uses the DoorDash Reservation Marketplace, which is now the same company.
SevenRooms — Master Services Agreement · 2026-08-24 — Read their agreementOur own terms
Tables has no terms of its own yet, and no venue pays for Tables until it has. If you have claimed a venue on n8rhood, you are under the n8rhood owner terms you accepted then — versioned, and stored against your venue.