Deleting means permanently erasing the data from active systems (backups may wait until next accessed or used), deidentifying it, or aggregating it, and notifying service providers, contractors and third parties as the statute requires. The business tells the consumer whether it complied and that a record of the request is kept. Where it refuses in whole or part, it explains the legal basis, deletes the rest, and if it sells or shares data it asks whether the consumer wants to opt out. It may offer deletion of selected portions only if a single option to delete everything is also offered.
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 7022 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.