Skip to content

Policies

Privacy Policy

Last updated 14 November 2026

1. Who we are

ResoFlow is a trading name of Caleonix LTD, a company registered in England and Wales (company number 17162652), registered office 71-75 Shelton Street, London, England, WC2H 9JQ. We’re registered with the Information Commissioner’s Office (ICO) under number ZC127147. We don’t need a statutory Data Protection Officer; for anything about your data, email [email protected].

ResoFlow is software that businesses (venues) use to run bookings, orders, tickets, gift cards, loyalty schemes and their teams. “Guests” means the people a venue serves through ResoFlow: anyone who books, joins a waitlist, asks to hear when a table frees up, orders, buys a ticket, buys or receives a gift card, joins a loyalty scheme, or calls a venue whose phone our assistant answers.

  • We are the controller for venue accounts, our own billing records, our own website and dashboard (analytics, cookies and ad measurement), our marketing to venues, people thinking of joining, and support conversations with us.
  • We are a processor for each venue for its guests’ and staff’s data (whoever enters it) and for the messages it sends its guests through us. The venue is the controller, and our Data Processing Agreement covers that relationship. If you’re a guest, the venue you dealt with is responsible for your data.

2. What we collect

Venue owners and accounts

  • Your name, email address and UK mobile number, and whether the mobile has been confirmed.
  • Your business’s name, address and basic details; your plan, products, business type and usage; a log of actions on the account; and, if you tell us, which booking system you’re moving from and how you heard about us.
  • How your sign-up went — the steps you reached and, if a card was turned down, the reason in general terms (never card details) — so we can make signing up easier.
  • Your password is handled by our sign-in provider; we never store it. Card details stay with Stripe; we keep only the card brand, last four digits and Stripe references.
  • Sign-in records — when you signed in, the internet address and a rough town for each device, so we can warn you about a sign-in from somewhere new — and records that stop the security check repeating after you sign in and, if you tell us a computer is yours, stop us asking about it again there. If you use passkeys, their public key and the name you gave them; your face, fingerprint or device PIN never leave your device.
  • Which versions of the Terms, this policy and the DPA you accepted when you created your account, when, and your confirmation that your business operates in the UK.
  • Business check. When you first switch on marketing emails or texts, or choose your own text sender name, we check Companies House, the Food Standards Agency’s food hygiene register and whether your Stripe account can take payments. We keep what we find and your declaration that the business is yours, and use them only to confirm the business, register your sender name or phone number and re-check it. We never look up directors and never ask for documents for this check. If you add a phone number through ResoFlow, we also give the UK phone network, through our phone provider, your business’s name, address and registration number (for a sole trader, a VAT number or tax reference) and the owner’s name, email and mobile, only to register that number.
  • Venue list. Unless a venue opts out, the public details it already publishes may appear at resoflow.co.uk/venues. It never shows anything about guests.

Venue staff (we process this for the venue)

  • Name, username, role and any permission changes; optionally a work email, phone and job title. Only the venue’s authorised accounts see it, and staff can change their own optional details and choices on their Profile page.
  • A PIN (stored scrambled), the staff devices they use, the internet addresses they sign in from (for security alerts and the venue’s Activity log), their theme and alert choices, and sign-in and session records so the owner can review and end sessions.
  • If alerts are turned on — for a staff device or from a member of staff’s own rota page — a push token for that device and when it was last used. Alerts never carry contact details, notes or anything about health.
  • If the venue uses the Team tools:
    • Rotas — shifts, areas, breaks, manager notes, contracted hours, whether someone is under 18 or has opted out of the 48-hour week (never a date of birth), and when shifts were published or changed. ResoFlow can draft a week, but a person at the venue decides every shift. Staff get private links to their own rota page and calendar feed; anyone with the links can see and act as that person until the venue renews them. Unless the venue switches it off, the rota page also shows colleagues on the published rota — names, times and areas only.
    • Rota requests — times they can’t work, time off, swaps and cover. Sickness is recorded as dates only — never a reason — and only the person, owners, admins and rota approvers see that it was sickness; everyone else sees “Off”. A record that someone was off sick is health information, which the venue is responsible for having a lawful basis to keep.
    • That they’ve seen their rota, and how they want to hear about it (push alert, email or both).
    • Clocking in — clock-in, clock-out and break times and the device used; any correction, with who made it and why (the member of staff can see the reason). If the venue uses clocking in, its managers are told when someone hasn’t clocked in a set time after their shift started.
    • Holiday and pay — holiday allowance and use; optionally an hourly rate, pension membership and National Insurance band (never a date of birth). Only owners and admins see pay, and anyone the owner gives permission to see it.
    • Tipping policy — each published version, the draft shared with staff, staff comments (with their names), and requests for a tips record.

