Home / Privacy notices people will actually read: turning transparency into understanding
20th November 2026
Laura Crowe, Senior Associate
Legal training places emphasis on detail, hence the familiar joke: why use one sentence when five will do?
Yet the real skill in giving legal advice and drafting documents lies not in making complex issues sound more complicated, but in making them understandable. After all, if we cannot explain a concept clearly, how well do we understand it ourselves?
That matters particularly in data protection, where the audience may include children or people in vulnerable circumstances. If someone cannot work out what happens to their data, adding more detail will not necessarily make the explanation more transparent.
Transparency does not mean describing every aspect of processing in minute detail. It means giving people the information they need, in language and a format they can understand. The starting point should be the intended audience, not the organisation’s internal terminology.
This reflects the ICO’s guidance: privacy information must be concise, transparent, intelligible, and easily accessible, using clear and plain language. It must also cover the applicable requirements, including purposes, lawful bases, recipients, retention, and individual rights. Clarity is not an excuse to leave out required information; it is the means of making that information useful.
A privacy notice should be written for the people who will actually read it. Customers purchasing a product, employees using workplace systems and applicants completing recruitment forms all interact with personal data in different ways. A single, catch-all notice may be administratively convenient, but it is unlikely to provide each audience with the information most relevant to them.
The ICO recommends tailoring privacy information to the needs and expectations of the intended audience. In some cases, such as when processing children’s data or supporting individuals in vulnerable circumstances, additional care may be needed in both language and presentation. Effective transparency is not simply about replacing legal jargon with plain English. It is about explaining data use in a way that is meaningful and relevant to the individual reading it.
Before drafting a notice, make sure you understand what happens to the data in practice. Engage with the teams that collect, access, and use personal data to confirm the purposes of processing, data sources, sharing arrangements, and retention periods. Information audits and data mapping can provide a useful foundation. Even the clearest privacy notice will fail to support transparency if it does not accurately reflect the organisation’s actual processing activities.
A privacy notice should explain how personal data is used, not document every aspect of an organisation’s internal systems.
Individuals will usually gain more value from a clear explanation of why their data is shared with a delivery provider, payroll service, or recruitment platform than from a list of technical system names and operational processes. Equally, vague descriptions such as “business purposes” or “trusted partners” can undermine transparency by leaving key questions unanswered. The challenge is to strike the right balance.
The distinction is between operational detail that adds little value and information that genuinely helps individuals understand what happens to their data. Simplification should never conceal a processing purpose, downplay a significant use of personal data, or obscure the extent of data sharing. A useful test is whether a reader can understand how and why their data is used, what the implications may be, and how they can exercise their rights, rather than simply whether every required topic has been mentioned somewhere in the notice.
Not every reader needs every detail at the same time. The ICO advocates a layered approach, providing the most important information upfront and allowing individuals to access more detailed explanations when needed. This can be complemented by just-in-time privacy information presented at the point where personal data is collected or used.
In practice, this means placing concise, relevant explanations alongside the forms, features or processes they relate to, and linking directly to more detailed information. A recruitment form, for example, can explain how application data will be assessed, while an online checkout can highlight data sharing necessary for delivery. Information that is unexpected, intrusive, or particularly significant should be made prominent rather than left for readers to discover in a lengthy privacy notice.
However, layering should not create barriers to understanding. The second layer must be easy to find, clearly signposted and logically organised. Meaningful headings and descriptive links help users navigate to the information they need. The objective is not simply to reduce the length of the first screen, but to make relevant privacy information accessible, understandable, and usable when it matters most.
Use concrete language, make the key points prominent, and keep supporting detail easy to find. Test whether your intended audience understands the explanation and not simply whether they approve of it. Give someone responsibility for keeping it accurate as practices change.
A privacy notice should leave readers better informed, not merely leave the organisation satisfied that it has covered every topic. The question is not just “Have we included everything?” but “Have we made it make sense?”
Note that this piece is general commentary, not advice on a particular processing activity. If you require specific advice, please contact Laura Crowe, CIPP/E in our Commercial Team who will be happy to assist.