Skip to main content
web60

Infrastructure

A Subject Access Request From an Unhappy Customer: Finding Everything Your Website Kept

Graeme Conkie··12 min read
Flat illustration of a teal folder spilling white document sheets that fan out along thin teal lines to a cluster of teal and navy circles, on a warm off-white background

The email is three lines long and noticeably more formal than anything the customer has sent before. The heat pump is still too loud, the electricity bills are still too high, and they are no longer asking for a callout. They are asking, under Article 15 of the GDPR, for a copy of all the personal data the business holds about them.

Treat this as a composite rather than one real job: a heat pump installer in Wicklow, two vans, a WordPress site with a quote form, and a dispute that has been simmering since the commissioning visit. The details are invented; the shape is not. In its 2025 annual report, the Data Protection Commission says the majority of access request complaints it reviews have something else at their core: a soured working relationship, a money dispute, or a situation that began as poor customer service.

The installer has two instincts. Forward it to the solicitor and wait. Or reply with a PDF of the original quote and call it done. Neither survives contact with the law, and the website is a large part of the reason.

A Complaint Email With a Legal Clock Attached

Start with the numbers, because they explain why this is not a niche worry. The Data Protection Commission's Annual Report 2025 records 1,280 complaints relating solely to the right of access, a little over two in every five complaints it received that year and comfortably the largest category. Top of the list of queries the regulator fielded was not hacking or cookies. It was people asking what to do when an organisation had simply not answered their access request.

That is the trap. Silence.

The DPC's guidance gives you one month from receipt to respond. You can extend by two further months where the request is genuinely complex, but only if you tell the person within that first month and explain why. In most cases you cannot charge for it. And the customer does not owe you a reason: the European Data Protection Board's guidelines on the right of access state that the person does not have to explain why they want their data, and that it is not up to the business to judge whether the request will actually help them.

The Court of Justice of the EU went further in October 2023. In a case involving a German dentist, a patient wanted his records specifically so he could pursue her for alleged errors in his treatment. The court's press release on Case C-307/22 says the dentist had to provide the first copy free of charge, and that the patient was not obliged to provide reasons for his request. A request made to build a case against you is still a valid request.

Now consider the installer on day thirty-one, still waiting for the solicitor to get around to it. The original argument was about decibels and a refund. Now there is a second, much cleaner complaint, one a regulator can assess from a single date: did you answer or not? The customer's hand just got stronger, and nothing about the heat pump changed.

Where a Small Business Website Keeps Personal Data

Most owners think of their website as a brochure. Pages, photos, a phone number. That picture is roughly right for what visitors see and badly wrong for what the site stores.

