ReserveInbox

Your guests. Your data. On your server.

ReserveInbox stores reservations and guest data where your website runs – not in someone else’s cloud.

Architecture

Where the data lives – and what leaves.

  • Console and booking form run inside your website on your server; the staff app connects only to that address.

  • Push notifications to staff go from your server straight to the Apple and Google services.

  • Feedback from the app – with a screenshot if wanted – goes to the venue’s inbox and can be forwarded to the maker.

Access

Devices, not passwords.

  • Each device is enrolled once with a company code; there are no passwords and no user accounts for staff.

  • Only a checksum of the code is stored, codes expire, and every device can be signed off on its own.

  • What a device may see is set by its seat – about twenty permissions from service to guest export.

Protection in operation

Protection while you operate.

Spam protection

Several independent checks in the booking form and a limit per network.

A log of every change

A log that only grows; every write from the app counts exactly once.

Sealed allergy notes

Stored sealed with consent, shown to the kitchen with an access log, erased by destroying the key.

Retention, export, erasure

You set the periods; on erasure only the date, time, service and status of a booking remain.

Consent per booking

Every booking stores the consent and the version of the privacy notice.

Public deletion page

Every installation comes with an account and data deletion page, reachable without signing in.

reserveinbox.com

This website.

  • reserveinbox.com sets no cookies and loads no fonts, scripts or images from other servers.

  • Your choice of light or dark design stays only in your own browser’s storage.

See ReserveInbox in a personal demo.

We show you the console and the staff app with demo data.

Less admin. More hospitality.