Guests (we process this for the venue)

  • Contact details — name, email address and phone number.
  • Bookings — date, time, party size, table, notes and history, and answers to the venue’s own booking questions (we stop venues asking about health, religion or other sensitive subjects, apart from allergies and diet). An optional birthday (day and month), used for birthday messages and offers.
  • Allergies and dietary needs — see section 3.
  • Messages with a venue, including replies to its emails. Replies reach the venue through us: they’re kept in the venue’s inbox, or passed to its own email without our keeping their words.
  • Website enquiries — through a venue’s website contact form: your name, email, any phone number, your message and the page you sent it from, kept in the venue’s Messages and emailed to the venue, which keeps your details on its guest list (never as a yes to its news).
  • Phone calls — if a venue uses our AI phone assistant, Rezo answers its calls and says at the start that it is an automated assistant and that the call is transcribed (or recorded). We keep your number, a written transcript and a short summary for the venue, and a recording of the call only if the venue switches recording on. No recording is kept of a call put through to the venue’s own phone. If the line can’t take a call, we note your number so the venue can ring back. A booking, change or message you make on the call is kept like one made any other way.
  • Messages we send you — a copy of each email and text we send you for the venue, other than its marketing campaigns (the campaign itself holds what it said), so its team can see what you received, and a record that each one was sent, campaigns included (what, when, how and whether it arrived — never its words).
  • “Notify me” requests — your name, email or mobile, and the date, times and party size you wanted, so we can tell you if a table frees up.
  • Pre-orders and party food — dishes chosen, names against dishes, short notes for the kitchen (often about an allergy), totals and payments; for a party choosing on separate links, each guest’s name, optional email and any dietary note (shown to the venue, never to the rest of the party).
  • Orders (at the table, for collection or for delivery) — what you order, notes, tip, table, your contact details and the time you asked for; for delivery, your address and door notes (checked against the venue’s delivery area with Google Maps — as you type an address, Google sees what you type and your IP address, never your name); your 18+ confirmation for alcohol and your answer to the allergy question; and any refund the venue repays outside the card.
  • Reviews you leave — see How reviews work.
  • The profile a venue keeps about you — a VIP flag, tags, notes, a seating preference and family details (children, highchair, children’s menu). Booking, ordering, joining its loyalty scheme or buying something there creates or updates it.
  • Your account at a venue — you sign in with a one-time code emailed to you, and can add your own details, allergies and preferences, which the venue’s team sees. Signing in alone doesn’t create a customer record.
  • Activity the venue’s records show — visits, cancellations, missed bookings, orders, spend and earlier names or numbers. A UK mobile number with no email keeps its own record.
  • Event tickets — the buyer’s name, email and phone, and any attendee names. Event waitlists — your name, email and how many tickets you want.
  • Payments — your card is handled by Stripe on the venue’s own Stripe account and never by ResoFlow; we keep only Stripe references (including a saved-card mandate), the card’s brand and last four digits, and the venue’s records of money paid at the venue.
  • Loyalty schemes you choose to join (never automatically) — your member code, balance and history, groups you belong to (for a university or work email we keep only its ending and a one-way fingerprint, never the address) and who invited you. You can leave a scheme at any time from your account.
  • Offer codes you use, and offers you save.
  • Gift cards — the buyer (name and email when bought online; optional at the venue) and, for a gift, the recipient’s name and email and the buyer’s message. A recipient never gets a customer profile or marketing because of a gift.
  • A venue’s news sign-up — the address you type, until you confirm.
  • Wallet passes (bookings, tickets, loyalty cards and gift cards) — a device identifier and push token, only to keep the pass up to date.
  • Data a venue imports, such as its customer list and visit history from its previous system — handled exactly like data entered in ResoFlow.

