Technology, data and AI

Subject access requests from guests and staff: a how-to

How a restaurant or pub should spot, verify and answer a subject access request from a guest or employee, with the one-month clock, searches and redaction.

Ava research teamPublished 7 min read

On this page
  1. What a subject access request is
  2. The clock: one month, sometimes more
  3. Why staff requests are rising
  4. Guest requests: usually simpler
  5. Verifying identity without obstructing
  6. Searching: reasonable and proportionate
  7. Redacting other people
  8. Responding step by step
  9. Fees, refusals and repeat requests
  10. Getting ready before the first request
  11. Frequently asked questions
  12. References

Key takeaways

  • You normally have one month to respond, extendable by two further months for complex or numerous requests if you tell the person within the first month[1].
  • The clock pauses while you wait for information you reasonably need to find what the request covers[1].
  • You must provide what a reasonable and proportionate search finds, free of charge in most cases[2][1].
  • Most venue requests come from staff and former staff, often around disputes; employment tribunal time limits are now 6 months[3].

What a subject access request is

Anyone whose personal data you hold can ask you for a copy of it, along with information about how you use it. This is the right of access under UK GDPR, and a request to use it is called a subject access request, or SAR. It does not need to use those words, mention the law or arrive in a particular format. An email from a former server asking for “everything you have on me”, a guest's message on Instagram asking for the CCTV of their visit, or a letter from a solicitor acting for an employee can all be valid requests.

The most important skill for a venue is recognising a request when it arrives, because the clock starts then. Train managers to forward anything that looks like a request for someone's own information to one named person on the same day.

The clock: one month, sometimes more

You must respond without undue delay and within the applicable time period, which is one month from the relevant time[1]. The relevant time is the latest of when you receive the request, when you receive any information you asked for to confirm identity or clarify the request, and when any permitted fee is paid. You can extend the period by two further months where that is necessary because of the complexity or number of the person's requests, but only by telling them before the first month ends and giving your reasons[1].

There is also a useful pause. If you reasonably need more information to identify what the request relates to, for example because you hold a large amount of data about the person, you can ask them for it, and the days between asking and receiving the answer do not count towards the deadline[1]. Use this honestly, to narrow a vague request, not as a way to delay.

Time limit for most employment tribunal claimsEmployment Rights Act 2025 changes, as summarised by Acas
Time limit for most employment tribunal claimsComparison. Before 1 October 2026: 3 months; From 1 October 2026: 6 months.3 monthsBefore 1 October 2026Before 1 October 2026: 3 months6 monthsFrom 1 October 2026From 1 October 2026: 6 monthsTime limit for most employment tribunal claimsComparison. Before 1 October 2026: 3 months; From 1 October 2026: 6 months.3 monthsBefore 1 October 2026Before 1 October 2026: 3 months6 monthsFrom 1 October 2026From 1 October 2026: 6 months

Source: Acas, 2026[3]

Show the data
ItemValue
Before 1 October 20263 months
From 1 October 20266 months

Why staff requests are rising

In hospitality, most requests come from employees or former employees, and they often arrive alongside a grievance, a dismissal or a pay dispute. The legal backdrop makes this more likely. Since 1 October 2026, the time limit for most employment tribunal claims has been 6 months, up from 3[3]. From 1 January 2027, employees can claim unfair dismissal after 6 months in a job instead of 2 years[4]. Since 6 April 2026, employers must keep records of annual leave and holiday pay for at least 6 years[5]. More people with possible claims, more time to bring them and more records to request all point the same way.

A request from someone in a dispute is still a valid request. You cannot refuse it because you suspect they want evidence for a claim. Answer it properly and on time; a sloppy or late response often becomes part of the dispute itself.

Guest requests: usually simpler

Requests from guests are less common and usually narrower. A guest might want to know what notes you keep about them after a complaint, ask for footage after an incident in the car park, or simply be curious about what a booking platform shares with you. The search is normally limited to the booking system, emails, any complaint file and CCTV.

Two points catch venues out. First, if the guest booked through a platform that is a controller in its own right, it may hold far more about them than you do; answer for your own data and tell them they can also ask the platform. Second, CCTV is usually overwritten quickly, so act on the same day to preserve footage if the request mentions a specific date. If the footage has already been overwritten in the normal way before the request arrived, explain that clearly in your reply.

Verifying identity without obstructing

You need to be satisfied that the person asking is who they say they are, or is properly authorised to act for them. Be proportionate. A current employee emailing from their known work or personal address rarely needs further checks. A request from an unfamiliar email address for CCTV of a busy Saturday night might justify asking for a photo or details only the guest would know, such as the time and table of their booking. If a solicitor or family member asks on someone's behalf, ask for written authority.

