NPC Advisory 2026-01: public data is not free to use
The NPC's 13 April advisory says personal data anyone can see online still needs a lawful basis to collect. What that means for CRMs and lead lists.
Published · 3 min read

The National Privacy Commission's Advisory No. 2026-01, dated 13 April, sets out its guidelines on scraping publicly available personal data. Its central point fits in one sentence: that personal data is public does not mean the person consented to its use for purposes beyond those reasonably contemplated when it was shared. An organisation that collects names, photos or profiles from websites, apps or social media, by script or by hand, still needs a lawful basis under the Data Privacy Act of 2012, has to tell the people concerned, and may take only what the purpose needs. Newsbytes reported it on 28 April, and law firms followed in May.
What it asks of anyone who collects
The rules are specific. The purpose has to be defined and legitimate, and the data used for nothing unrelated to it. The organisation must run a privacy impact assessment, including for scraping that a contractor does on its behalf, and keep it up to date. Scraping sensitive personal information is prohibited unless strict conditions are met, and data about minors, the elderly and persons with disabilities gets heightened scrutiny. Scraping that breaks a website's terms of service, or gets around its defences such as robots.txt or a CAPTCHA, is unauthorised and can bring criminal, civil and administrative liability. A contract with whoever does the scraping does not take the accountability off the organisation that commissioned it.
Where it meets a CRM
The part most offices will meet is Section 7. An organisation that uses personal data scraped by someone else, such as a lead list bought from whoever scraped it, has to check by contract or other reasonable means that it was gathered lawfully. If it was not, using it is unauthorised as well. Its privacy notice has to say when personal data came from public sources, which ones and why. Baker McKenzie's reading is that it matters to any organisation that collects, uses, purchases or hosts such data, marketing included.
That puts one question to every contact in a CRM: where did this person come from? I have built two CRMs, for a window furnishings retailer and a storm-damage restoration contractor, and it is the question I would now put to any CRM used here. A contact who asked for a quote arrived with a purpose they chose. A name copied from a public directory arrived with none, and under the advisory the organisation needs a lawful basis for it, a notice to the person and a privacy impact assessment. A CRM that records the source of each contact, who added it and when, can answer that. A bare list of names cannot.
The advisory speaks to the other side too. An organisation whose website publishes personal data, a staff page or a list of officers, should tell those people their details may be scraped and take reasonable measures against it, the advisory says, which may include an inventory of what is published and why, rate limits and bot detection. Data behind a log-in is not publicly available by the advisory's own definition, which is one more reason to put a member directory behind one.
Five checks for your contact lists
- Make the source a required field on every contact: where it came from, who added it and when.
- For any list you bought or were given, ask in writing how it was compiled, and keep the answer. If it was scraped unlawfully, using it is unauthorised too.
- If staff copy details from social media or directories into your systems, treat it as scraping: write down the purpose and the lawful basis, and cover it in a privacy impact assessment.
- Say in your privacy notice when you collect from public sources, which ones, and for what.
- Set a retention period for anything collected this way, and delete it when the purpose is done.
If nobody can say where half your contacts came from, the problem is usually the system holding them. The case studies show the CRMs I have built, and the fit check is the place to start.
Sources
- National Privacy Commission (the NPC's PDF, as hosted by Newsbytes.PH), NPC Advisory No. 2026-01: Guidelines on Data Scraping of Publicly Available Personal Data, 13 April 2026
- Newsbytes.PH, NPC issues guidelines on scraping of publicly available personal data, 28 April 2026
- Baker McKenzie, Philippines: NPC Tightens Rules on Data Scraping, 8 May 2026
- DivinaLaw, NPC Advisory No. 2026-01
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
