Data processing agreement
Last updated 24 August 2026.
Roles
The restaurant is the controller for guest, reservation and staff data it processes through DinnerBoost. DinnerBoost is the processor and acts only on the restaurant's documented instructions, which are the product features it uses.
Subject matter and duration
Processing covers QR menu delivery, order taking, waiter and kitchen workflow, reservations and waitlist, guest feedback and aggregate analytics. It lasts for the duration of the subscription.
Categories of data
Order contents and notes, table and session identifiers, optional guest ratings and comments, reservation names and phone numbers entered by staff, and staff account data (email, display name, role, activity timestamps). No payment card data and no special category data are processed.
Sub-processors
Supabase (database, authentication, storage — Frankfurt, eu-central-1) and Lovable (application hosting and the AI gateway used for menu extraction and translation). Menu text submitted for AI extraction is not used to train models. We notify restaurants before adding a new sub-processor. The complete, current list is on the sub-processors page.
Security
Encryption in transit, row-level security scoping every table to one restaurant, role-based staff access, signed and expiring table sessions, hashed invite tokens and an append-only audit log of operator changes.
Assistance and deletion
We assist with data subject requests, breach notification and impact assessments. On termination the restaurant may export its data; after 30 days the data is deleted from production and within 90 days from backups.
Signing
Using DinnerBoost accepts these terms. If your legal team needs a countersigned copy, write to support@dinnerboost.com and we will return a signed PDF.