Ask for verification quickly, ideally in your acknowledgement. Remember that the clock starts again from when you receive what you asked for, but only if the request was reasonable.

Searching: reasonable and proportionate

The person is entitled to the confirmation, data and information you can provide based on a reasonable and proportionate search[2]. That does not mean reading every message ever sent in the venue, but it does mean looking in the places where their data is likely to be. In a restaurant, that list is longer than most owners expect.

Where personal data about guests and staff is commonly held in a venue
Where to lookWhat it might holdWho checks it
Booking systemBookings, notes, no-show records, allergy notesRestaurant manager
EPOS back officeStaff logins, voids, discounts, sales by serverGeneral manager
Rota and time-tracking appShifts, clock-ins, absence, holiday recordsRota manager
Payroll and HR filesContract, pay, tips allocation, disciplinary and sickness recordsOwner or HR
Email accountsMessages about the person, complaints, referencesEach manager for their own inbox
WhatsApp and staff group chatsMessages naming the person, on work or personal phonesManagers who run the groups
CCTV recorderFootage of the person, if still within the retention periodWhoever manages the system
Paper recordsAccident book, incident reports, handwritten notesGeneral manager

Staff group chats deserve attention. Messages about an employee in a managers' WhatsApp group are personal data about that employee, whether or not the phones are owned by the business. If they are relevant, they are in scope.

Redacting other people

Documents and footage often include other people: colleagues in a disciplinary email, guests at neighbouring tables on CCTV. You must balance the requester's right of access against those people's rights. Usually that means redacting names and identifying details of others, blurring faces in footage, or asking the other person for consent. Keep a short note of what you redacted and why.

Responding step by step

  1. Log it on day one

    Record the date received, who asked, what they asked for and the deadline. Use a simple shared spreadsheet.

  2. Acknowledge

    Reply within a couple of days confirming receipt, the deadline, and any identity check or clarification you need.

  3. Preserve

    Stop routine deletion of relevant data, especially CCTV, until the request is closed. Deleting data after a request arrives to avoid disclosing it can be an offence.

  4. Search

    Work through the table above. Ask each person who holds data to search and send results by a set date.

  5. Review and redact

    Remove anything that is not the requester's data, redact third parties, and consider whether any exemption, such as legal advice, applies.

  6. Send the response

    Provide a copy of the data and the supporting information: purposes, recipients, retention, source and rights. If they asked electronically, reply electronically unless they asked otherwise[2].

  7. Close the log

    Record what you sent and when, and keep that record.

Example acknowledgement: “Thank you for your request dated 3 March for a copy of the personal data we hold about you. We will respond by 3 April. So we can search the right places, could you confirm whether your request includes CCTV, and if so the dates of the visits you are interested in?”

Fees, refusals and repeat requests

Responding is free in almost every case. You can charge a reasonable fee based on administrative costs, or refuse to act, only where a request is manifestly unfounded or excessive, for example because it is repetitive[1]. You can also charge a reasonable fee for further copies of the same data[2]. If you refuse, you must tell the person why and explain that they can complain to you, to the regulator and to the courts. Use refusal rarely and document your reasons, because the burden is on you to justify it.

Getting ready before the first request

  • Name one person to handle requests, with a deputy for holidays.
  • Add a privacy contact to your privacy notice so requests reach the right inbox.
  • Keep a short list of systems and who can search each one.
  • Set CCTV retention to a sensible period and know how to export and blur footage.
  • Agree a rule for staff group chats, such as keeping work discussion in business channels only.
  • Store requests and responses securely; they are personal data too, and losing them would be a data breach.

Frequently asked questions

Can a subject access request be made verbally or on social media?

Yes. There is no required format or wording. Treat a clear request for someone's own information as valid however it arrives, and confirm it in writing.

Can we charge for answering a subject access request?

Not usually. A reasonable fee is allowed only where a request is manifestly unfounded or excessive, or for further copies of data already provided.

Do we have to hand over CCTV footage?

If it shows the requester and you still hold it, it is in scope. Blur or redact other people where needed, and pause routine deletion once a request arrives.

Can we refuse a request from an ex-employee who is suing us?

Not simply because of the dispute. You can refuse only if the request is manifestly unfounded or excessive, and you must explain why.

References

  1. legislation.gov.uk (The National Archives) (2026). UK GDPR Chapter III, Section 1: Articles 12 and 12A (transparency and time limits) (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 15: Right of access by the data subject (opens in a new tab) ↑

  3. Acas (2026). Employment Rights Act 2025: what is changing and when (opens in a new tab) ↑

  4. Acas (2027). Employment Rights Act 2025: what is changing and when (opens in a new tab) ↑

  5. Acas (2026). Employment Rights Act 2025: what is changing and when (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo