About this DPA
This Data Processing Agreement (the “DPA”) is part of the ResoFlow Terms of Service. It covers the personal data your venue handles through ResoFlow, as Article 28 of the UK GDPR requires. You agree to it when you create a ResoFlow account.
“You” means the business that holds the ResoFlow account. “We” means Caleonix LTD (company number 17162652), which runs ResoFlow. Legal terms such as “controller” and “personal data breach” mean what they mean in the UK GDPR.
1. Who’s who
- You are the controller of the personal data processed through ResoFlow for your venue. We are your processor.
- The companies listed in section 7 process it for us. The few listed there that work under their own terms instead — such as the wallet and push services, the public registers and accounts you connect yourself — are listed separately.
2. What we process and why
We process personal data only as reasonably needed to provide ResoFlow to you under the Terms of Service.
| Subject matter | Personal data of your guests, your staff, the people who run your account, and anyone who contacts ResoFlow support. |
|---|---|
| Duration | The life of your account, plus 30 days after it is deleted or terminated (section 12). Backup copies then age out as our Privacy Policy sets out; support messages are kept as it sets out too. |
| What we do with it | Taking and managing bookings, waitlists, event tickets and orders · sending your emails and texts to guests, and handling their replies · messages through your website’s contact form (kept in your Messages on every plan) · payments taken through your Stripe account, payments recorded at the venue, refunds and no-show protection · the optional features you switch on (such as offers, loyalty, gift cards, pre-orders, reviews, wallet passes, team and rota tools, sending events to your own web addresses, and keeping your own email-marketing account in step with the guests who said yes to your email news) · analytics for you · customer support through the in-app chat, our email addresses, Rezo (our AI assistant) and our team’s internal messaging. |
| Whose data | Guests — anyone who books, joins a waitlist or asks to hear when a table frees up, buys a ticket or a gift card (or receives one), orders, chooses food by link, joins your loyalty scheme, messages you, calls your phone line through Rezo, or signs up for your news; they needn’t have booked. Your staff, added by you. Account owners and admins. Support contacts — people outside your venue who email our support addresses or use the chat on our website. |
| What data | Guests: contact details; booking, ticket, order, pre-order, gift card, loyalty and review records; visit history imported from your previous system; dietary and allergy notes; answers to your booking questions; delivery addresses; marketing choices and proof of consent (including a one-way fingerprint of someone who said no, so they aren’t sent marketing again); your team’s notes and tags; messages with you; calls Rezo answers for you (the caller’s number, a transcript and summary, and a recording only if you switch recording on); copies of the emails and texts we send them for you (other than marketing campaigns), and a record that each was sent, campaigns included (kept as our Privacy Policy sets out); delivery and link-click records for your marketing; invite-reward links between members; payment references and records of money taken at the venue (never a card number); wallet-pass device tokens. Your staff: name, role and permissions, optional work contact details, a scrambled PIN, sign-in and device records and, if you use the team tools, shifts, availability, time off, clock-in times, holiday records, rota acknowledgements and alert choices, push tokens for their own phones (if they turn alerts on) and optional pay rates (seen by owners and admins, and anyone you give permission to see pay). Unless you switch it off, each member of staff’s rota page also shows the names, shift times and areas of colleagues on the published rota — never pay, notes, contact details or time off. Owners and admins: name, contact and billing details, two-step sign-in and passkey records (never biometric data), sign-in history (including internet addresses and a rough town for each device), push-alert settings, acceptance records and a record of their actions. Support contacts: email address, message, the IP address and browser at the time, and Rezo conversation records. Our Privacy Policy lists all of this in more detail. |
| Special category data | Guests’ allergy and dietary information (with a booking, an order or a pre-ordered dish, and the answer to an allergy question), processed under Article 9(2)(a) — explicit consent: the guest gives it so it can be catered for. A booking’s note stays with that booking; it is kept on the guest’s profile only if the guest asks for that or your staff save it on purpose. Staff sickness: if you record time off as sickness, only the dates are kept — never a reason or health details — and it shows as sickness only to that person, your owners and admins and your rota approvers; everyone else, and the person’s private rota link, sees “Off”. |
| AI | Rezo and our AI tools receive only what each job needs. Rezo can read one booking you name, with the guest shown by initials only — never contact details, notes or allergies — and each look-up is recorded in your Activity log; for a member of staff it reads only their own published shifts. Rezo conversation summaries and reports of a wrong result are kept for the short periods in our Privacy Policy. None of what our in-app AI tools receive is used to train AI models. If you use Rezo on your phone line, it answers your callers through the sub-processors in section 7 and acts only through the skills you switch on; it never takes card details. |
| Payments on your own Stripe account | Deposits, no-show fees, tickets, gift cards, orders, pre-orders and payment links are paid to you on your own connected Stripe account — you are the merchant. Stripe processes those payments under your own agreement with Stripe, not as our sub-processor; we pass Stripe what each payment needs on your instruction, and never see or store a guest’s card details. Platform fees are as the Terms of Service set out. |
3. Your promises
You confirm that you:
- have a lawful basis under the UK GDPR for the processing you ask us to do;
- give us accurate, lawfully obtained personal data;
- handle requests from people about their own data, with our help (section 9);
- tell us promptly if your instructions to us change in a way that matters.
4. Our promises
We will:
- process personal data only on your documented instructions — signing up and using ResoFlow as it is offered is your instruction — and tell you straight away if we think an instruction breaks data protection law;
- make sure everyone authorised to process it is bound by confidentiality;
- keep the security measures in section 6 (UK GDPR Article 32);
- follow section 7 when we use sub-processors;
- help you meet your duties under Articles 32 to 36 of the UK GDPR (security, breaches, impact assessments and consulting the ICO);
- give you the information you reasonably need to show we keep to this DPA, and allow audits (section 11);
- delete or return the data when your account ends (section 12).
5. Support access
When you ask for help, or when we need to look into a fault, a security event or a billing question, our authorised team may view your account and the personal data in it. Viewing is read-only. We may use the AI services listed in section 7 in this work; they act within the same limits and receive personal data only where the work needs it.
We change your data only during a time-limited support session you start — with a one-time code, by accepting a request, or under a standing permission you set (90 days at most) — and never to move money, delete data or transfer the account.
Outside a session we may also:
- use our own account tools as the Terms of Service allow — for example billing and plan changes, suspending an account or a feature, switching off a misused promo code, removing a review you have reported, or a change of owner;
- change your venue’s name or web address when you ask us in writing (the old web address keeps forwarding to the new one, and the account owner is emailed when it changes);
- apply a setup we prepared with you while the owner is with us (a setup done remotely needs a session);
- return a guest’s payment that ResoFlow could not complete or refund automatically.
Every session, every name or web-address change, every setup applied and every payment returned this way is recorded in your Activity log, as is every time our team sees a guest’s email address. The account owner is emailed when a session ends. If your venue has joined another person’s account, the emails about a changed web address and an ended session go to the venue’s original owner too.
6. Security
- Data is encrypted in transit and at rest.
- Our websites, venues’ own domains and public forms are protected against attacks and automated abuse.
- Access is role-based, with least-privilege defaults and per-person permissions. Two-step sign-in is available to every owner and admin; staff sign in only on devices an owner or admin has paired; and sensitive actions — such as deleting data, refunds, role changes and exports — need the person to confirm who they are again.
- Sign-in accounts use Firebase Authentication, with passwords hashed by Google. Google runs it only in the United States, so your owners’ and staff’s sign-in accounts are processed there (section 8).
- Our server logs are kept in the EU (Belgium) and deleted after 30 days.
- Activity log records are kept while your account is open, on every plan (how far back you can see depends on your plan). Billing records are also copied to a separate tamper-resistant log and kept 7 years, as HMRC requires.
- We use error tracking, uptime monitoring and periodic security reviews.
- Backups: daily snapshots kept 31 days, 7-day point-in-time recovery, and a weekly copy of the database and sign-in accounts kept 91 days in the EU.
- A written incident-response process, reviewed periodically and after any material incident; material incidents are reported on our status page. A summary is available from [email protected].
7. Sub-processors
You give us general written authorisation to use sub-processors, on these conditions:
- We give at least 30 days’ notice before adding a new sub-processor that will process personal data as part of the way you already use ResoFlow. A new sub-processor that only powers an optional feature is listed here before you switch the feature on; switching it on is your authorisation for that feature, and you are free not to. To get these notices by email, email [email protected] with the subject “Subscribe to subprocessor updates”.
- You may object on reasonable grounds and, if we can’t resolve your objection, end your contract without penalty.
- Each sub-processor is bound by a written contract with data-protection duties substantially the same as this DPA’s (its data processing agreement is linked under its name).
- We stay responsible to you for what our sub-processors do.
The list below is the current list and is updated in this section.
| Who | What for | Where | Safeguard |
|---|---|---|---|
| Google LLC (Firebase / Google Cloud) Google Cloud DPA | Database, hosting and server code; sign-in accounts. | EU (Belgium); sign-in accounts in the US | UK adequacy; standard clauses for sign-in |
| Google LLC (Vertex AI) Google Cloud DPA | AI services that help us provide and support ResoFlow, including ResoFlow’s own AI features. They’re not allowed to use your data to train their models. | EU or US | UK adequacy (EU); the standard legal clauses (US) |
| Anthropic Ireland, Limited (Claude) Anthropic DPA | AI services that help us provide and support ResoFlow, including ResoFlow’s own AI features. They’re not allowed to use your data to train their models. | United States | The standard legal clauses (EU SCCs with the UK Addendum) |
| ElevenLabs ElevenLabs DPA | Answers and transcribes phone calls with an AI voice — for venues that use our phone assistant, and on our own phone line. Records a call only where the venue switches recording on. | United States | The standard legal clauses (EU SCCs with the UK Addendum) |
| Google LLC (Firebase Cloud Messaging) Google Cloud DPA | Push alerts to devices that have turned them on — no contact details. | US / global | Standard clauses |
| Cloudflare, Inc. Cloudflare DPA | Security, CDN, DNS, bot checks and cookieless page counts; serves venues’ own domains. | Global (nearest data centre) | Standard clauses |
| Stripe Inc. Stripe DPA | Our own subscription billing. (Guest payments on your own Stripe account are processed under your own agreement with Stripe — see section 2.) | US / Ireland | Standard clauses |
| Resend Inc. Resend DPA | Sending and receiving email, including from a venue’s own domain. | EU (Ireland) | UK adequacy |
| divergent UK Operations Ltd (PureSMS) divergent DPA | Our main text (SMS) provider. Text records kept 3 months. | EU (Germany) | UK adequacy |
| Twilio Inc. Twilio DPA | Texts, used alongside PureSMS; phone numbers and calls for our phone assistant, including the business details UK rules need to register a number. | US / Ireland | Standard clauses |
| Slack Technologies LLC Slack DPA | Internal messaging: support conversations (including website chats) and their files, business activity updates and service alerts. | US | Standard clauses |
| Functional Software Inc. (Sentry) Sentry DPA | Error tracking; a short masked replay on signed-in screens only, never guest pages. | EU | UK adequacy |
| PostHog PostHog DPA | Product analytics and masked recordings of visits to our own website and dashboard, only after an analytics-cookies yes — never on guest pages. | EU | UK adequacy |
| BetterStack BetterStack DPA | Uptime monitoring and our status page. | EU | UK adequacy |
| Google LLC (Google Analytics 4) Google Ads Data Processing Terms | Aggregate web analytics. | US | Standard clauses |
| Google LLC (Google Maps Platform) Google Maps Platform DPT | Address look-up, maps on venue pages and delivery distances — never a guest’s name or contact details. | US | Standard clauses |
ResoFlow’s own AI features — Rezo and the other AI tools in ResoFlow — may use either AI provider above: Google (Gemini, through Vertex AI, in the EU or the US) or Anthropic (Claude, in the US); phone calls are answered through ElevenLabs (our Privacy Policy says what they receive). “Standard clauses” means the UK International Data Transfer Agreement, or the EU Standard Contractual Clauses with the UK Addendum (section 8). “UK adequacy” means the data stays in the EU, which UK law treats as adequate.
Listed for transparency — these work under their own terms, not as our sub-processors:
| Who | What for | Where |
|---|---|---|
| Apple Distribution International Ltd. (Apple Wallet) Apple Privacy Policy | Wallet passes a guest chooses to add: bookings, tickets, loyalty and gift cards. | Ireland / EU |
| Google LLC (Google Wallet) Google Privacy Policy | Wallet passes a guest chooses to add: bookings, tickets, loyalty and gift cards. | US |
| Apple Inc. (Apple Push Notification service) Apple Privacy Policy | Relays encrypted push alerts to Apple devices; it can’t read them. | US / global |
| Mozilla Corporation (Firefox push service) Mozilla Privacy Notice | Relays encrypted push alerts to Firefox; it can’t read them. | US / global |
| Microsoft Corporation (Windows push service) Microsoft Privacy Statement | Relays encrypted push alerts to Microsoft Edge; it can’t read them. | US / global |
| OpenStreetMap Foundation (Nominatim) OSMF Privacy Policy | Places a venue’s address on its wallet passes — the venue’s address only. | UK / EU |
| rdap.org About RDAP | Checks when a venue’s own domain expires — the domain name only. | Public registries |
| Stripe (your own Stripe account) Stripe Connected Account Agreement | Guest payments you take through ResoFlow, under your own agreement with Stripe. | US / Ireland |
| Companies House Companies House register | Business check — the company number or name a venue gives us. | UK |
| Food Standards Agency Food hygiene ratings | Business check — the venue’s postcode. | UK |
| Mailchimp (your own Mailchimp account) Mailchimp Data Processing Addendum | Your own Mailchimp account, if you connect it: the name, email and marketing yes of guests who said yes to your email news, and their unsubscribes back. It works for you under your own Mailchimp terms. | As your agreement with Mailchimp sets out |
Our website’s status badge loads BetterStack’s public status feed straight from your browser; BetterStack sees that request (such as your IP address) but receives no personal data from us. This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com.
8. International transfers
Some sub-processors work outside the UK. Personal data goes outside the UK and the EU only under the UK International Data Transfer Agreement (IDTA) or the EU Standard Contractual Clauses with the UK Addendum. Where a US sub-processor is certified under the EU–US Data Privacy Framework and its UK Extension, that may apply as well.
9. Helping with people’s rights
You handle requests from people about their own data, and we help:
- Your team can download or delete one guest’s data from that guest’s page in Customers (Download their data and Delete customer), and the account owner can download the whole account’s data. If your venue has joined another person’s account, the venue’s original owner is emailed the download link too.
- For anything harder, email [email protected].
- We respond to any such request within 7 working days.
10. Personal data breaches
We will tell you without undue delay, and in any case within 72 hours of becoming aware, of any personal data breach affecting your data. We’ll include what we know of: what happened; roughly how many people and records are involved, and of what kinds; the likely consequences; and what we have done or plan to do about it.
You are responsible for telling the ICO (UK GDPR Article 33) and the people affected (Article 34) where that is needed.
11. Audits
You may audit our compliance with this DPA once in any 12 months, on 30 days’ written notice, at your own cost, with our reasonable help and under a mutual non-disclosure agreement.
12. When your account ends
When your account is deleted or terminated, you have 30 days to ask for a full export of your data: email [email protected] from the owner’s sign-in email (for a venue that has joined another person’s account, the account owner’s or the venue’s original owner’s). Within 7 working days we send a secure download link, valid for 24 hours. After the 30 days we permanently delete the data, apart from anything the law requires us to keep (see the retention table in our Privacy Policy).
Cancelling a paid plan or product doesn’t start this window. What you cancelled ends at the end of the paid period — a cancelled plan moves the account to the Free plan (or to the products it keeps), and a cancelled product leaves your subscription — and your account stays open.
13. Liability, precedence and law
- Liability under this DPA is governed by section 15 (Limitations of liability) of the Terms of Service.
- If documents conflict, this order applies: the UK GDPR, then this DPA, then the Terms of Service.
- This DPA applies for as long as we process personal data for you (section 2).
- It is governed by the laws of England and Wales, like the Terms of Service.