The EDPB guidelines expect a business to search for personal data throughout all its IT systems and non-IT filing systems, using search criteria that match how the information is organised, such as a name or customer number. They also stress that personal data reaches well beyond name and address, listing examples like purchase history and activity logs. WordPress runs roughly two in five websites (39.2% on W3Techs' count this week), and a typical small business site has at least three of the places below.

Where it livesWhat it usually holdsHow you find it
User accounts and commentsName, email, comment historyThe WordPress export tool
Form entriesQuote requests, messages, phone numbersDepends entirely on the form plugin
Orders and bookingsAddresses, order history, staff notesThe plugin's own screens
Mailing listEmail, sign-up date, consent recordThe plugin or outside email service
Server and security logsIP addresses, timestamps, pages requestedAsk your host

User accounts and comments

If the customer ever created an account or left a comment, WordPress holds their name, email address and whatever they wrote. This is the easy part, because WordPress has a built-in tool for it, covered further down.

Form entries

This is where the installer's quote request sits. Or does not. Some form plugins store nothing at all and simply email each submission onwards. Contact Form 7, one of the most widely installed, works that way, which is why a separate plugin called Flamingo exists: the WordPress.org directory describes it as message storage for a form plugin that does not store submitted messages. Other popular form builders keep every entry in the database by default, sometimes for years.

So the honest answer to what your website kept is that it depends on which plugin you installed. In practice, the quote request with the customer's phone number, address and a note about their old oil boiler may be sitting in two places at once, the database and your inbox. Both are in scope.

Orders and bookings

Shops and booking plugins hold delivery addresses, order history, payment status and any notes staff typed against the order. That last part catches people out. An internal note reading "difficult customer, no more discounts" is information about that customer, and you should expect it to appear in the copy you send.

Mailing lists

Newsletter plugins store subscriber emails and, if set up properly, a record of when and how consent was given. Plenty of small businesses use an outside email service instead, often one based outside the EU. That detail matters for the explanation part of your answer, which comes later.

Server and security logs

Every visit leaves a line in a server log: an IP address, a timestamp, the page requested. Security tools keep their own records of login attempts. Whether a given log line can realistically be tied to one customer is often doubtful, and how long logs are kept varies from host to host. Ask your host what it keeps and for how long, then let your solicitor judge whether it is relevant to this request. Do not guess.

Flat illustration of stacked abstract drawers, each holding a small teal circle, joined by thin teal lines to a single navy node on an off-white background
Customer details rarely live in one place. A website alone can hold them in four or five.

The Export Tool WordPress Gives You, and Where It Stops

Since version 4.9.6, WordPress has shipped a tool under Tools, then Export Personal Data. You enter the customer's email address, WordPress sends them a confirmation link, and once they confirm you can download a zip file containing a readable summary of their user information, comments and media, plus anything from plugins that hook into the exporter.

That last clause carries the whole weight. The WordPress.org documentation is blunt about it: the tool only gathers data from WordPress and participating plugins, and you may need to go further to comply. A form plugin that never registered with the exporter is invisible to it. A booking plugin with its own tables is invisible too, and so is your inbox. Put simply, a clean export proves only that the export tool found nothing else, not that nothing else exists.

The practical gap-filler is a search of the database itself. Web60 includes a phpMyAdmin-style database manager in the dashboard, so an owner can search the tables for the customer's email address and verify what the export missed without paying a developer by the hour to do it. For the installer, that means finding the quote request, the order note and the newsletter sign-up in one sitting, rather than discovering one of them after the reply has gone out. Use it to look, not to edit. Changing or deleting records in the middle of a live dispute is a very bad idea.

There is a quieter advantage to building your own site here as well. An owner who set up their site with an AI builder knows which forms are on it, because they added them. Owners whose agency built the site years ago often have no idea which plugin stores what, and the person who knew has long since moved on. If you are starting from scratch, Web60's AI builder produces a full WordPress site in about a minute for €60 a year, with the database manager, backups and Irish hosting included rather than sold as extras.

The Explanation Is Half the Answer

The copy of the data is only part of what the customer is owed. The DPC's page on the right of access says people are also entitled to supplementary information: why you process their data, the categories involved, who receives it, how long you keep it, their other rights, their right to complain to the DPC, and where the data came from if not from them. The EDPB adds the safeguards that apply when data goes to countries outside the EU.

For a small business, the question of who receives the data is where the website comes back in. Think of the form plugin that forwards entries to a US email platform, the booking widget hosted somewhere else, the analytics script and the hosting company itself. Each one is a recipient you should be able to name without a week of digging.

The hosting line can be short. On Irish-hosted WordPress infrastructure where all site data stays in Ireland, that part of your answer is one sentence rather than a paragraph about international transfer mechanisms. Analytics can be simpler too: Web60's analytics are built in and privacy-first, with no cookie consent needed for tracking, so you are not adding a separate third-party analytics service to the list unless you choose to install one.

Retention belongs in the answer as well, and backups are part of it. Nightly backups hold copies of the same customer records, so when you write down how long you keep data, include how long backup copies are kept. Our WordPress security and backup guide covers how that side of a site should run.

Answering an Access Request in Five Steps

  1. Log the date. Write down the day the request arrived, because the one-month clock started then, whether it came by email, phone or a Facebook message, and the EDPB is clear that there is no required format.
  2. Verify identity, proportionately. The DPC says you may ask for evidence of identity, but the EDPB says anything extra you ask for must be proportionate, so a request from the email address you have used with this customer for months rarely justifies a passport scan.
  3. Search every system. Run the WordPress export, search the database for the customer's email address, then go through your inbox, phone, WhatsApp, accounts package and paper job sheets.
  4. Compile the copy and the explanation. Put the data and the supplementary information together in plain language, and blank out details about other people, such as a neighbour named in a site visit note.
  5. Send it and keep a record. Keep a copy of exactly what you sent and when, and list anything you withheld or redacted with the reason, which the DPC's 2025 report specifically asks organisations to do.

Some information can lawfully be held back, legal advice about the dispute itself being the obvious example. Those exemptions are narrow and depend on the facts, so step five is the point to bring your solicitor in, not step one. Getting the search done yourself is what keeps that bill small.

Where a Hosting Platform Cannot Help You

No hosting platform answers an access request for you, ours included. The judgement calls (what is exempt, what counts as someone else's data, whether a request is manifestly unfounded) belong to you and your adviser, and the DPC's own guidance says a business claiming a request is excessive has to be able to prove it.

There are businesses for whom a website host is the wrong place to start. If you run a dental or medical practice, a solicitor's office, or anything holding large volumes of sensitive records, an outsourced data protection officer or specialist adviser earns the fee many times over. A multi-site retailer with a compliance team that needs centralised audit trails across dozens of sites is genuinely better served by enterprise managed hosting built around that tooling. That is not most businesses with a quote form and a mailing list.

And if the same customer follows up demanding that you delete everything, that is a different right with its own traps, covered in our piece on handling a data deletion request on your website.

Flat minimal illustration of a grid of soft sage and teal squares with a looping navy line leading to a large teal envelope shape
The month starts the day the request arrives, not the day you read it properly.

The Installer, One Month Later

In the version of this story that goes well, the installer writes down the date on the first morning and replies within a couple of days to acknowledge the request. The export tool returns almost nothing. A search of the database finds the quote form entry and a booking note. The inbox, the phone and a folder of job sheets fill in the rest. Three weeks in, the customer receives a copy of everything, a one-page explanation in plain English, and a short list of what was redacted and why.

The heat pump dispute carries on. It was always going to. But it carries on as an argument about a heat pump, not as a complaint file with the regulator's name on it.

What to Do Before Anyone Asks

Set aside twenty minutes this week. List every form, plugin and outside service on your website that touches customer details, and note where each one stores its data and for how long. Add the places off the website: inbox, phone, accounts package, the drawer of paper job sheets.

When a request does arrive, that list turns a stressful month into a few hours of methodical work. It also makes your privacy policy more accurate, which is no bad thing on its own.

The request may never come. If it does, you will already know where to look.

Frequently Asked Questions

How long do I have to answer a subject access request in Ireland?

One month from the day you receive it. The DPC says you can extend by two further months where necessary, for example if the request is complex, but you must tell the person within the first month and give your reasons. If you decide not to act on a request, you must also tell them within one month and explain how they can complain.

Can I charge a fee for a subject access request?

In most cases, no. The first copy is free. The DPC says a reasonable, cost-based fee may be charged for additional copies or where a request is manifestly unfounded or excessive, and the business has to be able to show that. The Court of Justice confirmed in 2023 that national rules cannot make a person pay for their first copy.

Do I have to answer if the customer only wants the data for a dispute?

Yes. The customer does not have to give a reason, and the EDPB says it is not for the business to judge whether the request will help them. In Case C-307/22 the patient wanted his records to pursue his dentist, and the court still held he was entitled to a free first copy. Some material connected to legal advice may be exempt, so speak to your solicitor about anything you plan to withhold.

Can I ask for ID before I respond?

You can ask for evidence of identity where you have genuine doubt, but it must be proportionate. If the request comes from the email address you have always used with that customer, asking for a passport copy is usually more than you need. Ask only for what confirms they are who they say they are.

Does a subject access request cover emails and WhatsApp messages?

It covers personal data about the person wherever you hold it, not just on the website. The EDPB expects a search across all IT systems and paper filing. That includes your inbox, phone messages, accounts software and job sheets, as well as form entries, orders and mailing lists on the website.

What if my website does not store form submissions?

Then those submissions live in your inbox instead, and the inbox copies are in scope. Some form plugins only email entries onwards and keep nothing in the database, while others store every entry for years. Find out which kind you have before a request arrives, because the answer changes where you need to search.

Sources

Graeme Conkie
Graeme ConkieFounder & Managing Director, Web60

Graeme Conkie founded SmartHost in 2020 and has spent years building hosting infrastructure for Irish businesses. He created Web60 after seeing the same problem repeatedly — Irish SMEs paying too much for hosting that underdelivers. He writes about WordPress infrastructure, server security, developer workflows, managed hosting strategy, and the real cost of hosting decisions for Irish business owners.

More by Graeme Conkie →

Ready to get your business online?

Describe your business. AI builds your website in 60 seconds.

Build My Website Free →
Buy NowTry Free
Subject Access Request: A Small Business Guide | Web60