1. Parties and roles
The restaurant (“controller”) uses Serein, supplied by Safi Alsafi, trading as Serein (Trekroner Forskerpark 1, 2 104, 4000 Roskilde) (“processor”). The processor processes personal data on the controller’s behalf only, to provide the service described in the Service terms. For its own website, billing and account data the processor is a separate controller, as set out in the Privacy notice.
2. Subject, duration, nature and purpose
Subject: reservation, guest and booking-notification data entered by the controller, its staff and its guests. Nature and purpose: storing, retrieving, updating, sending booking emails, exporting and deleting that data in order to provide online booking and table management. Duration: for as long as the controller uses the service, plus the return and deletion period in section 9.
3. Types of data and data subjects
Data subjects: the controller’s guests, and its staff and invited team members. Data: names, email addresses, phone numbers, reservation details (date, time, party size, table), guest requests and notes entered by the controller, deposit payment status (card data is held only by Stripe), and staff account details and activity logs.
4. Instructions
The processor processes the data only on the controller’s documented instructions, which are the Service terms, this agreement, the controller’s settings and use of the service, and any written instruction that is consistent with them. The processor tells the controller without delay if an instruction appears to break data protection law.
5. Confidentiality
People who can access the data at the processor are bound by confidentiality and get access only as needed to run, secure and support the service.
6. Security
The processor takes the technical and organisational measures in the annex below, appropriate to the risk, as required by GDPR article 32.
7. Subprocessors
The controller gives a general authorisation to use the subprocessors on the Subprocessors page. The processor binds each of them to obligations equal to these, and stays responsible for them. The processor gives at least 30 days’ notice by email before adding or replacing a subprocessor. The controller may object on reasonable data protection grounds within that time; if the parties cannot agree, the controller may terminate the affected service.
8. Assistance and breaches
Taking into account the nature of the processing, the processor helps the controller to answer data subjects’ requests (access, correction, deletion, export; Serein has tools for these), to carry out impact assessments and to consult authorities. The processor tells the controller without undue delay, and within 48 hours, after becoming aware of a personal data breach that affects the controller’s data, with the information needed to meet the controller’s own duty to report.
9. Return and deletion
After a subscription ends the controller can export its data while the restaurant remains in the system. Permanent deletion is requested separately and removes the restaurant’s data from the live system immediately, once payment obligations are settled. Export first: there is no recovery or export period after deletion is confirmed. We do not currently keep separate backups of restaurant data, so deleted data does not persist in backup copies. Data that the law requires us to keep may be retained.
10. Audits and information
The processor gives the controller the information needed to show compliance and allows audits, including inspections, by the controller or an auditor it appoints. Audits happen at most once a year (unless a breach or authority requires otherwise), with reasonable notice, during working hours, under confidentiality and at the controller’s cost. The processor can meet the information duty with its providers’ audit reports and certifications where suitable.
11. Transfers
The primary database is stored in Ireland and the application runs in Dublin. Some providers belong to groups outside the EU/EEA (for example in the United States) and may access data to deliver or support their service. In that case the transfer relies on the EU–US Data Privacy Framework or the European Commission’s Standard Contractual Clauses.
12. Liability, law and precedence
Liability under this agreement follows the Service terms. Danish law applies, and disputes go to the courts stated there. If this agreement and the Service terms conflict on personal data, this agreement prevails.
Annex · Security measures
Data in the EU and encrypted in transit (HTTPS/TLS) and at rest by the providers. Tenant isolation through database row-level security and a restricted database role. Role-based access for owners, managers, hosts and viewers, with extra checks for billing and administration. Passwords handled by an identity provider with minimum length rules. Signed, expiring guest links; email verification and bot protection on public booking. Rate limiting against abuse. Audit records of staff changes. Webhook signature verification and idempotent processing for payments. Backups: we do not currently run automated database backups, so restaurants should export their data regularly with the export tools in Serein; we will tell customers before this changes. Least-privilege access for the operator, and no use of production guest data for testing or demonstrations.
Public guidance from the authorities: Datatilsynet (data protection) and Erhvervsstyrelsen (cookies and e-commerce).