Guests’ marketing choices

  • When you make a marketing choice we keep evidence of it: when, where, the exact wording shown and the choice — including a choice the venue’s team records for you in person or by phone (with their name).
  • Marketing texts go only to UK mobiles, at most one campaign text a week and never between 9pm and 9am, to people who visited, ordered or bought a ticket in the last 24 months, or said yes. A venue that imports customers records a yes only for those its file marks as having said yes, and confirms it has permission to upload them.
  • A yes or no to one channel covers that channel, and a no stays until you say yes again. If your record is deleted after you said no, the venue remembers that no as a one-way fingerprint, so a new record for you starts with the same no.
  • A venue may choose who gets its marketing from what it holds (for example, when you last visited), and may switch on automatic marketing emails. Each is off until switched on, goes only to people who can receive its marketing and haven’t switched that kind off, and a guest gets at most one a week.

People thinking of joining ResoFlow

  • Setup codes — if we prepare a venue’s account in advance, we keep the venue’s details, its proposed set-up, the owner’s name and email, any logo or images, and files and answers sent through a private upload link (which may include a customer list or bookings the owner chooses to send — the venue must be entitled to share them).
  • A visit from our team — if one of our team visits your venue, we note who we spoke to and their contact details (if given), your venue’s details, notes, and any photos you share with us. We use these only to follow up and to set up your account.
  • Launch or industry waitlist — your email, the industry or description you gave, the consent wording and when, a one-way network identifier and your browser’s user-agent. Used only to tell you when we’re ready for you; remove yourself with the link in your confirmation email, or ask us.
  • Booking a call — your name, email, phone, topic, notes and time slot, and a one-way network identifier. Used only to arrange the call.
  • Leaving your email with Rezo on our contact page — your address, first name if given, and the consent wording. Used only for that follow-up; withdraw by replying or emailing [email protected].

Support conversations with us

  • What you send (messages, attachments, and any documents or photos you send us about your account), your IP address and browser, and when you read our replies in the in-app chat (so we don’t also email a reply you’ve seen). If you’re not a venue user and email support@, billing@, policies@, security@ or privacy@, or use the chat on our website, we also keep your email address and the name you give.
  • Calling us — our phone line is answered first by Rezo, which says it is an automated assistant and that the call is transcribed. We keep your number, a transcript and a summary. We check your number against the mobiles on our venue accounts to recognise you, and before discussing a particular account we send a one-time code to that account’s phone or email. Rezo can only look things up and explain them; it may put you through to our team, and anything it can’t help with becomes a support conversation with us.
  • Our Rezo Phone demo line: the call isn’t recorded and we don’t keep anything from it, except a scrambled form of your number for one day so the demo can only be rung a few times a day.
  • Your conversations with us and with Rezo are seen by you and by ResoFlow — not by others at your venue. Messages ResoFlow sends to a venue go to its account owner, and a copy of our account emails is kept in your Messages.
  • When a chat with Rezo closes, Rezo keeps a short summary (never the transcript) to help next time; switch it off in Account → Preferences. If someone at a venue reports a Rezo result as wrong, we keep the report (which may quote a guest’s review or message) to put it right.
  • Sending something to our team through Rezo (only if you say yes) — what Rezo wrote, the page it’s about and, signed in, your name and venue; on our website, your email only if you add it. Used to improve ResoFlow.

