The Privacy Notice People Actually Read
Two documents rather than one: the complete notice that satisfies the requirement, and the page that answers what people want to know.
STAFF PRIVACY NOTICE
Issued at hiring, re-issued when anything changes
- Who we areThe employing entity, namedGroup companies are separate controllers and need naming
- What we holdBy category, matching the record of processingContradictions between the two are the commonest finding
- WhyThe purpose, specificallyBusiness purposes is not a purpose
- On what basisPer purpose, not per categoryWhere it is legitimate interests, say which interest
- Who sees itInternal roles and named supplier typesLine managers see what, exactly
- How longWith the triggerSix years after employment ends, not six years
- What you can ask forListed, with how to exercise themIncluding the right to complain to the regulator
- ChangesHow you will be toldThe commitment people actually test
Every employer has a privacy notice. Almost none has one that changes what anybody believes, because the document satisfying the legal requirement and the document answering people's questions are not the same.
The practical lesson in “The Privacy Notice People Actually Read” is that a record is useful only when its purpose, owner and lifecycle are clear. For teams researching workforce analytics software, more information can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
What the requirement asks for
Identity of the controller, categories of data, purposes, lawful bases, recipients, retention, rights, and how to complain.
For a separate benchmark relevant to “The Privacy Notice People Actually Read”, consult the OWASP privacy-risk project. Use it to test purpose, data flow, retention, access and response procedures rather than substituting a generic checklist for the organisation’s actual records.
Delivered before or at the point of collection. For staff that means at hiring, and again whenever something material changes.
This is a complete list and meeting it produces a document of several pages in the language of the obligation.
Why that document fails at the other job
People do not read it, which means their beliefs about what the employer collects are formed by rumour and by the worst thing they have heard.
And those beliefs are what they act on. An organisation that has complied and informed nobody has paid the cost of the obligation and received none of the benefit.
The second document
One page, plain, answering the four questions people actually have.
What is not collected — the most reassuring content available and absent from nearly every notice.
Whether a line manager can see individual records, stated either way.
Whether any of this reaches performance or disciplinary processes.
What the systems could do that has been switched off, with a commitment to announce any change.
None of that is required. It costs an afternoon and it is the only version anybody will read.
Keeping the two aligned
The short page must not contradict the formal notice, and neither may contradict the record of processing.
A regulator comparing the three looks for inconsistency before gaps, because a contradiction shows that nobody is maintaining them — which its own note covers.
Dating both and updating them together is the whole of the discipline.
Issuing it, and re-issuing it
At hiring, and again whenever anything material changes. A notice issued once in 2019 describes an organisation that no longer exists, and the date on it is the first thing anybody checks.
What goes in the short version
Four things, none required: what is not collected, whether a line manager sees individual records, whether any of it reaches performance processes, and what the systems could do that is switched off.
Dating both and updating together
The formal notice and the short page must not contradict each other or the record. A regulator comparing three documents looks for inconsistency before gaps, and the only defence is a shared review cycle.
Who reads which version
Nobody reads the formal notice and everybody reads the short page, which is the entire argument for producing both. The formal one satisfies the obligation; the short one changes what people believe.
Four lines on the form itself
At the point of application, not a link to the staff policy. What is collected, why, how long if unsuccessful, who sees it including any agency. It does more than a linked document nobody opens.
The date on it
First thing anybody checks. A notice issued four years ago describes an organisation with different systems, different suppliers and different retention, and the date says so before anybody reads a word.