South Korea - Public Data Processing Guide

Guide on Processing Publicly Available Personal Data for AI Development and Services

Guide on Processing Publicly Available Personal Data for AI Development and Services (AI 개발·서비스를 위한 공개된 개인정보 처리 안내서) - Personal Information Protection Commission

South Korea

RAI-KR-NA-GPPAPXX-2024
Effective: 17 Jul 2024
In Force(In Force)As published at pipc.go.kr · checked 9 Sep 2026

South Korea - Public Data Processing Guide is In Force in South Korea as of 9 Sep 2026, according to pipc.go.kr.

GuidelineData Protection and PrivacyGovernance and OversightAccountability and Documentation
Export PDF

South Korea's Personal Information Protection Commission (PIPC) sets out compliance standards for AI developers processing web data in the 2024 Guide on Processing Publicly Available Personal Data for AI Development and Services. The guideline took effect on July 17, 2024, and is In Force. Statutory compliance is overseen by the PIPC.

Summary

The Guide on Processing Publicly Available Personal Data for AI Development and Services remains In Force as of September 2026. Issued by South Korea's Personal Information Protection Commission (PIPC) on July 17, 2024, the instrument establishes official compliance criteria under the Personal Information Protection Act (PIPA) for utilizing publicly accessible web data in AI model training and services. The most recent dated policy milestone occurred on August 6, 2025, when the PIPC introduced a comprehensive lifecycle guide on generative AI that consolidated and complemented this dataset-focused guidance.

The Guide clarifies that publicly available data on the internet remains subject to PIPA protections. It establishes that AI developers may rely on the legitimate interests ground under Article 15 of PIPA as a legal basis for collecting and processing publicly available personal data, provided they satisfy a three-part test: specifying a legitimate development purpose, establishing data processing necessity, and conducting a balancing test that weighs AI innovation benefits against data subjects' fundamental privacy rights.

To safeguard individuals, the Guide outlines lifecycle safety measures including pre-ingest scrubbing of unique identifiers, anonymization, model training controls to limit memorization, post-deployment output filtering, and accessible redress channels for data subjects. Organizations are urged to form dedicated AI privacy teams under a Chief Privacy Officer and to document legitimate interest assessments before launching AI systems.

As administrative guidance, the instrument itself is non-binding and no regulatory authority directly enforces the Guide on its own. However, the Personal Information Protection Commission oversees compliance with the underlying Personal Information Protection Act and holds authority to conduct inspections and audits, issue binding corrective orders, mandate the suspension of unlawful data processing, and impose administrative fines for PIPA statutory violations.

Full article

Read full text ↗

Overview

The Personal Information Protection Commission (PIPC) published the Guide on 17 July 2024 to clarify how "publicly available personal data" may be lawfully processed for AI development and services under South Korea's Personal Information Protection Act (PIPA). The document frames publicly available personal data as information that is lawfully accessible by anyone (for example, data on public websites, blogs, online repositories such as Common Crawl, public filings, press and broadcast media). While publicly accessible, such data remains protected under PIPA; thus the Guide provides interpretive criteria for a legal basis (notably the "legitimate interests" basis), minimum safety measures, governance expectations and concrete examples of acceptable and unacceptable practices. The Guide is expressly advisory (non-binding) but is intended to reduce legal uncertainty and to inform both compliance and enforcement conversations at the PIPC. PIPC press material and the Guide's distribution are published on the Commission's site and the national privacy portal (see Sources).

Definitions

The Guide defines several core terms in a practical manner: "publicly available personal data" (data lawfully accessible to anyone without circumvention), "collection and use for AI development" (ingest, cleaning, labeling, training, validation, and deployment of AI models), "identifiable personal data" (data allowing identification of a natural person), "sensitive personal data" (health, biometric, unique identifiers, minors), and "legitimate interests" (the legal basis assessed through purpose legitimacy, necessity, and interests balancing). The Guide distinguishes publicly available data from non-public or restricted-access information (e.g., private communications, content behind authentication, paid-content behind contractual terms) and treats the latter as not covered by its permissive examples.

Governance and Institutional Framework

