GDPR requests

Every open request from a Worker to remove their data or for a copy of it under the GDPR, with its one-month deadline.

For: Customer Administrator · System AdminLast checked: 2026-11-13Open this page in Obtempera ↗

GDPR requests lists every open request from a Worker to remove their data or to have a copy of it, the two requests the GDPR gives one month to answer: the ones Workers made in their portal, and the ones an administrator recorded for a Worker who asked by phone, letter, email or in person. Open it from Customer Settings (under Also configured by you) or, for Obtempera, from the GDPR requests tile in Platform Admin. A request to leave a Project or to leave Obtempera is not listed here: it is on the Worker's record, under Requests. A Customer's Administrators see their own Customer's Workers; Obtempera sees every Customer's. Nobody else has this page: not a Contractor's administrators, a reviewer or a Report Viewer. For a Worker of an external Contractor, though, that Contractor's administrators action the request on the Worker's record (see State below). The ? beside the page title opens this article.

Under the title, the page says how many requests are open and how many are overdue, and whose they are: Your Customer's Workers only, or Every Customer for Obtempera. With none open, it says No open GDPR requests. and how to record a removal request.

The soonest deadline is first, so overdue requests are at the top. State narrows the list to Overdue, Reminder sent or Open. Obtempera also has Customer (every Customer with an open request) and a search box for a Worker's name or email (press Enter). One page lists at most 1,000 requests; when there are more, the page says how many are shown out of how many, and the filters find the rest.

What each row says

  • Worker and their Contractor.
  • Kind: Remove my data or Copy of my data.
  • Asked: the day the request reached you, and how: in the Worker Portal, or who asked, how, and who recorded it.
  • Respond by: one calendar month from the day they asked.
  • State: Open, Reminder sent (three weeks have passed and the administrators it went to were reminded) or Overdue (the month has passed; the Customer's and the Contractor's Administrators and Obtempera were emailed). For a removal request, what would stop Erase now today is shown beside it, for example the Worker still being on a Project. Dealt with by {Contractor}'s administrators marks a Worker of an external Contractor: that Contractor's administrators action the request on the Worker's record, and the Customer's administrators follow it here.
  • Covers: a request covers one Customer's records only. Obtempera also sees whether the person has records at other Customers, and whether each of those has its own request of the same kind.

Open goes to the Worker's record, where the request is actioned or erased under Requests. A copy request is answered there with Mark actioned, which releases the copy to the Worker. While any request is open, Today shows an Open GDPR requests section with the count, the next day one must be answered by, and how many are overdue.

Marking a request actioned

Mark actioned closes the request with a note the Worker sees. It records what was done; it does not erase anything itself, and nothing checks that records were erased first. If the Worker is still on a Project, say so in the note (for example that their records are kept until their work ends and the retention period runs out). To erase at once, use Erase now instead, which needs their assignments to have ended. If the same person also has a record at another employer of the same Customer, their signature of the Customer's Privacy Notice is not erased with this record: it covers both, so it stays with their other record, and they are not asked to sign again.

An archived Contractor or Customer

A request is still answered within the month after the organisation is archived. An archived Contractor's administrators cannot sign in, so the Customer's Administrators (or Obtempera) mark its Workers' requests actioned, erase, and record new ones; the row says so. At an archived Customer nobody at the Customer can sign in, the Worker included, so Obtempera records the request for a Worker who asks by phone, letter or email, and actions or erases it. Nothing else at an archived organisation is unlocked.

Recording a request made outside Obtempera

Open the Worker and, under Requests, choose Record a removal request. Say who asked (the Worker, or someone for them), how, the day they asked, and add a note if you need to. It is raised on each of the person's records at your Customer, the administrators are told by email, the Worker is emailed (once, in their language) that it was recorded and by when it will be answered, and it then follows the same path as a request from the portal, with the month counted from the day they asked. Each step is recorded in the audit trail.