Collected automatically

  • IP address, browser, operating system and device details.
  • Push alerts on your own devices: a push token, device type and browser, last use and your alert choices. Alerts never carry a phone number, email address, allergies or notes.
  • Cookies and similar storage — see our Cookie Policy. Google ad measurement and the Meta pixel, only if you choose advertising cookies on our own website — see section 6.
  • Google’s advert click reference, kept with a new venue’s sign-up record for 90 days, and (only if you chose advertising cookies) a hashed copy of your sign-up email.
  • Error reports (which may include a user ID), with a short, fully masked replay around an error on signed-in screens only.
  • Only if you choose analytics cookies, on our own website, sign-up and sign-in pages and the venue dashboard (never a guest’s page or a venue’s own website): which pages and features are used, and a recording of the visit so we can see where people get stuck. The recording shows our own menus, buttons and headings; everything typed, every picture and everything from a venue’s own records stays hidden. Signed-in people are known by an account reference, never by name or email.
  • Clicks on tagged links in marketing emails, and taps on the link in a venue’s campaign text (counted once, against a one-way reference). Our emails contain no tracking pixel, so opening one is never recorded.
  • Map images on venue pages load straight from Google Maps, and a video on a venue’s website from YouTube or Vimeo once you press play, so they see your IP address.

How people sign in

With Google, an email and password, or a passkey; staff use a PIN on a staff device; guests use an emailed code. We don’t buy marketing data or social-network friend lists.

3. Allergies and dietary needs

Allergy and dietary information is special category data. The venue is the controller and relies on your explicit consent (UK GDPR Article 9(2)(a)) when you choose to tell it. You can ask the venue to remove it at any time.

  • What you type when you book or order stays with that booking or order.
  • It’s saved to your customer profile at the venue only when you choose (for example by ticking “remember it” as you book, or in your account), and when you’re signed in we ask each time whether a saved allergy is for this visit. You can remove it from your profile at any time.
  • We show it only to the venue’s staff (on screen, on kitchen tickets and dockets, and in its new-booking emails) and on your own receipt for an order or pre-order. The venue is responsible for acting on it.

4. How we use your information

  • To run ResoFlow — accounts, bookings, orders, tickets, gift cards, loyalty, Team tools, payments and support.
  • Payments. Through Stripe Connect, a venue can take a deposit, payment in full, extras or a no-show fee on its own Stripe account, and can save your card when you book or with a “save a card” link. Saving a card never charges it by itself; the link shows any fee first. If your booking needs the venue’s approval, the deposit or payment shown to you is taken from the saved card when the venue accepts — never if it is declined or not answered, and the card is then released. If the venue also holds cards against no-shows and your booking has no deposit or payment in full, the card stays saved after the venue accepts, as the card held against no-shows for your booking. If the card is declined when the venue accepts, it is kept so it can be tried once more (a day later if your bank asked us to try again, or once by the venue) and released as soon as no try is left, at the latest the day after your booking. A no-show fee is charged when the venue marks a no-show or, if it switches this on, when you cancel after the free-cancellation deadline you agreed to — the fee and deadline are shown before you confirm. A party organiser may be asked to save a card for unpaid shares; it is then charged once, with a receipt naming whose share it paid (never what they chose), and never used for a no-show fee. The money goes to the venue; ResoFlow may take a platform fee.
  • Service emails and texts — to venues about their account, billing, credit and set-up (including reminders to finish signing up); to guests about their bookings (including one if a venue moves your upcoming booking to ResoFlow from another system), orders, payments, tickets, gift cards and loyalty membership, and messages from a venue about their visit. Emails about money can’t be switched off and are never marketing, and gift card emails are service messages too. Loyalty members get a warning before their record is deleted and before an unused balance expires, even if they’ve said no to marketing.
  • Marketing — a venue’s to its guests, on the bases in section 5; ours to venue owners, with consent.
  • AI tools — see below.
  • Support — answering chats and emails, with support messages, website chats and the files sent with them copied into Slack so our team sees them.
  • Keeping ResoFlow working and safe — monitoring performance, fixing faults, and preventing fraud, abuse and unauthorised access.
  • Legal duties — tax records, ICO orders and court orders.
  • Anonymous statistics — figures that can’t identify anyone (for example, total bookings), which we may use and share freely.

