Privacy and preparation
The secure transfer, rights and quality distinction: three verdicts per file
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
A secure transfer proves a file moved intact and unread by outsiders; it does not prove the company may license the contents or that they fit the buyer's task. Treat secure delivery, right to license and buyer fit as three verdicts with separate evidence, owners and sign-offs: transfer logs and checksums settle the first, contract and notice review the second, an acceptance test on the delivered file the third.
License terms
The secure transfer
Key takeaways
- A secure transfer settles one verdict of three: secure delivery, not the right to license or buyer fit.
- NIST's Privacy Framework separates cybersecurity risk from privacy risk that arises during authorized processing, which is what a licensing delivery is.
- HHS treats a cloud provider holding only encrypted health data as a business associate, and the EDPB says encryption cannot protect a transfer when the importer holds the keys.
- Every combination of pass and fail across the three verdicts can occur; only one of the eight should release a dataset.
- De-identification informs all three verdicts and settles none, because identifiability depends on the recipient and contracts survive redaction.
What does a secure transfer prove, and what does it leave open?
A secure transfer proves that a file moved intact and that outsiders could not read it on the way. It does not prove that the company may license what is inside, or that the contents fit the buyer's task. Those are three verdicts, and each needs its own evidence, its own owner and its own sign-off.
Call them secure delivery, right to license and buyer fit. Secure delivery covers confidentiality and integrity in transit and at rest: who could read the data, whether it arrived unchanged, who received the key. Right to license covers ownership, customer and vendor contracts, privacy notices, software terms and the privacy basis for the processing. Buyer fit covers whether the delivered records serve the task in the signed scope: the fields, history, labels and quality the buyer's acceptance test asks for.
NIST's Privacy Framework explains why the first verdict cannot stand in for the second. It says cybersecurity risks arise from unauthorized activity related to the loss of confidentiality, integrity or availability, while privacy risks arise as a byproduct of intentional, authorized data processing. A licensing delivery is authorized processing by design, so a flawless transfer removes one class of risk and leaves the other exactly where it was.
Why encryption cannot answer a permission question
Encryption controls who can read data; it does not decide who is allowed to have it or what they may do with it. Regulators in three jurisdictions make the point in ways a licensing team can use.
In the United States, HHS says a cloud provider that maintains electronic protected health information for storage is a HIPAA business associate, not a conduit, even if it stores only encrypted data and never views it. The encryption changes nothing about the relationship or the agreement it requires. HHS's breach notification rule shows what encryption does change: notification duties attach to unsecured protected health information, and HHS guidance names encryption and destruction as the methods that make it secured. Encryption alters the consequences of a failure, not whether a disclosure was permitted.
In the EU, the EDPB's Recommendations 01/2020 on supplementary measures for international transfers say transport encryption and data-at-rest encryption, even taken together, do not constitute a supplementary measure that ensures an essentially equivalent level of protection if the data importer is in possession of the cryptographic keys. A licensee has to decrypt the data to train or evaluate on it, so when personal data goes to a recipient in a third country, encryption in transit and at rest cannot be the safeguard that makes the transfer lawful.
In the UK, the ICO lists seven principles in Article 5 of the UK GDPR: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality (security); and accountability. Secure transfer evidence speaks to one of the seven. The other six need records of their own, and none of them is produced by a transfer tool.
The evidence crossover matrix: which record settles which verdict
Most preparation records settle exactly one verdict, and the ones that seem to settle several usually inform them without deciding any. Mapping every record to the verdicts it settles, informs or says nothing about shows the gaps before a buyer finds them.
Read the matrix by column. The security column fills quickly, because transfer tools produce records automatically. The rights column depends on documents only people produce: a review of contracts, notices and software terms, and a signed scope. The fit column depends on a test run against the file that actually shipped. Only the de-identification review touches all three columns, and it settles none of them, which makes it easy to mistake for a universal pass. The matrix below scores eight common records.
| Record | Secure delivery | Right to license | Buyer fit |
|---|---|---|---|
| Transfer log with recipient identity and time | Settles, for transit | Silent | Silent |
| Checksum manifest matched on receipt | Settles, for integrity | Silent | Informs: the agreed files arrived, not that they work |
| Encryption-at-rest and key release record | Settles, for storage and key custody | Silent | Silent |
| Rights review of contracts, notices and software terms | Silent | Settles, for the sources reviewed | Silent |
| Signed license with scope and permitted use | Silent | Settles, for what it names | Informs: defines the task the fit test uses |
| De-identification method and residual risk review | Informs: less harm if a copy leaks | Informs: one input to the privacy basis, not ownership | Informs: may remove fields the task needs |
| Schema and completeness validation | Silent | Silent | Informs: format and coverage only |
| Acceptance test on the delivered file | Silent | Silent | Settles, for the agreed task |
Eight pass and fail combinations, one release: a scored example set
Because the verdicts are independent, every combination of pass and fail can occur, and only one of the eight combinations should release a dataset. The scored set below gives an illustrative case for each, drawn from the kinds of systems suppliers license, so a review team can check that its process would catch every failing pattern.
Two patterns deserve attention. Cases B, C and D pass security and fail something else, and they are the ones a security-led process waves through: the delivery evidence is complete and convincing. Case E fails only security, the failure a rights-led or quality-led process tends to miss. All eight are illustrative scenarios, not records of real deals.
| Case | Secure delivery | Right to license | Buyer fit | Illustrative example and verdict |
|---|---|---|---|---|
| A | Pass | Pass | Pass | Work orders sent by SFTP, rights cleared, acceptance test met: release |
| B | Pass | Pass | Fail | Encrypted bucket of sales call notes; the buyer's task needs outcome codes the CRM never captured: hold |
| C | Pass | Fail | Pass | Checksummed help desk export that includes a reseller's tickets its contract bars disclosing: hold |
| D | Pass | Fail | Fail | Clean transfer of an export whose software terms restrict reuse, with too little history: decline |
| E | Fail | Pass | Pass | Right records, rights cleared, sent as an unencrypted email attachment: stop and re-deliver |
| F | Fail | Pass | Fail | Shared-link upload of a cleared archive missing the fields in scope: stop, then re-scope |
| G | Fail | Fail | Pass | Useful ticket history including client records held as a processor, sent over open FTP: stop and escalate |
| H | Fail | Fail | Fail | Unreviewed mailbox dump on a personal drive: stop and escalate |
Who signs each verdict, and why the signatures stay apart
Each verdict should be signed by the person whose evidence it rests on, and no signer should countersign a verdict on the strength of another's evidence. A security engineer can attest that the channel, the encryption and the key release worked; that attestation is worthless as rights evidence, however thorough it is.
At a glance
Who signs each verdict, and why the signatures stay apart
Assign the owners before preparation starts, because each verdict needs evidence that is cheap to create early and expensive to reconstruct later. The split below is a default for a supplier preparing records for license; smaller companies can combine roles, but they should still keep three separate records:
- Secure delivery: the security or IT owner signs, resting on the transfer log, the checksum match on the recipient's side and the key release record.
- Right to license: counsel or the rights owner signs, resting on the review of customer and vendor contracts, privacy notices and software terms, and on the signed scope.
- Buyer fit: the data owner signs with the buyer's acceptance criteria in hand, resting on the acceptance test run against the delivered file, not a sample or an earlier version.
- Privacy processing: the privacy specialist records the de-identification method and residual risk review, which feeds the rights and fit verdicts but replaces neither.
Does de-identification bridge the three verdicts?
No. De-identification is an input to all three verdicts and a settlement of none, which is exactly why it is tempting to treat it as all three.
Identifiability depends on who receives the data, which no transfer record can see. The ICO's pseudonymisation guidance notes that pseudonymised data shared without the additional information may be anonymous in the recipient's hands, depending on whether that recipient could realistically re-identify people. Under HIPAA's expert determination method, 45 CFR 164.514(b)(1), a qualified expert must determine that the risk of identification is very small for an anticipated recipient, alone or with other reasonably available information, and document the methods and results. The same file can pass for one recipient and fail for another, however securely it travels.
De-identification also creates no ownership or license right. A customer contract that bars disclosure still bars it after names are removed, and a software vendor's terms still apply to the export. On the fit side, removing identifiers can strip the very fields a task depends on. Fitness is relative to purpose even in regulation: for high-risk AI systems, Article 10(3) of the EU AI Act asks that training, validation and testing data be relevant and sufficiently representative, and as error-free and complete as the system's intended purpose allows. That standard cannot be checked from a transfer log.
Final-delivery checklist: three sign-offs that cannot borrow from each other
Release a dataset only when all three verdicts are signed on the final file, each by its own owner, with its own evidence attached. Use the checklist below at the last gate; a missing line holds the release rather than being waived by a strong line elsewhere.
At a glance
Final-delivery checklist: three sign-offs that cannot borrow from each other
Checklist · 8 items
- Secure delivery: the channel and recipient identity match the agreement, the recipient's checksums match the manifest, and the key was released to the named recipient only after receipt was confirmed.
- Secure delivery: access granted for the transfer has been closed or set to expire, and the record of that closure exists.
- Right to license: every source system in the package appears in the rights review, with contracts, notices and software terms checked and any excluded data listed.
- Right to license: the package matches the signed scope file by file; nothing outside the scope travelled with it.
- Privacy processing: the de-identification method and residual risk review are recorded for this version and this recipient, not carried over from a sample.
- Buyer fit: the acceptance test ran on the delivered file and passed against the criteria in the signed scope.
- Buyer fit: any field removed or generalized during preparation was checked against the task, and the buyer was told where coverage is reduced.
- Three signatures from three owners are attached to the delivery record, and none relies on another's evidence.
0 of 8 ticked. Tick each item as you go.
The release decision, its limits and what to measure next
Decision: never treat a secure transfer as approval to license. Release only when secure delivery, right to license and buyer fit each carry their own signed evidence on the final file; hold or re-scope when any one is missing, however strong the other two look.
The limits are real. The matrix and the eight cases are an editorial framework and illustrative scenarios, not a measured study of deliveries, and the regulator material is quoted for its own jurisdiction: HHS and the eCFR for HIPAA entities in the United States, the EDPB for transfers under the EU GDPR, the ICO for the UK GDPR, the EU AI Act for high-risk systems only, and NIST as voluntary guidance. This page is general information, not legal advice; counsel should apply the actual agreements and governing law to the specific records.
The evidence still needed is local: how often each of the eight patterns appears in your own deliveries, how long each verdict's evidence takes to produce, and which verdict most often holds a release. A review log with one line per verdict per delivery answers all three within a few cycles.
How the three verdicts line up with a SourceX deal
SourceX's own pages keep the three verdicts apart. Its trust page says dataset diligence packets are prepared per dataset because rights, privacy processing and quality differ between datasets, and it describes a rights review of whether the supplier owns the original records and can license them, including any customer or vendor contract limits, with the supplier confirming its rights in the agreement. Its legal framework page says the relevant software terms are checked for each source, and if a tool's terms restrict a use, that data is excluded or the deal is scoped to fit.
Delivery is a separate step on those pages: after SourceX gives the go-ahead, the trust page says the data is "extracted, transferred and de-identified through approved processing routes", and large datasets can stay in the supplier's own storage or ship on encrypted drives. An acceptance review of the delivered data comes before Closing. A supplier who keeps its own three-verdict record arrives at each of those steps with the evidence already in hand. The first step is a short company assessment with no data upload, and an assessment is not an offer.
Frequently asked questions
Does an encrypted transfer make a data license compliant?
No. Encryption protects confidentiality in transit and at rest, but it does not create the right to share the data or decide what the recipient may do with it. HHS, for example, treats a cloud provider holding only encrypted health data as a business associate all the same.
Is a checksum match proof that the right data was delivered?
It proves the files that arrived are the files listed in the manifest, unchanged. It does not prove the manifest lists the right records, that the company may license them, or that they pass the buyer's acceptance test.
Who should sign off on a data delivery?
Three owners: the security or IT owner for the transfer, counsel or the rights owner for the right to license, and the data owner for buyer fit against the signed scope. Each signs on their own evidence for the final file.
Does de-identification settle the rights question?
No. It reduces identifiability for a particular recipient, but customer contracts, vendor terms and ownership still apply to the de-identified records. It can also remove fields the buyer's task needs, so it informs all three verdicts without settling any.
What should happen when only the security check fails?
Stop and re-deliver over an approved channel, then record what was exposed and to whom. The rights and fit verdicts may stand, but the failed transfer may need its own incident review under the agreement and the law that applies.
Sources
- NIST Privacy Framework v1.0 says cybersecurity risks arise from unauthorized activity related to loss of confidentiality, integrity or availability, while privacy risks arise as a byproduct of authorized data processing. Source
- HHS says a cloud provider that maintains ePHI for storage is a HIPAA business associate, not a conduit, even if it stores only encrypted data and does not view it. Source
- HHS's Breach Notification Rule page says notification duties apply to unsecured PHI and that HHS guidance names encryption and destruction as the methods that secure it. Source
- EDPB Recommendations 01/2020 (version 2.0) say transport and at-rest encryption, even together, are not an effective supplementary measure when the data importer holds the cryptographic keys. Source
- The ICO lists the seven UK GDPR principles in Article 5, of which integrity and confidentiality (security) is one. Source
- The ICO notes that pseudonymised data shared without the additional information may be anonymous in the recipient's hands, depending on whether the recipient could realistically re-identify people. Source
- 45 CFR 164.514(b)(1) requires a qualified expert to determine that identification risk is very small for an anticipated recipient and to document the methods and results. Source
- Article 10(3) of Regulation (EU) 2024/1689 asks that data sets for high-risk AI systems be relevant, sufficiently representative and, to the best extent possible, free of errors and complete in view of the intended purpose. Source
- SourceX's trust page: diligence packets are prepared per dataset because rights, privacy processing and quality differ; rights review covers ownership and contract limits; data is extracted, transferred and de-identified through approved processing routes. Source
- SourceX's legal framework page says software terms are checked for each source and restricted data is excluded or the deal is scoped to fit. Source
See if your company qualifies
A short company assessment. No data uploads are needed.