Data Rights & Removal

1. Scope of this page

How to request removal or restriction of material connected to a Datapink dataset, and how the request reaches the people who can act on it.

This page is for requests about material we have collected, or that sits in a dataset we have built: a page we crawled, a document we ingested, or personal data inside one of them.

The form at the bottom of this page sends the request straight to the people who handle it. It is stored on our own server and emailed to a company address, and it is used only to verify, assess and answer the request.

Commercial enquiries go through the contact page instead. Questions about how this website itself handles personal data are answered in the privacy policy.

Where a request concerns a dataset we built for a customer, that customer decides what happens to their own data, so the request is routed to them, and we tell you when that happens.

2. What you can request

Removal or restriction of material tied to a specific source, made by the rights holder, the data subject, the site operator, or on another stated basis.

You can ask us to remove material, or to restrict what is done with it — for example to stop crawling a source, to exclude a document from future releases, or to take personal data out of a dataset.

A request needs a specific source. Give the URL or source identifier, one per request, and describe what you are asking for in enough detail that we can find the material through lineage.

Tell us on what basis you are asking: as the rights holder or their authorised representative, as the person the data is about, as the operator of the site the material came from, or on another basis you describe. The basis decides which assessment path the request takes.

We may come back to you for more information where we cannot identify the material, or cannot yet establish your relationship to it.

3. How we verify and process a request

Every request is logged, verified against the requester's relationship to the material, assessed against the source policy, and traced through lineage into the next dataset version.

1. step 01

   Request received

   URL or source, what is being asked for, the basis of the request and how to reach the requester.

2. step 02

   Verification

   We confirm the requester's relationship to the material before acting on it.

3. step 03

   Assessment

   The request is assessed against the source policy and the applicable obligations, with the decision recorded.

4. step 04

   Dataset-version impact

   Affected records are traced through lineage, and the change is carried into the next dataset version.

4. Response terms

How we answer a request, what we record about the decision, and why no number of days is promised here.

We confirm receipt of every request, and we tell you the outcome once the assessment is done. Requests are handled promptly and in the order they arrive, with those concerning personal data taken first.

We do not promise a number of days here. How long a request takes depends on how easily the material can be identified, what is needed to verify your relationship to it, and whether a customer has to be involved.

The decision is recorded with the reviewer and the date. Where we decide not to act on a request, we tell you why. Where we do act, affected records are traced through lineage and the change is carried into the next dataset version, which means material already delivered under an earlier version is not retrospectively altered.

If you are not satisfied with how we handled the request, write to our Legal Team at [email protected] and it will be looked at again.