1. Purpose and scope
This procedure explains how Carefully Coded Ltd ("we", "us") handles requests from individuals to use their rights under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.
It covers the rights to be informed, of access, to rectification, to erasure, to restrict processing, to data portability, to object, and rights related to automated decision-making.
It applies to everyone who works for us, including staff and contractors, and to requests received by any route: email, post, phone, social media, in person or through a client.
2. Responsibilities
The data protection lead, Tom Emmerson, Director, is responsible for handling every request, keeping the request log and making sure timescales are met. Contact: tom@carefully.codes.
Anyone else who receives a request must forward it to the data protection lead on the same working day. A request does not need to use the word "request" or name the law to be valid.
3. First steps for every request
When a request arrives, the data protection lead will:
- log it (see section 6);
- work out whose data it is and whether we hold it as a controller (our own business data) or a processor (data we hold for a client);
- follow section 4 or section 5.
If we hold data about the person in both roles, we handle each part under the right section and tell the person which parts we have passed to a client.
4. When we are a processor
When the request relates to data we process for a client, such as a council or other public authority ("the Authority"), the client is the controller and decides how to respond. We do not respond to the requester ourselves, beyond any acknowledgement the client approves, unless the client instructs us in writing.
| Step | Action | Timescale |
|---|---|---|
| 1 | Pass the request to the client's nominated contact, with all details we received | Within 2 working days of receiving it |
| 2 | Locate the relevant data in the systems and devices we operate for the client | On receiving the client's instructions |
| 3 | Supply the requested data, or make the requested correction, erasure or restriction, as the client instructs | Within 5 working days of the client's request |
| 4 | Confirm completion to the client in writing | When step 3 is done |
We will provide the data in a secure, commonly used format agreed with the client, and send it by a secure method. If we cannot meet a timescale, we will tell the client as soon as we know, with the reason and a new date.
Where a client contract sets stricter terms or shorter timescales than this procedure, the contract takes precedence.
5. When we are a controller
5.1 Timescale
We will respond without undue delay and within one calendar month of receiving the request. If we need to confirm identity or ask for clarification, the month starts when we receive what we need.
We may extend this by up to two further months if a request is complex or the person has made several requests. If we do, we will tell them within the first month and explain why.
5.2 Confirming identity
We only ask for proof of identity where we have genuine doubt about who is asking. We ask only for what is necessary, and we delete identity documents once identity is confirmed.
If someone makes a request on behalf of another person, we will ask for evidence that they are authorised to act for them.
5.3 Searching and responding
The data protection lead will search all places where the person's data may be held, including email, file storage, accounting and business systems, and paper records. We will:
- for access requests, provide a copy of the data together with the information required by Article 15, such as purposes, recipients and retention periods;
- remove information about other people unless they have agreed or it is reasonable to disclose it;
- for rectification, erasure or restriction, make the change and tell anyone we have shared the data with, unless this is impossible or would involve disproportionate effort;
- for portability, provide the data in a structured, commonly used, machine-readable format;
- for objections to direct marketing, stop immediately.
We respond in writing, by email unless the person asks otherwise, and send personal data securely.
5.4 Fees and refusals
We do not charge a fee. We may charge a reasonable fee, or refuse, only where a request is manifestly unfounded or excessive. If we refuse a request in full or in part, we will explain why, and tell the person of their right to complain to the Information Commissioner's Office (ICO) and to seek a remedy through the courts.
6. Request log
We log every request, in either role, whether or not we hold any data. The log records:
- a reference number and the date received;
- the requester's name and how they contacted us;
- the right being used;
- whether we are controller or processor, and the client concerned;
- the date passed to the client, if applicable;
- dates of identity checks, any extension, and completion;
- the outcome, and the reason for any refusal or exemption.
The log is kept securely, with access limited to the data protection lead. We keep log entries and responses for 6 years after the request is closed, in line with our Data retention and secure deletion policy.
7. Building for rights
When we build systems for clients, we design them so that the client can find, export, correct and delete an individual's data. This helps clients meet their own timescales.
8. Review
The data protection lead reviews the request log every quarter to check timescales were met, and reviews this procedure at least once a year. Related policies: Data protection policy and Privacy notice.