Privacy and preparation
Supplier data processing route clarity: a 7-step route sheet
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Supplier data processing route clarity means knowing, in writing, who performs each step that touches your records, on whose instructions, where, what they can see and which document authorizes them. A processing partner described by role can be acceptable when the terms fix its obligations and give notice before it changes. Map seven steps on a route sheet before signing, and pause wherever identifiable records travel without a named authority.
Redaction
Supplier data processing
Key takeaways
- Route clarity is five answers per step: who performs it, on whose instructions, where, what they see and what authorizes it.
- A partner named only by role can be enough when the terms fix its obligations, keep a current list and give notice before changes.
- Labels mislead: under EU guidance, whoever decides why and how data is processed is the controller, whatever the contract says.
- Health and California personal data add instruments: business associate terms for de-identification and service provider contracts with fixed purposes.
- Ask for a route overview at assessment and a full route sheet at terms; deep vendor review before a deal exists rarely pays.
What does supplier data processing route clarity mean?
It means you can say, for every step that touches your records, who performs it, on whose instructions, where it happens, what the performer can see and which document authorizes it. Add one answer for the route as a whole: what can change after you sign, and whether you hear about it first.
The decision this page supports is narrow. A company weighing a data licensing deal has to decide whether the processing route described to it is clear enough to approve the scope and terms. It is not deciding whether to license at all, or where de-identification should ideally happen; it is deciding whether it knows enough about the hands its records will pass through.
Three kinds of evidence settle the question: the documents that describe the route, such as the agreement, a processing schedule or a list of processors; the permissions each step relies on, inside and outside the company; and a written answer to every gap. A route described only on a call or a slide is not yet clear.
Is a processing partner described only by its role clear enough?
Often yes, provided the terms fix what that partner must do and tell you before it changes. Naming a vendor feels like control, but the protection comes from obligations, notice and responsibility, and EU data protection law shows how those can work without a name in the main agreement.
Under Article 28(2) of the GDPR, a processor may not bring in another processor without the controller's prior specific or general written authorization. Where the authorization is general, the processor must tell the controller about intended additions or replacements, giving it the chance to object, and Article 28(4) requires the same data protection obligations to be passed down to that other processor by contract.
The European Commission's standard contractual clauses between controllers and processors (Implementing Decision 2021/915) turn this into two options: specific prior authorization, or general authorization with advance notice of changes. In either case the first processor keeps its list of other processors up to date and remains fully responsible to the controller for their performance.
Those rules govern personal data under EU law, but the pattern is a sound standard for any supplier. A role-based description is clear enough when four things are written down: the role and its tasks, the obligations that bind whoever fills it, a current list you can see on request, and notice before a change with a way to object. It is not clear enough when identifiable records will reach a party nobody will identify to you.
The route sheet: seven steps where someone touches your records
List every step between the first conversation and a delivered dataset and give each one the five answers; a step without them is where the route is unclear. The performer column shows a typical allocation in intermediary-led deals, not any agreement's terms, so replace it with what your documents say.
Two steps deserve the most care. De-identification is the last point at which identifiable records exist outside your control, so its performer, location and authority matter more than any later step. Onward sharing is the first point at which de-identified output reaches parties you never contracted with, so the license terms, not the processing terms, govern it. Fill in the sheet for your own deal:
| Step | Usually performed by | What the performer can see | Authority to check | Clarity test |
|---|---|---|---|---|
| Fit assessment | The intermediary, from your answers | Descriptions and counts, no records | Confidentiality terms | No records requested before terms |
| Inventory and field selection | Your system owners | Your own systems | Internal approval and software vendor terms | Field list agreed in writing |
| Extraction | Your team, or a helper using your access | Identifiable records | Admin rights and software vendor terms | Named account, scope and export log |
| Transfer or in-place access | Your team and the intermediary | Identifiable records in transit or at rest | Security and confidentiality terms | Method, encryption and storage location stated |
| De-identification | The intermediary or its processing partner | Identifiable records | Processor terms, plus business associate or service provider terms where needed | Performer, location and method in writing |
| Quality review and packaging | The intermediary or its processing partner | De-identified output | Agreement and processing schedule | Reviewers and re-identification checks named |
| Delivery and onward sharing | The intermediary, to licensees | The de-identified dataset | License grant and sublicensing terms | Permitted recipients and uses listed |
Which legal role does each party play along the route?
The role follows what a party actually does at each step, not what the contract calls it, so the same party can hold different roles at different points. Counsel makes the classification; the route sheet gives counsel the facts it needs.
EU guidance is explicit about the test. The European Data Protection Board's Guidelines 07/2020 treat controller and processor as functional concepts: the controller decides why and how data is processed, including essential means such as which data, for how long and who receives it, while practical choices such as software or detailed security measures can be left to a processor. A processor that goes beyond the controller's instructions infringes the GDPR.
In a licensing deal the roles shift along the route. A party that de-identifies records on your behalf and under your instructions looks like a processor for that step. Once it holds a de-identified dataset under a license and uses it for its own purposes, it acts for itself. Ask which steps each party performs for you and which for itself, and expect the documents to say so.
Health records add an instrument. HHS guidance says a HIPAA covered entity may use a business associate to de-identify protected health information on its behalf only to the extent the business associate agreement authorizes it, and an HHS FAQ treats de-identification as a use of that information. Once information is de-identified under the Privacy Rule it is no longer protected health information, although other laws can still apply.
California adds another. The California Privacy Protection Agency's 2023 regulations require a contract with a service provider or contractor to prohibit selling or sharing the personal information and to limit its retention, use and disclosure to the purposes the contract specifies; a vendor without a compliant contract is not a service provider or contractor under the CCPA.
Four route designs: who sees identifiable records, and what each requires
Choose the design by who must see identifiable records, because that sets the instruments you need and most of your effort. The table compares four common designs; the effort column counts work for your own team, which the company carries whatever the deal pays.
No design suits every company. Preparing in-house keeps identifiable records at home but moves the hardest work onto your staff; a processing partner adds capacity and tooling but adds a hand to the chain. What matters for clarity is that the design is chosen on purpose and written down, not inferred from whoever asked for the export first.
| Route design | Who sees identifiable records | Instruments usually needed | Your team's effort |
|---|---|---|---|
| You de-identify, then deliver | Only your staff | License terms and an internal method sign-off | High: method, tooling, review and residual-risk checks |
| The intermediary processes inside your environment | Your staff and named intermediary users | Processor or service provider terms and access rules | Medium: accounts, supervision and logs |
| The intermediary or its processing partner processes in a controlled environment | The intermediary and the partner | Processor terms with change notice; business associate terms for health records | Low to medium: exports, transfer and output review |
| The licensee processes after receipt | The licensee | Notices and contracts that permit transferring identifiable data | Low effort, but the heaviest permission burden |
The route clarity effort worksheet
Size the work of getting the route clear before you start it, because most of it falls on a few people for a few days. The worksheet lists the lines that usually carry the hours; fill the drivers with your own counts and keep the owner column honest.
At a glance
The route clarity effort worksheet
Illustrative: a 250-person property management company plans to license six years of maintenance work orders from two systems. Its route review comes to about 15 internal hours: 3 hours to list fields that carry tenant names, phone numbers and free-text notes, 4 hours for counsel to read the processor terms and two customer contract templates, 3 hours to confirm export rights with its two software vendors, 3 hours to agree the transfer method and storage location, and 2 hours for the approver to sign off the memo. The figures are invented to show the arithmetic; your counts set yours.
- Field map: which fields in each system carry personal or confidential details. Hours driver: number of systems and free-text fields.
- Contract read: processor terms, customer contract templates and privacy notices that govern the records. Hours driver: number of distinct templates.
- Vendor terms: export and automated-access rules for each software vendor. Hours driver: number of vendors and plans.
- Transfer plan: method, encryption, storage location and who holds the keys. Hours driver: data volume and whether records leave your environment.
- Gap questions: a written question for every blank on the route sheet, with the answers filed. Hours driver: number of blanks.
- Sign-off: the approver reads the memo and records a decision. Hours driver: number of approvers.
Should a supplier chase route clarity before a deal exists?
Only a little, because eligibility and indicative offers do not ensure selection, closing or any particular payout. Vendor audits, security questionnaires and contract redlines spent on a deal that never reaches terms are hours the company does not get back.
Stage the effort instead. At the assessment stage, ask for a one-paragraph route overview: which roles will touch records, whether de-identification happens before records leave your systems or after, and whether health or California personal data changes the instruments. At the terms stage, ask for the full route sheet, and do not sign while any step that sees identifiable records is blank.
The case for writing the route down at all is that provenance information goes missing quickly once data changes hands. The MIT Media Lab audit in Nature Machine Intelligence (2024) looked at more than 1,800 text datasets and counted license information missing for more than 70% of those on widely used hosting sites, alongside error rates above 50%. A route recorded at the moment of handoff is far easier to defend than one reconstructed after a question arrives.
The route decision memo: approve, clarify or pause
Record the decision on one page so the people who sign and the people who export work from the same route. Approve when every step that sees identifiable records has a performer, location and authority in writing and the terms include change notice. Clarify when a step is described by role without obligations or notice. Pause when identifiable records would move before signing, or when no document authorizes a step that sees them.
At a glance
The route decision memo: approve, clarify or pause
The memo covers one deal on one date, reports no study result and is general information for the decision, not legal advice. Its next evidence is usually a document: a processing schedule, a list of processors or a clause that answers a blank. Record these fields:
- Deal reference, date and the documents read, with their versions.
- Route sheet status: each of the seven steps marked written, described by role, or blank.
- Instruments confirmed: processor terms, business associate terms, a service provider contract or none, with clause references.
- Change rule: how you will hear of a new processor or location, and how you can object.
- Effort spent and remaining, by owner, from the worksheet.
- Decision: approve, clarify with the questions sent, or pause with the trigger to reopen.
- Next evidence needed and the person who owns it.
Where preparation sits in a SourceX licensing deal
In the signed documents, read against a few published facts. Data preparation is one of the steps SourceX runs for businesses licensing operational data to AI developers; the others are sourcing and qualification, rights review, contracting, delivery and payment. The process opens with a short assessment of the company, and whether it qualifies can be seen without uploading any data.
For the route itself, the published facts name two possible hands for de-identification, SourceX itself or its processing partner, and two places a large delivery can be: the seller's own storage, or encrypted drives in shipment, since SourceX does not host multi-terabyte datasets. Scope and terms are approved, and the agreement signed, by the company before any record is delivered; from that point SourceX may use, sublicense and distribute the de-identified dataset to whatever extent the agreement permits. Ask for the route sheet's answers during contracting, especially for any step that sees identifiable records, and rely on the signed documents rather than this summary.
Frequently asked questions
Does a data licensing intermediary have to name its processing partner?
Not always in the main agreement. A partner can be described by role when the terms bind it to the same obligations, a current list is kept and you get notice before a change, which is how EU processor rules work. Ask for the identity and location of any party that will see identifiable records before you sign.
Is a processing partner a subprocessor of our company's data?
It can be, for steps it performs on your behalf, such as de-identification under your instructions. For steps it performs for itself or for a licensee, it is not acting for you. Counsel classifies each step, and the route sheet records what each party actually does.
Do we need a business associate agreement for outside de-identification?
If you are a HIPAA covered entity and an outside party will de-identify protected health information for you, HHS guidance says it may do so only as the business associate agreement authorizes. Once properly de-identified, the information is no longer protected health information, though state law and contracts can still apply.
Can the party that prepares our data keep using it afterwards?
Only as the documents allow. A processor acting on your instructions should not use your records for its own purposes, and California's regulations require service provider contracts to limit retention and use to specified purposes. Use of the de-identified dataset after licensing is governed by the license grant, so read both sets of terms.
What should we do if the processing route changes after signing?
Use the change rule in the terms: notice of a new processor or location and a window to object. If the draft terms have no change rule, ask for one before signing, because a route that can change silently is not clear.
Sources
- GDPR Article 28(2) bars a processor from engaging another processor without prior specific or general written authorization, with notice of changes and a chance to object; Article 28(4) flows obligations down. Source
- Commission Implementing Decision 2021/915 standard contractual clauses offer specific or general authorization of sub-processors; the processor keeps its list current and stays fully responsible. Source
- EDPB Guidelines 07/2020 treat controller and processor as functional concepts; essential means stay with the controller, non-essential means such as software can be left to a processor. Source
- HHS guidance: a covered entity may use a business associate to de-identify PHI on its behalf only to the extent the business associate agreement authorizes it. Source
- HHS FAQ: de-identifying PHI is a use of PHI, and information de-identified under the Privacy Rule is no longer PHI, subject to other applicable law. Source
- CCPA regulations (2023 final text, section 7051): service provider contracts must bar selling or sharing and limit retention, use and disclosure to specified purposes; without one a vendor is not a service provider. Source
- The MIT Media Lab audit of 1,800+ text datasets (Nature Machine Intelligence, 2024) found license omission above 70% and error rates above 50% on popular hosting sites. Source
See if your company qualifies
A short company assessment. No data uploads are needed.