AI tools

Our in-app AI tools — including Rezo, our assistant — answer support questions, read files and pictures you give them (such as a menu, floor plan or poster), draft words and pictures for you, help you search, and check answers against our guides; our own team uses them to summarise and draft support work. They run on the AI services listed in section 6, and nothing sent to them is used to train any AI model. Rezo can also answer a venue’s phone, if the venue uses our phone assistant, through the provider for phone calls named in section 6.

Each job receives only what it needs. They’re never given card details, passwords or PINs, and guests’ contact details are left out or removed wherever a job doesn’t need them — Rezo can look up one booking at your venue with the guest shown by initials only, and each look-up is recorded in your Activity log. A copy of a picture or file Rezo reads is deleted once read, and only what you check and save is kept; words typed into search aren’t kept, and from an answer check we keep only the score. In the app, Rezo prepares changes for you to check and never changes anything itself. On a venue’s phone line, Rezo can make, change or cancel a booking, add someone to the waitlist, take a message or text a link — only when the caller asks, only in the ways the venue has switched on, and never taking card details. Jobs that cost Rezo credits show their price first; asking is free.

6. Who we share it with

We never sell personal data. We share it only with the providers that help run ResoFlow: payments, email, texts, phone calls, hosting, databases and sign-in, AI, support messaging, security and performance, analytics, error tracking and uptime, maps and delivery distances, wallet passes, push alerts, and public registers. Each one — what it does and where — is listed in our Data Processing Agreement. Providers that process data for us are bound by a data processing agreement; the wallet and push services and the public registers work under their own terms, linked there. Google Ads and Meta (below) aren’t on that list: they receive data under their own terms.

  • AI service providers that help us provide and support ResoFlow, including Rezo and our other AI tools in the app, which may use either: Google (Gemini, through Vertex AI, in the EU or the US) and Anthropic Ireland, Limited (Claude, in the US). Transfers to the US are made under the standard legal clauses. Both are listed in our DPA, and they may not use your data to train their models. Phone calls Rezo answers — for a venue or on our own line — go through ElevenLabs, which runs the conversation on an AI model through its own providers, in the US, under the standard legal clauses; it is listed in our DPA too.
  • Google Ads — only if you choose advertising cookies on our website. It learns when a visitor from one of our Google adverts starts signing up, opens our demo, looks at our prices or presses Book a call, as an independent controller under Google’s own terms and privacy policy. It learns that a new venue signed up, its business type and, later, that it first paid us (never the amount), with Google’s click reference and a hashed copy of the sign-up email address — never names, phone numbers or anything about venues’ guests. For that sign-up and payment data Google acts as our processor, under the Google Ads Data Processing Terms; for its own measurement it is an independent controller. No remarketing or personalised adverts. Untick it under Cookie preferences (in our footer) and it stops at once. To have the record deleted after signing up, ask us.
  • Meta (Facebook and Instagram) — only if you choose advertising cookies on our website. The Meta pixel tells Meta which of our pages you open (and the page you came from) and when you book a call with us or leave your email in our chat — never what you type — with your browser’s usual details, such as your IP address, and Meta’s cookies. We and Meta Platforms, Inc. (for EU visitors, Meta Platforms Ireland Limited) are joint controllers for collecting and sending this, under Meta’s Business Tools Terms; ask us about that part at [email protected]. Meta then uses it as its own controller under its Privacy Policy, including for the adverts it shows you. Untick advertising cookies under Cookie preferences (in our footer) and it stops at once; on Facebook or Instagram you can also turn off “Your activity off Meta technologies” in Meta’s Accounts Centre.
  • Wallet passes (Apple and Google), only if you save one. A pass carries what it shows (such as a booking’s details, a ticket holder’s name, or a card’s balance and code) and some carry the venue’s location so your phone can show them nearby; your location is never sent to the venue or to us.
  • A venue’s own webhooks (for example Zapier or Make). If a venue sets one up, we send the events it picks to the addresses it chooses; a guest’s name and contact details are included unless the venue switches them off, and allergy details, codes and payment links are never sent. If a destination is down, a message waits up to 24 hours in our EU cloud — even if the guest’s details are deleted meanwhile. The venue is the controller for that transfer; these destinations aren’t our sub-processors.
  • A venue’s own Mailchimp account, if the venue connects one. We keep the audience it picks in step with the guests who said yes to its email news — their name, email, and when and where they said yes; nothing else. A no in either place becomes a no in both, and deleting a guest here deletes them there too. The venue is the controller, and Mailchimp works for the venue under its own terms, not as our sub-processor. If the venue disconnects, we stop at once; what is already in its Mailchimp account stays in its care.
  • A venue’s own bookings calendar. If a venue on the Pro or Complete plan turns it on, its own calendar app (for example Google, Apple or Outlook Calendar) fetches its bookings from a private address: each booking’s time, party size, table, status and the first letter of the guest’s first name — never their surname, contact details, allergies or notes. Anyone the venue gives the address to can see this until the venue gets a new address or turns it off. The venue is the controller for that transfer; its calendar provider isn’t our sub-processor.
  • If ResoFlow is sold or merges, we’ll give notice before personal data moves under a different privacy policy.

