Malaysia PDPA
Bring commercial data handling, DPO decisions and breach reporting into one operating plan.
Data Privacy Act of 2012 (RA 10173), implementing rules and NPC circulars
Map PIC and PIP duties, check registration and rehearse the breach decision with your data protection officer.
Personal information controllers and processors within RA 10173’s scope, including some activities outside the Philippines with a link to the country.
A defensible data inventory, registration decisions, security safeguards and required breach notifications.
Check current NPC circulars for registration and reporting mechanics. Outsourcing duties does not remove the controller’s responsibility for deciding whether to notify.
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.
Philippines Data Privacy Act 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 Set local roles and check registration · DPO + legal [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.
A payroll processor finds unfamiliar requests to export employee records. It preserves the logs and sends known facts and timestamps to the controller. The controller records when it reasonably believed a breach occurred, tests the notification criteria and sends any required notice through the NPC channel.
Compare the neighboring reporting trigger, clock and controller duties for regional operations.
Use Circular 16-03 to confirm the trigger, recipients, permitted delay and information to provide.
Official reference (opens in a new tab)Checklist, instructions and 9 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Set local roles and check registration | DPO + legal | At initiation and on changes | Set a start date | Role map; Processing inventory | Open |
| Build rights and lawful handling processes | Privacy operations + product | Before processing and on requests | Set a start date | Privacy notices; Rights workflow | Open |
| Document safeguards and processor duties | Security + procurement | Before onboarding a processor and ongoing | Set a start date | Impact assessments; Supplier terms; Control evidence | Open |
| Make and record the breach decision | DPO + responsible controller | On awareness of a suspected breach | Set a start date | Breach assessment; Notification record | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify which entity is a PIC or PIP for each process. Assign local owners, check which DPO and processing-system registrations apply and keep portal receipts.
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.
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.
Document legal grounds, notice and sensitive-data handling. Test rights fulfillment across your own systems and processors.
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.
Review high-risk processing, access controls, processor instructions and escalation times. Track approved safeguards and check whether they operate.
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 executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Record data types, unauthorized acquisition and likely serious harm under the notification criteria. Notify the NPC and affected subjects when required and save the receipt.
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.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.