← Back to concept explainers

Concept Fable

Data processing agreement

Conclusion first:A Data Processing Agreement (DPA) is a contract that sets out how a vendor or processor handles personal data on behalf of a customer. It typically specifies controller and processor roles, processing purposes, data types, security measures, sub-processors, cross-border transfers, data subject requests, breach notification, audit rights, and deletion or return upon contract termination. When enterprises procure AI / Agents, the DPA is a foundational document for privacy review, especially when the system touches customer records, employee data, call recordings, tickets, or sales leads.

Data Processing Agreement, DPA · Procurement/Privacy

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

Fable

Before the clinic hires someone to copy medical records, it first writes down clearly who can view them, how much can be copied, and where the copies go

The medical clinic in the south of the city had more and more patients, and medical records filled the cabinets. The director brought in a team of copyists to organize the old records into an index so doctors could find them easily on follow-up visits. The copyists were quick, and on the first day they moved three boxes of files. The young apprentice thought it was convenient, but the director frowned: medical records are not ordinary ledgers; they contain names, prescriptions, family matters, and illnesses. Some said that since the copyists were paid to do the work, of course they would not misuse it. Others suggested giving a few verbal reminders not to take the records to taverns. The director did not agree.

He had both parties sit down and write a detailed agreement: the copyist could only handle medical records per the clinic's instructions, could not keep copies without authorization, could not give them to anyone without consent, had to notify in case of a leak, and had to return or destroy them when done.

The detailed agreement also specified which medical records could leave the room, which could only be copied in the inner chamber, how out-of-town copyists were managed, and who was responsible for responding when patients came to ask. The copying team found it troublesome, but because of this they knew the boundaries.

After the organizing began, the clinic checked the records once a week. The scribes were not the owners of the medical records; they only handled them on behalf of the clinic, and all uses had to return to the original commission.

Later, another clinic handed over medical records based on trust alone, and by the time something went wrong and they asked about responsibility, it was already too late. The detailed agreement of the South City Clinic seemed clumsy, but it made cooperation auditable and accountable.

The curator understood that when outsiders handle sensitive materials, the real protection is not a phrase like "we will be careful," but writing roles, purposes, boundaries and remedies into enforceable commitments.

The copying team later wanted to hand part of the archives to acquaintances outside the city to rush the work. The detailed agreement came in handy: without the clinic's consent, they could not pass it on again; if outsiders truly needed to participate, the list, locations, and protection measures all had to be written out first.

When patients asked who had touched their medical records, the clinic could produce the records. The director could also require the copying team to prove that duplicates had been destroyed. Cooperation did not slow down much because of this, but it shifted from 'I trust you' to 'I can check whether you acted according to the agreement.' The more sensitive the medical records, the more these details need to be written down in advance, rather than patched in after something goes wrong.

Reveal

This story is about: data processing protocols

A Data Processing Agreement (DPA) is a contract that sets out how a vendor or processor handles personal data on behalf of a customer. It typically specifies controller and processor roles, processing purposes, data types, security measures, sub-processors, cross-border transfers, data subject requests, breach notification, audit rights, and deletion or return upon contract termination. When enterprises procure AI / Agents, the DPA is a foundational document for privacy review, especially when the system touches customer records, employee data, call recordings, tickets, or sales leads.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Medical clinic records: personal data and sensitive business data
  • Scribe: a vendor handling data on behalf of the client
  • Verbal reminder: trust without contractual constraint
  • Detailed terms: Data Processing Agreement
  • Can only act on the clinic's instructions: the processor acts on the controller's instructions
  • Out-of-town wonton maker: subprocessors and cross-border/external processing arrangements
  • Return or destruction: data return and deletion obligations after termination

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.

controllerprocessorsubprocessorsGDPRdata transferSCCs

Related distinctions

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

京ICP备2026014272号