CCPA/CPRA
Privacy policy, notices and choice design – CCPA/CPRA

CCPA/CPRA 1798.130(a)(5): Disclose rights and data practices in the privacy policy, refreshed yearly

The online privacy policy, and any California-specific rights statement (or the website, where no policy exists), must set out the consumer rights under sections 1798.100 to 1798.125 with at least two ways to submit requests; the categories of personal information collected in the previous 12 months, their sources, the business or commercial purposes and the categories of third parties receiving it; and two separate lists of categories sold or shared and categories disclosed for business purposes during the previous 12 months, or a statement that none were. The content must be updated at least every 12 months. Categories must use the statutory terms in section 1798.140 (1798.130(c)).

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • S541-102 Publish a clear privacy notice and disclose sale and targeted advertising with the opt-out route

Virginia CDPA · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Privacy policy, notices and choice design – CCPA/CPRA

You are reading one control. How much of CCPA/CPRA have you already done?

CCPA/CPRA 1798.130(a)(5) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CCPA/CPRA your existing evidence covers. Hold GDPR and 17 of 89 CCPA/CPRA controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the GDPR pair alone.

Query this from an agent

The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.