Providing privacy information is a legal requirement
We see lots of links to privacy notices on the web, but does anyone ever read them?
Yes, they can be annoying when they invade the screen. Maybe we don’t see their relevance. Or perhaps we trust the organisation that has collected our data to use it sensibly. Then again, some privacy notices are so long-winded that reading them becomes a chore. Others are too complicated, written in legal speak that only a few will understand.
Yet a privacy notice is a key document. It is meant to tell us how and why the organisation uses our personal data and how it keeps it safe. In fact, this is one of our a data protection rights, and something I am sure we'd want to help enable.
So how do we make privacy notices relevant and readable?
The UK GDPR says that privacy information must be provided at the time an organisation collects an individual’s personal data. So on a website, a pop-up notice would certainly meet that requirement. But so too would a link to the notice or a download if they were clearly highlighted at the point data was to be collected. But these methods don’t necessarily result in the privacy notice being read.
So if an organisation wants to do more than the minimum required by law; and actually encourage individuals to see how you use their data, then the following might help.
- When linking to or highlighting privacy information, use proactive wording such as Find out what we do with your personal data here.
- Use a dashboard approach, with links such as How is my data used? Who can see my details? How we protect your data, etc. (Such links can also be added to user profiles where applicable).
- Keep privacy notices as short as possible; and use a layered approach (providing key information first, and then linking to a layer of more detailed information).
- Segment information to the relevant audience where appropriate (for example, provide information on using volunteers data to that particular group only, rather than to others such as supporters and donors etc).
- Use clear and plain language. Definitely avoid legal speak, jargon and technical wording.
- Make it accessible. If your user community uses other languages, then provide your privacy information in those languages.
Of course, many organisations will collect personal data in person or through paper forms. If these apply to you then your privacy information should still be provided at the point of collection. You can do this orally, or in writing, but the above points still apply.
To help, the Information Commissioner's Office (ICO) has a template that can be used to develop a privacy notice; and they have a whole detailed section on the Right to be Informed which explains how to provide privacy information.
For your organisation providing privacy information is a legal requirement, so you need to get it right. Indeed, its importance is up there with other key policies such as health and safety or safeguarding, so it must be fit for


