Organisations that move personal data across Asia Pacific and North America often have no single contract or adequacy decision that works in every jurisdiction they touch. The Cross-Border Privacy Rules (CBPR) systems offer a different route: an annual, third-party certification of a company's privacy programme that participating governments have agreed to recognise and enforce. Since 2 June 2025 there are two parallel versions, the original APEC CBPR and PRP systems and the Global CBPR and Global PRP systems run by the Global CBPR Forum, and the Global programme requirements change on 1 April 2027. This guide explains how the systems work, who certifies, what the requirements demand of security and privacy teams, how CBPR compares with Binding Corporate Rules and other transfer tools, and how to prepare for certification and keep it. It is written for privacy, security and third-party risk teams. Status is as stated on the Forum and APEC websites, checked November 2026.
Key takeaways
- Two systems, one origin. The Global CBPR and Global PRP systems went live on 2 June 2025, based on the APEC CBPR and PRP systems, and the Forum says the two will diverge over time.
- Controllers and processors certify separately. CBPR covers controllers; PRP covers processors and their handling of a controller's data, with flow-down duties to subprocessors.
- Certification lasts one year. The Forum states that Global CBPR and Global PRP certifications are valid for a year, so evidence collection is a yearly cycle, not a one-off project.
- The requirements grow on 1 April 2027. The Global CBPR programme requirements move from 50 to 57, adding a Preventing Harm section with breach notification to individuals, children's data and risk assessment.
- It is not a GDPR transfer tool. CBPR helps where a member jurisdiction's law recognises it, such as Singapore and Japan, but EU and UK GDPR transfers still need SCCs, BCRs, adequacy or another mechanism those laws provide.
What CBPR is and how the two systems relate
APEC describes CBPR as a government-backed data privacy certification that companies can join. It implements the APEC Privacy Framework, endorsed by APEC Leaders in 2005 and updated in 2015, and the CBPR system itself was endorsed by APEC Leaders in 2011. Participating economies must show that the programme requirements are legally enforceable against certified companies before they join.
The Global CBPR Forum was established in 2022, through a declaration published on 21 April 2022, by the nine jurisdictions then taking part in APEC CBPR: Australia, Canada, Japan, the Republic of Korea, Mexico, the Philippines, Singapore, Chinese Taipei and the United States. Unlike APEC, the Forum is open to jurisdictions outside the Asia Pacific region. METI and Japan's Personal Information Protection Commission announced that the Global CBPR system launched on 2 June 2025, the day Accountability Agents began granting certifications.
| Aspect | APEC CBPR and PRP | Global CBPR and Global PRP |
|---|---|---|
| Administered by | APEC | Global CBPR Forum |
| Basis | APEC Privacy Framework (2005, updated 2015) | Global CBPR Declaration (2022) and Global CBPR Framework |
| Participating jurisdictions | Nine APEC economies listed by APEC | Ten members and four associates listed by the Forum (November 2026) |
| Programme requirements (CBPR) | 50 | 50 until 31 March 2027; 57 from 1 April 2027 |
| Programme requirements (PRP) | Processor requirements under APEC PRP | 18, in Security Safeguards and Accountability Measures sections |
| Enforcement cooperation | Cross-border cooperation between regulatory authorities | Global Cooperation Arrangement for Privacy Enforcement (Global CAPE), October 2023 |
| Dual participation | Until 1 April 2027 the Global and APEC CBPR requirements are identical and companies may take part in both | |
Forum members listed in November 2026 are Australia, Canada, the Dubai International Financial Centre, Japan, the Republic of Korea, Mexico, the Philippines, Singapore, Chinese Taipei and the United States. Associates are Bermuda, Mauritius, Nigeria (joined September 2025) and the United Kingdom. Associate status signals interest, not recognition of the certification in that jurisdiction's transfer law, so check each law before relying on it. See the Global Privacy Regulatory Map.
CBPR versus PRP: which certification applies
- Global CBPR: for controllers, the organisations that control the collection, holding, processing, use, disclosure or transfer of personal information. It certifies the whole privacy programme against the CBPR requirements.
- Global PRP: for processors that handle data on behalf of controllers. The Forum describes it as a way to show they can implement a controller's data protection requirements. A cloud provider, payroll bureau or managed service provider serving many controllers is the typical candidate.
- Both: a SaaS company that is a controller for its own customer and staff data and a processor for customer content can hold both marks. The Forum allows certified companies to display either or both marks.
What the 18 PRP requirements expect of a processor
| PRP requirement (question) | What an assessor looks for |
|---|---|
| 1 to 2: security policy and safeguards | A written security policy covering controller data, and physical, technical and administrative safeguards such as access control, encryption, boundary protection, audit logging and monitoring, reviewed periodically |
| 4 to 5: detection and testing | Capability to detect, prevent and respond to attacks and security failures, and safeguard testing at appropriate intervals |
| 6: breach notice | A process to notify the controller of privacy or security breaches |
| 7 and 10: return, deletion, correction | Secure return or disposal at the controller's instruction or end of contract; deletion and correction on request |
| 9 and 11: instructions | Processing limited to the controller's purposes and measures that keep staff to its instructions |
| 14: government access | Notice to controllers of subpoenas, warrants or orders requiring disclosure, unless prohibited by law, with staff trained on it |
| 15 to 17: subprocessors | Notice to controllers when subprocessors are engaged, and binding mechanisms requiring subprocessors to follow instructions, restrict onward subprocessing, provide evidence and accept spot checks |
| 12 and 18: accountability | A named person responsible for PRP compliance and staff training on client instructions |
The CBPR programme requirements in practice
The current Global CBPR requirements (valid until 31 March 2027) are organised under eight principles: Notice (questions 1 to 4), Collection Limitation (5 to 7), Uses of Personal Information (8 to 13), Choice (14 to 20), Integrity of Personal Information (21 to 25), Security Safeguards (26 to 35), Access and Correction (36 to 38) and Accountability (39 to 50). APEC says governments may add requirements, but certified companies must still meet the full baseline.
Security Safeguards: the section security teams own
- Policy and safeguards (Q26 and Q27): a written information security policy, and safeguards including access control, encryption, boundary protection, audit logging and monitoring. Map these to your existing control set rather than writing new ones.
- People (Q29 and Q30): security training and oversight for staff, and safeguards covering systems design and disposal, attack detection and response, and physical security.
- Disposal and response (Q31 and Q32): a secure disposal policy and measures to detect, prevent and respond to attacks.
- Testing and assurance (Q33 and Q34): safeguard testing at appropriate intervals, plus third-party certifications or risk assessments. An ISO/IEC 27001 certificate or SOC 2 report is useful evidence here, though it does not replace the CBPR assessment.
- Processor security (Q35): processors must run security programmes proportionate to data sensitivity, notify you promptly of breaches and fix the cause.
Accountability: vendor due diligence written into the requirements
Questions 46 to 50 turn third-party risk management into a certification test. You must perform due diligence on processors and agents (Q46), use contract terms that can require them to follow your privacy practices, restrict subcontracting without consent, be certified and notify you of breaches (Q47), obtain self-assessments (Q48), and carry out spot checks or monitoring (Q49). Where due diligence is impractical you must explain why and describe the other protections in place (Q50). See the Third-Party Risk Management Guide.
What changes on 1 April 2027
The Forum announced on 23 March 2026 that the Global CBPR requirements grow from 50 to 57, with three existing requirements updated. From 1 April 2027 first-time applicants and recertifying companies must certify against the new set at their recertification date.
| Area | New or updated requirement (2027 numbering) | Preparation |
|---|---|---|
| Preventing Harm (new section) | Accountability for sensitive data (PR 1) and children's data (PR 2 and 3); risk assessment and mitigation (PR 4); notifying affected individuals of breaches (PR 5) | Classify sensitive and children's data, link it to a DPIA or risk method, and add individual notification to the incident plan |
| Choice | Choice on direct marketing (PR 22); recording choices (PR 26); withdrawal of consent (PR 27) | Consent records that are queryable, with timestamps, and a working withdrawal path |
| Accountability | Records of processing activities (PR 46); suitably qualified programme staff (PR 47) | A maintained ROPA and role descriptions with training evidence for privacy staff |
The Forum publishes both versions and a marked-up comparison on its documents page. A company certified in 2026 should run a gap assessment against the 2027 set at least six months before its renewal date. See the Data Mapping and ROPA Guide.
Accountability Agents and the certification process
Certification is available only to companies that have a Forum-recognised Accountability Agent operating in their jurisdiction. APEC describes Accountability Agents as independent public or private sector bodies that certify companies, monitor them, receive and investigate complaints and resolve disputes between consumers and companies.
| Accountability Agent | Jurisdiction | Systems |
|---|---|---|
| BBB National Programs | United States | Global CBPR, Global PRP |
| Infocomm Media Development Authority (IMDA) | Singapore | Global CBPR, Global PRP |
| Institute for Information Industry (III) | Chinese Taipei | Global CBPR |
| Japan Institute for Promotion of Digital Economy and Community (JIPDEC) | Japan | Global CBPR |
| Korea Internet Security Agency (KISA) | Republic of Korea | Global CBPR |
| NCC Group Security Services, Inc. | United States | Global CBPR, Global PRP |
| Schellman | United States | Global CBPR, Global PRP |
| TRUSTe | United States | Global CBPR, Global PRP |
| VeraSafe | United States | Global CBPR, Global PRP |
Agents are listed alphabetically from the Forum's Accountability Agents page as of November 2026; the list is a fact, not a recommendation. Confirm the current list before you start, because agents are added over time.
Step by step
- Confirm eligibility: check that a recognised agent operates where your headquarters sits and that it certifies the system you need (some certify CBPR only).
- Scope the certification: decide which legal entities, brands and data flows are in scope. Customers read the directory entry, so a narrow scope that excludes the product they buy helps no one.
- Complete the intake questionnaire: the Forum publishes separate CBPR and PRP intake questionnaires. It is a self-assessment of policies, practices and processes; answer with evidence references, not prose.
- Remediate with the agent: the agent reviews the questionnaire and works with you until every requirement is met. Expect questions on processor contracts, consent records and security testing.
- Certification and listing: once compliance is verified the agent issues the seal and the certification appears in the Forum's compliance directory.
- Operate and renew: certification is valid for a year. Keep a running evidence file so recertification is a refresh, and plan the 2027 requirement change into the next cycle.
Where CBPR works as a transfer mechanism
CBPR does not replace domestic law: the Forum states that certified organisations must still comply with the privacy laws wherever they operate. Its value as a transfer tool depends on each jurisdiction's law recognising it.
- Singapore: according to a 2020 Herbert Smith Freehills note, since the June 2020 revision of the Personal Data Protection Regulations a recipient holding a valid CBPR certification (as an organisation) or PRP certification (as a data intermediary) can satisfy the PDPA's Transfer Limitation Obligation; the PDPC now publishes a sample clause for transfers to APEC and Global CBPR and PRP certified organisations, so check its current guidance before relying on this. IMDA is itself an Accountability Agent. See the Singapore PDPA Guide.
- Japan: APEC states that Japan recognises the CBPR system for cross-border transfers under its domestic law, and JIPDEC began accepting Global CBPR applications on 2 June 2025. See the Japan APPI Guide.
- North America: APEC notes that CBPR is recognised in the trade agreement between Canada, Mexico and the United States. Recognition in a trade agreement is not the same as a transfer rule in domestic privacy law; check the Canada PIPEDA and Bill C-27 Guide and the Mexico Data Protection Law Guide.
- EU and UK: CBPR is not one of the GDPR's Article 46 transfer safeguards. The UK is a Forum associate, but UK GDPR transfers still rely on adequacy regulations, the UK transfer addendum or IDTA, BCRs or a listed exception. See the International Data Transfers Map.
CBPR compared with BCRs, SCCs and other tools
| Tool | Who approves | Scope | Renewal | Best fit |
|---|---|---|---|---|
| Global or APEC CBPR | Recognised Accountability Agent | A company's whole controller programme, recognised where member law accepts it | Annual | Groups and SaaS firms with heavy Asia Pacific and North American flows |
| Global or APEC PRP | Recognised Accountability Agent | Processor handling of controller data | Annual | Service providers that want one credential for many controller customers |
| Binding Corporate Rules | Lead EU supervisory authority with EDPB opinion (GDPR Art. 47) | Intra-group transfers from the EU | Updated as the group changes; no annual recertification | Multinational groups with large, stable intra-group EU exports |
| Standard Contractual Clauses | Adopted by the European Commission; signed by the parties | Each exporter and importer relationship, with a transfer impact assessment | Reviewed when laws or flows change | Any EU or UK transfer without adequacy |
| Adequacy or framework decision | Government or regulator of the exporting jurisdiction | All transfers to the covered destination or certified recipient | Periodic review by the issuing authority | Flows to adequate destinations, such as EU to Japan |
Decision guidance: choose CBPR when most of your restricted flows start in jurisdictions whose law recognises it, or when customers in those markets ask for it in procurement. Choose BCRs when the main problem is intra-group export out of the EU. Most multinationals end up with a layered approach: SCCs or BCRs for European exports, CBPR or PRP for Asia Pacific, and adequacy where it exists. A small company with a single market rarely needs CBPR unless a key customer requires it; a processor selling to Singaporean or Japanese enterprises gets a reusable credential from PRP. See the Binding Corporate Rules (BCRs) Guide and the Standard Contractual Clauses (SCCs) Guide.
Where identity and access fit
Several requirements are access control questions in disguise. Access and Correction (Q36 to 38) needs a reliable way to find a person's records across systems, which depends on a clean identity inventory and data map. Security Safeguards Q27 names access control and audit logging, and assessors increasingly ask how service accounts, API keys and integration tokens that read personal data are owned and reviewed. Processor subcontracting (PRP Q15 to 17) is often realised as OAuth grants or API keys issued to a subprocessor, so the subprocessor register and the non-human identity inventory should agree. See the Identity Data Privacy and Consent Guide.
Measuring a CBPR programme
- Evidence currency: percentage of programme requirements with evidence refreshed within the last 12 months; target 100% by the renewal date.
- Processor coverage: percentage of processors handling in-scope data with completed due diligence and contract terms meeting Q46 and Q47.
- Subprocessor notice lag: days between engaging a subprocessor and notifying controllers (processors, PRP Q15).
- Request handling: median days to complete access and correction requests, and the share closed within your stated deadline.
- 2027 readiness: number of the seven new requirements with an owner and evidence plan, tracked monthly until certification against the new set.
- Complaints: count of complaints raised through the Accountability Agent and time to resolution.
Framework mapping
| CBPR area | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | ISO/IEC 27001:2022 Annex A |
|---|---|---|---|
| Legal and transfer obligations | GV.OC-03 | PT-2 | A.5.31, A.5.34 |
| Notice | GV.OC-03 | PT-5 | A.5.34 |
| Security Safeguards | GV.PO-01, PR.DS-01 | AU-2 | A.5.15, A.8.15, A.8.24 |
| Processor due diligence and contracts | GV.SC-05, GV.SC-07 | SA-9, SR-6 | A.5.19, A.5.20 |
| Breach notification (2027 PR 5, PRP Q6) | RS.CO-02 | IR-6 | A.5.26 |
| Records of processing (2027 PR 46) | ID.AM-07 | PM-5(1) | A.5.9, A.5.34 |
Common failure patterns
- Treating the seal as a GDPR answer: marketing claims that CBPR "covers international transfers" lead teams to skip SCCs for European exports. It does not; keep each transfer tool tied to the law that recognises it.
- Scope that misses the product: certifying a holding company or one brand while customers buy from another entity leaves procurement questionnaires unanswered.
- Processor terms that stop at the first tier: PRP Q16 and Q17 require flow-down to subprocessors, including evidence and spot checks. Contracts signed years ago often lack these.
- Annual cycle treated as a project: evidence is gathered in a rush before renewal, with stale screenshots and policies that no longer match practice.
- Ignoring the 2027 change: companies certified in 2026 find at renewal that individual breach notification, consent withdrawal and a ROPA are now requirements, with no time to build them.
- Consent records that cannot be queried: Choice requirements need proof of what each person chose and when; a mailing tool's opt-out flag alone rarely satisfies an assessor.
Practitioner checklist
- Map each restricted data flow to the jurisdiction's transfer rule and note where CBPR or PRP is recognised.
- Decide whether you need CBPR, PRP or both, and confirm a recognised Accountability Agent covers your headquarters and system.
- Download the current and 2027 programme requirements and the intake questionnaire from the Forum's documents page.
- Map Security Safeguards Q26 to Q35 to existing controls and reuse ISO/IEC 27001 or SOC 2 evidence.
- Update processor and subprocessor contracts for due diligence, instruction, breach notice, certification and spot checks.
- Build a ROPA, a consent record store and an individual breach notification step before your first renewal after 1 April 2027.
- Reconcile the subprocessor register with the inventory of API keys and service accounts that reach personal data.
- Keep a living evidence file and calendar the annual recertification three months ahead.
Standards and references
- Global CBPR Forum: Certification FAQs
- Global CBPR Forum: Global CBPR System Program Requirements
- Global CBPR Forum: Global PRP System Program Requirements
- Global CBPR Forum: Updates to the Global Cross-Border Privacy Rules System
- Global CBPR Forum: Accountability Agents
- APEC: What is the Cross-Border Privacy Rules System?
- METI: Launch of the Global CBPR System
- Herbert Smith Freehills: Singapore recognises regional certification for overseas transfers
- PDPC: Sample Clause for Data Transfers to APEC and Global CBPR and PRP Certified Organisations
Related NHI Mgmt Group resources: International Data Transfers Map · Global Privacy Regulatory Map · Singapore PDPA Guide · Binding Corporate Rules (BCRs) Guide · Privacy Management Standards Compared. This guide summarises the APEC and Global CBPR and PRP systems and is not legal advice.