7. Where your data is kept

Our database, servers and server logs (deleted after 30 days) are in Google Cloud’s europe-west1 region in Belgium. Sign-in accounts (Firebase Authentication: your sign-in email, hashed password and any second step) are processed in the United States; guests don’t have one. Sentry keeps our error data in the EU. Cloudflare sits in front of our websites (and a venue’s own connected domain) as a global network, so your request passes through its nearest data centre. Other providers’ locations are in the list in our DPA.

Where data leaves the UK we use the UK International Data Transfer Agreement or the EU Standard Contractual Clauses with the UK Addendum, plus the EU-US Data Privacy Framework and its UK Extension where a US provider is certified. Google Ads and Meta use their own safeguards (for Meta, those in its Business Tools Terms).

8. How long we keep it

We keep personal data only as long as we need it, or the law requires.

DataHow long
Venue account dataWhile the account is open. When an account is deleted or closed: 30 days (you can ask for a final export — Terms §13), then deleted. Cancelling a paid plan alone doesn’t start this.
Sign-ups not finishedDeleted 7 days after sign-up
Billing records and billing audit entriesUp to 7 years (HMRC)
Terms acceptance and business check recordsThe life of the account. After it closes, we keep a short record — the business’s name and company number, the owner’s email, which terms were accepted and when — for 6 years, in case of a contract claim.
A venue’s activity log and analytics totalsWhile the venue’s account is open
Our own routine logs; sign-up totals; delivery and click records of our own emails to venues24 months
Sign-in and device records — sign-in records, sign-in proofs, remembered computers, passkeys, devices we recognise on your sign-in, push tokens, staff devicesUntil removed, signed out or no longer used: sign-in records and proofs 31 days after last use (staff 12 hours); remembered computers 30 days unused; push tokens 60 days unused; passkeys and devices we recognise 13 months unused. A staff device’s address and browser are deleted when it is removed or after 180 days unused; its name and dates are kept so its old link can’t be used again.
Alerts in a venue’s dashboard30 days
Staff work records — rotas, rota requests, clock records, holiday and pay records, tips-record requestsWhile the person works at the venue (never more than 10 years after each record’s date). After they leave, a period the venue chooses — default 6 years, at most 10 — then their name and personal details are deleted and the pay and hours figures are kept without a name. Deleted shifts and weeks stay in Recently deleted for 30 days. A private rota link works until renewed, the person is removed, or 13 months unused.
Tipping policy recordsWith the venue’s account
Today’s notes (short notes a venue’s team leave for each other)30 days after the last day the note was for (a pinned note: 30 days after it is removed)
Guest profiles, and bookings with no paymentA period the venue chooses — default 2 years, at most 4 — from the guest’s last activity with the venue (a booking or visit, an order, a gift card or event ticket, loyalty activity, an enquiry, or a yes to its email news). Members are warned before deletion, and someone with a yes to its news gets one “Still want news?” email while the venue can still send news, then is removed after 30 days without an answer; a loyalty membership and balance go with the profile. A booking with no contact details (such as a walk-in) loses its name and notes after that period.
Loyalty and offer-code historyAs long as the guest’s profile; a line no longer linked to a profile, 2 years
Payment and gift card recordsThe life of the venue’s account. After the venue’s retention period, or if you ask to be erased, your personal details are permanently removed; the money facts and their payment reference stay. A card with money on it is never deleted by itself. Payment-link records are deleted 13 months after they were made; a payment we couldn’t complete keeps contact details only until it’s refunded or completed. A saved card is never charged after the booking is resolved, and is voided if you’re erased.
Messages with a venueWith the guest’s profile: kept while the guest is active, then for the venue’s chosen period from their last activity, or until erasure. A booking’s messages go with the booking.
Phone calls answered for a venueThe caller’s number, transcript and summary: 90 days. A short summary of a call from one of the venue’s guests (when, how long, what happened, the booking): with the guest’s profile. A recording (only if the venue records calls): 30 days. A booking or message from the call goes with that booking or the guest’s messages.
Messages we send to guestsA copy of each message other than a marketing campaign: 120 days after the visit (or after it was sent, when there is no visit). The record that it was sent, campaigns included: as long as the booking, guest record or account it belongs to.
Replies forwarded to a venue’s own emailWords removed once sent; the record of sending 90 days; an undeliverable one up to 12 months so it can be sent again
Short-lived links, codes and requests — “Notify me” requests, event waitlist places, check-in codes, sign-in codes and their request records, news sign-ups waiting for confirmation, loyalty confirmation and stamp links, unpaid checkouts, party food links, kitchen tickets sent to a printer, the kitchen’s copy of a pre-orderUntil used or shortly after their date — never more than 30 days after the booking, order, event, email or request they belong to
Small job records — review requests waiting to send, marks that a birthday message was sent, our announcements in a venue’s dashboardReview requests: 7 days after sending. Birthday marks: 30 days. Announcements: 90 days after they end
Marketing recordsConsent and its evidence: while relied on, deleted with the profile (we keep the most recent evidence). “No marketing” marker: the life of the venue’s account. Email “do not send” list: 24 months, or on erasure. Records of each guest’s campaign emails: with the guest’s profile (with no profile, the venue’s chosen period). Campaign text link taps: 90 days, or on erasure.
Erasure records (scrambled email or phone, so deletions survive a backup restore)120 days
Delivery logsEmails (the activity log’s Emails tab) 120 days (bounced 90 days; failed sends up to 12 months); texts with the guest’s profile (with no profile, the venue’s chosen period). Never longer than the venue keeps the guest’s details.
Records our providers keep (for example for email, texts, payments and error reports)Under their own retention rules, which their contracts with us limit
Ad videos a venue makes; website drafts never boughtAd videos: 30 days after they’re made. A website draft never bought: 90 days without the owner signing in or saving it
Exports and reportsData export downloads 24 hours; scheduled report PDFs 30 days; emailed reports 8 days (link 7 days); monthly accounts packs (no customer names or contact details) 7 years, or until the account closes
AI drafts and reads; Rezo summaries; reported Rezo results7 days; 30 days; 90 days
Support conversations and copies of account emailsA venue’s: while its account is open, then deleted with it. Outside senders’ conversations: 30 days after the last message. Attachments go with their conversation. Documents or photos sent about your account: deleted once dealt with, never more than 13 months after. Questions we keep to improve Rezo’s answers, and what you send our team through Rezo: 24 months. Calls to our phone line (your number, transcript and summary): 90 days; one-time codes (kept only in scrambled form): each works for 10 minutes and is deleted within a few days. A support conversation opened from a call is kept like our others.
Visit records (who we spoke to, notes and photos)12 months after our last contact. A logo or cover photo taken at a visit: deleted within a week unless used for your setup.
People thinking of joiningSetup codes and uploads: 30 days after we last worked on the setup, never more than 90 days in all (once used, part of the venue’s account; setup files emailed to us, within 30 days after the setup is used or cancelled). Call bookings: 90 days after the call. Waitlist sign-ups: until the launch you asked about, at most 12 months after you signed up, or until you ask us to remove you. An email left with Rezo: until the follow-up ends, at most 12 months.
Published reviewsWhile the venue’s account is open, or until you ask us to erase your details
Cookie consent records6 months
Advert click records on a new venue90 days from the click
BackupsDaily for 31 days, 7-day point-in-time recovery, and a weekly copy for 91 days in the EU; sign-in accounts are copied weekly and kept 90 days. Erased details leave backups within 91 days, and are erased again if we ever restore one.

