This document is the privacy policy setting out the personal information that datalaw.kr actually processes. It contains, in order, the items required by article 30(1) of the Personal Information Protection Act ("PIPA") and Enforcement Decree article 31(1).
This English version is a translation for readers who do not read Korean, and where it differs from the Korean version, the Korean version prevails.
Each section carries a folded note headed "Why this item is written this way". Privacy policies look much alike from one company to the next, but what actually sets them apart is not the wording but the judgement behind choosing that wording. Rather than copying someone else's policy, this page sets out the provisions and the reasons for each choice alongside the text. It is published in this form on the view that people doing the same work can then see what they need to change to fit their own circumstances.
1. Items, purposes and retention periods of the personal information processed
| Category | Items processed | Purpose | Retention period |
|---|---|---|---|
| Newsletter subscription | Email address | Sending the newsletter | Until the subscription is cancelled |
| Email inquiries | Sender's email address, name, and what you write in the body of the email | Replying to the inquiry and reviewing the matter | Three years after the reply and review end (where the inquiry leads to an advisory relationship, SEUM Law's retention standards apply) |
| Inquiry form | Email address for the reply, what you write and send, name (or a role title, optional), company and role (optional), type and urgency of the matter (optional), the address of the page from which the form was opened, and the inquiry number assigned on receipt | Replying to the inquiry and reviewing the matter, checking for conflicts of interest, and linking follow-up handling of the same inquiry | Three years after the reply and review end (where the inquiry leads to an advisory relationship, SEUM Law's retention standards apply) |
| Site access | IP address, browser and operating system information, requested address, and the page you came from (referrer) | Hosting and security of the site (blocking attacks and overload), and compiling visit statistics | Subject to the log retention policy of the hosting and security provider (Cloudflare); the operator views only aggregate statistics, not individual records |
| Situation guide usage counts | The category (incident and investigation (A), overseas headquarters (B), transactions (C), enforcement database situations (S1–S5), penalty surcharge calculator (FC), breach notification and reporting checker (BC), breach damages judgment finder (DM), or general) and the type of action (viewing a guide, following a link, moving to the inquiry screen, clicking an email link, downloading material, displaying a calculation or checking result, opening the report view, moving to the notice template, form submission result, or arriving from a link in an AI answer (ChatGPT)); the number of emails the server accepted for sending | Improving the guide paths, tools and inquiry function, and checking for inquiries that failed to send | Only approximate daily counts are stored, with no individual identifier or inquiry number; deleted automatically after 90 days |
| Data table view statistics | The conditions chosen in a data table (provision breached, year, type of disposition) and whether a search term was entered (yes or no) | Finding out which provisions and years of the data are actually used, so that the data can be improved | Only daily aggregate values are stored, and they are deleted automatically after 90 days |
This site has no membership sign-up, log-in or comments. The only fields users fill in directly are the newsletter sign-up and the inquiry form. Personal information not listed in the table above is not collected, and the site is not a service directed at children under 14.
Why this item is written this way — Why the policy states what is not collected
The first table is where privacy policies most often go wrong. Many published policies keep items that are not actually collected (date of birth, mobile number and so on) because they were left in a standard template. The Personal Information Protection Commission has pointed out, in enforcement cases, differences between a privacy policy and actual processing, and the first evaluation item under the privacy policy evaluation scheme introduced in 2023 (article 30-2 of the Act) is "whether the matters to be included are properly set out".
So this policy also carries the sentence that what is not in the table is not collected. With that one line in place, the operator, too, can see clearly that the policy has to be amended whenever something new comes to be collected. The last row (data table view statistics) was in fact added on the day this policy was published.
The retention period for inquiry emails is set at three years because, even where an inquiry does not lead to advice, a record of who made contact about what matter has to be kept so that conflicts of interest can be checked.
When the inquiry form was opened in September 2026, the same order was followed once more. Until then the only field on this site where users could enter anything directly was the newsletter sign-up, and the form changed that. So the "inquiry form" row was added to the table and published first, and the form was opened after that. What is received through the form is forwarded by email and stays in the mailbox; it is not stored in a separate database. That is why its retention period is stated as the same as for email inquiries. The address of the page from which the form was opened is received as well because the operator needs to know which article you read before getting in touch in order to improve that article. It is listed separately in the table because it is a value the form attaches automatically, not something users fill in. The inquiry number is also attached automatically on receipt and is used only to link the email to the same matter in the internal inquiry log; it is not sent to visit statistics.
The last row (data table view statistics) is where that principle actually operated. On 13 September 2026, when this policy was first published, the feature had been built but not switched on, so the table had no row for it, and the policy said only that it had been "prepared but not switched on". When the feature was switched on the same day, the row was added first and deployed together with it. The policy has to change first and the processing has to follow; if it happens the other way round, this document becomes a document that differs from reality.
The design of the counts came from the same thinking. If you want to know what people searched for, the easiest way is to store the search terms as they are. Some people may type a company name or a case into the search box, however, so the search term is built not to be sent at all. Only predefined values such as provision, year and type of disposition are accepted, and anything not in that format is discarded whole by the server. That is enough for improving the data.
2. Provision of personal information to third parties
This site does not provide the personal information it collects to third parties. It provides it only where a law makes special provision or an investigative authority requests it through lawful procedure, and even then it responds to the minimum extent after checking the basis and scope of the request.
3. Entrustment of personal information processing
| Entrustee | Work entrusted | Place of processing |
|---|---|---|
| Stibee (스티비 주식회사) | Sending the newsletter and managing the subscriber list | Korea |
| Cloudflare, Inc. | Hosting, security and visit statistics for the site; human verification, processing and email forwarding for the inquiry form; forwarding of email sent to the inquiry email address given on this site (datalaw.kr) | Section 4 below |
If an entrustee changes, this policy is amended and published again.
Cloudflare's self-serve terms of use incorporate its Customer Data Processing Addendum (DPA). Under that addendum the operator of this site is the controller and Cloudflare is the processor. Cloudflare processes personal information to the extent needed to perform the agreement, and it publishes a list of sub-processors and a procedure for notifying changes.
Why this item is written this way — What separates provision to a third party from entrustment
Both amount to "handing data to someone else", but article 17 (provision) and article 26 (entrustment) have different requirements. The dividing line is whose purpose the processing serves. If the recipient uses the data for its own purposes, it is provision. If the recipient processes the data only for the entrusting party's purposes and within the scope of its instructions, it is entrustment. Entrustment is in principle possible without consent but has to be disclosed in the privacy policy (article 26(2) and (3) of the Act), and the entrusting party answers for violations committed by the entrustee (article 26(7)).
Outsourced newsletter sending and hosting are typical cases of entrustment. What is often missed in practice is that hosting and cloud services are entrustment too. It is easy to think of it as renting a server rather than handing over personal information, but as long as users' access information is processed on that server, it has to be listed as entrustment. How liability is divided when an incident occurs in an entrustment relationship is set out separately in the note on entrustment and liability.
4. Cross-border transfer of personal information
This site is delivered over the network of Cloudflare, Inc. Inquiries pass through a processing function on Cloudflare Pages, a Cloudflare Worker and an email forwarding service, and are forwarded to the operator's receiving mailbox. Email sent directly to the inquiry email address given on this site (datalaw.kr) is also forwarded to the same mailbox through Cloudflare's email forwarding service (Email Routing). The table below covers not only access information but also the inquiry items processed along the way.
| Item | Details |
|---|---|
| Personal information transferred | IP address, browser and operating system information, requested address and the page you came from; the email address, content, optional entries, address of the page the inquiry came from and human verification token from the inquiry form; and the sender and recipient addresses, subject, body and attachments of email sent to the inquiry email address (datalaw.kr) |
| Countries, timing and method of transfer | The United States and the processing locations of Cloudflare's global network. The Developer Platform sub-processor locations published by Cloudflare include the United States, the European Economic Area (EEA), the United Kingdom, Japan, Australia, India, Canada and Singapore. Access information is sent over the information and communications network when you visit the site, the inquiry content when you submit an inquiry, and the email when you send one |
| Recipient | Cloudflare, Inc. (contact: privacyquestions@cloudflare.com) |
| Recipient's purpose of use and period of retention and use | Hosting, security and statistics for the site; human verification, processing and email forwarding for the inquiry form; forwarding of email sent to the inquiry email address. The inquiry processing function does not keep the body in a separate database or in Workers Logs, and Logpush is not used. Email is forwarded only to a fixed destination verified in the Cloudflare account, and the Email preview feature, which stores the sent original for about seven days, is not used. Email sent to the inquiry email address (datalaw.kr) is likewise only forwarded to the same fixed destination. Cloudflare states that its email forwarding service does not store or read the content of email, but forwarding records (sender and recipient addresses, subject, message identifier and processing result) remain in Cloudflare's analytics feature for 31 days. Retention in the receiving mailbox follows the period in section 1, and other service logs follow Cloudflare's retention policy and the Customer Data Processing Addendum |
| How to refuse the transfer and the effect of refusal | Because this site can be accessed only through the network above, the only way to refuse the cross-border transfer is to stop accessing the site. To refuse transmission through the inquiry form or forwarding of email, you can get in touch by telephone instead of using the form or email. The newsletter subscription can be cancelled separately |
The ground for the cross-border transfer is article 28-8(1)(3)(a) of the Personal Information Protection Act. Disclosing the matters in each item of article 28-8(2) in the table above is what that ground requires.
Why this item is written this way — Relying on disclosure in the privacy policy rather than consent
A cross-border transfer needs one of the grounds listed in article 28-8(1). For the hosting and forwarding work needed to deliver the web pages users request and to receive and reply to inquiries, this site relies on item (3)(a). The ground is not established merely because consent is hard to obtain, and processing beyond what is needed to provide the service has to be examined for a separate ground. The anonymous counts do not collect individual visit histories or inquiry content.
This is where practice often goes wrong. Once item (3)(a) is chosen, all five matters in article 28-8(2) have to be stated. Many policies leave the last of them, "the method and procedure for refusal and the effect of refusal", empty or say only "contact customer service". If there is in fact no way to refuse, the right course is to say that there is none. That is why the last row of the table above is written as it is.
Even services that appear to use only Korean providers often involve cross-border transfers through CDNs, email delivery tools or error-collection tools. The problems that arise when the Korean entity of a foreign group uses headquarters systems as they are are discussed in the gap between headquarters policies and Korean law.
5. Procedure and method of destruction
When the retention period expires or the purpose of processing is achieved, personal information is destroyed without delay. If you cancel your newsletter subscription, your email address is deleted from the subscriber list. Inquiry emails are deleted by a method that makes them unrecoverable, starting with those whose retention period has passed. Electronic files are permanently deleted by a method that makes restoration impossible, and any printouts are shredded or incinerated.
6. Rights and duties of data subjects and legal representatives, and how to exercise them
Users may at any time request access to, correction or deletion of, or suspension of processing of their personal information, and may withdraw consent.
- How to exercise: If you make a request by email (hyunsub.lee@datalaw.kr), action is taken within 10 days and you are told the result.
- Cancelling the newsletter: You can cancel it yourself through the unsubscribe link at the bottom of any email you receive. It takes effect immediately, with no separate confirmation step.
- Representatives: A legal representative or a person you have authorised may make a request on your behalf. In that case a power of attorney is checked.
7. Installation and operation of devices that collect personal information automatically, and how to refuse them
This site does not use cookies. Nor does it create and store any value that identifies visitors.
- Visit statistics: The site uses Cloudflare Web Analytics, which collects only page-level aggregates, without cookies or individual identifiers. If you block JavaScript in your browser, you are left out of these aggregates, and you can still see all the content of the site in that state.
- Searching and filtering the data tables: The tables work by downloading everything when the page opens and then filtering it, so the characters you type into the search box are not themselves sent. Only which provision, year and type of disposition you chose, and whether you entered a search term (yes or no), are sent. They are accumulated only as daily totals and deleted automatically after 90 days. Access IP, browser information and cookies are not used for these counts, so individual users cannot be traced. If you block JavaScript, you are left out of these counts too. You can still read the public content of the tables, but interactive features such as search and filters are limited.
- Situation guide usage counts: Only the guide path (A, B, C, enforcement database situations S1–S5, penalty surcharge calculator FC, breach notification and reporting checker BC, breach damages judgment finder DM, or general) and the type of action are counted, by date. S1–S5 are only broad topic divisions: the notification clock, entrustment structures, exfiltration by insiders, the safety measures defence, and the scope of the surcharge calculation. In the calculator, the checker and the judgment finder, the only things counted are the fact that a result was displayed on screen, the fact that the report view was opened, and the fact that you moved to the notice template. If you arrive through a link in a ChatGPT answer, the marker attached to the address (
utm_source=chatgpt.com) is used to count one "arrival from a link in an AI answer" and nothing more. The page address, the content of the question and the referrer are not sent. Values you enter, such as revenue, dates, numbers of people and incident conditions, and the results of calculations, checks and searches, are not sent. Separately from the browser's count of successful form submissions, the number of emails the server accepted for sending is also kept, only as a daily total, to check for failed submissions. Inquiry content, email addresses, inquiry numbers, search terms, decision numbers, company names, page addresses, IP addresses and browser information are not put into these counts, and no cookie or visitor identifier is created. Because individual users' paths are not linked, these counts are not numbers of unique visitors or rates of conversion into engagements. If you block JavaScript in your browser, you are left out of the on-screen action counts, but a successful form submission is still included in the server's acceptance count. - Display setting: Your choice between light and dark display is stored inside your browser (local storage). This value is not sent to the server.
- Human verification on the inquiry form: To keep the form from being abused by automated programs, the site uses Cloudflare Turnstile. For its security assessment Cloudflare processes signals such as the access IP address, TLS fingerprint, browser information (User-Agent), site key and origin domain, but it does not access the email address or inquiry body written in the form, and does not store or transmit them. This site's processing function does not send the access IP as an additional item in the verification request. It uses only whether verification succeeded, and it does not separately store the response or any user identifier. The verification token expires after five minutes and can be used only once. Cloudflare's role and the items processed are described in detail in the Cloudflare Turnstile privacy addendum.
Why this item is written this way — If no cookies are used, can this section be left out?
Article 30(1)(7) of the Act requires matters about automatic collection devices to be stated "only where applicable", so leaving this section out entirely when no cookies are used would not be a breach. It is kept nonetheless because the fact that there are none is itself information users need.
A site that writes about personal information would have that to explain first if it tracked visitor behaviour with cookies. So when measurement tools were chosen, not using cookies and not storing individual identifiers were made conditions. For the same reason, the table search statistics were built so that the search term itself is not sent. Knowing which provision was chosen is enough to improve the data.
8. Measures to ensure the security of personal information
- HTTPS is applied across the whole site to encrypt data in transit.
- Access to the subscriber list and inquiry emails is limited to the operator personally, and two-step verification is applied to the accounts.
- Content received through the inquiry form is not stored in a separate database; it is only forwarded to the operator's mailbox. The program that handles the forwarding does not record the content.
- The items collected are kept to the minimum needed for the purpose. The inquiry form does not ask for unique identification information or sensitive information, as those terms are used in PIPA. In the free-text field, please write only an initial outline of the matter, and send sensitive information or detailed material by the method you are given after the conflict check.
9. Chief privacy officer
| Item | Details |
|---|---|
| Chief privacy officer | Hyunsub Lee (lawyer, partner at SEUM Law) |
| Contact | hyunsub.lee@datalaw.kr · +82-2-562-3117 |
Inquiries, complaints and requests for redress concerning the processing of personal information can be made through the contact details above.
Why this item is written this way — A chief privacy officer exists even without a duty to designate one
The proviso to article 31(1) of the Act and Enforcement Decree article 32(1) allow a personal information controller that qualifies as a small business owner under Korean law not to designate a chief privacy officer. However, article 31(2) of the Act provides that in that case the business owner or representative becomes the chief privacy officer, so the conclusion "we have no duty to designate" does not turn into "we have no chief privacy officer". That is why this policy, too, gives a name and contact details.
The amended Act in force from 11 September 2026 added two things to this. Article 30-3, which states the representative's ultimate responsibility, was newly inserted. In addition, a business whose revenue or volume of personal information held meets the criteria in the Enforcement Decree must obtain a board resolution for the designation, change or removal of its chief privacy officer and report that designation, change or removal to the Commission (article 31(3)). The latter duty falls only on businesses that meet the size criteria, so it does not apply to this site. How the rules on holding the role together with another post and on designation actually apply is set out in combining the CISO and CPO roles.
10. Remedies for infringement of rights
If you need advice or redress for an infringement involving personal information, you can apply to the bodies below. You can use the same routes not only for processing by this site but also for disputes with other businesses.
- Personal Information Dispute Mediation Committee: 1833-6972 (kopico.go.kr)
- Personal Information Infringement Report Center (the Privacy Call Center run by the Korea Internet & Security Agency): 118 (privacy.kisa.or.kr)
- Korean National Police Agency cybercrime reporting system (ECRM): 182 (ecrm.police.go.kr)
How dispute mediation actually proceeds and what outcomes it produces is set out in the dispute mediation case search (Korean), which compiles every result handled by the Committee.
11. Changes to this policy
When this policy is changed, the changes and their effective date are published on this page. If a change is unfavourable to users, notice is given from seven days before the effective date.
| Effective date | Change |
|---|---|
| 14 November 2026 | Changed the inquiry email address given on the site to a datalaw.kr address. Stated that email sent to that address is forwarded through Cloudflare's email forwarding to the same mailbox as before, and that forwarding records (sender and recipient addresses, subject, message identifier and processing result) remain with Cloudflare for 31 days (sections 3, 4 and 9) |
| 14 November 2026 | Added "arrival from a link in an AI answer (ChatGPT)" to the action types in the situation guide usage counts. Only the fact of arrival is counted, and the page address, question content and referrer are not sent (sections 1 and 7) |
| 28 October 2026 | Added the breach damages judgment finder (DM) to the categories in the situation guide usage counts. Only the fact that a search result was displayed on screen is counted, and the conditions chosen and the results are not sent (sections 1 and 7) |
| 27 October 2026 | Added the penalty surcharge calculator (FC) and the breach notification and reporting checker (BC) to the categories in the situation guide usage counts. Listed in the action types clicking an email link, downloading material and displaying a calculation or checking result, which were already being counted, and opening the report view and moving to the notice template, which are newly counted (input values and results are not sent; sections 1 and 7) |
| 25 October 2026 | Deleted "Cyber Investigation Division, Supreme Prosecutors' Office: 1301" from the bodies offering remedies for infringement, and added the web address of the police reporting system (on 2 October 2026 the prosecutors' offices were reorganised into a new prosecution body (공소청), and that contact point could not be confirmed; no change to processing) |
| 29 September 2026 | Stated "checking for conflicts of interest" as a purpose of processing for the inquiry form, and added "inquiry number" to the items collected listed in the inquiry form's consent wording, so that the policy and the consent wording match (no change to processing) |
| 21 September 2026 | Added the inquiry number and the count of emails accepted by the server (inquiry content and inquiry numbers are not stored in statistics) |
| 21 September 2026 | Added the enforcement database situation guides (S1–S5) to the scope of the existing anonymous usage counts |
| 21 September 2026 | Expanded the explanation of the Cloudflare DPA and sub-processors, Turnstile security signals, inquiry processing logs and email forwarding settings |
| 21 September 2026 | Clarified the inquiry items forwarded, the right to refuse and the remedies, and added anonymous counts for the situation guides |
| 19 September 2026 | Reflected the inquiry form items and processing route (deployment history for that day checked) |
| 13 September 2026 | First established and published |
| 13 September 2026 | Added data table view statistics (sections 1 and 7); reflected in the same deployment that switched the feature on |
Frequently asked questions
Q. What personal information does datalaw.kr collect?
Q. Is personal information transferred outside Korea?
Q. How do I exercise my rights as a data subject?
Sources
- Personal Information Protection Act, article 30 (Establishment and disclosure of Privacy Policy): the items a privacy policy must contain
- Enforcement Decree of the Personal Information Protection Act, article 31 (Details of Privacy Policy and Methods for Disclosure Thereof): the matters delegated by article 30(1)(8) of the Act
- Personal Information Protection Portal: the portal run by the Personal Information Protection Commission, with guidance on drafting privacy policies and a channel for reporting infringements