Questions
GDPR redaction questions
Brief answers to what people ask about redacting and releasing records, each tied to its source.
Last reviewed against Information Commissioner's Office, GOV.UK and DLA Piper. Sources
For an order of work see the plan of action, and for every date see the key dates.
Quick answers
Questions people ask
What is GDPR redaction?
It means removing or masking material before you release a record, so the requester receives their own data and nobody else's. The ICO describes the task as supplying information, not whole documents[1].
What can you redact from a disclosure?
Details of other people, unless they agree or releasing them is reasonable without their agreement[1]. Anything within an exemption, for example privileged legal advice, can also be held back[3].
Do you need to keep a record of redaction decisions?
Yes. Each decision has to be defensible, so the ICO's advice is to write down what you chose and the reason for it[1]. For exemptions, note the grounds and the prejudice you identified[3].
Is a black box enough to redact a file?
Not by itself. The ICO's tip is to save a computer redaction as a new file, and for paper to check that nothing can be read behind the mark[12].
How long do you have to answer an access request?
The limit is one month from receipt, ending on the matching date the next month[4]. If a request is complex, or one individual sent several, up to two more months are possible provided you write to them in month one[4].
How should you send a redacted disclosure?
Choose a method that suits the sensitivity, such as an encrypted file with the code sent by another route, or special delivery for paper[2]. Verify the address before sending[2].
Why are spreadsheets risky to disclose?
They can carry hidden rows, columns, sheets and filters. The ICO's checklist lists hiding rows, columns or worksheets among ineffective ways to protect data[6].
Can you refuse a request because it names other people?
No. A reply is still required, and it should contain as much as possible without revealing the other person[1].
Keep reading
Read next
Who is in scope
Which UK organisations need a redaction and disclosure process, and how to tell whether your records make it urgent.
Read the guide
Key dates
The dates that shape redaction and disclosure for UK access requests: ICO guidance updates, rule changes and reprimands, each sourced.
Read the guide
Action plan
An ordered plan to build a redaction and disclosure process: procedure, review, exemptions log, secure delivery and deadlines.
Read the guideHow CyPro can help
Need a hand getting ready?
Reading the rules is one job. Mapping them to your organisation, closing the gaps and showing the evidence are several more. CyPro's consultants can take any of them off your plate.
Fractional CISO for the board
A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.
More on cypro.co.uk
Penetration testing
A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.
More on cypro.co.uk
Hardening and segmentation
Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.
More on cypro.co.uk
24/7 security monitoring
Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.
More on cypro.co.uk
Incident response
If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.
More on cypro.co.uk
Vulnerability scanning
Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.
See the scanning service
Get ready
Need to know what this means for you?
A disclosure that leaks, or a redaction you cannot explain, becomes a complaint to the ICO. A GDPR consultant can review your disclosure workflow, exemption log and release checks before a request tests them.