Things worth knowing
Reservations are never public. They hold a stranger’s name, telephone number and plans for Saturday night, so they have no URL at all and are only visible in wp-admin.
Every request is saved before any email is sent. Shared hosting loses mail regularly. If an email never arrives the request is still under Reservations, which is the copy that matters.
If your notification emails do not arrive, install an SMTP plugin and send through a real mail service. This is true of every WordPress site and is not something a theme can fix.
The board is right even when your page is cached. A caching plugin keeps whatever the server printed; Counter prints the boards for the next day or so with the times they start, and a small script changes the board when your visitor’s clock passes one. Without the script, the server’s board stands.
The dietary filter and the large-party swap use no JavaScript. The one small script adds the niceties (the header tightening as you scroll, the board’s letters settling when it changes, the print button, the booking summary) and everything works without it. Nothing moves for visitors who ask their device for reduced motion.
Menus, journal entries and reservations survive a theme change. The screens for editing them do not, they are part of Counter. That is the trade-off for one self-contained theme with nothing else to install.
Somebody asks for their data
Tools → Export Personal Data and Tools → Erase Personal Data. Type the email address, and WordPress will collect every reservation request sent from it, name, telephone, the day and sitting, allergies, the message, or delete them outright.
The whole record goes when you erase. A reservation stripped of who it was for is not anonymised data, it is a row nobody can use.
Settings → Privacy has suggested wording for your privacy policy, written for a restaurant taking table requests: what a request keeps, your guests’ rights under the UK and EU GDPR and US state laws such as California’s, and that the site sets no cookies. Fill in the two parts in square brackets (how long you keep requests, and your regulator) and edit the rest to match what you actually do. It is a starting point, not legal advice.
There is no automatic clear-out. If you want to keep less, delete old requests from the Been and gone view, but that is your decision to make, not the theme’s.