John is 68, retired and, for the past year, the volunteer treasurer of his local bowls club. One Tuesday morning he sits down at his desk with a list of things to send. His insurer wants the bank statement showing his payment to the glazier, to refund the window broken in the storm. His new electricity supplier wants a copy of his ID card for the contract. And the residents’ association is waiting for the club’s annual report, the one with the list of members.
John has the three files ready. The bank statement covers the whole month, with the balance, his pension and every payment. The ID card is a quick photo taken on the kitchen table, front and back. In the report he has covered the members’ phone numbers with black rectangles. He is about to press “Send” when he stops: does the person receiving these files really need everything in them?
This recommendation, R43 of the Cyber Welfare Framework, invites you to do what John did that morning: share documents with only what is needed. Before you send a copy of your ID, a utility bill, a contract or a screenshot, ask what the recipient actually needs, and prepare a copy that contains just that. It does not ask you to refuse legitimate requests, just to take a few extra minutes first.
What this recommendation says
Recommendation R43 states that every document you send should carry only the information needed for the purpose you are sending it for.
Four terms to clear up straight away:
- to redact means to genuinely remove information from a file, so that it cannot be recovered; a black rectangle drawn over text often only covers it, and the text stays underneath;
- to crop means to cut an image or a scan so that only the useful part remains, such as a single line of a bank statement;
- metadata is the information hidden inside a file that you do not see on the page: the author’s name, the dates it was created and edited, sometimes the place where a photo was taken, comments and tracked changes;
- data minimisation is the principle that only the data needed should be used: the GDPR, the EU’s General Data Protection Regulation, in Article 5(1)(c), requires data to be “adequate, relevant and limited to what is necessary”. It is an obligation on whoever collects the data, and a good question for whoever hands it over too.
In practice, the recommendation comes down to six actions, to choose according to the document:
- ask what is needed, and why, before preparing the copy;
- redact properly whatever is not needed, with a tool that removes the content;
- crop screenshots, photos and scans;
- remove metadata before sending;
- add a watermark, where it makes sense, with the purpose and date;
- choose a secure channel and ask how long the copy will be kept.
What it is not. It is not a way round procedures required by law: where a procedure requires the whole document, for example when you open a bank account, you follow the procedure. It is not about the location saved in photos, which is the subject of the recommendation on turning off photo geotagging, nor about codes in images, which is covered by the recommendation to stop posting photos with QR codes. And it does not deal with online age and identity checks, which are the subject of the recommendation on proving only what is asked: R43 is the practical step that goes with it, when a document really does have to be sent.
Where it applies. To every file you hand over to others: copies of ID documents, utility bills, payslips, bank statements, contracts, minutes, screenshots of chats or payments. It covers both your own data and that of the people who appear in your documents: members, colleagues, family, clients.
Why it matters
Think of a letter written on a pad of thin paper: you post the top sheet, but the one below still carries the groove of the pen. A digital file often works the same way: what you see on the page is only part of what you send.
This is how it works. Every time you send a document you create a new copy, somewhere you cannot see: an inbox, a chat, a company’s archive. That copy contains everything in the file, including what you did not mean to show, and stays there until someone deletes it.
Regulators have been pointing this out. On 29/04/2026 the Garante, the Italian data protection authority, reminded hotels and B&Bs that they may not keep copies of guests’ documents for longer than strictly necessary, and that photographing documents with a smartphone or having them sent through messaging apps exposes people to real risks, such as identity theft and unauthorised access to their data. Earlier, on 13/08/2025, the same authority and AgID, the Agency for Digital Italy, had reported the theft of thousands of scans of passports and ID cards from the systems of some Italian hotels: according to the agency, data of this kind can be used to create fake documents, open accounts or prepare tailored scams.
Then there is the less visible side. The ICO, the UK’s data protection regulator, in its guidance on redacting documents (published on 31/07/2025 and under review following the UK’s new data law that year), warns that text covered by a rectangle stays in the file, that sometimes copying and pasting it elsewhere is enough to bring it back, and that documents can contain comments, tracked changes and properties such as the author’s name.
The practical effects show up in four areas:
- copies that stay: a document sent today may still be in an inbox in ten years;
- data that adds up: a full bank statement tells the story of your pension, your spending and your habits, not just the payment that was asked for;
- covers that do not cover: a name hidden badly is still in the file, for anyone who looks;
- other people’s data: a list of members or a contract contains information that is not yours to hand out.
| Benefit of sharing only what is needed | Why it matters |
|---|---|
| The recipient gets what they need, and no more | What you do not send cannot be lost, forwarded or reused |
| Fewer complete copies around | Fewer openings for identity theft |
| Redactions that hold | Data that has really been removed does not reappear with copy and paste |
| No hidden information in the file | The author’s name and tracked changes stay with you |
| A copy tied to one purpose | A watermark makes it harder to reuse for something else |
A concrete example
Back to John.
First he rings his insurer. The assessor needs only proof of the transfer to the glazier, with date, amount and payee. John takes a screenshot of that single payment in his online banking, crops it down to one line and sends it through the insurer’s portal rather than by email.
Then he writes to the electricity supplier. They reply that the copy of his ID really is needed, to identify him for the contract. John makes a clean scan on a clear table and adds a semi-transparent watermark: “Copy for electricity supply contract only”, with the date. He checks first that a watermark is acceptable: it is, as long as the details stay legible. He uploads the file to the customer area and asks how long they will keep it: for the length of the contract.
Finally, the report. His granddaughter, in for lunch, clicks on a black rectangle and selects the phone number underneath. John realises the rectangle was covering, not redacting. The residents’ association, they learn, needs the number of members and the subscriptions, not their contact details. John deletes the phone column from the original file, then checks the document’s properties: the previous treasurer’s name appears as author, and there are still two comments in the margin. He removes the metadata, saves a new copy and reopens it to check.
Three documents sent, and each contained only what the recipient needed.
When to apply it
There are moments when the rule makes an obvious difference.
- When someone asks for a copy of an ID document. It is the file that says most about you in the least space.
- When you send proof: of a payment, an address, an income. One line is usually enough, not the whole bank statement or payslip.
- When you share a screenshot. It often shows names, numbers and notifications that have nothing to do with it.
- When a document contains other people’s data: members, colleagues, tenants, clients.
- When you publish a file online, where anyone can download it and open its properties.
- When the request arrives out of the blue, by email or message, with an urgent tone. An unexpected request for documents deserves a check before anything else, as the recommendation to be wary of emails pretending to be your bank explains.
How to apply it
A short sequence, to repeat.
- Ask what is needed, and why. Whoever asks should be able to explain. Sometimes the type and number of the document are enough, or showing it in person; sometimes the full copy is needed, and then you send it.
- Start from a copy, never the original. Work on a duplicate, so the original stays intact.
- Crop what is not needed. For screenshots and scans, cut the image down to the useful part. Then save a new image, rather than editing the old one.
- Redact properly. For text, use the feature that removes the content, often called “redact”, not a black rectangle or highlighter. If your software does not offer it, you can print the document, cover the text by hand and scan the covered copy again.
- Remove metadata. Many document programs have a hidden-data check that finds the author, comments and tracked changes. For photos, location is handled as the recommendation on turning off photo geotagging explains.
- Add a watermark, if it makes sense. A line of semi-transparent text with recipient, purpose and date. Ask first whether it is accepted: some organisations reject it if it covers details or codes they need to read.
- Check the result. Open the final copy again, try to select the text in redacted areas, zoom in, look at the properties.
- Choose the channel and ask about retention. Prefer the organisation’s upload form or secure area to email or chat, and ask how long they will keep the copy: their privacy notice has to tell you.
The steps in order, including what to do if a file has already gone with too much in it, are in the guide on how to redact a document before sending it. What a file hides, and how that information is read and removed, is explained in the post on document metadata.
Common mistakes to avoid
- Thinking a black rectangle is enough. In a digital file it often only covers: the text stays underneath and can be copied. On paper, marker pen may show through against the light.
- Sending front and back “just in case”. If the procedure asks for one side, the second is extra data someone will have to look after.
- Forgetting other people. A list, a group photo or a set of minutes contains data about people who are not there to decide.
- Covering with a light blur. The ICO warns that redactions made with simple image-editing tools can sometimes be reversed. It is better to remove the part entirely, or cover it with a solid block on a new image.
- Using a watermark instead of redaction. A watermark ties the copy to a purpose, but it hides nothing.
How this connects to the Cyber Welfare Framework
R43 brings data minimisation into an everyday act: sending a file. It puts into practice the principle of the recommendation on proving only what is asked, and hands back to you the decision on how much each copy you leave behind says about you.
| Pillar | How this contributes |
|---|---|
| Skills | Knowing how to crop an image, properly redact text, find and remove a file’s metadata and add a watermark |
| Awareness | Understanding that a file contains more than it shows, that covering is not redacting and that every copy sent stays somewhere you do not control |
| Secure Behaviour | Asking what is needed before every send, preparing a minimal copy, choosing the channel and asking how long it will be kept |
Digital maturity levels.
- FL1 — Basic. You send documents as they are, in full, through the first channel to hand. It is the most common starting point, not a fault.
- FL2 — Beginner. Before sending you ask what is needed, crop screenshots and no longer send more than necessary.
- FL3 — Autonomous. You redact with tools that remove the content, remove metadata, check the result and choose the channel.
- FL4 — Skilled. You handle documents containing other people’s data, use watermarks with judgement and keep a note of what you sent, to whom and for how long.
- FL5 — Expert-Guide. You help family, colleagues or a club prepare minimal copies, calmly and without blame for past sends.
R43 is the key step from FL1 to FL2, and it remains an active habit at every level after that.
How to check you are applying it properly
Three honest questions.
- Before the last document I sent, did I ask what was really needed?
- If someone tried to select the text under my covers, would they find it?
- Do I know who keeps a copy of my ID document today, and until when?
Quick checklist
- ☐ Before sending a document I ask what is needed and why
- ☐ I work on a copy, not the original
- ☐ I crop screenshots and scans down to the useful part
- ☐ I redact with a tool that removes the content, and check the result
- ☐ I remove metadata before sending
- ☐ I use the organisation’s channel and ask how long it will keep the copy
If a box stays empty, that is your next step. For a more structured measure of your level, take the digital resilience self-assessment.
In short
Every document you send becomes a copy somewhere you do not control, often with more than is needed: extra lines, other people’s data, covers that do not cover, information hidden in the file.
The answer is simple: ask what is needed, crop, redact properly, remove metadata, add a watermark where it makes sense, choose the channel and ask how long it will be kept. Where the law requires the whole document, follow the procedure.
Sending documents is a normal part of life. How much each copy says is your decision.
Something to think about. If you could reread today every document you sent last year, how many would you send unchanged?
Explore this recommendation
This recommendation is the pivot of a content unit. Each post looks at a different aspect.
- Document oversharing risks — what gets hit, in terms of the confidentiality, integrity and availability of your documents
- Consequences of a badly redacted document — the concrete effects on the operational, financial, legal, reputational and personal levels
- How to redact a document before sending it — the mitigations, from the minimal copy to what to do after a wrong send
- Signs a document reveals too much — the indicators to check before you press “Send”
- Document metadata — file properties, true redaction, cropping, watermarks and clean export, with their strengths and limits
- Attacks on shared documents — the ways covers, metadata and copies are exploited
Related resources
Short reads from the Resources section, for anyone who wants to focus on a single aspect:
- Share Sensitive Documents Online: Send Only What Is Needed
- Spear Phishing: Why Scam Messages Know So Much About You
- Data Encryption: Already On, and Worth Understanding
Start with the first step: the Cyber Welfare Programme guides you free of charge, one recommendation at a time.




