APPI
APPI: Rights of Identifiable Persons (Articles 32 to 39)

APPI APPI-A37: Procedure for Receiving Requests

Where a procedure is prescribed for receiving requests, keep it within reasonable bounds, obtain only the information necessary to identify the retained personal data, and have regard to the convenience of the identifiable person.

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

What else in your programme already covers this

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

CCPA/CPRA · 2 controls

GDPR · 2 controls

  • GDPR-Art.11 Processing which does not require identification
  • GDPR-Art.12 Transparent information, communication and modalities for rights
  • APP-12 APP 12 - Access to personal information
  • CCM-DSP-11 Personal Data Access, Reversal, Rectification and Deletion

ISO 27701:2019 · 1 control

SOC 2 · 1 control

  • SOC2-P8.1 P8.1 Inquiries, complaints, disputes and compliance monitoring

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 APPI: Rights of Identifiable Persons (Articles 32 to 39)

You are reading one control. How much of APPI have you already done?

APPI APPI-A37 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of APPI your existing evidence covers. Hold APEC Cross-Border Privacy Rules (CBPR) System and 16 of 30 APPI 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 APEC Cross-Border Privacy Rules (CBPR) System pair alone.

Query this from an agent

The graph holds this control, the 11 it maps to, and the evidence behind each claim, over MCP and REST.