Any company that collects names, contact details, payroll records, or customer information in the Philippines is handling personal data, and that brings it under the country’s privacy regime. For foreign founders, this is one of the easier compliance areas to overlook and one of the more visible ones to get wrong, because clients and regulators both pay attention to it.
The law and the regulator
The governing law is the Data Privacy Act of 2012 (Republic Act 10173), often shortened to the DPA. It is enforced by the National Privacy Commission (NPC), an independent body with the power to investigate complaints, issue compliance orders, and impose penalties. The DPA applies broadly: it covers organisations that process the personal data of individuals in the Philippines, and it reaches foreign-owned companies operating here just as it reaches local ones. Setting up your entity is only the first step. Privacy compliance sits alongside the other obligations you take on once you are operating, as covered in our guide to how to set up a company in the Philippines.
Who has to register with the NPC
The NPC’s registration rules are in NPC Circular 2022-04, dated 5 December 2022. Under its Section 5, a personal information controller or processor must register its data processing systems and its DPO when it:
- employs 250 or more persons;
- processes sensitive personal information of 1,000 or more individuals; or
- processes personal data that is likely to pose a risk to the rights and freedoms of data subjects; or
- carries out automated decision-making or profiling, which requires registration in all cases (Section 5(A)).
Sensitive personal information is defined in Section 3(l) of the DPA. It covers, among other things, health and education data, race and religious or political affiliations, and government-issued identifiers such as SSS numbers and tax returns. A company below these thresholds may register voluntarily. Otherwise it submits a sworn declaration (Section 6), and it still has to meet every other DPA obligation.
For a new data processing system or a first DPO appointment, registration is due within 20 days from the system’s commencement or the appointment’s effectivity date (Section 7). Systems that already existed when the circular took effect had 180 days to register (Section 39), and that period has passed.
Read Section 5 of the circular before deciding that a company is exempt. A company close to a threshold can register voluntarily under Section 6.
Government agencies have a separate DPO rule. Section 10 of the circular says a Government Agency “is required to designate and register a DPO,” with a rank tied to the rank of the agency head. The duty has no headcount test. “Government Agency” is defined in Section 2(F) and covers national agencies, local government units, government-owned and controlled corporations, government financial institutions, and state colleges and universities. The Section 6 sworn declaration covers a PIC or PIP outside mandatory registration. It does not mention the DPO, so it does not replace the Section 10 registration. Section 5 has no separate government rule for processing systems, so the same thresholds apply to a government agency’s systems.
PIC vs PIP: which role you play
The DPA uses two roles for the organisations that handle personal data, and one company can hold both.
- Personal information controller (PIC). A person or organisation that controls the collection, holding, processing, or use of personal information. This includes one that instructs another party to process personal information on its behalf. A party that only performs functions as instructed by another is excluded from this definition (Section 3(h)).
- Personal information processor (PIP). A natural or juridical person qualified to act as such, to whom a PIC may outsource the processing of personal data (Section 3(i)).
What each role must do, under the statute:
- The PIC is accountable for personal information under its control, including information it has transferred to a third party for processing. It must use contracts or other reasonable means to give a comparable level of protection while the third party processes the data (Section 21(a)).
- The PIC must designate one or more individuals accountable for its compliance, and make their identity known to any data subject who asks (Section 21(b)).
- The PIC must implement reasonable and appropriate organisational, physical, and technical security measures. It must also make sure third parties that process personal information for it apply the same measures (Section 20(a) and 20(d)).
Practical application for foreign-owned operators:
- A BPO is usually a PIP for its clients’ customer data. Call recordings and account details are processed on the client’s instructions, so the client is the PIC. The client stays accountable under Section 21, which is why clients ask for contract terms, security evidence, and breach cooperation before they sign.
- The same BPO is a PIC for its own staff data. Payroll records, government ID numbers, leave records, and medical certificates are the BPO’s own records, so the BPO needs its own privacy notice, its own security measures, and its own accountable DPO.
Appointing a Data Protection Officer
Every PIC must designate someone accountable for its DPA compliance (Section 21(b)). That person is the Data Protection Officer (DPO) in practice. The DPO monitors practices, handles data-subject requests, and acts as the contact point for the NPC. The DPO should have enough authority and knowledge of the law to do the job properly. Where the NPC thresholds apply, the DPO must also be registered with the Commission. For employers, the DPO’s remit overlaps heavily with how you collect and store staff records, which is why privacy planning belongs in your broader approach to hiring employees in the Philippines.
The core compliance obligations
Beyond registration and the DPO, the DPA imposes ongoing duties on every organisation that processes personal data:
- Lawful basis and consent. Processing is allowed only when one of the conditions in Section 12 applies. Consent is one of them, but not the only one. For sensitive personal information, Section 13 sets stricter rules, and consent must be specific to the purpose before processing starts.
- Privacy notice. Data subjects must be given a description of the personal information, its purposes, the scope and method of processing, the recipients, the identity and contact details of the controller, the retention period, and their rights, before the data enters the system or at the next practical opportunity (Section 16(b)).
- Security measures. The law requires reasonable and appropriate organisational, physical, and technical safeguards, a security policy, regular monitoring for breaches, and a process for responding to incidents (Section 20). The measures should match the nature of the data and the risks of the processing.
- Breach notification and reporting. Section 20(f) requires prompt notice to the NPC and affected data subjects when sensitive personal information, or information that could enable identity fraud, has been acquired by an unauthorised person and the acquisition is likely to cause a real risk of serious harm. The timing and reporting steps are set out in the NPC’s breach rules, covered below.
These obligations are continuous, not one-off, and they sit naturally within your wider corporate compliance calendar alongside tax, reporting, and regulatory filings.
Breach notification and the annual security incident report
Two reporting duties apply to every PIC and PIP that handles personal data.
Notifiable breaches. When a breach meets the Section 20(f) test, the NPC must be notified within 72 hours of knowledge or reasonable belief that the breach occurred (NPC Circular 16-03, Section 17(A)). The full report is due within five days (Section 17(C)). Affected data subjects must also be notified within 72 hours (Section 18(A)). Plan your incident response around that clock from the start, not after the first breach. NPC notification may be delayed only as far as needed to determine the scope of the breach, prevent further disclosures, or restore the integrity of the system (Section 17(B)). NPC Advisory No. 2026-02 (11 May 2026) limits how a PIC can combine requests for exemption, postponement and alternative notice, and states that the Commission’s inaction is not approval.
Annual security incident report. Under Section 22 of NPC Circular 16-03, all security incidents and breaches must be documented, including those that do not need notification, and a summary of all reports must be submitted to the NPC each year. For the 2025 reporting year, the report was due 31 March 2026. NPC Advisory No. 2026-03 (8 September 2026) reopened the filing period until 10 November 2026. Submissions must go through the DBNMS online platform, and a report showing zero incidents is required when none occurred (Sections 5 and 6 of the advisory).
Check the NPC’s advisories before you set your filing date, because the deadline changes from year to year. Add the ASIR to your yearly calendar alongside your other annual compliance filings.
Which circular applies. NPC Circular 2023-06 on the security of personal data is dated 1 December 2023. It gives a PIC twelve months from its effectivity to comply (Section 37), and it requires a PIC to follow the NPC’s breach management issuance when a breach occurs (Section 33). The breach timing and reporting rules above therefore come from NPC Circular 16-03. Check privacy.gov.ph for any later breach circular before you file.
Why this matters most for foreign-owned BPOs
The Philippines is a global hub for outsourcing, and data privacy is where that industry’s compliance burden concentrates. A BPO typically processes its clients’ customer data, such as call recordings, account details, and payment information, on the clients’ behalf. Under the DPA, that makes the BPO a personal information processor for that data, with its own security and cooperation duties, while the client remains the controller. The BPO is also a controller for its own staff records, as explained above.
For foreign-owned operators, the commercial reality reinforces the legal one. International clients, particularly those subject to GDPR or similar regimes, increasingly demand evidence of DPA compliance before they will sign: a registered DPO, NPC registration where applicable, documented security controls, and a breach-response plan. Demonstrable compliance has become a precondition for winning contracts, not merely a way to avoid penalties. If outsourcing is your model, build privacy compliance into the structure from day one. Our guides to setting up a BPO in the Philippines and outsourcing to the Philippines cover where it fits, and our BPO company setup page covers the entity side.
Getting it right from the start
The most common mistake foreign founders make is treating data privacy as something to address later. In practice, the DPA’s expectations (a named DPO, a privacy notice, basic security measures) are far easier to build in while you are setting up than to retrofit once you are operating at scale. Identify whether your processing activities meet the NPC’s registration criteria, decide whether you act as controller or processor for each data set, appoint a DPO early, and document your lawful basis and security practices before you take on your first batch of client or customer data. Because the NPC revises its rules and reporting deadlines, verify the current requirements on privacy.gov.ph and treat compliance as an ongoing obligation rather than a single filing.
Frequently asked questions
Does my foreign-owned company in the Philippines need to register with the NPC?
NPC Circular 2022-04 requires registration of all data processing systems and the DPO when a company employs 250 or more people, processes sensitive personal information of 1,000 or more individuals, or processes personal data likely to pose a risk to data subjects' rights. Any system that involves automated decision-making or profiling must also be registered.
What is a Data Protection Officer and do I have to appoint one?
Every personal information controller must designate one or more individuals who are accountable for its compliance with the Data Privacy Act (Section 21(b) of RA 10173). Where the NPC thresholds apply, that person must also be registered with the NPC. The DPO should have enough authority and knowledge of the law to oversee privacy compliance.
What are the core obligations under the Data Privacy Act of 2012?
The core obligations are: establishing a lawful basis for processing (Section 12, with stricter rules for sensitive personal information under Section 13), providing a clear privacy notice, implementing organisational, physical, and technical security measures, and notifying the NPC and affected individuals of breaches that carry a real risk of serious harm.
Why does the Data Privacy Act matter especially for BPOs?
A BPO usually processes its clients' customer data on the client's instructions, which makes it a personal information processor for that data. It is a personal information controller for its own staff records. Foreign clients increasingly require demonstrable NPC compliance, a registered DPO, and breach procedures before signing contracts.
Is there an annual report I have to file with the NPC?
Yes. Under Section 22 of NPC Circular 16-03, incidents that do not need immediate notification must still be documented, and a summary is submitted to the NPC each year. The annual security incident report (ASIR) is filed through the NPC's Data Breach Notification Management System. The 2025 ASIR was due 31 March 2026. NPC Advisory No. 2026-03 reopened the filing period until 10 November 2026.
Official sources
Primary references this guide is checked against.
- Lawphil: Republic Act No. 10173, Data Privacy Act of 2012 (text of Sections 3, 12, 13, 20, 21)
- NPC Circular 2022-04, Registration of Personal Data Processing System and DPO (5 December 2022)
- NPC Circular 16-03, Personal Data Breach Management (15 December 2016)
- NPC Advisory No. 2026-02, Clarification on the Submission of Personal Data Breach Notification through DBNMS (11 May 2026)
- NPC Advisory No. 2026-03, Grant of Additional Period to Submit 2025 Annual Security Incident Reports (8 September 2026)
- NPC Circular 2023-06, Security of Personal Data in the Government and the Private Sector (1 December 2023)
Related guides
Appointing and Registering a Data Protection Officer in the Philippines
Who must appoint a data protection officer in the Philippines, who must also register the DPO with the NPC, and what the DPO owns when a breach happens.
Accounting and Audit Firm in the Philippines: How to Choose
How a foreign-owned company chooses and checks an accounting or audit firm in the Philippines: the audit triggers, CPA licence checks and questions to ask.
SEC penalties for late GIS and AFS: 2026 relief ends
SEC MC 16 pauses monthly late-filing penalties on GIS and AFS until December 31, 2026. Base fines still apply, and the monthly charge returns January 1, 2027.
