Self-Service vs 'Done-for-You' Data Removal: What's the Difference?

Two models, the same underlying rights

When people talk about "removing" their data, they usually mean exercising data-protection rights — such as the right of access or the right to erasure under the UK GDPR — by asking the organisation that holds the data to act. The right is the same whoever sends the request. What differs is the model used to send it.

In a self-service model, you make and send your own requests and keep track of the replies. You see exactly which organisation you contacted, what you asked for, and how each one responded. In a "done-for-you" model, a service sends requests on your behalf — usually by acting as your authorised agent, with your permission — and then reports back on what happened.

Neither model creates a new right or a stronger one. A request from you and a request sent on your behalf both rely on the same law, and both land with the same decision-maker: the organisation holding your data, known as the data controller. This is general information, not legal advice.

What actually changes between them

The choice between the two models is really a choice about who holds the pen and how much of the process you see directly. Each approach has honest trade-offs, and it helps to name them plainly rather than treat one as simply "better."

Self-service keeps you closest to the detail: you decide what to send, to whom, and when, and you read each reply yourself. "Done-for-you" can save effort, but it asks you to delegate authority and to trust the service's account of what it did. Knowing where the trade-offs sit makes it easier to pick what suits you.

• Who sends it: you, in your own name (self-service), versus a service acting as your authorised agent on your behalf (done-for-you).
• Visibility: self-service shows you every request and reply directly; done-for-you usually gives you a summary the service compiles.
• Control: in self-service you approve each step yourself; in done-for-you you hand over standing authority to act for you.
• Who decides the outcome: the same in both — the data controller decides each request, and neither model can guarantee a result.
• Recourse: in both models, if a controller mishandles a request, your route is to complain to the Information Commissioner's Office (ICO).

Where OSINTA sits, and how to choose

OSINTA is built around a self-service model with a guiding hand. It helps you see your own digital footprint, understand which right fits your situation, and prepare a clear request — then you decide whether and where to send it. The system suggests; you decide. It does not act as your agent, send requests in your name without you, or claim to remove data for you.

That design is deliberate. Keeping you in the sender's seat means you always see what was asked and how each organisation replied, with nothing happening on your behalf that you did not choose. It also keeps expectations honest: because the data controller decides every request, no model — self-service or done-for-you — can promise an outcome.

When you compare approaches, the useful question is not "which removes more" but "which keeps me informed and in control while being honest about what it can and cannot do." A model that shows you each request, explains who actually decides, and points you to the Information Commissioner's Office (ICO) if something goes wrong is one you can trust. This is general information, not legal advice.

Frequently asked questions

Related terms

• Data Subject Access Request (DSAR)
• Data broker
• Right to erasure
• Data controller