How long is booking data kept — and what do guests agree to?
Set the auto-delete period for booking data, and manage the cancellation, terms and privacy policies guests agree to when booking.
One settings page covers this: Settings → Guest policies. Its Privacy section controls how long booking data is kept, and the rest of the page holds the cancellation, terms and privacy policies guests agree to when they book. (Retention used to live on its own Data retention page; it moved here in August 2026 so everything a guest is told, and everything you keep about them, is in one place.)
Only Owners and Admins see these pages. Other staff who reach them by link can view but not change anything.
Data retention period
- Go to Settings → Guest policies and open Privacy.
- Set Keep a guest’s history for — 6, 12, 18, 24, 36 or 48 months (the default is 24 months). The period counts from each guest's last activity with you: any booking or visit, table order, gift-card or event-ticket purchase, loyalty scan, enquiry from your website, or a yes to your news by email restarts it (a yes counts until they say no). A guest who has a booking or event ticket still to come (one that isn't cancelled) is never removed before it. Someone whose only link with you is a yes to your news gets one Still want news? email before their details would be removed: if they press yes they stay for another period; if not, they're removed 30 days later. That email goes only while you can send news (Your website, Plus and above, or a product with marketing) and your marketing isn't paused; otherwise their details are removed at the end of the period with no email. While a guest keeps coming back, their whole history stays — their profile, every booking (however old), their messages with you, their loyalty and offer-code history, the record of the texts and campaign emails you sent them, their notes and counts. Once a guest has had no activity for the whole period, everything about them is removed together: their profile, their bookings, their loyalty and offer-code history (a line no longer linked to anyone goes two years after it was made), their name on the Activity log, the record of texts and campaign emails sent to them, and the stored copies of emails about them — and their messages with you once those, too, have been quiet for the period. A booking with no contact details (a walk-in, say) has no guest to stay active: once it is this old, its name and notes are removed, but the visit itself — date, time, party size and table — is kept, so your busy-times history stays complete. This helps you stay GDPR-compliant. The one exception is bookings that carry a payment (a deposit, full prepayment, event ticket, paid extras, a paid pre-order, a charged no-show fee or a gift-card payment): the guest's personal details are removed just the same, but the payment facts and their payment reference are kept for your financial records for as long as your account is open. On a paid pre-order the dishes are kept the same way; the names on the plates and each dish's own note for the kitchen (often an allergy) go with the guest's other details — when their history is removed, or straight away when a guest asks for their data to be erased (and a guest who asks for a copy of their data gets their pre-order, notes included).
- Click Save changes. The retention period feeds your guest privacy notice automatically — when you change it, the notice guests see updates itself, and the save confirms with "Saved — this also updated your guest privacy notice."
If you run a loyalty scheme, the same page has Warn loyalty members first and When those reminders send: loyalty members are emailed before their details are deleted — a visit resets their clock — and you choose 2 or 3 reminders and how many days before deletion each goes out (between 1 and 180 days each, furthest out first — the defaults are 60 then 14 days, and deletion only happens at least 7 days after the final reminder). Any loyalty activity — a visit, an earn, a redemption — restarts the member's retention clock, and the reminder email's wording is editable in Settings → Email templates ("Data-deletion warning (loyalty members)").
Event purchase records also retain the original ticket tier and selected add-on names, quantities and prices. These catalogue facts contain no guest contact details and are included in the venue's data export. They remain available with the payment record when a checkout hold expires or a catalogue changes.
You first choose this period when you set up: the sign-up's Your venue in a minute page asks it under Your guests, your data, and if ResoFlow set your venue up with you, the set-up asks it too. Both write the same setting as this page.
Your team's details after they leave
The same Privacy section has Keep a staff member’s details after they leave for — 6, 7, 8 or 10 years (the default is 6 years). Everything about someone is kept while they work for you. When you remove them, the period starts; at the end of it their name, contact details, availability, time off (including sick days), shift swaps and rota notes are removed, and their shifts, clocked hours and pay rate are kept without a name, for your pay records. Pay and hours records must be kept for 6 years, so 6 is the shortest choice. If you add the same person back before the period ends, nothing is removed. If your plan or products include the Team area, the set-up asks this period too (And your team’s details, after someone leaves? at sign-up).
If you close your account
You have 30 days to change your mind, then everything is deleted. Before then, download your data (Your data, in your account): it includes every monthly accounts pack and a file of every payment and refund. HMRC asks you to keep your business records for 6 years, and once the account is deleted we can't get them back. ResoFlow keeps only its own billing records (7 years), a short record of which terms you agreed to (6 years) and combined totals that never name a venue.
Guest policies
Settings → Guest policies has three cards — Cancellation and no-show, Terms and conditions and Privacy. They're ready to use out of the box; you only add wording if you want to.
- Each policy is built from three layers: ready-to-use UK wording you can read but not edit (click View the wording that's always included); clauses Added automatically from your settings — shown as chips like "Deposit refund: full refund up to 24h before" or "Data kept: 24 months", each with a Change link to the page that controls it; and your own optional free text.
- To add house rules, type in Add your own wording (optional) — up to 5,000 characters per policy. If the box is empty, Insert reviewed wording drops in a professional starting point to tailor.
- Click Preview what guests see to read the full assembled policy exactly as a guest will.
- Click Save changes. Cards show a Customised badge once you've added your own wording, or Ready to use otherwise.
What guests agree to
Every booking, table order, event ticket and gift card purchase freezes a snapshot of the exact policy at the time — past ones keep what the guest agreed to; edits only apply to future ones. The agreement mechanism matches the surface: online bookings show "By booking you agree to the cancellation policy and terms" (completing the booking is the agreement, with no tick-box); phone or in-person bookings record a staff "guest agreed (verbal/in-person)" tick; table orders show "By paying you agree to … Order Terms." and ask whether anyone in the party has a food allergy or intolerance — a Yes or No must be chosen before paying (plus an 18-or-over tick when the order contains alcohol); event tickets and gift cards agree at their own checkouts. Settings → Guest policies → Terms by purchase type shows each mechanism and the exact terms per purchase type.
Because the deposit, no-show fee and cancellation-deadline settings write themselves into these policies, changing those settings also updates the policy text — the pages involved show a "This also appears in your guest cancellation policy" note.
Related: When do guests get their deposit back? · How do I handle a guest's data request? · How do I bulk-delete data (tables, bookings, guests…)?