In short
Jarell Oshodi, Deputy Chief Privacy Officer at the CDC, argues that privacy compliance is built on a few repeatable disciplines rather than on memorising every law. Her MIND URS framework starts with knowing exactly what personal data you hold, then layers on privacy by design, clear notices, trained staff, well-written vendor contracts, risk assessments and a rehearsed breach response. Done together, these reduce the risk of noncompliance and build the client trust that her session frames as a competitive advantage.
Key takeaways
- Six strategic pillars of privacy compliance.
- The acronym is MIND URS.
Map your data before anything else
Oshodi calls mapping your data the most important part of privacy compliance. A data inventory identifies what personal data sits in your systems, what you share, who owns it and what its retention schedule is. It does not need to be sophisticated: it can be a spreadsheet or an automated tool.
The value is in what the map reveals. "It's helpful when trying to minimize data, which helps to lower the risk because lots of times we have data that we don't need." (0:58) She gives examples: records kept ten years when the retention schedule allowed five, or social security numbers collected without a legitimate purpose. Once you can see that data, you can dispose of it. The same map becomes essential later, when an organization has to respond to a data incident or breach.
Build privacy in, and tell people about it
The I in MIND URS stands for implementing privacy by design. Oshodi urges teams building a product or service to consult privacy professionals or attorneys throughout the process, not at the end. That is when you discover unnecessary collection, consent requirements, or that a law applies: GDPR if you market to clients in Europe, or California's CCPA if you market to Californians and your revenue is above the threshold. Privacy considerations should cover the whole life cycle of personal data, from collection and use to storage, archival and disposal. "It should always be in the back of your head." (4:43)
The N is for notify. Employees, customers and third parties such as vendors and contractors all need proper privacy notices. A good notice explains what is collected, why, for how long, the valid business reason, the security measures in place and the data subject's rights. Those rights vary by sector, state and country, Oshodi notes, citing HIPAA for health information and FERPA for educational entities, and may include the right to access, correct or delete data.
Make privacy everyone's job, including your vendors
D stands for developing privacy operations. That means training, keeping the board informed about new privacy developments, and creating privacy champions in marketing, HR, finance, procurement and IT. Simple tools such as flow charts help colleagues understand how to minimize data and protect other people's personal data.
U is understanding contracting. When an organization shares data with vendors, those vendors must protect it to the same standard, with comparable administrative, technical and privacy controls such as firewalls, encryption and appropriate retention periods. Oshodi's bar is high: vendors should protect data "Just as well, if not better than you are collecting the data." (7:44) Equally important is making sure vendors understand what they agreed to in the contract.
Assess the risk and rehearse the breach
R covers risk assessments, including privacy impact assessments and data protection impact assessments. 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)
The final letter is the security function: breach response procedures, a data incident response plan, and tabletop exercises so people know what to do if a breach or incident occurs.
Getting into privacy work
In the Q&A, an attendee asked how to prepare for a privacy career. Oshodi says certifications such as the CIPP, the more technical CIPT, or the CIPM for managers show commitment, but are not required; she worked in the field for years before earning hers. As a hiring manager, she would rather see hands-on experience with privacy impact assessments or breach response, along with strong research and writing.
Above all, she values resourcefulness. "You're enterprising, you take the initiative and you can figure things out because privacy is always changing." (13:12) Nobody expects you to know every law, she adds, because nearly all privacy laws rest on the fair information practice principles and differ mainly in degree, with GDPR perhaps the strictest. Understanding those principles, such as data subject rights, data minimization and consent, is the best preparation.
Watch the talk
"Data Privacy as a Competitive Differentiator" by Jarell Oshodi, about 15 minutes: https://www.womentech.net/video/data-privacy-competitive-differentiator-jarell-oshodi
About the speaker
Jarell Oshodi is the Deputy Chief Privacy Officer at the Centers for Disease Control & Prevention (CDC) and a licensed attorney with the Law Office of Jarell Oshodi, LLC, where she provides data protection guidance to small and mid-size companies. She holds the CIPP/US and CIPM certifications and is an advisory board member of the Birth Equity Advocacy Project and a Black maternal health advocate.
Questions this talk answers
- Where should a privacy compliance program start?
- What should a privacy notice tell people?
- How should organizations handle vendors that receive personal data?
- Why do privacy impact assessments matter?
- Do you need a certification to get a job in privacy?
Drafted with AI from the talk transcript. Editor review pending.