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

CCPA/CPRA CCR 7003: Make disclosures readable, accessible and linked conspicuously

Every disclosure and communication to consumers must use plain, jargon-free language. The required notices must also display well on small screens, be offered in each language the business ordinarily uses with California consumers, and be accessible to people with disabilities (online notices following an accepted standard such as WCAG 2.1). A conspicuous link on a website must look like comparable links on the page in size and colour, and in mobile apps the link must sit in the privacy policy reachable from the app store page and inside the app.

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

What else in your programme already covers this

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

GDPR · 1 control

  • GDPR-Art.12 Transparent information, communication and modalities for rights

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 CCR 7003 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 1 it maps to, and the evidence behind each claim, over MCP and REST.