Legal

Data processing agreement

The UK GDPR Article 28 terms under which PreOrderly Limited processes host and guest personal data for venues.

Last updated 10 November 2026 · Version 1.5

Download as a Markdown (.md) file

1. Parties and scope

1.1 This agreement is between the Customer that has accepted our terms of service (/legal/terms) (the "controller") and PreOrderly Limited, company number 17526914 ("PreOrderly", the "processor"). It forms part of the terms of service and applies for as long as PreOrderly processes Customer Personal Data.

1.2 "Customer Personal Data" means personal data about the Customer's hosts and guests (and people in their parties) that PreOrderly processes on the Customer's behalf to provide the Service. Data about the Customer's own team, billing and account checks is controlled by PreOrderly and covered by our privacy policy, not this agreement.

1.3 "Data Protection Law" means the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003 and any law that replaces or amends them. Words such as controller, processor, personal data, personal data breach, processing and data subject have the meanings given in the UK GDPR.

2. Details of the processing

ItemDetails
Subject matter and purposeCollecting group PreOrders for the Customer's bookings: inviting hosts and guests, recording attendance, food choices, dietary menus and allergy declarations, seating, deposits and payments, sending booking emails on the Customer's behalf, and producing kitchen, allergy and service sheets and reports.
DurationThe term of the Customer's account, plus the deletion periods in section 10.
Nature of processingCollection through personal guest and host links, storage, organisation, display to the Customer's authorised users, email delivery, transfer to the Customer's Stripe account for payments, export, anonymisation and deletion.
Data subjectsHosts (the person who made the booking), guests, and people in a guest's party (including children) added by a host or party lead.
Categories of personal dataNames; email addresses (optional for people in a party); host phone numbers; hosts' acceptance of the booking terms and privacy notice (version and time); attendance; menu, dish and modifier choices; dietary menu; table seating; extras chosen; payment amounts and status (not card details); notes; records of emails sent; and link access tokens (stored as hashes).
Enquiry page (private event enquiries)If the Customer switches on its enquiry page: the enquirer's name, email address, optional phone number and note, the date, time, room, guest number, menu and extras asked for, and the time they agreed to be contacted about it. No health data and no payment details are collected. Unaccepted enquiries are deleted 90 days after they are sent.
Special category dataHealth data: whether a guest has allergies and, only with the guest's explicit agreement (or confirmation of permission by the person answering for them, recorded with a timestamp), which allergens and any notes for the kitchen, and the Customer's allergy review notes.
RetentionGuests' allergy and dietary answers are erased, and other guest personal data anonymised, 90 days after the event (or sooner if the Customer removes or anonymises a guest). Host business contact details on the Customer's list of hosts are kept until the host removes them or asks the Customer to, and at most the period the Customer chooses (12, 24 or 36 months, 24 by default) after the host's last booking. Payment records are kept six years. The account's audit log (who did what in the account) is kept two years. See section 10.

3. The Customer's responsibilities as controller

3.1 The Customer decides why and how Customer Personal Data is processed and is responsible for having a lawful basis for it (and, for allergy data, a condition under Article 9 UK GDPR), for giving hosts and guests a privacy notice that explains its use of PreOrderly, and for the accuracy of what it enters.

3.2 The Service includes an explicit agreement step before allergy details are saved. The Customer decides whether that agreement is the right condition for its own purposes and must not ask PreOrderly to store allergy details any other way.

3.3 The Customer confirms, for each purpose for which it uses the Service, its lawful basis under Article 6 and its Article 9(2) condition for allergy and dietary information, and that the Service's explicit agreement step is suitable for that condition.

3.4 The Customer's use of the Service, and its configuration of it, are its documented instructions to PreOrderly. The Customer will make sure its instructions comply with Data Protection Law.

4. PreOrderly's obligations as processor (Article 28(3))

PreOrderly will:

  • (a) process Customer Personal Data only on the Customer's documented instructions (these terms, the Customer's use of the Service and any further written instructions), including about international transfers, unless the law requires otherwise, in which case PreOrderly will tell the Customer first unless the law forbids it; and tell the Customer if it believes an instruction breaks Data Protection Law;
  • (b) make sure that everyone it authorises to process Customer Personal Data is bound by confidentiality;
  • (c) take the technical and organisational security measures required by Article 32, including those in Annex 2;
  • (d) use sub-processors only as set out in section 5;
  • (e) taking into account the nature of the processing, help the Customer respond to data subject requests, mainly through the Service's tools (editing, removing and anonymising guests, and exporting data), and pass on without undue delay any request it receives directly, without responding to it except to say it has been passed on;
  • (f) help the Customer meet its obligations on security, personal data breaches, data protection impact assessments and prior consultation (Articles 32 to 36), taking into account the information available to PreOrderly;
  • (g) at the end of the Service, delete or return Customer Personal Data as set out in section 10; and
  • (h) make available the information reasonably needed to show compliance with Article 28 and allow for and contribute to audits, as set out in section 9.

Support access: PreOrderly's support staff access Customer Personal Data inside the Customer's account only on the Customer's documented instruction, given when an admin grants support access in the Service. Each grant is time-limited (24 hours, 72 hours or 7 days; each session at most 2 hours), view only unless the Customer allows changes, revocable at any time, and every page viewed and action taken is logged and shown to the Customer. Support staff cannot change sign-in details, the team, billing or payments, export data or delete the account.

5. Sub-processors

5.1 The Customer gives PreOrderly general authorisation to use the sub-processors listed on the sub-processors page (/legal/subprocessors).

5.2 PreOrderly will give the Customer at least 30 days' notice of any new or replacement sub-processor by email to the account owner and by updating that page. The Customer may object on reasonable data protection grounds within that period. If we cannot resolve the objection, the Customer may end its subscription and receive a refund of fees prepaid for the period after the change.

