MP Kate Osborne and the Fabled Subject Access Request

The Labour Party has finally admitted that it is months late responding to a Data Subject Access Request (DSAR) it received in September 2025. After a long period of silence, an email arrived in January 2026 that quietly confirms the delay, name drops the Information Commissioner’s Office (ICO), and then asks whether I still want them to process the request at all.

If you have ever wondered what happens to your data rights when a political party finds your case inconvenient, this is a live example.

You can read the full message here as a PDF:

Download the Labour Party DSAR update email (PDF)

PDF: Labour Party Data Protection Team email, 9 January 2026, acknowledging a significant delay in responding to my DSAR and asking if I still want them to continue.

What Labour actually admits in this email

The update, sent from the Labour Party Data Protection Team on 9 January 2026, does three things in quick succession.

It confirms that my DSAR was received on 01 September 2025.
It admits there has been a “significant delay” due to internal changes and an audit of outstanding casework.
It claims Labour has been “actively engaged” with the ICO, then asks me to confirm by 23 January whether I still want them to proceed, or they will close the request.

So months after the statutory deadline has expired, the party that wants to run the country is asking the data subject if they still want their request processed, as if this is a favour and not a legal obligation.

The rest of the email is boilerplate. It repeats generic lines about third party data, internal complaints processes, and legal privilege. It is the kind of template you write when you expect most people to give up and move on.

Context – this started with Kate Osborne MP’s office

The DSAR does not exist in a vacuum. It comes out of a longer story that regular readers will recognise from our coverage of Kate Osborne MP, her office, and the way “security” and “distress” have been used to shut down scrutiny.

Previous pieces set out how comments were disabled on her Facebook page during a period of spending scrutiny, how critics were framed as a risk, and how that bled into recruitment and casework:

The short version is simple.

I am a constituent who applied for a job in Kate Osborne MP’s office. In that process, and in related correspondence, I raised legitimate concerns about comments being disabled on her public Facebook page. I used Keir Starmer’s page as a comparison. He manages to keep comments open despite a hostile minority, so why does a backbench MP need to close down public engagement entirely.

That is not abuse, that is basic democratic literacy.

When raising concerns becomes a “distress” problem

Instead of responding on the substance, Kate Osborne’s acting manager, Cameron, sent an email that was emotionally loaded and personalised. My concerns were described as “accusations”. My tone was presented as a problem in its own right. The response then went a step further and stated that further emails from me would not be responded to, supposedly “to avoid causing distress”.

Legally, I still have the right to write to my MP. In practice, that right is being hollowed out. I have been placed in a category where my correspondence is marked for non response, regardless of how carefully or reasonably I write.

That is not safeguarding, that is reputational management dressed up as safeguarding language.

The irony is obvious. “Security” and “distress” were invoked to shut down uncomfortable questions, yet Kate Osborne is quite happy to post a video from what is clearly her own back garden on the same public platform. Apparently it is too risky to allow constituents to comment on spending, but not too risky to broadcast your home environment to the internet.

Recruitment, retaliation, and the quiet cost of speaking up

This is not just a social media spat translated into email. There was a job application involved. I had put myself forward to work in Kate Osborne MP’s office.

Instead of my application being assessed on its merits, my feedback about transparency was treated as evidence of a problem. By pathologising my tone and putting me in a “do not respond” bucket, the office blurred the line between fair recruitment and retaliation for criticism.

In real terms, that meant a job opportunity in an MP’s office was undercut, not because I lacked skills or experience, but because I refused to be a quiet, compliant tick in a diversity box while public scrutiny was being managed away.

Labour HQ joins the pattern

This is where the DSAR comes in.

If you have an MP’s office that is quick to turn criticism into a safeguarding narrative, it makes sense to ask what has been written about you internally, how your case has been handled, and what labels have been attached to your name.

So I submitted a Subject Access Request to the Labour Party, asking for personal data they hold about me relating to this situation, including emails and internal records where I am mentioned. Labour acknowledged the request. Then nothing.

The request was logged in September 2025. By January 2026, Labour’s own Data Protection Team finally surfaced, admitted there had been “significant delay”, and asked me if I still wanted them to proceed. They also dropped the usual boilerplate about third party data and “context”, hinting that internal comments about me might be withheld on that basis.

The ICO has already made it clear that my request stands, and Labour HQ are months out of time. They are now scrambling to reopen a process that should have been completed long ago, while still trying to keep the scope as narrow and comfortable as possible.

So we now have three layers that sit together quite neatly:

An MP’s office disabling public comments during scrutiny, while citing security.
An acting manager turning a legitimate challenge into a “distress” narrative and putting a constituent on a practical non response list.
Labour HQ dragging its feet on a data request until the ICO steps in, then asking politely if I still want them to do the thing the law already requires.

This is not a one off, it is a culture.

Complaints, silence, and the next steps

I raised a formal complaint with the Labour Party about Cameron’s conduct and the way my job application and constituent contact were handled. I set out the background, the recruitment implications, and the democratic implications. That complaint has not been properly answered, and my follow ups have been ignored.

At this point, the failure to handle the complaint has become part of the complaint. You cannot claim to take accountability seriously, then selectively ignore the people who put in the work to document what is happening.

So the next steps are straightforward.

Press Labour HQ for a clear data disclosure deadline, scope, and controller position, rather than letting them hide behind “complexity” and generic policy lines.
Press the Labour complaints team to confirm, in writing, whether my complaint has been logged, investigated, and taken seriously at Party level, not just quietly buried in the same office that created the problem.
Keep a precise record of dates, responses, and non responses for potential reference to the ICO, the Parliamentary Commissioner for Standards, or any other relevant oversight body.

This is bigger than one MP

It is very easy to treat this as a personal feud between an awkward constituent and a stressed constituency office. It is not.

When an MP’s office disables public comments during scrutiny, then brands critics as a distress risk, then silently sidelines them as job applicants and constituents, that is a clear example of how power protects itself from scrutiny at a very local level.

When the wider Party responds to a lawful data request months late, only after the ICO has been involved, and still tries to narrow the scope with pre written boilerplate, it shows that the culture is not confined to one inbox in one town.

If you want another flavour of this culture, look at our coverage of North East Mayor Kim McGuinness, public money, and the Tokyo trip FOI trail:

Public FOI strategy – why we started asking questions

Different office, different role, same reflex to control what gets seen and when.

Democracy does not break in grand, dramatic moments. It erodes in small administrative decisions. A comment setting turned from “on” to “off”. An email quietly categorised as “do not respond”. A request left in limbo until the requester loses interest. A complaint that never gets answered because the right people know it will not be escalated unless the constituent makes a fuss.

I am making a fuss.

If you think this is overkill for one MP, ask yourself a simple question. If this is how they handle the constituent who documents everything and knows their rights, what happens to the people who do not.

If you have had similar experiences with party offices, public bodies, or charities playing games with your requests, you can reach out to [email protected]. Proof, paperwork, and timelines always welcome.