Business Identity
Name and contact details for the business and its designated privacy contact or agent, enabling consumers to submit requests or ask questions about data handling.
A clear CPRA Compliance Notice fulfills statutory transparency obligations, reduces regulatory risk, and documents consumer choices. It helps operationalize rights such as opt-out of sharing or targeted advertising and supports consistent handling of requests under California law and agency enforcement.
Organizations and teams that interact with California consumers typically draft and maintain CPRA notices.
Responsibility commonly spans privacy, legal, product, and vendor management functions to ensure notices remain current and accurate.
Name and contact details for the business and its designated privacy contact or agent, enabling consumers to submit requests or ask questions about data handling.
Clear listing of personal information categories collected (identifiers, commercial info, internet activity, sensitive data when applicable), avoiding technical jargon while covering real processing activities.
Specific purposes for processing (service delivery, analytics, advertising, fraud prevention), mapped to data categories so consumers understand why data is collected.
Explicitly state rights under CPRA — access, deletion, correction, limits on use of sensitive data, and the right to opt out of sharing or targeted advertising.
Describe retention periods or criteria for determining retention and explain data minimization practices; include how retention aligns with business needs and legal obligations.
Identify categories of third parties with whom data is shared, whether data is sold or shared for cross-context behavioral advertising, and links to opt-out mechanisms.
| Setting | Recommendation |
|---|---|
| Public Posting | HTML page + downloadable PDF for records |
| Authentication | User email verification; consider MFA for sensitive requests |
| Request Intake | Web form with automated ticket creation |
| Audit Logging | Store timestamps, IPs, and correspondence for proof |
Notices and request mechanisms should be published where consumers expect them and integrated with secure intake systems.
Use systems that produce immutable audit records and retention logs; platforms with SOC 2, AES-256 storage, and TLS transport support regulatory defensibility.
45 days to respond to consumer requests, with a 45-day extension permitted in complex cases.
Notify consumer of extension and reason within the original response window.
Implement opt-out preferences promptly; technical propagation should be near real-time when feasible.
Maintain request records and responses for at least 24 months for audit purposes.
Update public notice whenever processing changes; retain prior versions for evidence.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |