In short
Privacy compliance starts with knowing what personal data you hold, according to attorney Jarell Oshodi. Her MIND YOURS framework moves from mapping data and building privacy into products, through notices, operations, vendor contracts and risk assessments, to a rehearsed plan for when a breach happens. In a short Q&A she adds that newcomers to privacy need resourcefulness and practical experience more than encyclopedic legal knowledge.
Key takeaways
- Build a data inventory map that shows what personal data you hold, who owns it and how long to keep it.
- Apply privacy by design across the personal data life cycle, from collection to disposal.
- Write privacy notices that explain what is collected, why, for how long, the security measures in place and data subject rights.
- Hold vendors to the same administrative and technical privacy controls through contracts.
- Prepare a data incident response plan and test it with tabletop exercises.
M: map your data before anything else
Oshodi opens her framework with what she calls the most important part of privacy compliance. A data inventory identifies what information an organization shares, what personal data sits in its systems, who owns it and what the retention schedule is. She is clear that this does not need to be elaborate: it can be an Excel spreadsheet, or it can be automated with one of the many software tools available.
The value of the map is that it exposes data nobody needs. She describes records kept for ten years when the retention schedule allowed five, and social security numbers held without a legitimate purpose. Disposing of that data lowers risk directly.
"So an inventory map is most important when it comes to data privacy compliance and also when it comes to a data incident or data breach, which we will get to at the end." (2:01)
I and N: build privacy in, then tell people about it
The second step is implementing privacy by design. Oshodi urges teams building a product or service to consult privacy professionals or attorneys throughout the process. That consultation can reveal unnecessary data collection, consent requirements, or the fact that marketing to clients in Europe brings GDPR into play, or that marketing to California clients above the revenue threshold brings in the California Consumer Privacy Act. Privacy has to cover the whole life cycle of personal data: collection, use, storage, archival and disposal.
"And that's what we mean here by implementing privacy by design. It should always be in the back of your head." (4:43)
Notification comes next. Employees, customers and third parties such as vendors and contractors all need proper privacy notices. A good notice tells data subjects what is collected about them, why, for how long, the valid business reason and the security measures in place. It must also explain their rights, which vary by sector (she cites HIPAA for health information and FERPA for educational entities), by state and by country. Those rights can include access, correction and, in certain instances, deletion.
"And finally, it's important that privacy policies inform data subjects of their data subject rights." (5:14)
D, U and R: operations, contracts and risk
Developing privacy operations means training, keeping the board informed about new privacy developments, and creating privacy champions in marketing, HR, finance, procurement and IT. Oshodi recommends simple aids such as flow charts so colleagues understand how to minimize data and protect other people's personal data.
Understanding contracting is about vendors. If a company shares data with vendors, they should protect it as well as, if not better than, the company itself, with the same administrative and technical controls, such as firewalls, encryption and short retention periods, and a clear understanding of what they agreed to.
Risk assessments, including privacy impact assessments and data protection impact assessments, help an organization understand its exposure. They matter most where sensitive information is involved, such as social security numbers, racial or medical information, or data about children.
"That type of data requires even higher controls in place to protect it because there's a greater harm to, um, that could possibly occur if that information is breached." (8:46)
S: be ready for the breach
The final letter is the security function. Oshodi calls for proper breach response procedures, a data incident response plan and practice runs so people know their roles before an incident happens.
"This is where you need to make sure that you have proper data, um, breach response procedures in place, a data protection or a data incident response plan, uh, and even conduct tabletop exercises to make sure that people understand what they are supposed to do in case there is a breach or incident." (8:46)
This loops back to the first step: the data map is what lets a team know quickly which data an incident has touched.
Breaking into privacy: experience and resourcefulness
Asked about career preparation, Oshodi recommends the CIPP for newcomers, the CIPT for more technical people and the CIPM for managers. They give employers confidence that a candidate is committed, but they are not required; she has worked in privacy for about 12 years and earned the CIPP only about five years ago. As a hiring manager, she prefers practical experience.
"Um, and I, as an employer, as someone who hires, I would say, I would much prefer someone with experience, someone that maybe, uh, had experience in, uh, completing privacy impact assessments or experienced in a data breach response and incidents." (12:16)
Because privacy keeps changing, she values people who are enterprising and take the initiative. In her view, nearly all privacy laws rest on the Fair Information Practice Principles and differ mainly in degree, with Europe's GDPR perhaps the strictest. Understanding those principles carries over from one law to the next.
"We don't, no one expects you to know every privacy law, but you should be able to be resourceful, um, and be a great problem solver." (13:12)
Watch the talk
Data Privacy as a Competitive Differentiator by Jarell Oshodi, Jarell Oshodi, 15 minutes: https://www.womentech.net/video/data-privacy-competitive-differentiator-jarell-oshodi-0
About the speaker
Jarell Oshodi is a licensed attorney in Georgia who has spent the past decade working in data governance, information security, privacy and FOIA, and who founded the Law Office of Jarell Oshodi, a firm dedicated to protecting clients' data and providing privacy training and workshops. She holds a Bachelor of Science from Hampton University, a JD from Mercer University and the CIPP and CIPM privacy certifications (as she described in the talk).
Questions this talk answers
- Where should a privacy compliance program start?
- What should a privacy notice tell people?
- How should companies manage privacy risk with vendors?
- Which certifications help someone break into privacy?
- Do privacy professionals need to know every privacy law?
Drafted with AI from the talk transcript. Editor review pending.