Skip to main content

When a customer asks what you hold about them

Answer Data Access Requests With Exports

A customer who once gave you a testimonial writes in asking for a copy of the personal data you hold about them. Under UK data protection rules that is a subject access request, with a deadline. The testimonial is only part of the answer: there may be a recording, a contact record and request emails too. This checklist walks a small team through finding it all, using the CSV export as the starting point. It is a working aid, not legal advice.

  • Log the request and the deadline the same day
  • Search every space export for this one person
  • Send their data, and nobody else’s

The problem, solved

Why testimonial data makes access requests awkward, and how to work through it

The legal points come from the UK ICO guidance listed in the sources, read on 2026-11-19. Other countries’ rules differ; check with a qualified adviser.

  • Their data could be in several brands

    A customer who bought from two of your brands may have left testimonials in two spaces.

  • They recorded a video, not just text

    A recording of someone’s face and voice is personal data too, and a spreadsheet may not hold it.

  • We also hold them as a contact

    Requests were sent to them, so their name and email may sit in your contacts and lists as well as on a testimonial.

  • The file is full of other customers

    The ICO says you do not have to provide information that would reveal another person, and you should not send a whole library.

  • We must find them again next time

    The same customer may write back, or ask for deletion after seeing the copy.

  • Too many people see the request

    An access request is itself personal information and should not travel round the whole marketing team.

Flip the switch to see how StoryProof handles each one.

Access request checklist

Handle one testimonial access request

One run per request. Items marked ICO follow the regulator’s guidance; the rest are practical steps for testimonial data.

Day one
Find their data
Prepare the reply
Close

Nothing you tick leaves this page or is stored.

Where a testimonial giver’s data can sit

A starting map. Your own setup may hold more.

Practical map only. Whether each item must be disclosed is for your adviser.
PlaceHow to checkInclude in the reply?
Testimonial rows in each spaceSearch each space’s CSV exportYes, their rows only
Video or audio recordingsOpen their testimonials in the appYes, or describe and offer a copy
Contact record and listsLook up the contact in the appYes
Consent emails and formsYour inbox and filesYes
Published uses (site, ads, print)Your own notes of where you used the quoteAs supplementary information

In StoryProof

From request to reply

  • You will need
  • Access to workspace settings for every space
  • A secure way to send files
  • Your privacy notice to hand
  1. 1

    Log and verify

    Record the arrival date, set the deadline one month later, and confirm the requester’s identity.

  2. 2

    Export and search every space

    Download each space’s CSV and search each one for the person’s names and emails.

  3. 3

    Check what the export may miss

    Look in the app for recordings and the contact record, and in your own files for consent emails.

  4. 4

    Build and send the reply

    Put their rows into a fresh file, remove other people’s details, add the supplementary information and send it securely.

  5. 5

    Tag and record

    Tag their testimonials with the request reference and file a note of what was sent.

What happens next: If the customer then asks for their testimonial to be removed, that is a separate request. See the deletion page linked below.

Before you start

Limits of this page

  • Not legal advice

    It applies UK ICO guidance as read on 2026-11-19. Laws elsewhere set different deadlines and exceptions. Have an adviser review your process.

  • Export contents are not listed

    This page does not say which fields the CSV contains or whether media is in it. Inspect the export so your reply describes it accurately.

  • No per-person export is claimed

    The export runs per space. Pulling out one person’s rows is a spreadsheet step you do yourself.

  • Records outside StoryProof

    Consent emails, ad accounts and print files are outside the tool, and you still have to search them.

FAQ

Questions people ask

Short answers to what usually comes up next.

How long do we have to reply?

The ICO says without undue delay and at the latest within one month of receiving the request, extendable by up to two further months where necessary. Other laws set their own deadlines.

Can we charge for answering?

The ICO says that in most cases you cannot charge a fee.

Is a CSV file acceptable as the reply?

For an electronic request the ICO expects a commonly used electronic format. A spreadsheet file of their rows, plus any recordings, is one option; confirm the format with your adviser.

Should we send the testimonial even though they wrote it?

Their testimonial is part of the personal data you hold about them, along with anything you added to it, such as tags. Include it.

What if the request came through social media?

The ICO notes requests can be made verbally or in writing, including via social media. Treat it as a request and start the clock.

Still have a question? Ask the StoryProof team or book a demo.

Keep testimonials where you can find them

One library per brand, tags you can filter, and a CSV export of every space.

Sources

  1. A guide to subject access, Information Commissioner’s Office (UK). Checked 2026-11-19.
  2. How to deal with a request for information: a step-by-step guide, Information Commissioner’s Office (UK). Checked 2026-11-19.

Last updated 2026-11-19.