← Back to concept explainers

Concept Fable

Personal data

Conclusion first:Personal data refers to information related to an identified or identifiable natural person. As long as it can directly or indirectly point to a specific person, it may constitute personal data.

Personal Data · Privacy

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

Every sheet of paper may point to a person

The port service station used to treat only names and ID numbers as privacy. Other receipts, chat records, locations, device numbers, and purchasing habits were all treated as ordinary business materials. The counter staff often said: this doesn't have a full name on it, so it's nothing serious.

The station launched a document assistant that could aggregate customer letters, customer service records, and contracts. It quickly learned to piece fragments into a complete customer profile. The stationmaster was delighted at first, feeling he could finally see clearly what customers needed.

Once an assistant generated a report. No name appeared, yet it wrote "the night-shift nurse who lives at South Pier, complained about cold chain last week, and uses a certain model of equipment." Colleagues knew at a glance who it was. The report did not leak the name, but it had already pointed the person out.

The stationmaster first required names to be masked. But the combination of location, occupation, time and behavior in the report could still be linked to an identifiable natural person. Someone else suggested masking only ID numbers, but the problem did not disappear, because device numbers, order trajectories and complaint content linked together could still trace the person back.

They reclassified the data: anything that could be linked to an individual, alone or in combination with other information, was treated as personal data. In classification they looked not only at field names, but also at usage scenarios, combinable materials and information already in the recipient's hands.

Before the document assistant calls data, it first judges the purpose and legal basis, trims displayed fields by role, and the duty log also avoids storing identifiable combinations. Business did not stop; it was just that each document was no longer casually copied into the public register, passed to an outside document box, or taken out of the port just because it "had no name."

The service station finally accepted a broader definition: any information that can point to a person must be treated as personal data. A name is only the most obvious signpost; many small paths together can also lead to the same person's door.

Later, whenever the station made a new form, they would ask one question: does this piece of data alone point to a person, does it point to a person when combined with other data, and does it become easier to point to a person once handed to an outsider. After asking these three questions, many fields that had been collected casually simply disappeared.

Reveal

This story is about: personal data

Personal data refers to information related to an identified or identifiable natural person. As long as it can directly or indirectly point to a specific person, it may constitute personal data.

Examples include names, mobile phone numbers, email addresses, device identifiers, orders, work orders, chat records, location, account behavior, and information that is not obvious on its own but can identify an individual when combined.

Metaphor mapping

  • Old ledgers, warehouses, or counters: customer, employee, contract, and work order data accumulated in the enterprise
  • Bronze bird, puppet, assistant, or study boy: enterprise Agent / RAG systems connected to business data
  • Naive fixes: deleting only names, pasting slogans, signing confidentiality pledges, or simply banning tools
  • Failure moment: data continues to spread through logs, training, retrieval, outsourcing, cross-border transfer or tool calls
  • Structural solution: build classification, permissions, minimization, auditing, retention and technical controls around personal data
  • Final insight: privacy governance must follow the flow and use of data, not just guard a single entrance

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

PIIdata subjectGDPRcontrollerprocessor

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号