Delivery
Sending a disclosure securely
A well redacted pack can still be lost in transit. Match the delivery method to the sensitivity, verify the address and make sure the requester can open the file.
Last reviewed against Information Commissioner's Office, GOV.UK and DLA Piper. Sources

The standard
Reasonable steps, every time
Methods
Choose by sensitivity
Encrypted files
Encrypt the information and pass the access code by a separate route. The ICO notes this gives the person direct access to their data [2].
Secure portal
An online system can meet the request if the person can download a usable copy and has no objection. Make clear that another format is available on request [2].
Post
Post is secure in many situations, and for sensitive material the ICO suggests special delivery or a courier [2].
Format
Can they read it?
An electronic request must be answered in a commonly used electronic format [2]. People should not have to buy or install software to read the result, so a proprietary format they cannot open does not qualify [2].
If they ask for something risky
Where a requested delivery method raises a security concern, explain the concern and propose an alternative [2].
Before you press send
A short list
Run through these every time:
- The address matches the request and has been verified.
- The attachment is the redacted copy, saved as a new file [12].
- The access code is travelling by a different route.
- The log records what was sent, to where, and when.
Repeat copies
Do not over-supply
A person who downloads a copy from a portal and then keeps asking for more copies in other formats may be treated as making a manifestly unfounded or excessive request, according to the ICO [2]. Offer a sensible choice at the start so this does not arise.
Keep reading
Read next
Spreadsheets
Why spreadsheets leak in disclosures and what the ICO checklist says: hidden rows, filters, links, CSV conversion and the Southend case.
Read the guide
Exemptions
The exemptions that justify withholding material from an access request, how prejudice works and what to tell the requester, per the ICO.
Read the guide
Third party names
When to redact another person's name in a disclosure: the ICO's three questions, confidentiality, staff and what the requester already knows.
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.