9. How we keep it safe

We use appropriate technical and organisational measures to protect personal data, including encryption and limited, role-based access. Our team accesses a venue’s account only to support it, as section 5 of our Data Processing Agreement sets out, and never sees card numbers.

No system is 100% secure. If you think someone has got into your account, email [email protected] straight away.

10. Children

Account holders must be 18 or over, and their staff 16 or over. Guests booking or buying tickets should be 16 or over; the venue looks after any younger guest’s data. A guest may note children in their party (for example, a highchair), but we don’t collect data directly from children. If you think we have, email [email protected] and we’ll delete it.

11. Your rights

You can ask to access, correct, erase, restrict or move your data, object to processing based on legitimate interests, and withdraw consent at any time. We don’t make decisions about you by solely automated means with legal or similarly significant effects: a no-show fee follows the venue’s rules you saw before you booked, loyalty earns and redemptions follow what you do (a manual change is made by a named person with a reason), a venue may choose not to ask a regular for a deposit based on their history (it only ever means being asked for less), and Rezo makes no decisions about you: on a venue’s phone it only does what the caller asks, under the venue’s own booking rules.

We answer verified requests within 7 working days.

  • Venue owners — download your venue's data or close your venue at any time in Settings → Danger zone (your own personal data: Account → Your data), or email [email protected] from your account email.
  • Guests — ask the venue first; if it can’t help, email [email protected] and we’ll pass your request on. A venue can export or delete a record kept under your mobile number just as it can for an email address (payment records are kept without your details).
  • People who emailed our support addresses — email [email protected] from the same address.

You can also complain to the Information Commissioner’s Office: https://ico.org.uk/make-a-complaint/.

12. Cookies

We use essential storage to run ResoFlow, and analytics and advertising cookies only with your consent — so a Do-Not-Track browser is covered by default. We don’t show adverts on our site or build ad profiles; if you choose advertising cookies, Meta may use what it learns for the adverts it shows you (section 6). See our Cookie Policy.

13. Changes to this policy

We give 14 days’ notice, in the app and by email, before a material change takes effect. Typo fixes, formatting and clarifications just move the “Last updated” date.

14. Contact us

See also our Terms of Service and Cookie Policy.