The Guide places responsibility on organizations to establish AI privacy governance structures centered on a designated privacy lead (e.g., Chief Privacy Officer) or an "AI privacy team" with cross-functional representation (legal, security, ethics, product, engineering). It recommends adoption of policies and standard operating procedures for dataset sourcing, retention, access control, and de-identification. The Guide calls for documented Legitimate Interest Assessments (LIAs) or Data Protection Impact Assessments (DPIAs) tailored for AI use-cases, with versioning and executive sign-off. Reporting channels and lines of accountability to senior management must be in place, and organizations are encouraged to integrate privacy-by-design and privacy-by-default into model development lifecycles. The Guide's governance blueprint aligns with PIPC's broader policy work on AI privacy risk management and transparency guidance, as articulated on the PIPC site (PIPC).

Key Focus Areas

The Guide identifies several thematic priorities: (1) Legal bases and interpretive criteria (chiefly legitimate interests) for collection and use; (2) Risk-based safeguards commensurate with the nature of data and AI use; (3) Technical measures to remove or protect direct identifiers prior to ingest and to minimize model memorization of personal data; (4) Data subject rights, transparency and remediation channels; (5) Special protections for sensitive categories (including default restrictions and higher scrutiny); and (6) Documentation and auditability to demonstrate compliance. Each focus area is explained with concrete examples and flowcharts for decisions, including how to assess whether content scraped from a public website can be retained for training or must be removed/reduced because of high identifiability or sensitivity.

Implementation Framework

The Guide recommends a lifecycle approach to implementation: (i) Purpose specification and planning (record purpose, reuse limits, retention); (ii) Source evaluation and pre-ingest filtering (exclude restricted or sensitive sources; adopt robots.txt and terms-of-service checks where relevant); (iii) Data processing controls (token removal, identifier scrubbing, pseudonymization/anonymization where feasible); (iv) Model training safeguards (techniques to limit memorization and to detect model exposure of training personal data); (v) Post-deployment monitoring (user-facing filters, output sanitization, and human review); and (vi) Continuous governance (documented LIAs/DPIAs, audits and incident response). The Guide sets expectation for demonstrable, repeatable processes rather than one-off decisions.

Monitoring and Evaluation

The Guide urges organizations to implement monitoring metrics and evaluation protocols for privacy risks. Recommended practices include periodic privacy risk re-assessments coinciding with model retraining, membership inference and data-exposure testing on models, logging and metrics for attempted access to sensitive datasets, and annual or event-triggered independent audits. The Guide suggests specific test methods (e.g., probing models for memorized personal data, evaluating differential privacy parameterization) and encourages publication of transparency reports summarizing data sources, mitigation measures, and redress channels to foster public confidence.

Penalties, Liability, and Appeals

Although the Guide itself is interpretive and non-binding, PIPC clearly signals that failure to meet standards may lead to enforcement under the Personal Information Protection Act. Potential regulatory actions under PIPA include administrative orders to suspend or correct processing, mandatory remedial measures, and civil or criminal liability where specified statutory thresholds are met. The Guide highlights the importance of maintainable documentation because lack of records or demonstrable safeguards increases enforcement risk. The PIPC's enforcement posture is also discussed in other PIPC materials linked from the Guide.

Relationship to Other Instruments

The Guide situates itself among broader PIPC initiatives and other sectoral and international instruments: it references previous PIPC materials (e.g., AI privacy risk management model, transparency guidance, and related safety guides), the national privacy portal, and international supervisory developments (e.g., CNIL and UK regulator approaches to web-scraped data). The Guide is intended to complement — not supplant — statutory obligations under PIPA, sectoral rules and contract law (including website terms-of-service), and other public guidance on secure AI development.

International Alignment

The Guide expressly compares South Korea's interpretive approach with contemporaneous rulemaking and guidance in the EU, France, the UK, and other supervisory authorities that are addressing the legality of using web-scraped or publicly available data for AI training. It recommends practitioners to align with recognized international privacy frameworks and to adopt technical and governance measures consistent with global best practices, for example, minimizing exportability of identifiable data, adopting strong access control, and documenting cross-border transfer mechanisms when models or datasets move across jurisdictions. The Guide also notes ongoing PIPC dialogues with international counterparts.

