APEC Cross-Border Privacy Rules (CBPR) System
CBPR Program Requirements: Notice

APEC Cross-Border Privacy Rules (CBPR) System CBPR-PR-01: Privacy statement published

The applicant publishes clear and easily accessible statements of the practices and policies governing the personal information it holds.

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 3 controls

APPI · 2 controls

  • APPI-A21 Notice or Public Announcement of the Purpose of Use
  • APPI-A32 Matters Concerning Retained Personal Data to Be Made Accessible

GDPR · 2 controls

  • GDPR-Art.12 Transparent information, communication and modalities for rights
  • GDPR-Art.13 Information to be provided where personal data are collected
  • AUCDR-PS-1 Privacy Safeguard 1 - Open and transparent management of CDR data
  • APP-1 APP 1 - Open and transparent management of personal information

CCPA/CPRA · 1 control

ISO 27701:2019 · 1 control

  • 7.3.2 Determining information for PII principals
  • 161R1-PM-20 Dissemination of Privacy Program Information

SOC 2 · 1 control

  • SOC2-P1.1 P1.1 Privacy notice to data subjects

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 CBPR Program Requirements: Notice

You are reading one control. How much of APEC Cross-Border Privacy Rules (CBPR) System have you already done?

APEC Cross-Border Privacy Rules (CBPR) System CBPR-PR-01 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of APEC Cross-Border Privacy Rules (CBPR) System your existing evidence covers. Hold GDPR and 43 of 59 APEC Cross-Border Privacy Rules (CBPR) System 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 13 it maps to, and the evidence behind each claim, over MCP and REST.