Use privacy risk thinking to challenge unnecessary employee data collection in HR systems.
A field is a liability until its purpose is proven. HR technology teams often inherit vendor templates, old spreadsheets, and executive requests as if every data point deserves a permanent home. Purpose Before Collection The first privacy question is not whether the system has a field. It is whether the organization has a legitimate, current purpose for collecting that data at this moment in the employee or candidate journey. Candidate data, employee data, payroll data, and accommodation data do not all belong in the same access pattern. Controls Follow Sensitivity Once a field is necessary, the next question is control.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in