Version 4 · Effective 4 November 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service between William Henry Peter Davey trading as Mise Team ("Processor", "we") and the Customer ("Controller", "you"). It applies whenever we process personal data on your behalf in providing the Service.
In this DPA, "Data Protection Law" means the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003 and, where applicable to a customer established in the EEA, the EU GDPR. Terms such as "controller", "processor", "personal data", "processing", "data subject" and "personal data breach" have the meanings given in Data Protection Law.
If there is a conflict between this DPA and the Terms of Service in relation to personal data, this DPA prevails.
1. Roles
You are the controller of the personal data in your Customer Data (your guests, staff, suppliers and contacts). We are your processor and act only on your documented instructions.
We are an independent controller of the limited personal data we need to run our own business: your account holders' contact details, billing records, support correspondence, usage and security logs. That processing is described in our Privacy Policy at https://www.miseteam.com/legal/privacy.
Where you connect a third-party service (such as Stripe, Xero or Square) you instruct us to send data to and receive data from that service. The provider processes that data under its own agreement with you.
2. Details of processing
Subject matter: provision of the Mise Team restaurant-management service (bookings, guest records, staff and HR, rotas and time, kitchen and compliance records, stock and finance, messaging and AI assistance).
Duration: the term of the Agreement plus the retention and deletion period in section 9.
Nature and purpose: hosting, storing, organising, displaying, transmitting (email, SMS), analysing and deleting Customer Data so that you can run your venues; generating AI outputs from content you submit.
Categories of data subject: your guests and event attendees; your staff, applicants and leavers; your suppliers' and contractors' contacts; your Authorised Users.
Types of personal data — guests: name, contact details, booking history, party details, notes, dietary requirements and allergies (special category: health), payment and deposit references (card data is held by Stripe, not by us), marketing preferences and feedback.
Types of personal data — staff: name, contact and emergency details, date of birth, National Insurance number, bank details for payroll export, right-to-work documents (which may reveal nationality and immigration status), contracts and pay, hours, holiday and absence including sickness (special category: health), training, disciplinary and HR notes, clock-in location where enabled, and photos where uploaded.
Special category data is processed only because you have chosen to record it for your legitimate purposes as an employer or food business, under your own lawful basis and condition (for example, allergen safety and employment-law obligations).
3. Your instructions
Your instructions are: the Agreement, your configuration of the Service (settings, roles, retention rules, integrations, templates) and your use of its features. Further written instructions may be agreed by email.
We will tell you if, in our opinion, an instruction breaches Data Protection Law. We are not obliged to carry out an instruction we reasonably believe to be unlawful.
We will process personal data only on your instructions unless required to do otherwise by UK law, in which case we will tell you before processing (unless the law prohibits this).
4. Our obligations
Confidentiality: anyone we authorise to process personal data is bound by a duty of confidentiality and has access only to the extent needed.
Security: we implement appropriate technical and organisational measures, taking account of the state of the art, cost, the nature of the processing and the risks to individuals, as set out in Annex 2.
Assistance: taking into account the nature of the processing, we help you respond to data-subject requests (access, rectification, erasure, restriction, portability, objection) by providing tools in the Service and, where needed, by direct assistance. We will pass on without undue delay any request we receive directly, and will not respond to it ourselves except to redirect the individual to you.
We also help you meet your obligations on security, breach notification, data-protection impact assessments and prior consultation with the ICO, taking into account the information available to us.
Records and information: we keep the records required of a processor and will make available the information reasonably necessary to demonstrate compliance with Article 28.
Audits: once a year, or after a personal-data breach, you may audit our compliance by written questionnaire. If that is reasonably insufficient, an on-site or remote audit may be carried out on 30 days' notice, during business hours, no more than once per year, by you or an independent auditor bound by confidentiality, at your cost, and without disrupting other customers. Our hosting providers' SOC 2 / ISO 27001 reports are relied on for infrastructure controls.
5. Personal-data breaches
We will notify you without undue delay, and in any event within 48 hours, after becoming aware of a personal-data breach affecting your Customer Data. Notification goes to the account owner's email address.
The notice will describe, so far as known, the nature of the breach, the categories and approximate number of data subjects and records, likely consequences, measures taken or proposed, and a contact point. Information may be given in phases as it becomes available.
We will cooperate with you and take reasonable steps to contain, investigate and remedy the breach. You are responsible for deciding whether to notify the ICO or data subjects, and for doing so.
6. Sub-processors
You give general written authorisation for us to use the sub-processors listed at https://www.miseteam.com/legal/subprocessors (Annex 3). Each is bound by a written contract imposing data-protection obligations equivalent to this DPA.
We will give at least 30 days' notice before adding or replacing a sub-processor, by updating the list and emailing account owners. You may object on reasonable data-protection grounds within that period; if we cannot resolve the objection you may terminate the affected Sites and we will refund any fees prepaid for the period after termination.
We remain fully liable to you for the performance of our sub-processors' obligations.
7. International transfers
Customer Data is stored at rest in the United Kingdom (London region). Some sub-processors process data in the United States or the EEA when delivering email, SMS, payments or AI features.
We transfer personal data outside the UK only (a) to a country covered by UK adequacy regulations (including the EEA and, for certified organisations, the UK Extension to the EU-US Data Privacy Framework), or (b) under the ICO's International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, with supplementary measures where needed.
On request we will tell you which mechanism applies to each sub-processor.
8. Your obligations
You warrant that you have a lawful basis (and, for special-category data, an Article 9 condition) for the personal data you process in the Service; that you have given appropriate privacy information to your guests and staff; and that your instructions comply with Data Protection Law.
You are responsible for the accuracy and quality of Customer Data, for configuring roles, retention and marketing settings appropriately, and for consents required for electronic marketing.
You must not upload personal data that is not needed for running your venues, and you must not use the Service to process data about children under 13 except incidentally (for example, a child in a booking party).
9. Return and deletion
During the Agreement you can export Customer Data from the Service at any time.
When the Agreement ends we keep your Customer Data for 30 days so you can export or reactivate, then delete or anonymise it within a further 60 days, unless UK law requires retention. Copies in encrypted backups are overwritten on the normal backup cycle (no more than 90 days). On request we will confirm deletion in writing.
Some records are kept past those 90 days, and only for as long as stated: (a) the PAYE records an employer must keep — pay runs and the payroll exports sent with them, pay-rate changes, leaver and P45 details, starter checklists, and the employee record they belong to — until 3 years after the end of the tax year they relate to (Income Tax (PAYE) Regulations 2003); (b) clock-in and approved-hours records and pay runs, with the employee record they belong to, until 6 years after their date (National Minimum Wage Regulations 2015); (c) your personal-data breach log, until 6 years after each breach was closed, and your data-request log, until 6 years after each request was completed (UK GDPR art. 5(2) and 33(5)); and (d) anything about a person you have placed on legal hold, until the hold is lifted. Health notes, emergency contacts, free-text notes, location points and requesters' contact details are removed from the records in (a) to (c). We hold them only to meet those obligations, with no automated processing and no access for anyone but us, give you or HMRC a copy on request, and then delete them on the same nightly schedule.
Deletion carried out by you inside the Service (for example, deleting a guest or running a retention purge) is actioned immediately in the live database and removed from backups on the same cycle.
10. Liability and term
Each party's liability under this DPA is subject to the limitations and exclusions in the Terms of Service, except that nothing limits a party's liability to data subjects or supervisory authorities under Data Protection Law where the law does not permit it.
This DPA starts when the Agreement starts and lasts until we have deleted all Customer Data under section 9.
Contact for data-protection matters: privacy@miseteam.com.
Annex 1 — Processing details
Controller: the Customer named in the account. Processor: William Henry Peter Davey trading as Mise Team, Grafton House, Gretton Fields, Gretton, Cheltenham, Gloucestershire, GL54 5HH, United Kingdom.
Subject matter, duration, nature, purpose, data subjects and data types: as set out in section 2.
Processing locations: United Kingdom (primary storage and compute); United States / EEA for sub-processors listed in Annex 3.
Annex 2 — Technical and organisational measures
Encryption: TLS 1.2+ for all data in transit; AES-256 encryption at rest for the database, file storage and backups.
Tenant isolation: every record carries a restaurant (tenant) identifier and database row-level security policies enforce that users only see data for venues they belong to; the same checks are applied in server-side functions.
Access control: role-based permissions (owner, manager, staff) set by the Customer; staff-app features gated by site access; our own administrative access restricted to the proprietor, protected by strong credentials and used only for support, security and maintenance.
Authentication: email and password with minimum length and leaked-password checks, email verification, secure session tokens, and rate limiting of sign-in attempts; optional single sign-on where enabled.
Application security: input validation, parameterised queries, content-security and frame-protection headers, rate limiting on sensitive endpoints, dependency monitoring and regular code review.
Logging and monitoring: audit log of significant actions in the Service; server error monitoring with daily digests; access logs retained for security investigation.
Backups and resilience: automated database backups retained for a rolling period on our hosting provider's schedule; infrastructure hosted on providers with ISO 27001 / SOC 2 certifications.
Data minimisation and retention: automated nightly purging to the retention schedule (guest records 3 years after the last visit, enquiries 12 months, feedback 2 years, meeting audio 6 months, right-to-work copies 2 years after leaving, assistant conversations 90 days; a closed account 90 days after cancellation, except PAYE, minimum-wage, breach-log and data-request records and legal holds as in §9); guest erasure and export tools for the Customer; special-category and HR fields redacted from the change history; card data never stored (held by Stripe).
Incident response: documented breach procedure with 48-hour customer notification; post-incident review.
Confidentiality: anyone with access to personal data is under a duty of confidentiality; sub-processors bound by written data-processing terms.
Annex 3 — Sub-processors
The current list, with purpose and location for each, is maintained at https://www.miseteam.com/legal/subprocessors and is incorporated into this DPA. Transfer mechanism for each provider:
Supabase, Inc. (United Kingdom (AWS eu-west-2, London)): Stored in the UK. Support access from the US under the UK International Data Transfer Addendum to the EU Standard Contractual Clauses (in Supabase's DPA).
Vercel Inc. (Functions run in London (lhr1); static content served from a global CDN): US company: UK Extension to the EU-US Data Privacy Framework (certified), with the UK Addendum to the SCCs in Vercel's DPA as a fallback.
Stripe Payments UK Ltd / Stripe, Inc. (United Kingdom, EEA and United States): UK Extension to the EU-US Data Privacy Framework (certified) and the UK Addendum to the SCCs in Stripe's DPA.
Resend, Inc. (United States (EU sending region where configured)): UK International Data Transfer Addendum to the EU Standard Contractual Clauses (Resend DPA).
Twilio Inc. (United States, with EU routing where available): UK Extension to the EU-US Data Privacy Framework (certified) and Twilio's Binding Corporate Rules / UK Addendum in its DPA.
OpenAI, L.L.C. / OpenAI Ireland Ltd (United States, or the EEA where the EU data-residency project is selected): UK Extension to the EU-US Data Privacy Framework (certified) and the UK Addendum to the SCCs in OpenAI's DPA; EEA processing covered by UK adequacy regulations.
Mistral AI SAS (European Union (France / Sweden)): EEA: UK adequacy regulations.
Google LLC (Gemini API, paid tier) (United States and other Google Cloud regions): UK Extension to the EU-US Data Privacy Framework (certified) and the UK Addendum to the SCCs in Google Cloud's data-processing terms.
Zoho Corporation B.V. (European Union (Zoho EU data centres, Netherlands / Ireland)): EEA: UK adequacy regulations.
AI providers: only the provider selected for the Service receives AI inputs. Changing to a different provider is a sub-processor change and is notified under section 6 at least 30 days in advance.