However, that’s only one piece of the puzzle. People should also have control over how their data is being stored and processed – which requires companies to give users a peek behind the curtain. For example, if an employee requests access to their personal data, IT teams need to be able to quickly create a report that shows what information the company is tracking, who can access it and how it is leveraged to inform decision-making. Many organisations, however, have room for improvement – just 34% of respondents in a global privacy survey said they have conducted data mapping and understand their organisation’s data practices.
Admin guides and fact sheets can help companies clearly communicate how personal data is used by ML models, giving people the context they need to make an informed choice about what they will allow.
“It's really about what data is used as input, what the output of the machine learning capability is, how we are doing bias evaluation and how our machine learning model is trained,” said Sabine Hagege, Director, HCM Product Strategy at Workday. “People need a lot of information to understand how the data is processed.”
3. Get Granular with Consent
In many situations, users will be comfortable sharing some personal information for specific purposes. Companies are then responsible for making sure that data is only used in approved ways. And if a company works with consumers or employees in multiple jurisdictions, it must ensure that data isn’t shared with or pulled from regions with different privacy laws.
How can CIOs navigate all the moving parts? It starts with the proper configuration. Technology platforms that offer a localisation framework give IT teams the power to determine what type of information can be tapped for different people based on who they are, what role they play and where they’re located.
“It’s best when you can configure for each purpose you collect data for. So is it for diversity and inclusion or statistics and metrics?” said Hagege. “Then, on a country-by-country basis, use the consent response to configure your other processes and control how that data is used.”
4. Purge Data You Don’t Need
Many privacy rules also demand that personal data be deleted when it’s no longer needed. Consent should be given for a specific purpose and timeframe – and companies must permanently erase, or purge, that information afterwards.
To stay in line with expectations and regulations, each company needs a data purge plan. CIOs should work with their IT teams to determine which data should be purged when – and then schedule mass deletions on a regular basis.
However, that alone is not enough. Companies must also be able to purge an individual’s data at will, either because their status has changed or because they’ve requested it. For example, a CIO might want the data of every terminated employee purged immediately after they leave the company. Or a job candidate might request their data to be purged if they aren’t hired.
IT should make it easy for people to get their data deleted – but it’s important to remember that “purging is irreversible,” said Hagege. “So it's very important that you implement some controls and make sure that whoever has access to purge is fully aware that it can’t be undone.”
5. Keep Private Data Confidential
Getting consent to collect and use private information doesn’t make it any less private. CIOs must keep this in mind when determining who can view what data – and take the steps needed to keep sensitive information confidential.