Philippines Data Privacy Act
Map PIC and PIP duties, check registration and rehearse the breach decision with your data protection officer.
Law No. 27 of 2022 on Personal Data Protection
Document Indonesian processing roles, transfer decisions and the timing for written breach notices.
Controllers and processors handling personal data within the law’s territorial scope, including specified effects outside Indonesia.
An attributable processing record, safeguards, rights handling and decisions on external disclosures and breach notices.
Confirm the current implementing rules and reporting channel for your entity and sector before an incident. Keep controller and processor responsibilities explicit.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
Indonesia PDP Law kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Identify processing roles and purposes · Privacy lead + local counsel [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
An Indonesian marketplace moves fraud analysis to an offshore service. The project owner maps the destination and data types. Legal documents the applicable transfer conditions, and security verifies that access is limited to the purposes recorded in the assessment.
Check a separate jurisdiction if the same service also handles Singapore data.
Confirm the start of the clock, affected subjects, authority and content against the current law and implementing rules.
Official reference (opens in a new tab)Checklist, instructions and 8 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Identify processing roles and purposes | Privacy lead + local counsel | Before processing | Set a start date | Processing inventory; Role map | Open |
| Put notices and rights into operation | Product + privacy operations | Before collection and on requests | Set a start date | Privacy notices; Rights procedure | Open |
| Review processing risk and transfers | Risk owner + legal | Before high-risk activities or offshore access | Set a start date | Impact assessments; Transfer register | Open |
| Exercise written breach notification | Security + accountable controller | At a personal data protection failure | Set a start date | Incident log; Reporting templates | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Map legal entity, personal data categories and purposes. Decide which party controls processing and which handles it on instructions. Check DPO and assessment criteria.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Document legal grounds, write notices, record consent where used and test access, correction, deletion and other applicable requests.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Fictional details. Use the same fields with evidence from your work.
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Document required impact assessments. Check the applicable transfer hierarchy and safeguards, including where support staff have remote access.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
The register shows actual access paths, the basis for each transfer and a clear release decision.
Share the decision with supplier and access owners so they can implement the conditions before data is available.
Record awareness, scope and mitigation. Prepare notice to the subjects and authority under Article 46 and check any requirement to inform the public.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.