We’re excited to share our latest white paper outlining the CPRA requirements and compliance considerations for software producers. This document provides a thorough understanding of this critical legislation.
For software producers, the CPRA is set to introduce a new wave of data privacy regulations and compliance requirements that can be daunting to keep up with. Osterman Research suggests that compliance will be difficult without the right data discipline, and currently 54% of organizations do not have a real or near real-time data map. Relying on manual point-in-time software developer or engineer interviews to identify and map this data results in a bottleneck to the software development process and an incomplete and out-of-date perspective. However, with the right approach to data mapping and governance, you can ensure that you are compliant and prepared to respond quickly to data subject access requests. Privya’s automated code scanning and data mapping capabilities provide you with the visibility you need to understand your data processing practices, enabling you to protect your data and remain compliant with the CPRA.
Gain an understanding of:
- The history of the CPRA and how it differs from previous California privacy laws such as the California Consumer Privacy Act (CCPA).
- The changes and implications of the CPRA, to be better prepared to protect data and remain compliant.
- How to comply with privacy regulations involving what PII, PHI, and SPI is collected and/or processed during usage of their applications; where this data is both processed and stored; which third parties have access to the data; what is the purpose of keeping/tracking the data; how long each type of data should be retained; do geographical restrictions exist for either the processing or storage of each data type.
- Which application programming interfaces (APIs) can send or receive this data to/from other application services; and which algorithms/machine learning models leverage personal data.
Download the white paper here.
