JustDSARsLtd · Slough
Write to us
Operational support for subject access requests

A request has arrived. Let’s answer it properly.

Just DSARs helps British organisations do the practical work behind a data subject access request: logging it, keeping the clock, finding the information, organising review and redaction, and assembling a response the person can actually read.

Folders tied with ribbon beside a sealed envelope on a linen deskSupport, not legal advice
What usually arrives
An email, a letter, a line in a resignation note, sometimes a message to a manager who does not realise what it is.
What you need by the end
A complete, readable response, sent on time, with a record showing how you got there.
Where we fit
Between the request and the reply — the organising, searching and paperwork.

Photograph: illustrative generated image, not our premises.

Plain terms

Operational help. Nothing grander.

A subject access request is a right exercised by an individual under UK data protection law. Answering it is mostly organisational labour, with a handful of judgement calls that belong to you and your advisers. We take on the labour and make the judgement calls visible, so the right people can make them in time.

What we do

  • Set up a request log and a working timetable from the day of receipt.
  • Plan searches across mailboxes, shared drives and business systems.
  • Collate, de-duplicate and organise what is found.
  • Prepare material for review and apply redactions you have approved.
  • Draft the covering letter and the supplementary information.
  • Keep a decision record you can rely on later.

What we do not do

  • Give legal advice or represent you or the requester.
  • Decide which exemptions apply — that stays with the controller.
  • Act as your Data Protection Officer.
  • Collect identity documents through this website.
  • Promise outcomes in disputes, tribunals or complaints.
  • Claim certifications, accreditations or partnerships we do not hold.
The first forty-eight hours

Why requests go wrong early

Most late or incomplete responses are not caused by bad faith. They start with a request that sat in a general inbox for a week, a search that only covered one system, or a team that assumed the deadline was thirty working days.

The clock generally starts when the request is received, whether or not it uses the words “subject access”. Requests arrive by email, post, social media messages and conversations with staff. They often arrive inside something else: a grievance, a complaint, a dispute about an invoice, a letter from a former employee’s representative. The first job is simply to recognise them, record the date, and decide who owns the work.

After that comes the unglamorous middle: working out where the person’s information is likely to be, asking colleagues to search without tipping off half the organisation, collecting results into one place, and then reading them. That reading is where time disappears, because an email thread about a customer is rarely only about the customer.

The legal question is narrow. The practical question — where is everything, and who has read it — is enormous.
Six stations

How one request travels through our hands

  1. Recognise

    Confirm it is a request, log the receipt date and what was asked for.

  2. Verify

    Decide with you whether identity checks are reasonable and proportionate.

  3. Locate

    Agree a written search plan: systems, people, date ranges, terms.

  4. Review

    Read, de-duplicate, flag third-party material and possible exemptions.

  5. Respond

    Assemble the disclosure and covering letter in a format the person can use.

  6. Record

    Close the file with a decision log and lessons for next time.

Read the full workflow

Services

Five ways we can help

You can bring us in for the whole request or for one stubborn part of it. Open each drawer to see what we need from you and what you get back.

Request handling, end to end

For a single live request

We run the operational side of one request from intake to closure. You remain the controller and make the decisions; we keep the timetable, coordinate searches with named colleagues, organise review and prepare the response pack for your sign-off.

Search and collation

When the information is scattered

We write a search plan with your system owners, chase returns, remove duplicates and put results into a single, ordered review set. Searches are run inside your environment by your staff or under access you control.

Review and redaction support

When volume is the problem

We read material, mark what relates to the requester, flag third-party information and potential exemption points for your decision, and apply redactions consistently once approved.

Response drafting

When the words matter

We draft the covering letter in plain English, include the supplementary information required, explain anything withheld in general terms and arrange the disclosure so it can be navigated.

Process set-up

Before the next request arrives

We help you design an intake route, a log, templates and a short internal guide so staff recognise requests and pass them on quickly.

Detailed service descriptions

Try it now

Sketch a working timetable

A simple calendar sketch: from a start date you choose, it suggests an estimated one-month planning date and an internal checkpoint. It is illustrative only; your DPO or adviser and current ICO guidance confirm the actual legal deadline.

Two more tools: the review sizer and the response pack checklist

Illustrative

Calendar planning sketch

Enter a start date you want to plan from and, if you wish, a number of days to add for a period you are treating as paused. The tool does simple calendar arithmetic to suggest planning dates. It does not decide when the legal time limit starts, whether a pause or extension applies, or which days count. No names or request details are needed.

Illustrative planning only, not a legal deadline calculator. Confirm the statutory start date, any pause or extension, and the effect of weekends and bank holidays with your responsible Data Protection Officer or adviser and current ICO guidance.

Exchange

What we ask for, what you get back

From you

  1. The request itself and the date it arrived.
  2. A named decision-maker with authority to approve disclosure.
  3. A list of the systems and teams likely to hold information.
  4. Access arrangements you are comfortable with.
  5. Your existing policy, if you have one.

From us

  1. A dated timetable with checkpoints.
  2. A search plan and a record of searches.
  3. An organised, de-duplicated review set.
  4. Redactions applied to your decisions, with reasons logged.
  5. A plain-English response pack and a closing record.
Where it gets hard

Requests that need extra care

Some requests are routine. Others combine large volumes with sensitive relationships. We are honest about where our role ends in each.

Former or current employees

Often linked to a grievance or dispute, with years of email and HR records. We separate the request process from the dispute and keep the search methodical.

Our limit: we do not advise on the employment dispute or litigation strategy.

Email-heavy requests

Thousands of messages where the person is copied in or mentioned. De-duplication and threading make the reading humane.

Our limit: searches run on your systems under your control.

CCTV and recordings

We help locate footage before retention deletes it and log what exists.

Our limit: technical editing depends on your tools.

Mixed third-party information

Messages about colleagues, customers or family members. We flag every instance and record the balancing reasons you decide, so the response is consistent and explainable.

Our limit: the balancing decision is yours or your adviser’s.

Repeated or broad requests

We help you document clarification, volume and earlier responses, so any decision about extension or refusal rests on a clear record.

Our limit: whether a request is manifestly unfounded or excessive is a legal judgement.

Requests on behalf of someone else

Solicitors, relatives or advocates acting for an individual. We help you check and record the authority provided.

Our limit: we do not handle identity documents through this website.

More on difficult requests

Boundaries, stated early

We would rather say this now than in week three.

Clear boundaries protect you, the requester and us. If a request starts to need a lawyer, we will say so and help you brief one with an organised file.

  • Not a law firm
  • No legal representation
  • Controller makes disclosure decisions
  • No identity documents by web form
  • No guaranteed outcomes
  • No borrowed certifications
After the response

The file does not close itself

Responses sometimes prompt questions, corrections or complaints. A good closing record makes the next conversation shorter.

We keep a dated decision log through the request: what was searched, what was found, what was withheld and on whose decision. If the requester comes back, you can explain what happened without reconstructing it. If they complain to the Information Commissioner’s Office, your adviser has an organised file to work from.

Support is available for follow-up questions on requests we have worked on and for help with your process after the event. How support works.

Correspondence

Tell us what has landed on your desk.

A short, general description is enough to begin: when the request arrived, roughly where the information sits, and what is worrying you. We reply on working days, Monday to Friday, 09:00 to 18:00 UK time.

Open the enquiry form Get support on a live request

Registered office

JUST DSARS LTD
14 Hurricane Court Heron Drive, Slough, England, SL3 8FA

Map placeholder. This is our registered office address as recorded at Companies House. It is not a walk-in office, and no map is loaded automatically.

Search this address on OpenStreetMap