Return of confidential information clause

Sample clause

the end of a due diligence process between Fernhill Consulting and Marlow Logistics, a fictional freight business in Brisbane

1. Return or Destruction. Within 14 days after receiving a written request, or within 14 days after this agreement ends, the Receiving Party must return or destroy all Confidential Information in its possession or control, including all copies, notes and analyses derived from it. 1.1 Physical samples and original documents must be returned rather than destroyed. 2. Backups. Clause 1 does not require deletion of a copy held in a routine system backup that cannot reasonably be isolated. Any such copy remains subject to clause 8 until it is deleted in the ordinary course of the Receiving Party's backup cycle, and must not be restored for any purpose other than disaster recovery. 3. Retained Copies. The Receiving Party may retain one copy of the Confidential Information where it is required to do so by law, by a regulator, or by its professional insurer, and must tell the Disclosing Party what it has kept and why. 4. Certificate. Within 5 business days of complying with clause 1, the Receiving Party must give the Disclosing Party a certificate signed by an officer confirming what was returned and what was destroyed.

Sample wording, not legal advice.

Variants

What to negotiate

• Return or destroy, and who chooses

  Disclosing parties often want the choice, because returning a prototype and destroying a spreadsheet are different outcomes. Receiving parties want to destroy, since shipping material back costs money and returns nothing to the sender. The practical settlement is destruction by default, return for physical items and originals, with the disclosing party able to direct otherwise in the request.

• The backup carve out

  No standard backup system lets an operator pull one counterparty's files out of a nightly snapshot. Receiving parties ask for an express carve out; disclosing parties accept it once they understand the alternative is a promise that will simply be broken. The carve out should be paired with a continuing confidentiality obligation over the retained copy and a bar on restoring it for any other purpose.

• Whether a certificate is required

  A certificate signed by an officer turns an unverifiable promise into a document somebody has put their name to, which changes how seriously the task is treated internally. Receiving parties resist only where the deadline is unrealistic. Five business days after completing the work is usually enough, and naming the method of destruction adds little burden.

• Derived materials and notes

  Analyses, models and summaries built from the information are often more useful than the source files. Disclosing parties want them covered expressly. Receiving parties ask that internal board papers and legal advice referring to the material be excluded, which is reasonable, provided those documents stay subject to the confidentiality obligation.

The risk of leaving it out

Without the clause there is no deadline, no method and no proof, so material stays on laptops and shared drives indefinitely with nobody responsible for it. When a leak happens years later, the disclosing party finds that the other side was never obliged to return anything, and that the confidentiality obligation it relied on may have already expired.

Deletion promises that cannot be kept

A clause requiring deletion of every copy is common and rarely achievable. Backups run on cycles, disaster recovery systems replicate across sites, and email archives are retained under separate policies, often because a regulator requires it. Signing up to delete everything means signing up to a breach, which helps nobody. The honest version carves out routine backups, keeps them under the confidentiality obligation until they age out, and bars restoring them for any purpose other than disaster recovery. That gives the disclosing party a real protection instead of an unenforceable promise, and it gives the receiving party something its own technology team can actually implement.

Lawful retention and personal information

Advisers, auditors and regulated businesses often must keep engagement records for a fixed period, and insurers frequently require the same. A clause with no retention exception forces those parties either to breach the contract or to breach their own obligations. Where the material includes personal information, the Privacy Act 1988 and the Australian Privacy Principles also apply, and they include an obligation to destroy or de identify personal information that is no longer needed for a permitted purpose, subject to other legal requirements. A return of materials clause that ignores privacy leaves the receiving party balancing two sets of rules with no guidance.

Where it sits in a generated document

The document generator writes an agreement as numbered content, so the return obligation usually appears as a sub clause under confidentiality, with the backup carve out and the certificate as further sub clauses. The generated text is written from the description it is given and it never prints citations, so any deadline or statutory reference in a draft has to be checked before the document is used. Describing the backup carve out in the prompt is worth doing, because a plain request produces the unachievable version.

Documents that carry this clause

Mutual NDAA robotics company and a British parts maker want to look inside each other before agreeing to anything. Both sides are handing over trade secrets, which is the only real reason to make an NDA mutual.Consulting agreementAn advisory firm reviews three bakeries over seven weeks. What makes this agreement useful is not the fee clause but the two clauses that say what the advice is not.Employment contractA full time ongoing contract for an operations coordinator on $86,000 plus $10,320 of superannuation. Eleven numbered clauses, a leave table drawn from the National Employment Standards, and a notice table that scales with service.Employee confidentiality agreement with information classesMost employee confidentiality agreements treat every secret the same way. This one sorts information into four classes, gives each its own handling rule and its own survival period, and is executed as a deed so it still binds after the salary that supported it has stopped.

Questions people ask