What happens when the engagement ends?
Every NDA contemplates an ending. The relationship runs its course, the deal closes (or doesn't), the employee leaves, the vendor engagement wraps. At that point, the recipient still has the disclosing party's confidential material in their files, their email, their backups, and potentially in third-party systems the recipient doesn't control.
The return or destruction clause sets the rules for what happens next. A well-drafted clause defines what must be returned or destroyed, who is responsible, the timeline, and what carve-outs apply for material the recipient is legally required to retain (financial records, litigation holds, regulatory requirements).
A poorly drafted clause creates one of two problems. Either it demands more than the recipient can deliver (full destruction of every copy including backups, which is technically impossible in modern IT environments), or it provides no obligation at all, leaving the recipient holding confidential material indefinitely with no defined endpoint.
What sensible drafting looks like
A defensible return-or-destruction clause does five things: names the trigger (typically written request from the discloser, or termination of the agreement); names the obligation (return, destroy, or recipient's choice); names the materials covered (originals, copies, derivatives, summaries); names a reasonable timeline (30 days is common); and provides an archival carve-out for material the recipient must retain for legal, regulatory, or backup reasons.
The archival carve-out is the part most aggressive NDAs omit. Modern companies operate under records-retention obligations from multiple sources: Sarbanes-Oxley for public-company financial records, GDPR for personal data, HIPAA for health information, regulatory record-keeping for financial services, and litigation holds whenever a dispute is reasonably anticipated. Backup systems automatically copy data to redundant storage that cannot be selectively purged.
A return clause that requires destruction of all copies in any form conflicts with these obligations. Sensible drafting acknowledges that the recipient may retain copies required by law or stored in routine backups, with those copies remaining subject to the confidentiality obligations.
What this looks like in real contracts
Why backup carve-outs matter
Modern IT infrastructure makes complete destruction of digital data physically impractical. Email backups, cloud-storage version history, database transaction logs, off-site disaster recovery, and immutable cloud archives all create copies that cannot be selectively deleted on demand without violating other obligations or destroying unrelated material.
Sophisticated NDAs acknowledge this reality. The archival carve-out doesn't release the recipient from confidentiality — it simply recognizes that retained copies are subject to the same obligations as the original disclosure, and that the recipient cannot certify destruction of something they cannot physically destroy. Without this carve-out, signing a strict destruction clause is signing a representation the recipient cannot truthfully make.
What NDASentry flags in this category
4.1 Missing return-or-destruction obligation
The agreement contains no provision addressing what happens to confidential material at the end of the engagement. The recipient has confidentiality obligations with no defined endpoint and no procedure for releasing the material. This is more common in poorly-drafted NDAs than recipients realize.
4.2 Certification of destruction requirement
The agreement requires the recipient to certify in writing — sometimes by sworn affidavit — that all copies have been destroyed. Without an archival carve-out, this creates a false certification risk. Without a defined scope of search, the certification is open-ended in time and effort. Combined with a short timeline, this pattern is a common drafting overreach.
4.3 No backup or archival carve-out for destruction
The destruction obligation does not exclude routine backups, legally-required records, or records subject to litigation hold. The recipient is either forced to violate the NDA (by retaining required copies), violate other obligations (by destroying records they must retain), or sign a representation they cannot truthfully make.
We are scoring a corpus of public NDAs to publish prevalence data for each pattern in this taxonomy. The findings — including what percentage of real NDAs contain the patterns above, broken down by industry and jurisdiction — will appear here when the study is complete.