Privacy and preparation
Dataset buyer access revocation: what happens when a pilot ends
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
When a data pilot ends, every access path the buyer received should close on a date fixed before delivery, copies outside the supplier's control should be deleted or returned, and both sides should hold evidence: the approved package and its file digests, the named recipients, access logs, revocation records and a signed deletion certificate. Revoking credentials alone does not remove data already downloaded.
License terms
Dataset buyer access
Key takeaways
- Set the expiry of every link, role, token and key when you issue it, not when the pilot ends.
- Revocation stops new access; deletion or return of existing copies needs a contractual duty and a certificate.
- A manifest of SHA-256 digests lets both parties confirm the exact package received and later the exact package deleted.
- Decide in the pilot agreement which derived outputs survive; aggregate findings usually do, anything that can rebuild records usually does not.
- Conversion to a full license and legal retention are written exceptions, never silent extensions of pilot access.
What should happen to a buyer's dataset access when a pilot ends?
Every access path the buyer was given should close on a date fixed before the first file moved, every copy outside the supplier's control should be deleted or returned, and both parties should finish with a short evidence file that proves what was delivered, who touched it, when access ended and how the copies were destroyed. Dataset buyer access revocation is a technical step; closure is the paper trail that shows it happened.
Most pilots fail this test quietly rather than dramatically. A signed URL issued for a week, a bucket role added for a data scientist, an API token in a notebook and a copy on a laptop all outlive the evaluation unless someone has listed them. The contract may say the pilot ended on a given date, but the systems only know what someone configured.
The rule that keeps this manageable is to decide closure at the moment access is granted. Each credential gets an expiry when it is issued, each package gets a fingerprint when it is built, and each person who receives data is named. Closing the pilot is then a matter of checking a list, not reconstructing history.
Which access paths did the pilot open, and how does each one close?
List each channel separately, because each one expires differently and none of them reaches files the buyer already downloaded. The table below covers the common channels in data pilots; the expiry behavior noted for each is what the vendor or protocol documentation describes, and your configuration may be shorter.
Two points from the documentation matter for planning. Amazon S3 presigned URLs created with the AWS CLI or SDKs can last up to seven days, the S3 console caps them at 12 hours, and a URL stops working at its own expiry or when the signing credentials expire, whichever comes first. The Delta Sharing protocol lets a recipient profile carry an expiration time for its bearer token, but the field is optional, and the specification says a token without one can be treated as never expiring.
| Access path | How it ends | What closing it does not reach | Closing evidence |
|---|---|---|---|
| Signed or presigned download link | Expires at the time set when it was signed, or earlier if the signing credentials expire | Any file already downloaded through the link | Link issue log with expiry time, plus storage access logs showing each download |
| Shared bucket, role or account in the supplier's cloud | A person removes the grant or the role; nothing ends on its own unless an expiry was configured | Copies the buyer made into its own storage | Change record showing the grant removed, and the account list after removal |
| Open sharing protocol token (for example a Delta Sharing recipient profile) | Token expiration time, if one was set, or revocation on the sharing server | Tables the recipient already read into its own environment | Recipient record with expiration, revocation timestamp and query history |
| Hosted workspace or clean room the supplier controls | Supplier disables the workspace users and exports | Results the buyer was allowed to export during the pilot | User list at close, export log, workspace shutdown record |
| Encrypted file transfer or encrypted drive | Supplier withholds or destroys the decryption key; the drive is returned or sanitized | Decrypted working copies made before the key was withdrawn | Key disable or deletion record, drive return receipt, sanitization certificate |
| API key or service credential | Key is revoked or rotated on the supplier side | Responses already cached or stored by the buyer | Key revocation timestamp and the last successful call in the logs |
Why switching off access does not end the buyer's obligations
Revoking credentials stops new reads; it does nothing about the records, extracts and derived work already on the buyer's side. Ending the pilot properly therefore needs two separate decisions: when access closes, and what the buyer must do with everything it already holds.
The second decision belongs in the pilot agreement, not in a closing email. A common pattern is delete or return, with the supplier choosing which. Data protection law uses the same structure for service providers: under Article 28(3)(g) of the GDPR, a processor contract must require the processor, at the controller's choice, to delete or return the personal data when the service ends and to delete existing copies unless Union or Member State law requires storage. A data pilot buyer is often not a processor, so that article may not apply directly, but it is a useful model of how to write the clause.
Derived work needs its own line. During an evaluation the buyer may create embeddings, labeled subsets, evaluation scores, error analyses or a fine-tuned checkpoint. Decide in advance which of these survive the pilot. Aggregate findings about whether the data was useful usually should, because they are the point of the pilot. Anything from which records can be reconstructed, including model weights trained on the sample, usually should not, unless the parties sign a license that says otherwise.
Keep the categories distinct when you write this up. Who could access the files is a security question. Whether personal information could be shared is a privacy question. Who owns the records, and what rights the license granted for how long, are contract questions. Ending access answers only the first.
The access expiry and evidence closure checklist
Use the checklist below as the closing record for one pilot. Each row has an owner, and the pilot is closed only when every row has evidence attached or a written exception signed by the person named in the agreement.
| Item | What to record | Owner | Evidence that closes it |
|---|---|---|---|
| Approved version | Package identifier, record count, date range and the internal approval that released it | Supplier data owner | Release approval and package manifest stored together |
| Least-necessary recipients | Named people and service accounts that received access, and why each needed it | Buyer pilot lead | Recipient list signed at start and confirmed at close |
| Expiry set at issue | Expiry date and time on every link, token, role and key | Supplier security engineer | Credential register showing an expiry for each entry |
| Integrity fingerprints | A SHA-256 digest for each file in the package | Supplier data engineer | Manifest of digests sent separately from the files |
| Key separation | Where decryption keys are held and how they were sent | Supplier security engineer | Key custody note; key never in the same channel as the data |
| Transfer and access logs | Every download, query and export during the pilot | Supplier security engineer | Log extract for the pilot window, retained with the closing record |
| Receipt confirmation | Buyer's statement of which files arrived and their digests | Buyer pilot lead | Signed receipt whose digests match the manifest |
| Revocation | Time each path was closed and by whom | Supplier security engineer | Change records and a failed access test after close |
| Deletion or return | Every location copies were held, including backups, and the method used | Buyer security owner | Certificate of deletion naming systems, method, date and signer |
| Derived work | Which outputs the buyer keeps and which it destroyed | Buyer pilot lead with supplier counsel | Written statement mapped to the agreement's survival clause |
How do both sides prove which files moved and who could open them?
Agree on a manifest before the first transfer and compare against it twice: when the buyer confirms receipt and when it certifies deletion. The manifest lists each file with its size, record count and a SHA-256 digest. FIPS 180-4, the federal secure hash standard, describes these digests as a way to detect whether a message has changed since the digest was generated, so matching digests show both sides are talking about the same package.
Access limits are verified the same way: a list at the start, a list at the end, and logs in between. NIST SP 800-53 gives a vocabulary that security teams already use. Its account management control asks organizations to notify account managers when accounts are no longer required and when system usage or need-to-know changes, and its disable-accounts enhancement covers accounts that have expired. A pilot ending is exactly that event, so the supplier's existing account process can absorb it if the pilot accounts were registered properly at the start.
Encryption keys give the supplier a second lever. If the package was encrypted with a key the supplier controls, disabling or deleting that key makes remaining ciphertext copies unreadable. On AWS KMS, for example, a key scheduled for deletion waits between 7 and 30 days, during which it cannot be used for cryptographic operations and deletion can still be cancelled. Treat key deletion as a backstop, not a substitute for the buyer's deletion certificate, because decrypted working copies are outside its reach.
For deletion itself, borrow the record format from NIST SP 800-88, the media sanitization guideline. Revision 2 says a certificate of sanitization should be completed for each item sanitized and can be paper or electronic. A buyer deleting a pilot dataset will rarely sanitize whole drives, but the same fields work: what was removed, from which systems, by what method, verified how, by whom and when.
Worked example (illustrative): a 60-day evaluation of support tickets
The following case is illustrative and invented to show the sequence. A software company lets an AI developer evaluate de-identified support tickets for 60 days. The package is 8 files, about 40,000 tickets, delivered through presigned links valid for 72 hours, with an encrypted copy available through a shared bucket role for three named analysts.
- Day 0: the supplier's data owner signs the release approval and the manifest with 8 digests. Links are issued with a 72-hour expiry and the bucket role is created with an end date on day 60.
- Day 2: the buyer returns a signed receipt listing 8 files and matching digests. One analyst downloaded the files to a workstation, which is recorded as an extra location to clear at close.
- Day 45: the buyer reports that the data is useful and asks to extend. The supplier declines to extend pilot access and starts a separate license discussion instead, so the closure date stays fixed.
- Day 60: the bucket role expires. The supplier's engineer tries the role and records the access denial, then disables the encryption key and schedules it for deletion.
- Day 67: the buyer delivers a deletion certificate covering the bucket copy, the analyst workstation, a scratch volume and a backup set on its normal rotation, and a statement that it keeps only an aggregate evaluation report with no records in it.
- Day 70: the supplier's data owner reviews all 10 checklist rows, files the closing record with the release approval, and marks the pilot closed.
The exceptions: conversion to a full license, and records the law says to keep
Two situations justify keeping data past the pilot date, and both should be handled as written exceptions rather than silent extensions.
Conversion to a full license is the first. Even when both parties intend to sign, close the pilot access and issue new access under the new agreement. Carrying pilot credentials into production blurs which terms governed which use and leaves pilot-era recipients on the access list. If the gap between pilot and license matters commercially, agree a short written extension with a new end date rather than letting the old one pass.
Retention required by law or by a litigation hold is the second. The Article 28 wording itself recognizes that law can require storage. When the buyer says it must keep something, ask for the legal basis, the exact records held, who can access them and when the hold ends, and record that as a scoped exception in the closing file.
Backups are a practical exception rather than a legal one. Many buyers cannot surgically delete from backup sets. A workable term is that backup copies are not restored for any use and expire on the normal rotation, with the certificate stating the rotation end date.
Which closeout findings should hold back the next delivery?
Some findings at closeout mean the next delivery to this buyer should wait until they are resolved. Treat them as release blockers rather than follow-ups.
In each case the supplier's security engineer and the release approval owner should review the record together, and counsel should read the agreement before any demand is made to the buyer. A narrower next delivery, fewer recipients or a supplier-hosted workspace instead of downloads are reasonable conditions for continuing.
- Receipt digests that do not match the manifest, or files the buyer cannot account for.
- A recipient on the access logs who was never on the approved list.
- No deletion certificate, or a certificate that omits locations the logs show the data reached.
- Evidence that pilot data was used to train or tune a model when the pilot allowed evaluation only.
- A request to keep records with no legal basis or end date.
- Personal information found in the package that the de-identification step should have removed; that moves the matter to privacy review before anything else happens.
How does a pilot close inside a SourceX-run license?
Inside a SourceX license the agreement comes first: the company approves scope and terms and signs before delivery, and SourceX's later use, sublicensing and distribution of the de-identified dataset are bounded by that document. Pilot access, deletion duties and surviving outputs are therefore set in a signed document rather than negotiated at the end.
For the businesses it works with, SourceX handles rights review, contracting, data preparation and delivery. Large datasets stay in the seller's own storage or ship on encrypted drives rather than being hosted by SourceX, which keeps the revocation lever, the storage access or the key, with the company that owns the records. Finding out whether a company qualifies begins with a brief assessment, and no records have to be uploaded for it.
Frequently asked questions
Does revoking a buyer's credentials delete the data it already downloaded?
No. Revocation stops new access through that path, but files already downloaded, cached or copied stay where they are. Deletion or return of those copies has to be a contractual duty with a certificate as evidence.
Should a pilot agreement let the buyer keep its evaluation results?
Usually it should keep aggregate findings, such as accuracy scores or an error analysis that contains no records, because those are what the pilot was for. Anything from which records can be rebuilt, including embeddings or model weights trained on the sample, should be deleted unless a license says otherwise.
How long should pilot access links last?
As short as the transfer needs. A link only has to work long enough for the named recipient to download the package; longer-running access is better handled through a named role with a fixed end date that the supplier can check.
What should a deletion certificate for a pilot dataset include?
The package identifier, every system and location that held copies including backups, the deletion method, how deletion was verified, the date and the name of the person signing. Model the fields on the certificate of sanitization in NIST SP 800-88.
What if the buyer wants to extend the pilot at the last minute?
Agree a written extension with a new end date and the same recipients, or close the pilot and grant new access under a license. Letting the end date pass without a decision leaves access open with no terms behind it.
Sources
- Amazon S3 presigned URLs can be valid up to seven days when created with the CLI or SDKs, up to 12 hours from the console, and expire early if the signing credentials expire. Source
- The Delta Sharing protocol's recipient profile can carry a bearer token expiration time; the field is optional and a token without it can be treated as never expiring. Source
- GDPR Article 28(3)(g) requires processor contracts to provide for deletion or return of personal data at the end of the services, at the controller's choice, unless law requires storage. Source
- FIPS 180-4 specifies SHA-256 and describes hash digests as a way to detect whether a message has changed since the digest was generated. Source
- NIST SP 800-53 Rev. 5 control AC-2 covers notifying account managers when accounts are no longer required and when system usage or need-to-know changes; AC-2(3) covers disabling expired accounts. Source
- AWS KMS key deletion uses a waiting period of 7 to 30 days, during which the key cannot be used for cryptographic operations and deletion can be cancelled. Source
- NIST SP 800-88 Rev. 2 says a certificate of sanitization should be completed for each item sanitized and may be a paper or electronic record. Source
See if your company qualifies
A short company assessment. No data uploads are needed.