Despite all the advantages and benefits of AI, most of us are at the beginning of our AI governance journey.  We need to learn how to handle and protect data during its use.  Let’s talk about some of the key aspects of AI governance!

Our first monthly PETed Sip & Chat hosted by Janelle Hsia! Join us the 3rd Friday of every month at 11:00AM ET throughout 2025. Grab a beverage and come discuss Data Subject Requests (DSRs)!

Privacy impact assessments are a cornerstone of robust privacy compliance frameworks and an important part of a mature privacy program. PIAs proactively equip companies and institutions with an understanding of data processing and privacy impacts as well as possible remediation. Mandatory in California, Colorado, Connecticut, Texas, the EU and other regions, PIAs are non-negotiable in an increasing number of jurisdictions for high-risk processing activities (potentially harmful impacts to the individual).

Privacy impact assessments are a cornerstone of robust privacy compliance frameworks and an important part of a mature privacy program. PIAs proactively equip companies and institutions with an understanding of data processing and privacy impacts as well as possible remediation. Mandatory in California, Colorado, Connecticut, Texas, the EU and other regions, PIAs are non-negotiable in an increasing number of jurisdictions for high-risk processing activities (potentially harmful impacts to the individual).

This presentation will discuss how to ensure your company has AI policies and plans in place based on industry best practices and applicable regulations. It will take into consideration the developing frameworks and other quickly evolving regulations.

IOPD President R Jason Cronk welcomes you to ask all your burning questions about the Design Process Standard published last year. The need for this standard is a culmination of several factors, and details the components necessary in a design process to incorporate privacy considerations and reduce privacy risks to individuals. The process could be the design of products, services or business processes and spans the lifecycle from ideation to deployment.

What are the risks posed by the use of third-party code in the mobile ecosystem? How can you identify those risks before they become a regulatory headache?

Do your employees unknowingly put personal or sensitive information (like mobile number, email address, social security number, etc.) in emails or PDF documents and accidently expose that information to the wrong people? In a world when employees are using tools like ChatGPT for productivity, do they need help generating synthetic data or learning what data to redact before uploading?