Implementation Timeline

MilestoneDate
Guide published by PIPC (announcement)2024-07-17
Public briefings/FAQ and Q&A published2024-07–08-2024 (Q&A materials circulated July–Aug 2024)
PIPC publishes AI privacy risk management model (complementary materials)2024-12 (risk model release)
Further consolidated guidance on generative AI lifecycle2025-08 (PIPC: generative AI processing guide)

Sources and References

SourceType
Personal Information Protection Commission - Announcement: 인공지능(AI) 개발·서비스에 이용되는 ‘공개 데이터’ 처리 기준 제시Primary Source
South Korea Privacy Portal - 자료: AI 개발·서비스를 위한 공개된 개인정보 처리 안내서 (자료 게시)Primary Source

Requirements for a company

What an organisation has to do under South Korea - Public Data Processing Guide, at a glance. Not legal advice — the table below gives the provision and deadline for each item.

Must do

0

Nothing in this category.

Must not do

0

Nothing in this category.

Should do

9
  • Conduct and document Legitimate Interest Assessments or Data Protection Impact Assessments tailored to AI use cases before processing public data.AI developers and service providers processing publicly available personal data
  • Establish an AI privacy governance structure with designated privacy leadership to oversee dataset sourcing, retention, and de-identification.Organizations developing or deploying AI systems
  • Remove direct identifiers and scrub sensitive personal information from publicly collected datasets prior to model ingestion.AI developers processing publicly available datasets
  • Evaluate website terms of service and robots.txt protocols before scraping personal data from public online sources.Organizations scraping web data for AI development
  • Implement technical safeguards during model training to limit the memorization and subsequent exposure of personal data.AI developers training models on personal data
  • Deploy output sanitization filters and human review mechanisms post-deployment to prevent personal data disclosure in service outputs.Providers deploying AI services trained on personal data
  • +3 more in the table below

Should not do

1
  • Do not collect or ingest non-public communications, content behind authentication, or paid content under publicly available data criteria.Organizations collecting web data for AI model development

Who must do what

The obligations under South Korea - Public Data Processing Guide, most serious first. Not legal advice — verify against the official text before relying on it.

#WhoRequirementBy whenWhereSeverity
1AI developers and service providers processing publicly available personal dataConduct and document Legitimate Interest Assessments or Data Protection Impact Assessments tailored to AI use cases before processing public data.Prior to data processing—Recommended
2Organizations collecting web data for AI model developmentDo not collect or ingest non-public communications, content behind authentication, or paid content under publicly available data criteria.Prior to data collection—Recommended
3Organizations developing or deploying AI systemsEstablish an AI privacy governance structure with designated privacy leadership to oversee dataset sourcing, retention, and de-identification.——Recommended
4AI developers processing publicly available datasetsRemove direct identifiers and scrub sensitive personal information from publicly collected datasets prior to model ingestion.Prior to model ingestion—Recommended
5Organizations scraping web data for AI developmentEvaluate website terms of service and robots.txt protocols before scraping personal data from public online sources.Prior to web scraping—Recommended
6AI developers training models on personal dataImplement technical safeguards during model training to limit the memorization and subsequent exposure of personal data.During model development—Recommended
7Providers deploying AI services trained on personal dataDeploy output sanitization filters and human review mechanisms post-deployment to prevent personal data disclosure in service outputs.Prior to service deployment—Recommended
8AI service providers operating public-facing servicesEstablish reporting channels and redress mechanisms allowing data subjects to exercise rights regarding personal data in AI models.Upon service deployment—Recommended
9AI developers maintaining and updating deployed modelsRe-assess privacy risks and perform data-exposure testing on models whenever model retraining occurs.Upon model retraining—Recommended
10AI developers processing sensitive personal dataApply default restrictions and high scrutiny when processing sensitive personal data, unique identifiers, or data belonging to minors.Prior to data processing—Recommended

© Regulations.AI · updated on 20 Sep 2026 · reviewed against official sources on 9 Sep 2026 using Gemini 3.6 Flash