One organisation, several notices.
WHY SEVERAL
Different groups need different information.
WHAT AUDIENCES TYPICALLY EXIST
Customers Website visitors Employees Job applicants Suppliers Anyone whose data you hold indirectly
WHY EMPLOYEES NEED A SEPARATE ONE
What you process about staff differs entirely from customers.
WHAT THE EMPLOYEE NOTICE SHOULD COVER
Records held Monitoring, if any Who it is shared with Retention after leaving
WHAT THE APPLICANT NOTICE SHOULD COVER
What happens to unsuccessful applications How long they are kept
WHAT A SUPPLIER NOTICE SHOULD COVER
Contact details held Why, and for how long
WHAT TO DO ABOUT DATA OBTAINED INDIRECTLY
Tell the person, within a defined period, unless an exception applies.
WHY THAT IS OFTEN MISSED
People assume the obligation applies only to data collected directly.
WHAT TO INCLUDE THERE
Where you got it.
WHAT TO KEEP CONSISTENT ACROSS NOTICES
Contact details Rights information Complaint routes
WHAT TO VERSION
Every notice, with dates.
WHY
You may need to show what someone was told at a given time.
WHAT TO ARCHIVE
Previous versions.
