The privacy policy must give a full account of online and offline practices, be printable, follow the plain-language and accessibility rules of section 7003, and be reachable from a conspicuous link containing the word privacy on the homepage and in a mobile app's settings and download page. Beyond the statutory lists it must state whether the business knowingly sells or shares data of consumers under 16, whether it uses sensitive data beyond the permitted purposes, each consumer right (including the ADMT opt-out and access rights where Article 11 applies), how to exercise them, how identity is verified, how opt-out preference signals are honoured, how authorised agents may act, a contact point, the date of last update and, for businesses covered by section 7102, the annual metrics or a link to them.
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.
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.
CCPA/CPRA CCR 7011 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.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.