Applies from 1 January 2027 to ADMT already in use for significant decisions, and from first use for later deployments (7200). Before collecting the data to be processed by the ADMT, or before repurposing data already held, the business must give a prominent pre-use notice in its usual channel stating the specific purpose, the right to opt out and how (or, where an exception applies, the appeal route or the exception relied on), the right to access ADMT information, the bar on retaliation, and a plain explanation of how the ADMT uses personal information, what output it produces and how the output feeds the decision, and the alternative process for those who opt out. Trade secrets and security-sensitive details may be withheld, and one notice may cover several uses.
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 7220 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.