Regulated Sectors · Corporate Compliance
Data Privacy Act Compliance for Foreign Companies in the Philippines: RA 10173, NPC Enforcement, and the 2025–2026 Regulatory Landscape
Introduction: Why This Matters Now
If your company processes the personal data of anyone in the Philippines — through a Manila office, a BPO partner, an e-commerce platform open to Filipino consumers, or a global HR system that holds records of Philippine employees — you are very likely subject to the Data Privacy Act of 2012 (Republic Act No. 10173, “RA 10173” or “the DPA”). It is a law with criminal penalties, including imprisonment, and it sits alongside SEC registration, tax enrollment, and employment law as a prerequisite for doing business in the country.
The DPA has been in force for over a decade, but late 2024 through mid-2026 produced the most significant regulatory developments since its implementing rules took effect in 2016. The National Privacy Commission (NPC) has issued circulars and advisories that materially expand compliance obligations — particularly for foreign companies that collect, process, or store personal data of Philippine residents.
Three developments stand out. First, NPC Advisory No. 2024-04, issued on December 19, 2024, confirmed that the DPA applies to artificial intelligence systems across training, testing, and deployment. Second, NPC Advisory No. 2026-01, issued on April 13, 2026, set requirements for scraping publicly available personal data — including data used to train AI models. Third, the SEC’s Beneficial Ownership Disclosure Rules (effective January 1, 2026) require disclosure of the natural persons who ultimately own or control SEC-registered entities, creating a new intersection between corporate transparency and data privacy.
This guide covers, in ten parts: the legal framework; scope and extraterritorial application; key definitions; processing principles, lawful bases, and data subject rights; DPO registration; breach reporting; cross-border transfers and the 2024–2026 security, AI, and data scraping issuances; the SEC beneficial ownership intersection; penalties; and a compliance checklist.
Part I: Legal Framework — The Architecture of RA 10173
1.1 The Statute and Its Purpose
Republic Act No. 10173, entitled “An Act Protecting Individual Personal Information in Information and Communications Systems in the Government and the Private Sector, Creating for This Purpose a National Privacy Commission, and for Other Purposes,” was signed into law on August 15, 2012, and took effect on September 8, 2012. Its stated policy, in Section 2, is to protect the fundamental human right of privacy while ensuring the free flow of information to promote innovation and growth.
The law drew on the European Union’s Data Protection Directive (95/46/EC), and it shares many concepts with the GDPR that followed. A company that already complies with the GDPR has a head start — but Philippine law has its own requirements (NPC registration, the DPO mandate, specific breach timelines, and criminal liability for responsible officers) that need separate attention.
1.2 The Implementing Rules and Regulations (IRR)
The IRR of RA 10173 was signed on August 24, 2016, and took effect on September 9, 2016. Under Section 42 of the DPA, existing businesses were given a one-year transitory period from the IRR’s effectivity to comply. The IRR fills in the details the statute left to the NPC: the criteria for valid consent, standards for organizational, physical, and technical security measures, DPO and registration procedures, and the breach notification framework.
Foreign companies must treat the IRR as equally binding as the statute. The NPC has since issued circulars and advisories that supplement specific IRR provisions, including NPC Circular No. 16-03 (personal data breach management), NPC Circular No. 2022-04 (registration and DPOs), NPC Circular No. 2023-04 (consent), NPC Circular No. 2023-06 (security of personal data), NPC Advisory No. 2024-01 (model contractual clauses for cross-border transfers), NPC Advisory No. 2024-04 (AI systems), and NPC Advisory No. 2026-01 (data scraping), each discussed below.
1.3 The National Privacy Commission (NPC)
The NPC is an independent body attached to the Department of Information and Communications Technology (DICT). Its mandates include administering and implementing the DPA, monitoring compliance, investigating and resolving complaints, issuing compliance orders and enforcement notices, recommending prosecution to the Department of Justice, and coordinating with foreign data protection authorities.
Its enforcement powers are broad: it can issue cease and desist orders, impose temporary or permanent bans on processing, award indemnity to data subjects, and recommend criminal prosecution. For foreign companies subject to Philippine jurisdiction, the NPC is the primary regulatory interlocutor.
Part II: Scope and Extraterritorial Application — Does RA 10173 Apply to Your Company?
2.1 Who Must Comply: Section 4
Under Section 4, the DPA applies to the processing of all types of personal information and to any natural or juridical person involved in that processing — including personal information controllers (PICs) and personal information processors (PIPs) that, although not found or established in the Philippines, use equipment located in the Philippines, or that maintain an office, branch, or agency in the Philippines.
In practice, a foreign company using Philippine-based servers, data centers, or cloud infrastructure to process personal data falls within scope even without a local office.
For a foreign company with a Philippine subsidiary, the subsidiary is a separate juridical entity that is unquestionably subject to the DPA. The foreign parent may also be covered — for example, if it receives HR data from the subsidiary, operates a customer-facing platform used in the Philippines, or processes Philippine personal data on infrastructure in the country.
2.2 The Extraterritorial Reach: Section 6
Section 6 is the provision that most directly concerns foreign companies without a physical Philippine presence. It applies the DPA to acts done or practices engaged in outside the Philippines by an entity if:
- The act, practice, or processing relates to personal information about a Philippine citizen or resident;
- The entity has a link with the Philippines, and is processing personal information in the Philippines — or outside it, so long as the information is about Philippine citizens or residents. Such links include, but are not limited to:
- a contract entered into in the Philippines;
- a juridical entity unincorporated in the Philippines but with central management and control in the country; and
- an entity with a branch, agency, office, or subsidiary in the Philippines where the parent or affiliate of the Philippine entity has access to personal information; and
- The entity has other links in the Philippines, such as carrying on business in the Philippines, or the personal information having been collected or held by an entity in the Philippines.
This language is broad enough to capture a foreign e-commerce company whose platform is used by Philippine residents, a foreign SaaS provider whose servers process data submitted by Philippine users, or a foreign employer whose Philippine-based employees submit personal data to a global HR system hosted abroad. Whether a particular arrangement is covered is a factual question that calls for careful legal analysis — but the practical implication is that most foreign companies with Philippine customers, employees, contractors, or business partners should plan on complying.
2.3 The BPO Exception: Data of Foreign Residents
Section 4(g) of the DPA excludes from its coverage personal information originally collected from residents of foreign jurisdictions in accordance with the laws of those jurisdictions, including any applicable data privacy laws, which is being processed in the Philippines — for example, call center data processed on behalf of US or UK clients.
This exception matters for the BPO sector and for foreign companies that set up Philippine operations to provide data processing services. It does not extend to personal data of Philippine residents, even where the client is a foreign entity, and it depends on the data having been collected lawfully under the data subject’s home-country law.
2.4 How Common Foreign Business Models Are Affected
- Companies that outsource to Philippine BPOs. The foreign client is typically the PIC and the BPO provider the PIP. Under Section 14, a PIC may subcontract processing but remains responsible for ensuring proper safeguards are in place; compliance cannot simply be offloaded by contract.
- E-commerce platforms. Names, addresses, and payment details of Philippine consumers fall squarely within the DPA. Section 6 means a platform without a Philippine office can still be covered.
- SaaS, social media, and cloud providers. Services with Philippine users are covered under Section 6, and Section 4 reaches any provider using equipment located in the Philippines.
- Employers of Philippine-based staff (including remote workers). Employee records include sensitive personal information — government-issued identifiers, tax returns, and health records — which triggers the stricter rules for sensitive personal information under Section 13.
Part III: Key Definitions — PICs, PIPs, Personal Information, and Sensitive Personal Information
3.1 Personal Information Controller (PIC)
Under Section 3(h), a Personal Information Controller (PIC) is a person or organization who controls the collection, holding, processing, or use of personal information, including one who instructs another to collect, hold, process, use, transfer, or disclose personal information on its behalf. Put simply: if you decide why and how data is processed, you are a PIC. The PIC has direct accountability for the personal information under its control and bears the primary compliance obligations.
For a foreign company with a Philippine subsidiary, the subsidiary is the PIC for personal data collected in the Philippines. But if the foreign parent instructs the subsidiary to process personal data in a particular way, the parent may also be treated as controlling the processing — and may bear parallel obligations.
3.2 Personal Information Processor (PIP)
Under Section 3(i), a Personal Information Processor (PIP) is any natural or juridical person to whom a PIC outsources the processing of personal data. Your BPO provider, cloud host, or payroll processor is likely a PIP. A foreign company may itself be a PIP if it processes data on behalf of a Philippine entity.
The distinction matters because obligations flow differently. The PIC is primarily responsible for the lawfulness of processing, its lawful basis, and honoring data subjects’ rights. The PIP must follow the PIC’s instructions and implement security measures appropriate to the risk; under Section 14 it must also comply with all requirements of the DPA and other applicable laws, and the NPC can act against it directly.
3.3 Personal Information vs. Sensitive Personal Information
Personal information (Section 3(g)) is any information, whether recorded in material form or not, from which the identity of an individual is apparent or can be reasonably and directly ascertained by the entity holding it, or which, when put together with other information, would directly and certainly identify an individual. This captures names, addresses, contact details, employee numbers, financial data, and much more.
Sensitive personal information (SPI) (Section 3(l)) is personal information:
- About an individual’s race, ethnic origin, marital status, age, color, and religious, philosophical, or political affiliations;
- About an individual’s health, education, genetic or sexual life, or any proceeding for any offense committed or alleged to have been committed by that person, the disposal of such proceedings, or the sentence of any court in such proceedings;
- Issued by government agencies peculiar to an individual — including social security numbers, previous or current health records, licenses or their denial, suspension, or revocation, and tax returns; and
- Specifically established by an executive order or an act of Congress to be kept classified.
Under Section 13, processing of SPI is prohibited unless an exception applies — among them consent specific to the purpose and given before processing, processing provided for by existing laws and regulations with adequate safeguards, protection of the life and health of the data subject or another person where consent cannot be given, medical treatment by a medical practitioner or institution, and protection of lawful rights in court proceedings or the establishment, exercise, or defense of legal claims.
For foreign companies with Philippine employees, SPI routinely includes health records (HMO and PhilHealth data), SSS and tax identification numbers, and tax returns. Biometric data and labor union affiliation are not expressly listed in Section 3(l); pending bills to amend the DPA (see Part X) would add them.
Part IV: Processing Principles, Lawful Bases, and Data Subject Rights
4.1 The General Data Privacy Principles (Section 11)
Section 11 permits processing subject to the DPA and adherence to three principles: transparency, legitimate purpose, and proportionality. The IRR elaborates on each:
- Transparency: The data subject must be aware of the nature, purpose, and extent of processing. In practice, PICs publish a privacy notice stating what data is collected, why, how it is used, and with whom it is shared.
- Legitimate purpose: Processing must be compatible with a declared and specified purpose that is not contrary to law, morals, or public policy.
- Proportionality: Processing must be adequate, relevant, suitable, necessary, and not excessive in relation to the declared purpose.
Section 11 also requires that personal information be:
- Collected for specified and legitimate purposes, declared before or as soon as reasonably practicable after collection, and later processed only in a way compatible with those purposes;
- Processed fairly and lawfully;
- Accurate, relevant, and kept up to date where necessary — inaccurate or incomplete data must be rectified, supplemented, destroyed, or restricted;
- Adequate and not excessive in relation to the purposes of collection and processing; and
- Retained only as long as necessary for the declared purposes, for legal claims, for legitimate business purposes, or as provided by law, and kept in identifiable form no longer than necessary.
Under Section 21, the PIC is accountable for complying with these requirements and must be able to demonstrate compliance. These principles mirror GDPR concepts of purpose limitation and data minimization, but they are independently enforceable under Philippine law.
4.2 Lawful Basis for Processing Personal Information (Section 12)
Personal information may be processed only if not otherwise prohibited by law and at least one of the following applies:
- Consent: The data subject has given consent. Under Section 3(b), consent must be freely given, specific, and informed, and evidenced by written, electronic, or recorded means. NPC Circular No. 2023-04 requires an affirmative act — pre-ticked boxes or implied consent are not sufficient.
- Contract: Processing is necessary for, and related to, the fulfillment of a contract with the data subject, or to take steps at the data subject’s request before entering into one — for example, payroll processing under an employment contract.
- Legal obligation: Processing is necessary to comply with a legal obligation of the PIC — for example, reporting to the BIR.
- Vital interests: Processing is necessary to protect vitally important interests of the data subject, including life and health.
- Public order and public authority: Processing is necessary to respond to a national emergency, to comply with requirements of public order and safety, or to fulfill functions of public authority.
- Legitimate interests: Processing is necessary for the legitimate interests of the PIC or a third party, except where overridden by the data subject’s fundamental rights and freedoms under the Philippine Constitution. This requires a balancing test.
For SPI, the narrower Section 13 exceptions apply instead (see 3.3).
4.3 Rights of Data Subjects (Sections 16–18)
Philippine data subjects are entitled to:
- Be informed whether their personal information is being processed, and — before entry into the processing system or at the next practical opportunity — to be told the description of the data, the purposes, scope, and method of processing, the recipients, the identity and contact details of the PIC, the retention period, and their rights, including the right to lodge a complaint with the NPC;
- Object to processing (a right elaborated in the IRR, including for direct marketing, automated processing, and profiling);
- Reasonable access to their personal information, its sources, its recipients, the manner of processing, and information on automated processes used as the sole basis for decisions significantly affecting them;
- Rectification of inaccurate or erroneous data;
- Erasure or blocking — suspension, withdrawal, or ordering the blocking, removal, or destruction of personal information that is incomplete, outdated, false, unlawfully obtained, used for unauthorized purposes, or no longer necessary;
- Damages for harm sustained due to inaccurate, incomplete, outdated, false, unlawfully obtained, or unauthorized use of personal information; and
- Data portability (Section 18) — to obtain a copy of their data in an electronic or structured, commonly used format, where processing is electronic.
Under Section 17, these rights pass to the data subject’s lawful heirs and assigns after death or incapacity.
A Filipino employee, customer, or user may demand their data, correct it, or ask for its deletion, so your company needs a working process to receive, verify, and respond to these requests — including when the data sits on servers outside the Philippines.
Part V: Data Protection Officer (DPO) and NPC Registration
5.1 Mandatory Registration Criteria
Under NPC Circular No. 2022-04 (issued December 5, 2022; effective January 11, 2023), PICs and PIPs must register their Data Protection Officer (DPO) and Data Processing Systems (DPS) with the NPC if they:
- Employ at least 250 persons;
- Process the sensitive personal information of at least 1,000 individuals; or
- Process personal data in a way likely to pose a risk to the rights and freedoms of data subjects.
Organizations below these thresholds may register voluntarily; those that do not must submit a sworn declaration to the NPC.
5.2 DPO Requirements and Qualifications
Section 21(b) of the DPA requires every PIC to designate an individual accountable for the organization’s compliance. The DPO is the primary point of contact with the NPC, monitors compliance with the DPA and its IRR, and handles data subject requests and complaints. Under NPC issuances, the DPO should:
- Possess specialized knowledge in data privacy, typically shown through training or certification;
- Be formally appointed via a Board Resolution or Secretary’s Certificate;
- Ordinarily be an organic employee (external DPOs are permitted under certain contractual conditions — see 5.4);
- Hold a position that allows independent judgment without a conflict of interest; and
- Have their designation, postal address, dedicated telephone number, and email address published in the company’s website, privacy notice, privacy policy, and privacy manual.
The independence requirement is important: a DPO who reports to someone whose activities the DPO must review has a conflict. Many Philippine companies designate their Head of Legal or Compliance as DPO, provided that person has the requisite knowledge. For foreign companies, the DPO should be based in or readily accessible from the Philippines.
5.3 Registration Process
Registration runs through the NPC Registration System (NPCRS):
- Account creation: The DPO or an authorized representative creates an NPCRS account using a dedicated official DPO email address (e.g., dataprotection@company.com.ph — personal email addresses are not accepted).
- Registration proper: The organization encodes its details, including the Head of Organization, and details of all Data Processing Systems.
- Document upload and notarization: Supporting documents are uploaded. The NPCRS generates a DPO Form, which must be signed by the DPO and the Head of Organization, notarized, scanned, and re-uploaded.
- NPC review and validation: If deficiencies are found, the organization has a five-day window to rectify them.
- Payment and certificate issuance: After payment of the registration fee, the Certificate of Registration and NPC Seal of Registration can be downloaded.
Timing: A newly implemented DPS or newly appointed DPO must be registered within 20 days of the system’s commencement or the appointment’s effectivity. The Certificate of Registration is valid for one year and must be renewed annually (the renewal window is 30 days before expiration). The NPC may revoke registration for non-compliance with the DPA or its IRR.
5.4 DPO Registration for Foreign Companies
A Philippine subsidiary that meets the thresholds must register. For a foreign company without a subsidiary whose activities create a Section 6 link, registration turns on whether the NPC would regard it as a PIC or PIP subject to Philippine jurisdiction; a foreign company that actively targets the Philippine market (through a website, app, or commercial activity directed at Philippine residents) should expect to designate a DPO and register.
External DPOs are permissible. A company may appoint a third-party DPO (a professional services firm, DPO-as-a-service provider, or individual contractor) provided: (1) the contract has a minimum term of two years; (2) the contract has no exclusivity clause preventing the PIC from engaging other DPOs if needed; and (3) the DPO has a dedicated Philippine contact number and postal address.
Part VI: The Data Breach Notification Framework — 72 Hours and Counting
6.1 What Constitutes a Reportable Data Breach
Section 20(f) of the DPA requires the PIC to promptly notify the NPC and affected data subjects when sensitive personal information, or other information that may be used to enable identity fraud, is reasonably believed to have been acquired by an unauthorized person, and the PIC or the NPC believes the acquisition is likely to give rise to a real risk of serious harm to any affected data subject. The trigger is a breach that meets these criteria — not every security incident.
A security incident that does not meet this threshold (for example, a repelled intrusion attempt) may not be reportable, but it must still be documented and included in the organization’s Annual Security Incident Report (ASIR).
6.2 The 72-Hour Notification Rule
Under NPC Circular No. 16-03, the NPC must be notified within 72 hours upon knowledge of, or reasonable belief by the PIC or PIP that, a reportable breach has occurred; affected data subjects must also be notified within that period. The clock is comparable to the GDPR’s, and meeting it depends on having incident detection and response procedures in place before anything goes wrong.
The notification to the NPC must include:
- The nature of the breach — what happened and how, to the extent known;
- The categories and approximate number of data subjects affected;
- The personal data possibly compromised, by category and approximate volume;
- The likely consequences of the breach;
- The measures taken or proposed to address the breach and reduce harm to data subjects; and
- The contact details of the DPO or other designated compliance officer.
The notification to affected data subjects must tell them the nature of the breach and the data affected, the likely consequences, the measures being taken, and whom to contact.
Under Section 20(f), notification may be delayed only to the extent necessary to determine the scope of the breach, prevent further disclosures, or restore reasonable integrity to the system. Circular 16-03 adds that there should be no delay where the breach involves at least 100 data subjects, or where disclosure of sensitive personal information will harm or adversely affect the data subject. The NPC may exempt a PIC from notification where it would not serve the public interest or the data subjects’ interests, and may authorize postponement where notification could hinder a criminal investigation.
For foreign companies, your incident response plan must account for Philippine notification separately from any home-country obligations. Missing the deadline is a separate violation, and intentional or negligent concealment is a crime under Section 30 (see Part IX).
6.3 Full Report — Within Five Days
A full report must be submitted to the NPC within five days of the initial notification, unless the NPC grants additional time. It sets out the detailed analysis: root cause, systems affected, data compromised, and remediation. Treat it as a hard deadline — a late full report exposes the organization to enforcement action even if the 72-hour notification was complete.
6.4 Annual Security Incident Report (ASIR)
The ASIR summarizes all security incidents and personal data breaches — including those that were not reportable — during the covered period. The 2025 ASIR was due on March 31, 2026. Failure to submit the ASIR creates a presumption that no security incident or personal data breach occurred during the period — a presumption that can be damaging if the NPC later finds evidence of an unreported breach. The ASIR is submitted through the NPCRS.
Part VII: Cross-Border Transfers, Security Requirements, and the 2024–2026 Issuances on AI and Data Scraping
7.1 Cross-Border Data Transfers
The DPA does not prohibit transferring personal data out of the Philippines. Instead, Section 21 makes the PIC responsible for personal information under its control, including information transferred to a third party for processing, whether domestically or internationally. The PIC must use contractual or other reasonable means to provide a comparable level of protection while the data is processed by the third party.
On May 30, 2024, the NPC issued NPC Advisory No. 2024-01 on model contractual clauses (MCCs) for cross-border transfers, drawing on international frameworks including the ASEAN MCCs and the EU Standard Contractual Clauses. Use of the MCCs is voluntary, and the NPC does not review agreements for conformity — but they are a practical way to show accountability for transfers.
If Philippine employee or customer data is stored on servers in your home country or a third country, you should:
- Assess whether the recipient can provide a comparable level of protection;
- Put a data transfer or processing agreement in place — the NPC’s MCCs are a useful starting point;
- Document the lawful basis for the transfer (Section 12 or, for SPI, Section 13); and
- Apply the security measures required by NPC Circular No. 2023-06 to the offshore processing.
7.2 NPC Circular No. 2023-06: Security of Personal Data
NPC Circular No. 2023-06 (dated December 1, 2023) took effect on March 30, 2024, with a 12-month transitory period that ended on March 30, 2025. It updated the security requirements for personal data in both the government and private sectors, and applies to processing within and outside the Philippines, subject to the DPA. It calls for:
- Privacy Impact Assessments (PIAs) for processing systems — including new AI systems, data scraping operations, and HR platforms;
- Organizational, physical, and technical security measures, including encryption of personal data at rest and in transit, role-based access controls, audit trails of who accessed what data and when, regular vulnerability assessments and penetration testing, and secure disposal of data no longer needed; and
- Privacy by design — privacy considerations built into systems from the earliest stage, not retrofitted after deployment.
With the transitory period over, an organization not yet compliant with Circular No. 2023-06 is out of step with a binding NPC issuance.
7.3 NPC Advisory No. 2024-04: AI Systems and the DPA
On December 19, 2024, the NPC issued Advisory No. 2024-04, “Guidelines on the Adoption of Artificial Intelligence (AI) Systems for the Protection of Personal Data in the Philippines.” It clarifies that the DPA and its IRR apply to AI systems throughout their lifecycle — training, testing, and deployment. For foreign companies running AI-powered platforms or services in the Philippines:
Privacy principles apply to AI. Deploying an AI system that makes decisions about Philippine residents (hiring, lending, service denial) requires the same lawful basis, transparency, and accountability as any other processing.
Transparency. PICs must clearly inform data subjects about:
- The purpose, scope, nature, and scale of AI processing;
- The potential risks and expected outputs of the AI system;
- The mechanisms available to challenge AI decisions; and
- The identity and contact details of the AI system’s operator.
Data subject rights apply to AI. Data subjects keep their rights to object, correct, or erase personal data even after it has been incorporated into training datasets, and organizations need effective mechanisms for exercising them.
Fairness and bias mitigation. PICs must identify, monitor, and limit systemic, human, and statistical biases in AI systems. The NPC also warns against “AI washing” — falsely claiming AI capabilities or compliance.
Human oversight for high-impact decisions. Automated decisions that significantly affect individuals — AI-driven recruitment screening, credit scoring, service denial — should be reviewable by a human. A purely automated decision with no human review pathway is likely non-compliant.
PIAs for AI. The advisory strongly encourages, and for high-risk applications effectively expects, a PIA specific to the AI system, consistent with Circular No. 2023-06.
7.4 NPC Advisory No. 2026-01: Data Scraping and Publicly Available Personal Data
On April 13, 2026, the NPC issued Advisory No. 2026-01, “Guidelines on Data Scraping of Publicly Available Personal Data.” It covers PICs and PIPs that scrape data, and PICs that host publicly available personal data that may be scraped. Its core message: public availability of personal data is not blanket consent for its use, and data scraping is processing under the DPA.
For foreign companies engaged in market research, talent acquisition, competitive intelligence, or AI training that involves scraping Philippine sources (websites, public databases, social media):
Lawful basis required. Public availability alone is not a lawful basis.
Purpose limitation. Scraped data may be used only for the specific, legitimate purpose declared. Secondary use — for example, training a commercial AI model beyond a declared research purpose — needs its own lawful basis.
Transparency and notice. Data subjects must be informed, through an appropriate privacy notice or consent form, before processing or at the next practical opportunity, that their data is processed through scraping.
Proportionality. Scraped data must be adequate, relevant, suitable, and necessary for the purpose. Excessive or indiscriminate scraping is not permitted, and PICs must assess whether the purpose could be met by less intrusive means.
PIA requirement. A Privacy Impact Assessment must cover the scraping activity.
Sensitive personal information. Scraping SPI is generally prohibited unless strict conditions are met (valid lawful basis, enhanced security, and compelling justification).
Vulnerable data subjects. Scraping data of minors, elderly persons, or persons with disabilities requires additional safeguards.
Unauthorized practices. Bypassing website safeguards, using deceptive techniques, or violating platform terms of service is treated as unauthorized processing and may lead to civil, criminal, or administrative liability.
For foreign AI companies that have trained models on data scraped from Philippine sources, the line is now clear: scraping is processing, it needs a lawful basis, and every data privacy principle applies.
Part VIII: The SEC Beneficial Ownership Disclosure Rules — A New Intersection with RA 10173
8.1 SEC Memorandum Circular No. 15, Series of 2025 and No. 8, Series of 2026
Effective January 1, 2026, the SEC’s Beneficial Ownership Disclosure Rules under SEC Memorandum Circular No. 15, Series of 2025, with rules of procedure in SEC Memorandum Circular No. 8, Series of 2026, require SEC-registered corporations — including foreign corporations licensed to do business in the Philippines — to disclose their beneficial owners through the Hierarchical and Applicable Relations and Beneficial Ownership Registry (HARBOR). (For the filing mechanics, see our guide to SEC HARBOR for foreign companies.)
In summary:
- A beneficial owner is any natural person who directly or indirectly owns at least 20% of the voting rights, voting shares, or capital of the reporting entity, or who controls it through the other categories in the rules (contractual control, board election power, dominant influence, nominee arrangements, and others). A person exercising effective control at any level of the ownership chain must be identified even if their multiplied ownership is below 20%; senior management is identified only if no one qualifies under the other categories.
- Disclosures include complete name (original and transliterated), nationality, residential address, date of birth, government-issued identification numbers (TIN, passport), the nature and extent of the beneficial interest, the date it was acquired, and whether the person is a politically exposed person (PEP).
- Any change in beneficial ownership must be reported within seven calendar days.
8.2 The Intersection with RA 10173
The information gathered for HARBOR filings — names, birthdates, addresses, government ID numbers — is itself personal data (and, in the case of government-issued identifiers, SPI) that must be processed in compliance with the DPA. Your privacy notices, data processing agreements, and retention policies should cover the collection and storage of beneficial ownership information. Because the filing is required by SEC rules, the legal-obligation basis under Section 12(c) — and, for government-issued identifiers, the Section 13(b) exception for processing provided for by law — is likely a better fit than consent; this should be confirmed case by case.
Where beneficial owners are foreign nationals and the data moves between the Philippine company and a foreign parent or holding company, the cross-border accountability rules in Part VII apply.
8.3 Penalties for Non-Compliance
The SEC rules provide for fines of up to PHP 2 million, possible dissolution, disqualification of responsible directors and officers for five years (for false declarations), and liability for resident agents and country or regional heads of foreign corporations who fail to exercise due diligence in verifying beneficial ownership information. Foreign investors should make sure their resident agents are briefed and have a process for collecting and verifying the required information.
Part IX: Penalties and Enforcement — What Is at Stake
RA 10173 is unusual among data privacy laws in imposing criminal penalties, including imprisonment, alongside administrative sanctions.
9.1 Criminal Penalties (Sections 25–35)
| Offense | Personal information | Sensitive personal information |
|---|---|---|
| Unauthorized processing (Sec. 25) | 1–3 years; PHP 500,000–2,000,000 | 3–6 years; PHP 500,000–4,000,000 |
| Accessing personal information due to negligence (Sec. 26) | 1–3 years; PHP 500,000–2,000,000 | 3–6 years; PHP 500,000–4,000,000 |
| Improper disposal (Sec. 27) | 6 months–2 years; PHP 100,000–500,000 | 1–3 years; PHP 100,000–1,000,000 |
| Processing for unauthorized purposes (Sec. 28) | 1 year 6 months–5 years; PHP 500,000–1,000,000 | 2–7 years; PHP 500,000–2,000,000 |
| Unauthorized access or intentional breach (Sec. 29) | 1–3 years; PHP 500,000–2,000,000 | (same) |
| Concealment of security breaches involving SPI (Sec. 30) | — | 1 year 6 months–5 years; PHP 500,000–1,000,000 |
| Malicious disclosure (Sec. 31) | 1 year 6 months–5 years; PHP 500,000–1,000,000 | (same) |
| Unauthorized disclosure (Sec. 32) | 1–3 years; PHP 500,000–1,000,000 | 3–5 years; PHP 500,000–2,000,000 |
Section 30 is the offense most directly tied to breach notification: it penalizes anyone who, knowing of a security breach and of the duty to notify the NPC under Section 20(f), intentionally or by omission conceals it.
Under Section 33, any combination or series of these acts is punishable by 3 to 6 years and a fine of PHP 1,000,000 to PHP 5,000,000. Under Section 35, the maximum penalty in each range applies when the personal information of at least 100 persons is harmed, affected, or involved.
Under Section 34, if the offender is a corporation, partnership, or other juridical person, the penalty is imposed on the responsible officers who participated in, or by their gross negligence allowed, the commission of the crime; the court may also suspend or revoke the entity’s rights under the DPA, and an offender who is a foreign national is deported after serving the sentence. For foreign companies with Philippine subsidiaries, this means a president, compliance officer, or DPO whose gross negligence allowed a breach — or its concealment — can face personal criminal liability, not just the company.
9.2 Administrative Fines
The NPC’s administrative fines are calculated on the offending entity’s annual gross income for the year immediately preceding the infraction:
- Grave infractions (e.g., affecting more than 1,000 data subjects; serious violations of privacy principles or data subject rights): 0.5% to 3% of annual gross income.
- Major infractions (affecting 1,000 data subjects or fewer): 0.25% to 2% of annual gross income.
- Other infractions (e.g., failing to register true identity or contact details): up to PHP 200,000 per violation.
- Cap: The total administrative fine for a single act or omission is capped at PHP 5 million.
For example, the percentage range for a grave infraction by a company with PHP 1 billion in annual gross income would be PHP 5 million to PHP 30 million, but the cap limits the fine for a single act or omission to PHP 5 million. Multiple acts or omissions can be fined separately.
9.3 Other Enforcement Measures
Beyond fines and prosecution, the NPC can issue:
- Compliance and enforcement orders;
- Cease and desist orders prohibiting specific processing;
- Temporary or permanent bans on processing that is detrimental to national security, public interest, or data subjects’ rights; and
- Indemnity awards to data subjects injured by privacy violations.
The NPC also conducts compliance checks and may investigate on its own initiative, not only on complaint. Foreign companies operating in the Philippines should treat DPA compliance as a core legal obligation with real enforcement consequences.
9.4 Interaction with Other Philippine Laws
The DPA works alongside, and sometimes overlaps with:
- Republic Act No. 10175 (Cybercrime Prevention Act of 2012) — covers illegal access, data interference, and other computer-related offenses. A single breach may raise issues under both laws.
- Republic Act No. 8792 (Electronic Commerce Act of 2000) — the legal framework for electronic documents, signatures, and transactions.
- Republic Act No. 9160, as amended (Anti-Money Laundering Act), and Republic Act No. 9510 (Credit Information System Act) — Section 4(f) excludes information that banks and other financial institutions under the Bangko Sentral ng Pilipinas need to comply with these laws. The exclusion is limited to that information; the institutions’ other processing remains subject to the DPA.
- Republic Act No. 1405 (Secrecy of Bank Deposits Act) and Republic Act No. 6426 (Foreign Currency Deposit Act) — Section 4(e) provides that the DPA does not amend or repeal these laws (or the Credit Information System Act).
Part X: Compliance Checklist for Foreign Companies
Immediate (within 30 days):
- Determine whether your Philippine activities bring you within Sections 4 or 6, and whether you act as a PIC, a PIP, or both.
- Map your data flows: what personal data and SPI you collect from or about Philippine individuals (employee records, customer data, beneficial ownership data, payment data, biometric access data), where it goes — including offshore — and who has access.
- Confirm whether you meet the registration thresholds (250+ employees, SPI of 1,000+ individuals, or processing likely to pose a risk to data subjects).
- Appoint a DPO with the authority and expertise to oversee compliance and, if required, register the DPO and DPS with the NPC — the 20-day deadline runs from appointment.
- Review your breach response plan with specific steps for the 72-hour NPC notification and the five-day full report, and run a tabletop exercise to test it.
Short-term (within 90 days):
- Complete Privacy Impact Assessments and implement the organizational, physical, and technical measures required by NPC Circular No. 2023-06 (encryption, access controls, audit trails, security testing, secure disposal).
- Publish or update your privacy notice and privacy policy to meet Section 16 disclosure requirements, and set up a process for handling data subject requests.
- Adopt a data retention policy that defines retention periods and ensures deletion once the purpose is fulfilled.
- Execute data processing agreements with PIPs (BPOs, cloud providers, payroll processors, IT vendors) that include security and breach notification obligations, and put transfer agreements in place for data leaving the Philippines (the NPC’s model contractual clauses are a useful starting point).
- Maintain records of processing activities: legal basis, categories of data subjects and personal information, and recipients.
- Audit AI systems used in or affecting Philippine operations against NPC Advisory No. 2024-04: lawful basis, transparency, human review for high-impact decisions, bias mitigation, and a PIA.
- Audit data scraping activities against NPC Advisory No. 2026-01: lawful basis, purpose limitation, notice, proportionality, and a PIA.
- Train employees who handle personal data of Philippine individuals on their obligations.
- Submit the ASIR if not yet filed (the 2025 ASIR was due March 31, 2026 — file promptly, with an explanation for the late filing).
Ongoing:
- Monitor proposed amendments to RA 10173 (House Bill Nos. 892 and 898), which, if enacted, would expand the definition of sensitive personal information to include biometric and genetic data and labor affiliation, and would increase criminal penalties. Track new NPC circulars and advisories.
- Maintain SEC beneficial ownership compliance: HARBOR filings, updates within seven days of any change, and privacy-policy coverage of the related personal data.
- Renew NPC registration annually and update DPS registrations when new processing systems are deployed.
Conclusion: Privacy as a Strategic Investment, Not a Compliance Burden
The Data Privacy Act is not something to address after operations are up and running. It is an enforcement-backed law with extraterritorial reach and criminal penalties for responsible officers, and it shapes how foreign companies collect, process, store, and transfer personal data in the Philippines.
The regulatory direction is clear. The NPC’s 2024–2026 issuances extend its reach into AI systems and data scraping, tighten security expectations, and set specific rules on registration and breach reporting. The SEC’s beneficial ownership rules add another layer that intersects with data privacy in ways many foreign companies have not yet addressed.
The framework itself is manageable with planning, and companies already aligned with the GDPR will recognize many concepts. Treat privacy as a strategic investment: it protects your Philippine operations from enforcement risk and builds trust with Philippine customers and employees. Treating it as a box-checking exercise tends to leave a company responding to new circulars after the deadlines have passed.
TTFC Law advises foreign companies on data privacy matters, including DPO registration, breach response planning, and cross-border transfer arrangements. Contact us to discuss your obligations under the Data Privacy Act.
This article is for general informational purposes only and does not constitute legal advice. The Data Privacy Act of 2012 (Republic Act No. 10173), its Implementing Rules and Regulations, and the NPC circulars and advisories referenced herein are subject to change. Foreign companies operating or considering investment in the Philippines should consult a qualified Philippine-licensed attorney for advice tailored to their specific circumstances.
Primary Sources Referenced:
- Republic Act No. 10173 (Data Privacy Act of 2012) — lawphil.net/statutes/repacts/ra2012/ra_10173_2012.html; Official Gazette, officialgazette.gov.ph/2012/08/15/republic-act-no-10173/
- IRR of RA 10173 — privacy.gov.ph
- NPC Circular No. 16-03 (Personal Data Breach Management) — privacy.gov.ph
- NPC Circular No. 2022-04 (Registration of Data Processing Systems and Designation of DPOs) — privacy.gov.ph
- NPC Circular No. 2023-04 (Consent Guidelines) — privacy.gov.ph
- NPC Circular No. 2023-06 (Security of Personal Data in the Government and the Private Sector) — privacy.gov.ph
- NPC Advisory No. 2024-01 (Model Contractual Clauses for Cross-Border Transfers of Personal Data) — privacy.gov.ph
- NPC Advisory No. 2024-04 (AI Systems) — privacy.gov.ph/wp-content/uploads/2025/02/Advisory-2024.12.19-Guidelines-on-Artificial-Intelligence-w-SGD.pdf
- NPC Advisory No. 2026-01 (Data Scraping) — privacy.gov.ph/wp-content/uploads/2026/04/SGD_A_1.pdf
- SEC Memorandum Circular No. 15, Series of 2025 (Beneficial Ownership Disclosure Rules) — sec.gov.ph
- SEC Memorandum Circular No. 8, Series of 2026 (Rules of Procedure for Beneficial Ownership) — sec.gov.ph
- NPC Annual Security Incident Report requirements — privacy.gov.ph
Keep reading
The Philippine Competition Act for Foreign Investors: Prohibited Conduct, PCC Enforcement, and M&A Notification
Republic Act No. 10667 reaches foreign companies that do business in the Philippines — and foreign deals that affect Philippine markets. This guide covers what you need to know: the per se ban on price-fixing and bid rigging, the rules on abuse of dominant position, the PCC's investigative and penalty powers, and the compulsory merger notification regime, including the thresholds effective March 1, 2026 of PHP 9.1 billion (Size of Party) and PHP 3.8 billion (Size of Transaction), the 30-day filing deadline, the Phase 1 and Phase 2 review timeline, and the gun-jumping rules that can void a transaction.
Environmental Compliance for Foreign Investors in the Philippines: ECC Requirements, DENR Permits, and the Regulatory Framework
Foreign companies operating in the Philippines must navigate a complex web of environmental laws — from the Environmental Compliance Certificate under PD 1586 to discharge permits under the Clean Water Act and emission permits under the Clean Air Act. This guide covers every environmental permit, compliance obligation, and penalty that foreign investors need to know.
Foreign Investment in Philippine Renewable Energy: A Legal Guide to 100% Ownership, Service Contracts, and Fiscal Incentives
The Philippines now allows 100% foreign ownership in solar, wind, hydro, and ocean energy projects. This guide covers the legal basis under DOJ Opinion No. 21, DOE Circular No. DC2022-11-0034, the Revised Omnibus Guidelines, RA 9513 fiscal incentives, service contract requirements, and step-by-step entry strategies for foreign renewable energy investors.