← Back to concept explainers

Concept Fable

Purpose limitation

Conclusion first:Purpose limitation is a privacy protection principle: personal data should be collected for explicit, specific purposes and must not later be repurposed for incompatible uses without justification.

Purpose Limitation · Privacy

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

Fable

A roster kept only for bridge repairs

When the river town built the bridge, it registered residents' names, addresses, and crossing needs. Everyone was willing to fill it in because the purpose was clear: arranging temporary ferries and construction notices. Years later, when the town held a market, the chamber of commerce wanted to use this roster to push stall advertisements. The clerk assistant said the data was complete and organizing the list would take only a cup of tea. The residents were furious when they found out. They were not opposed to the market; they had submitted their information to build the bridge, not to have hawking follow them to their doorsteps.

The mayor first added a line at the end of the notice: "Information may be used for other matters." This did not solve the problem; instead, it made all later registrations untrustworthy.

The town re-established the rule: when collecting material, state the specific purpose, and subsequent use must be checked for compatibility; if incompatible, new grounds, new consent, or new collection is required.

The document register was also given purpose labels. Bridge repair materials could only serve construction notices, traffic arrangements and legally required retention, and could not be casually sent to marketing, profiling or training newcomers.

Later, when the chamber of commerce needed to contact residents, they switched to a voluntary sign-up form. Fewer people signed up, but trust was preserved.

The chamber of commerce was not reconciled and proposed running the advertisement only once. The mayor still did not agree. He had the chamber re-post a notice recruiting people willing to receive market news, keeping only bridge repair follow-up on the old roster. Later, fewer people signed up, but no one doubted anymore that the ferry notices carried hidden sales pitches.

Later, when the town built another canal, the first line of the registration form stated the purpose and duration. Seeing that the old roster had not been taken away and sold, residents were more willing to fill in the new form. Trust is not won by a broad notice, but by honoring the agreed boundary every time data is used. The mayor also had the clerk regularly purge expired rosters. Once the bridge was finished and the aftermath settled, whatever could be deleted was deleted, and whatever had to be kept came with a stated reason. Only when residents saw that their data had a destination and an endpoint were they willing to keep cooperating with public affairs. This boundary later became the first rule of registration affairs in River Town.

The mayor understood: once you get the material, it doesn't belong to you forever. The boundary of use must follow the material; being able to use it does not mean you should.

Reveal

This story is about: purpose limitation

Purpose limitation is a privacy protection principle: personal data should be collected for explicit, specific purposes and must not later be repurposed for incompatible uses without justification.

For example, a register created for bridge maintenance cannot simply be taken for marketing, model training, or reuse by third parties unless there is a new legal basis, valid consent, or a compatibility assessment.

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 purpose limitation
  • 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.

lawful basisconsentdata minimizationprivacy notice

Related distinctions

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

京ICP备2026014272号