CCPA/CPRA
Requests to know, delete and correct – CCPA/CPRA

CCPA/CPRA 1798.130(a)(1): Offer designated methods for requests to know, delete and correct

A business must provide at least two designated channels for access, deletion and correction requests, one being a toll-free number, plus its website where it has one. A business operating only online with a direct consumer relationship need offer only an email address. Under section 7020, the methods must reflect how the business mainly interacts with consumers (including an in-person method where it deals with them face to face), deletion may use a two-step confirmation online, requests to know must allow asking for data older than 12 months where it is held, and a request made through the wrong channel must be handled as if properly made or answered with directions to a proper method.

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-055 Provide two or more secure request methods, a website mechanism, and no forced account creation

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 Requests to know, delete and correct – CCPA/CPRA

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

CCPA/CPRA 1798.130(a)(1) 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.