Meet DPA 2012 obligations with controls you already run
DPA 2012 is the Philippines' Data Privacy Act of 2012 (Republic Act No. 10173), the national law that protects personal information processed by public and private organisations. It is enforced by the National Privacy Commission (NPC), whose Implementing Rules and Regulations (IRR) set out detailed duties on lawful processing, security measures, data subject rights, breach notification, outsourcing and registration.
Is DPA 2012 right for your organisation?
Any personal information controller or processor that processes personal data in the Philippines must comply, and the Act also reaches some organisations outside the country that process data about Philippine citizens or residents. It matters most for outsourcing and BPO providers, banks, healthcare, retailers and SaaS companies serving Filipino customers, and for organisations that meet the NPC's registration criteria.
It is a legal or regulatory requirement for organisations in scope.
- Official name
- Republic Act No. 10173, the Data Privacy Act of 2012
- Approved
- 15 August 2012
- Enforced by
- National Privacy Commission (NPC)
- Implementing rules
- IRR promulgated by the NPC on 24 August 2016
- Applies to
- Personal information controllers and processors, including some outside the Philippines
- Breach notification
- NPC and affected data subjects within 72 hours of knowledge of a qualifying breach
- Criminal penalties
- Imprisonment and fines of up to PHP 5 million per offence under the Act
- Type
- Law (mandatory)
- Region
- Philippines, Asia-Pacific
- In OneClickComply
- Supported today
OneClickComply makes it simple
DPA 2012 is mapped in OneClickComply's control library and available on request, so your existing security and privacy controls can be linked to the IRR's requirements on security measures, breach handling, outsourcing and registration. Evidence you already collect for ISO 27001 or GDPR then counts towards DPA 2012, and our audit team can help you interpret NPC expectations.
Requirements covered
The Act has 45 sections across 9 chapters, and its Implementing Rules and Regulations organise obligations into 14 Rules, with security measures in Rule VI (Sections 25 to 29) and breach notification in Rule IX (Sections 38 to 42).
Manual DPA 2012 vs. OneClickComply
- Reading the Act, the IRR and a stream of NPC circulars to work out what actually applies
- Keeping organisational, physical and technical security measures documented and current
- Chasing screenshots and exports from every system to prove controls work
- Tracking outsourcing agreements and processor obligations across many vendors
- Running separate evidence exercises for DPA 2012, GDPR and ISO 27001
- Requirements mapped to clear controls, with an in-house audit team to answer questions
- Policies generated from your environment and continuous monitoring that flags drift
- Evidence collected automatically from connected tools and admin consoles
- Vendor risk management that keeps processor reviews and contracts in one place
- One control set mapped across frameworks, so evidence collected once is reused
Everything you need for DPA 2012
Map DPA 2012 IRR security measures to controls you already operate
Collect evidence automatically from 13,000+ integrations, including the Companion AI browser agent
Generate privacy and security policies from your real environment with AutoComplete
Track breach response, risks and processor contracts in one risk register and vendor workflow
Fix supported misconfigurations in connected tools with OneClickFix, logged as evidence
Reuse ISO 27001 and GDPR evidence across DPA 2012 through control mapping
Three steps to DPA 2012 compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against DPA 2012 and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates DPA 2012-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
Philippines Data Privacy Act of 2012 requirements
The operative obligations in Sections 17 to 51 of the Implementing Rules and Regulations (Rules IV to XII); definitions, scope, the Commission's powers, penalties and miscellaneous provisions are omitted.
| Reference | Requirement |
|---|---|
| IRR Sec. 17 | General Principles |
| IRR Sec. 18 | Principles of Transparency, Legitimate Purpose and Proportionality |
| IRR Sec. 19 | General Principles in Collection, Processing and Retention |
| IRR Sec. 20 | General Principles for Data Sharing |
| IRR Sec. 21 | Criteria for Lawful Processing of Personal Information |
| IRR Sec. 22 | Sensitive Personal Information and Privileged Information |
| IRR Sec. 23 | Extension of Privileged Communication |
| IRR Sec. 24 | Surveillance of Suspects and Interception of Recording of Communications |
| IRR Sec. 25 | Data Privacy and Security |
| IRR Sec. 26 | Organizational Security Measures |
| IRR Sec. 27 | Physical Security Measures |
| IRR Sec. 28 | Technical Security Measures |
| IRR Sec. 29 | Appropriate Level of Security |
| IRR Sec. 30 | Responsibility of Heads of Agencies |
| IRR Sec. 31 | Requirements Relating to Access by Agency Personnel to Sensitive Personal Information |
| IRR Sec. 32 | Implementation of Security Requirements |
| IRR Sec. 33 | Applicability to Government Contractors |
| IRR Sec. 34 | Rights of the Data Subject |
| IRR Sec. 35 | Transmissibility of Rights of the Data Subject |
| IRR Sec. 36 | Right to Data Portability |
Always check the official DPA 2012 text for the exact wording.
DPA 2012 FAQs
What is the Philippines Data Privacy Act of 2012?
The Data Privacy Act of 2012, Republic Act No. 10173, is the Philippines' main data protection law. It protects personal information processed by government and private organisations, sets principles of transparency, legitimate purpose and proportionality, gives individuals rights over their data, and requires security measures. The National Privacy Commission enforces it, supported by Implementing Rules and Regulations issued in 2016 and further NPC circulars.
Who must comply with RA 10173?
Any natural or juridical person that processes personal information, as a personal information controller or processor, must comply if the processing happens in the Philippines. The Act also applies to some organisations outside the Philippines, for example where they process personal information about Philippine citizens or residents and have links to the country. Certain information, such as some journalistic and government functions, is excluded.
What are the penalties for violating the Data Privacy Act?
The Act sets criminal penalties of imprisonment and fines for offences such as unauthorised processing, access due to negligence, improper disposal, concealment of security breaches and unauthorised disclosure. Fines reach up to PHP 5 million per offence, and the maximum penalty applies to large-scale violations. The NPC can also issue compliance and cease and desist orders, including bans on processing.
How quickly must a data breach be reported under DPA 2012?
Within 72 hours. Under the IRR and NPC rules, the personal information controller must notify the National Privacy Commission and affected data subjects within 72 hours of becoming aware of a breach involving sensitive personal information or information that could enable identity fraud, where it is likely to cause a real risk of serious harm. Notification may be delayed only in limited circumstances.
Do organisations have to register with the National Privacy Commission?
Some do. Registration of data processing systems and a Data Protection Officer is required for controllers and processors that meet the NPC's criteria, which relate to headcount, the volume of sensitive personal information processed and the risk of the processing. The thresholds are set by NPC circulars that have been revised over time, so check the current circular before deciding.
How does the Data Privacy Act compare with GDPR?
They share many ideas. Both rest on lawful processing, purpose limitation and proportionality, give individuals rights including access, correction, erasure and data portability, require security measures and set breach notification duties. GDPR is broader and has its own fine structure, but a programme built for GDPR covers much of DPA 2012, leaving gaps such as NPC registration and Philippine-specific breach procedures.
Does ISO 27001 help with DPA 2012 compliance?
Yes, partly. ISO 27001 controls support the organisational, physical and technical security measures required by Rule VI of the IRR, along with incident management and supplier security. It does not cover privacy-specific duties such as lawful bases, data subject rights, NPC registration or breach notification to the Commission, so those need separate controls and documentation.
Does OneClickComply support the Philippines Data Privacy Act?
DPA 2012 is mapped in OneClickComply's control library and is available on request. Once enabled, your existing controls and evidence for frameworks such as ISO 27001 and GDPR are linked to the IRR's requirements, and our audit team can advise on NPC expectations. OneClickComply does not certify compliance, which remains your organisation's responsibility under the Act.
Related standards
All standards- Japan Act on the Protection of Personal Information (APPI)Law · Asia-Pacific
- New Zealand Privacy Act 2020Law · Asia-Pacific
- China Personal Information Protection Law (PIPL)Law · Asia-Pacific
- India Digital Personal Data Protection Act 2023Law · Asia-Pacific
- China Cybersecurity LawLaw · Asia-Pacific
- China Data Security LawLaw · Asia-Pacific
- South Korea Personal Information Protection Act (PIPA)Law · Asia-Pacific
- Hong Kong Personal Data (Privacy) OrdinanceLaw · Asia-Pacific
Get DPA 2012 ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.