Legal
Privacy policy
How PreOrderly Limited uses personal data: for venue teams and customers, website visitors, venues we contact about our service, and (on behalf of venues) hosts and guests.
Last updated 10 November 2026 · Version 1.5
Download as a Markdown (.md) file
Who we are
PreOrderly is run by PreOrderly Limited ("PreOrderly", "we", "us"), a company registered in England and Wales (company number 17526914), registered office Unit A, 82 James Carter Road, Mildenhall, IP28 7DE. We provide software that hospitality venues use to collect group PreOrders: food choices, allergy declarations and deposits from the hosts and guests of a booking.
We are not required to appoint a data protection officer. For anything about your personal data, email privacy@preorderly.app or write to us at our registered office.
Registered with the ICO
PreOrderly Limited is registered with the Information Commissioner's Office (ICO), the UK's data protection regulator, and pays the data protection fee, as UK law requires of organisations that handle personal data. You can search the ICO's public register of fee payers at ico.org.uk/ESDWebPages/Search. How to complain to the ICO is set out under "Your rights" below.
Our two roles
We handle personal data in two different roles, and which one applies depends on who you are:
- Controller: for the people who run venue accounts (owners, admins, managers and staff), for billing contacts, for visitors to our website, for people who contact our support, and for venues we contact about our service. We decide how and why this data is used, and this policy explains it.
- Processor: for hosts and guests of a venue's bookings (names, emails, attendance, food choices, dietary preferences, allergy declarations, seating and payment status). The venue you are booking with is the controller. We only process this data on the venue's instructions, under our data processing agreement (/legal/dpa). The venue's own privacy notice applies, and questions or requests about it should go to the venue first.
PreOrderly support only looks inside a venue's account when one of the venue's admins has asked us to, by granting support access in the app. That access is time-limited (24 hours to 7 days, and at most 2 hours at a time), can be withdrawn by the venue at any moment, and every page we view and everything we do is logged and shown to the venue. While helping, our support staff may see booking details, including guests' allergy declarations, because venues often need help with them.
If you are a host or a guest
The venue uses PreOrderly to collect the details it needs for your booking. What is collected: your name; your email address (optional for people in a party, such as children, added by the person answering for them); whether you are attending; your food choices and any dietary menu; whether you have allergies and, only if you agree, which allergens and any notes for the kitchen; table seating if the venue uses table plans; and the payments you make or owe for the booking. For hosts, also a phone number if the venue adds one.
Allergy details are health information (special category data). They are saved only if you explicitly agree, by ticking the box on the allergy step, or, when you answer for someone in your party or for a guest without an email address, by confirming that you have their permission or are their parent or guardian. We record when that agreement was given and whether it was given by the guest or on their behalf. Without that agreement you can still order: the allergy details you typed are not saved, and the venue only sees that you have allergies, so it can ask you. You can change your answer through your link until the venue's deadline.
Allergy details are used only so the venue can prepare food safely. They are visible to the venue's team and to you (and to the host or party lead for people they answer for). Please always tell staff about allergies when you arrive: dishes may be prepared where allergens are present. PreOrderly records declarations; it never decides that a dish is safe for anyone.
Emails about your booking (invitations, reminders, confirmations, payment requests and receipts, and cancellations) are sent by us on the venue's behalf. Reminder emails include a link to stop reminders for that booking; confirmations, payment emails and cancellations are still sent. Replies go to the venue.
Payments are taken by the venue through its own Stripe account. Card details are entered on Stripe's checkout page; we never see or store them. Stripe processes the payment for the venue under Stripe's own terms and privacy policy (stripe.com/gb/privacy).
Allergy and dietary answers (allergens, allergy notes, other needs, the dietary menu chosen and the record of your agreement) are health information, so they are erased 90 days after the event, by a daily job that records what it did. Your other personal details are anonymised at the same time: your name, email and link are removed, and the email log keeps only what was sent and when, not your address. The venue keeps anonymous order and payment records. The venue can remove you from a booking or anonymise you sooner.
If you are the host (the person who made the booking), you agree to the venue's booking terms and a short privacy notice when you accept the host role: what is stored, why, for how long and who to contact. We record the version of the notice and when you accepted it. The venue keeps your business contact details (name, email, phone and company) on its list of hosts after the event, so it can recognise you and help you book again. The venue does this on the basis of its legitimate interests in repeat business bookings. Your guests' details and anyone's allergy information are never kept this way.
From 7 days after the event you can remove your details yourself, with the Remove my details button on your booking page. Your name, email and phone are then removed from that booking and you are taken off the venue's list of hosts. Otherwise the venue keeps you on its list until you have had no booking with it for the period it has chosen (12, 24 or 36 months; 24 unless the venue changes it), and then your host record is deleted and your name and contact details on your old bookings are anonymised. You can also ask the venue to remove you at any time.
A venue's Admin can delete an archived booking. If guests paid through PreOrderly, the payment records are kept for six years for HMRC, but every guest's and host's name, email, phone, choices, allergies and notes on the booking are erased first; otherwise the booking is deleted completely.
To see, correct or delete your details, contact the venue. If you contact us instead, we will pass your request to the venue promptly and help it respond. If you are unhappy with how the venue handles your data, you can complain to the ICO (details below).
If you ask a venue about a private event
Some venues have an enquiry page, where you can ask about a private event: you choose a date and a room, a menu and extras, and send your name, your email address, optionally your phone number and a note. It is an enquiry, not a booking: nothing is charged, and no allergy, dietary or other health details are asked for. You tick a box to agree that the venue may use your details to reply to the enquiry; it is not for marketing.
The venue is the controller of what you send, and PreOrderly processes it for the venue. The room you asked for is held for you while the venue decides (48 hours unless the venue chooses another time). We email you a copy of what you sent, and the venue's team is emailed too. If the venue accepts, it makes a booking in PreOrderly with you as the host and sends you the normal host invitation; your details then follow the rules for hosts above. If the venue declines or does not answer, or you do not hear back, your enquiry is deleted 90 days after you sent it. The enquiry page sets no cookies. To see, correct or delete what you sent, contact the venue.
What we collect as controller
| Who | What we collect | Where it comes from |
|---|---|---|
| Venue users (owners, admins, managers, staff) | Name, work email, sign-in username if used, role and permissions, password (stored only as a secure hash by our authentication provider), the venue you last viewed and display preferences, and a record of important actions you take in the account (for example sending a PreOrder or changing a plan). For sign-in security: the devices you sign in on (a random device identifier stored only as a hash, a short description such as "Chrome on iPhone", and when each was last used), your sign-in sessions and their last activity, the emailed sign-in codes (stored only as a keyed hash) and wrong attempts, and a record of sign-ins, lockouts and device sign-outs. | You, or the admin who invites you, and your browser. |
| Account owners and the business | Business and venue name, website, address, phone, venue type and the confirmation that you operate the venue; your billing contact and subscription details; invoices and payment status (card details are held by Stripe, not us). | You and Stripe. |
| Account checks (fraud prevention) | What we found when checking that a new account is a genuine UK hospitality venue: a match in the Food Standards Agency hygiene ratings register, whether your email and website match, and, where we use them, public listings and Companies House records; any notes by the person who reviewed the account; a one-way hash of the network address the account was created from (never the address itself). | Public registers and your venue's own website. |
| People who contact us | Your name, email address and what you tell us. | You. |
| Website visitors | Technical data needed to deliver and protect the site: your IP address and browser details in server logs, and short-lived rate-limit counters keyed to your IP address (deleted after one day). We do not use analytics or advertising cookies. | Your browser. |
| Venues we contact about PreOrderly | See "Venues we contact about PreOrderly" below. | The venue's own public website. |
We do not sell personal data, and we do not use venue, host or guest data for our own marketing.
Why we use it and our lawful bases
| Purpose | Lawful basis (UK GDPR Article 6) |
|---|---|
| Providing the service to your organisation: accounts, sign-in, team access, support, service emails (for example verification, password reset, invitations, billing notices). | Contract with your organisation (Article 6(1)(b)). For team members who are not the contracting party: our and your organisation's legitimate interests in running the account (Article 6(1)(f)). |
| Billing and keeping financial records. | Contract, and legal obligation to keep accounting and tax records (Article 6(1)(c)). |
| Checking that new accounts are genuine venues, and preventing fraud, misuse and competitor access. | Legitimate interests in keeping the service safe and limited to genuine venues. |
| Security, logs, rate limiting, error monitoring and fixing problems. | Legitimate interests in running a secure, reliable service. |
| One helpful email to admins of a trial account that has not yet sent a PreOrder (if switched on). | Legitimate interests in helping you get set up. You can ask us to stop at any time. |
| Emailing venues about PreOrderly. | Legitimate interests (see below), within the rules of the Privacy and Electronic Communications Regulations (PECR). |
| Sending the demo video you asked for on our website, and marketing emails if you ticked the box. | Steps at your request and legitimate interests (Article 6(1)(b) and (f)); consent for marketing emails (Article 6(1)(a)), which you can withdraw at any time. |
| Handling legal claims and complying with the law. | Legitimate interests and legal obligation. |
Automatic account checks can approve a new account, but they never refuse one: an account that is not approved automatically is reviewed by a person, who makes the decision.
Venues we contact about PreOrderly
If you run a venue that takes group bookings, PreOrderly Limited may email the public business address on your venue's website (for example events@ or info@) to tell you about PreOrderly. For this data we are the controller.
What we hold: your venue's name, website, town and type; the public business email addresses shown on your website, the page each was found on and the date; the words on your site that suggest you take group bookings; your business's legal form (for example a limited company) and how we checked it; our emails to you, whether they were delivered or bounced, any click on the trial link in them, the visits described under "Your personal link" below, and your replies. We do not collect anything from social media, we do not buy lists, and we do not collect anything sensitive.
Where it comes from: your venue's own public website (we may find the website through a public business listing such as Google Maps), and public registers such as Companies House. We also store public venue details (name, website, address and any business email) from OpenStreetMap, which is open data under the Open Database Licence (© OpenStreetMap contributors), and the results of scanning your venue's public website; we delete these 12 months after we added them if you never engage with us. Our crawler, PreOrderlyBot, identifies itself (preorderly.app/bot), obeys robots.txt and reads at most a few pages on your venue's own domain.
Who we email: under PECR we email only businesses that are corporate subscribers, meaning limited companies, LLPs, PLCs and public bodies, and only at role-based business addresses on the venue's own domain. We do not send marketing emails to sole traders or partnerships, or to personal addresses, because they would need to have given consent.
Your personal link: each of our emails to a venue has a link and an access code that are personal to the person we wrote to. We note when you open the link or enter the code (the time and how many times), so we can follow up in a business context. The page then asks whether we may also note if you play the demo video or click Book a demo or Start your free trial. Only if you say yes do we set a first-party cookie for that (it lasts up to 60 days and is not used for advertising or by anyone else); if you say no, we note nothing more and the page works exactly the same. We do not store your IP address for this. The link and code stop working after 60 days. We never note any of this if you have unsubscribed or we have suppressed your address (and we clear the cookie), or if the address is a personal one (such as Gmail or Outlook) that we treat as an individual subscriber. Our emails say: We note when you open the personal link in our email so we can follow up. Reply "not interested" or unsubscribe and we'll stop straight away.
Why we may use it: our legitimate interests in telling relevant businesses about a business service, in a business context. We have assessed those interests against yours, keep the data to a minimum, send at most four short emails over about two weeks, and stop as soon as you reply, start a trial or ask us to stop.
How long we keep it: if you never engage with us, we delete your venue's details 12 months after we added them. If you tell us you are not interested, or ask us not to contact you, we delete the venue's details 12 months later. If you reply but do not become a customer, we delete them 24 months after our last contact. If you start a trial or become a customer, the rest of this policy applies.
How to object: every email has a one-click unsubscribe link. You can also object, or ask for access to or deletion of your details, at any time by emailing privacy@preorderly.app. When you unsubscribe or object, we stop emailing every address at your venue straight away and for good.
We keep a short suppression record (the email address, the reason and the date) after an unsubscribe, objection, bounce or deletion request, so that we never email that address again, even after the rest of the record is deleted. We send these emails through Resend.
Watching the full demo
When you ask for the full demo video on our website, PreOrderly Limited is the controller of the details you give us.
What we store: your name, your email address, your venue's name, the date you asked, whether you ticked the box to receive marketing emails and when, and the dates you opened the video link. To make the link work on one device only, we also store when it was first opened and a random code that your browser keeps in a cookie (only a hash of it is stored with us); the cookie is needed to watch the video and lasts 30 days. We add your venue to our sales records (using the domain of your email address, unless it is a personal address such as Gmail or Outlook), so we may also look at your venue's public website as described in "Venues we contact about PreOrderly".
Why: to email you the link you asked for (taking steps at your request) and, in our legitimate interests, to keep a record of who asked and to follow up about PreOrderly in a business context. We send you marketing emails only if you ticked the box (your consent), or if your business is a corporate subscriber and the rules in "Venues we contact about PreOrderly" allow it. We never send marketing emails to a personal address (such as Gmail or Outlook) or to a sole trader without your consent. The box is never ticked for you.
How long we keep it: 12 months after your last request, unless you start a trial or become a customer, in which case the rest of this policy applies. The link to the video works on the first device it is opened on, for 30 days; if it is not opened, it stops working 30 days after we send it.
How to opt out: every marketing email has a one-click unsubscribe link, which also withdraws your consent. You can also withdraw consent, object, or ask for access to or deletion of your details at any time by emailing privacy@preorderly.app.
International transfers
Our database and application servers are in London (United Kingdom). Some of our providers are based in the United States (Supabase, Vercel, Stripe and Resend) or Australia (Fastmail), and email delivery runs in the United States, so some personal data is transferred outside the UK or may be accessed from there for support and maintenance.
Where we transfer personal data outside the UK, we rely on UK adequacy regulations (including the UK Extension to the EU-US Data Privacy Framework, where the provider is certified under it) or on the International Data Transfer Addendum to the EU Standard Contractual Clauses (or the International Data Transfer Agreement) issued by the ICO, included in each provider's data processing terms, with a transfer risk assessment. You can ask us for more detail at the address below.
How long we keep data
| Data | How long |
|---|---|
| Guests' allergy and dietary answers (health data, processed for venues) | Erased 90 days after the event, or sooner if the venue removes or anonymises the guest. |
| Guest personal details, and host details on each booking (processed for venues) | Anonymised 90 days after the event, or sooner if the venue removes or anonymises them, or deletes the archived booking. Anonymous order and payment records stay with the venue's account. |
| Host business contact details on a venue's list of hosts (processed for venues): name, email, phone, company and the venue's notes | Kept for repeat bookings (the venue's legitimate interests) until the host removes their details (from 7 days after the event) or asks the venue to remove them, and deleted once the host has had no booking at that venue for the period the venue chooses: 12, 24 or 36 months (24 by default). Bookings linked to the host keep the host's name and contact details for the same time, and are then anonymised. |
| Enquiries about private events (processed for venues): name, email, phone, note, the date, room, menu and extras asked for | Deleted 90 days after the enquiry is sent if the venue did not accept it. If the venue accepted it, the enquirer's name, email, phone and note are removed from the enquiry record after 90 days, and the booking follows the rules for hosts. |
| Hosts' acceptance of the booking terms and privacy notice (processed for venues) | With the booking: the version and time stay with the anonymised booking record. |
| Payment records for guest payments (processed for venues) | Six years, as HMRC requires, also when a venue deletes the booking: names and contact details are removed from them. |
| Webhook delivery log (what was sent to a venue's own connected systems) | 30 days. |
| Venue account data | While the account exists. If a subscription ends, the account becomes read-only so you can export your data or restart. When an owner asks us to delete the account (Settings, Organisation), it and its data are deleted 30 days after the request. We review accounts that have been inactive for more than 12 months after their subscription ended and will contact the owner before deleting one. |
| Billing and invoice records | Six years after the end of the financial year they relate to, as UK tax and company law requires (held in Stripe and our accounts). |
| Account check evidence and our audit log of staff and account actions | While the account exists, and up to six years after it closes where needed for legal claims or fraud prevention. |
| Prospective customer data | As described in "Venues we contact about PreOrderly": 12 or 24 months. Suppression records are kept so we never email the address again. |
| Demo video requests (name, email, venue, marketing choice) | 12 months after the last request, unless you start a trial or become a customer. |
| Support requests and emails | Two years after the request is resolved or closed, then deleted automatically, unless they are needed for a legal claim. |
| Support access log (what PreOrderly support viewed and did in an account) | Two years, then deleted automatically. |
| Audit log (who did what in an account: team changes, settings, payments, billing, downloads and printing, sign-in security and PreOrder deletions) | Two years, then deleted automatically. It holds names, roles and plain-English descriptions, never guests' allergy or dietary answers, passwords or sign-in codes. Only the account's Admins can see it, and no entry can be changed or deleted before then. |
| Import history (who imported a spreadsheet of dishes, choices, menus or extras, the file name, how many items were saved and any row problems) | Two years, then deleted automatically. It holds names and plain-English messages, never guests' details or the spreadsheet's rows. Only people with menu access at the venue can see it. |
| Sign-in devices and sessions | Device records: deleted 90 days after the device was last used. Session records: 90 days after the session ended. Sign-in codes and wrong attempts: one day. The record of sign-ins and security events is part of the account's audit log (two years, above). |
| Allergy review trail and named allergy sign-offs (who reviewed or signed off a PreOrder's allergy information, when, and the outcome) | While the account exists, so the venue can show what it checked. They hold names, times and outcomes, never any guest's allergy or dietary answers, which are erased 90 days after the event. |
| Guest feedback (a guest's rating and comment about the event, if they choose to give one) | 12 months, then deleted automatically. |
| Attendance answers (whether a guest came) | 90 days after the event, then deleted automatically. |
| Developer access log (calls made with a venue's API key: time, method, path and result, never the data returned) | 12 months, then deleted automatically. |
| Server logs and rate-limit counters | Rate-limit counters: one day. Server logs: a short period set by our hosting provider. |
| Backups | Our database provider keeps backups on a rolling basis; deleted data leaves the backups within 30 days. |
How we protect data
Data is encrypted in transit (TLS) and at rest. Each organisation's data is kept separate by database access rules, and venue users only see what their role allows. Guest and host links are personal, unguessable and stored only as hashes. Access by PreOrderly staff is limited to named administrators and recorded. We keep backups, test restoring them and have an incident response plan. If a personal data breach affects data we process for a venue, we tell the venue without undue delay so it can meet its own duties.
Your rights
Under UK data protection law you have the right to: be informed; access your personal data; have it corrected; have it erased; restrict its use; object to its use (including an absolute right to object to direct marketing); data portability; and not be subject to solely automated decisions with legal or similarly significant effects. Some rights apply only in certain circumstances.
For data we control, email privacy@preorderly.app. We may ask you to confirm your identity, and we will reply within one month (we may extend this by two more months for complex requests, and will tell you if we do). Venue admins can also download a copy of their organisation's data at any time from Settings, Organisation. Hosts and guests should contact the venue, as above.
If you are unhappy, please tell us first so we can try to put it right. You also have the right to complain to the Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, ico.org.uk/make-a-complaint.
Children
Venue accounts are for adults acting for a business. A guest list can include children (for example on a children's menu); their details are added by a parent, guardian or the host, and allergy details for them are saved only when the person answering confirms they have permission or are the child's parent or guardian.
Changes to this policy
We will update this policy when how we use personal data changes, and change the date at the top. If a change is significant, we will tell account owners by email before it takes effect.
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.