5.3 PreOrderly will put in place with each sub-processor a written contract with data protection obligations that are at least as protective as this agreement, and remains responsible to the Customer for each sub-processor's performance.

5.4 Stripe is not PreOrderly's sub-processor for guest payments: the Customer contracts directly with Stripe for its own account. PreOrderly sends payment details for a booking (amount, description, the guest's email and references) to the Customer's Stripe account on the Customer's instructions.

6. International transfers

6.1 Customer Personal Data is stored in and processed from London, United Kingdom. Some sub-processors are based outside the UK (as listed on the sub-processors page) and may access or process data from there, and email delivery takes place in the United States.

6.2 PreOrderly will only transfer Customer Personal Data outside the UK, or allow a sub-processor to do so, where the transfer is covered by UK adequacy regulations (including the UK Extension to the EU-US Data Privacy Framework for a certified provider) or by appropriate safeguards under Article 46 UK GDPR, namely the ICO's International Data Transfer Agreement or International Data Transfer Addendum to the EU Standard Contractual Clauses, supported by a transfer risk assessment.

7. Security

7.1 PreOrderly will keep in place the measures in Annex 2 and review them regularly. It may change them as long as the overall level of protection does not fall.

8. Personal data breaches

8.1 PreOrderly will tell the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, and will aim to do so within 48 hours so the Customer can meet its 72-hour deadline to notify the ICO where required.

8.2 The notice will include, as far as known: what happened, the categories and approximate number of people and records affected, the likely consequences, and the measures taken or proposed. PreOrderly will provide more information as it becomes available, take reasonable steps to contain the breach, and keep a record of it. Notifying a breach is not an admission of fault.

9. Information and audits

9.1 PreOrderly will answer reasonable written questions about its processing and security. If that is not enough to show compliance, the Customer (or an independent auditor bound by confidentiality) may audit PreOrderly once in any 12 months, on at least 30 days' notice, during business hours, at the Customer's cost, in a way that does not disrupt the Service or expose other customers' data. Audits of sub-processors are carried out through their own reports and certifications.

10. Deletion and return

10.1 The Customer can export its data at any time (Settings, Organisation, Download your data), including after its subscription has ended.

10.2 Guests' allergy and dietary answers are erased, and other guest personal data is anonymised, automatically 90 days after each event, by a daily job that records each run. Host business contact details on the Customer's list of hosts (name, email, phone, company and notes) are kept, on the Customer's instructions, for repeat bookings until the Customer removes the host or the host uses Remove my details (offered from 7 days after the event), and are deleted automatically once the host has had no booking for the period the Customer sets in the Service (12, 24 or 36 months, 24 by default), when the host's details on their old bookings are anonymised too. When an owner asks for the account to be deleted, PreOrderly deletes the account and all Customer Personal Data 30 days after the request (the delay allows the request to be withdrawn and a final export). Deleted data leaves rolling backups within a further 30 days.

10.3 The Customer's Admins can delete an archived booking. Where guest payments were taken, PreOrderly keeps the payment records for six years (UK tax law) and erases every guest's and host's name, email, phone, choices, allergies and notes on that booking; otherwise the booking and everything on it is deleted. The deletion is recorded in the account's activity log.

10.4 PreOrderly may keep Customer Personal Data longer only where the law requires it, and will then protect it and process it only for that purpose.

11. Liability and general

11.1 Each party's liability under this agreement is subject to the limits in the terms of service. Nothing in this agreement limits either party's direct liability to data subjects under Data Protection Law.

11.2 If this agreement conflicts with the terms of service about personal data, this agreement prevails. It is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.

Annex 1: Sub-processors

The current list, with each provider's purpose, location and transfer safeguard, is on the sub-processors page (/legal/subprocessors).

Annex 2: Technical and organisational measures

  • Hosting in London (United Kingdom) for the database and application servers.
  • Encryption in transit (HTTPS/TLS only, with HSTS) and at rest (provider-managed encryption of the database and backups).
  • Tenant isolation enforced in the database by row-level security, so one organisation's users cannot read another's data; role-based permissions inside each organisation (owner, admin, manager, staff).
  • Guest, host and payment links use long random tokens, stored only as salted hashes, and can be revoked or replaced; links are not indexed by search engines and pages behind them are not cached.
  • Data minimisation: allergy details stored only with explicit agreement; automatic erasure of allergy and dietary answers and anonymisation of guest data 90 days after each event, and removal of host contact details once the host has had no booking for the Customer's chosen period (or when the host or the Customer removes them); no card details stored.
  • Access by PreOrderly staff limited to named platform administrators, with administrative actions recorded in an audit log; secrets kept only in the hosting providers' encrypted settings and rotated on staff changes.
  • Application security: content security policy, rate limiting of sign-in, sign-up and public links, server-side permission checks on every action, dependency updates and automated tests including database security tests.
  • Resilience: daily backups and point-in-time recovery, with restore tests; monitoring and alerts for errors and scheduled jobs.
  • Incident response plan with containment, investigation, notification of controllers and post-incident review.
  • Everyone given access to Customer Personal Data (staff or contractors) is bound by confidentiality and given only the access their work needs.

Company details

PreOrderly Limited, registered in England and Wales, company number 17526914. Registered office: Unit A, 82 James Carter Road, Mildenhall, IP28 7DE. Email support@preorderly.app (general and support) or privacy@preorderly.app (personal data).

PreOrderly Limited, registered in England and Wales, company number 17526914. Registered office: Unit A, 82 James Carter Road, Mildenhall, IP28 7DE.

Data processing agreement · PreOrderly