15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →
Templates / Contract

Free Non-Disclosure Agreement Template

A Non-Disclosure Agreement covers what counts as confidential information, how both sides can use and share it, how long duties last, and what happens if it leaks.

Non-Disclosure Agreement template preview

Language:

en

Last updated:

October 2026

Share template

Data exports, system access, pricing, and customer lists can’t get shared on a handshake, because one loose file can turn into a leak or an internal mess later. This Non-Disclosure Agreement gives both sides the same promises in writing, in a verdigris and violet layout under Raleway headings and Roboto body text.

The wording defines confidential information broadly, including things that don’t get labeled “confidential”, then ties that to how the information can be used, who it can be shared with, and what care is expected around access and credentials. The later sections cover the usual exceptions, how long the duty continues, what gets returned or deleted when discussions end, and a clear line on ownership and what sharing does not license.

  • Mutual promise Opens by making the NDA bilateral, so both sides protect the other’s confidential information under the same terms.
  • What is confidential Spells out what counts as confidential, including commercial details and practical items like exports, dashboards, code, notebooks, and credentials.
  • How we protect it Limits use to evaluating or carrying out the discussed work, and restricts sharing to people who need access under equivalent duties.
  • Returning and deleting Covers what gets returned or deleted at the end, and what limited copies can stay for backup, audit, or legal retention.
  • If something goes wrong Explains what either side can seek if information leaks or gets misused, and ends with the signature block.

In Plutio, you fill in your names, dates, and any terms that need to match how the work will actually run, then send it for signature. Once both sides sign online, the finished contract sits with the agreement as a record you can point back to if a question comes up later.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What to include in a Non-Disclosure agreement

PartWhat it covers

This agreement is a mutual promise

Establishes that the confidentiality duty runs both ways, so either side can share information without one-sided risk.

What is confidential

Defines what the agreement treats as confidential, including commercially sensitive business information and technical materials like exports, schemas, code, and access credentials.

How we protect it

Limits how either side can use the other’s information and sets expectations for safeguarding access, including sharing only on a need-to-know basis under matching obligations.

What is not confidential

Lists the standard carve-outs, like public information, prior knowledge, lawful third-party disclosure, and independent development, plus what happens when disclosure is legally required.

How long this applies

States when the agreement starts, what kinds of sharing it covers, and that confidentiality continues after discussions or work ends for the period you agree in writing.

Returning and deleting

Covers returning or deleting shared materials on request or at the end of work, while allowing limited retention for backup, audit trails, or legal compliance.

Who owns what

Keeps ownership with the original party and clarifies that sharing information doesn’t grant broader rights to use methods, code, data, or internal materials beyond the agreed purpose.

If something goes wrong

Explains the remedies if a breach happens and includes the Signature so the agreement can be accepted and stored with signed terms.

Who it is for

Data & AI consultancies, agencies, and in-house teams sharing access, exports, code, or commercial details while scoping work in data engineering, machine learning, business intelligence, or AI automation.

The contract in full

This agreement is a mutual promise. Both of us will look after the other’s confidential information on the terms below, so we can move quickly without risking a leak or a misunderstanding.

What is confidential

Confidential information is anything either of us shares that a reasonable person would treat as private or commercially sensitive, even if it is not marked “confidential”. This includes pricing, margins, customer and supplier lists, contracts, internal reporting definitions, operating volumes, product plans, roadmaps, security practices, and any non-public financials.

It also includes data exports, database samples, screenshots, warehouse and shipping reports, BI dashboards, queries, schemas, field mappings, model features, prompts, code, notebooks, runbooks, and any login details, API keys, tokens, or other credentials. Notes I take from what you share, and notes you take from what I share, count too.

How we protect it

Each of us will use the other’s confidential information only to evaluate, plan, or carry out the work we are discussing together. I will not use your data, reports, or access for anything else. You will not use my methods, code, or internal materials for anything else.

Each of us will share the other’s confidential information only with people who genuinely need it for that purpose, and only if they are bound to protect it at least as tightly as this agreement. Each of us will protect the other’s confidential information with the same care we use for our own sensitive information, including keeping credentials secure and limiting access to what is needed (for example, read-only access where that fits the task).

What is not confidential

Confidential information does not include information that is already public through no fault of the receiving person. It also does not include information the receiving person already knew before it was shared, as long as that earlier knowledge was gained without breaking any duty of confidence.

It is not confidential if it is received lawfully from someone else who had the right to share it. It is not confidential if it is developed independently without using the other side’s confidential information.

If either of us is required to disclose information by a regulator, court, or other legal process, that disclosure is allowed. Where notice is allowed, the person required to disclose will give the other side a heads-up and will share only what is required.

How long this applies

This agreement applies to confidential information shared between us from the date the last of us signs it. It covers information shared in writing, orally, on calls, in meetings, and through access to systems.

The duty to protect the other side’s confidential information continues after our discussions end or after any work ends. It continues for the period we agree in writing.

If we do not go ahead with work together, this agreement still applies to anything we shared while exploring it.

Returning and deleting

If the other side asks, or when our work together ends, each of us will promptly return or delete the other side’s confidential information that we hold, including copies. That includes exports, documents, credentials, code samples, and any files created from or containing the other side’s confidential information.

Each of us can keep a limited copy where we genuinely need it for reasonable archiving, backup, audit trails, or to meet a legal or compliance duty. Anything kept still stays confidential under this agreement, and access stays limited to people who need it for that retention purpose.

Who owns what

Nothing in this agreement transfers ownership. Each of us keeps all rights in our own confidential information, materials, know-how, and intellectual property.

Sharing information under this agreement does not grant the other side a licence to use it beyond evaluating or carrying out the work we are discussing. For example, if you share data and reporting definitions, I can use them to analyse and build within the agreed work. If I share code patterns, templates, or methods, you can use them only to evaluate my work unless we agree something broader in writing.

Any separate service terms we agree later can set different usage rights, but this agreement alone does not.

If something goes wrong

Both of us understand that a leak or misuse of confidential information can cause harm that money alone may not fix. The harmed side may ask for an order to stop the breach or prevent further disclosure, as well as claim damages.

This applies equally to both sides.

Signature

Legal Notice: Please consult legal advice and carefully review the content of this contract template before implementing this template in your business.

Questions about this contract template

What should a mutual NDA include?

A mutual NDA usually defines what counts as confidential for both sides, how that information can be used, who it can be shared with, and what standard of care applies. This template also covers exceptions, return or deletion, ownership, and remedies if a breach happens.

What counts as confidential information if nothing is marked confidential?

Confidential information can still include anything a reasonable person would treat as private or commercially sensitive, even without a label. The template also names practical examples like exports, dashboards, code, notebooks, and credentials.

How long does a non-disclosure agreement last?

An NDA can start from the date the last party signs and cover information shared in writing, orally, or through system access. This template keeps the confidentiality duty in place after discussions or work end for whatever period the parties agree in writing.

Does an NDA cover data exports, code, and login credentials?

An NDA can cover technical materials as well as business details. This template explicitly includes exports, database samples, queries, schemas, field mappings, notebooks, runbooks, and credentials like API keys and tokens.

What happens to confidential information when the work ends?

An NDA often requires return or deletion of the other side’s confidential information, including copies, when asked or when work ends. This template also allows limited retention for archiving, backups, audit trails, or legal and compliance duties, with confidentiality still applying.

What can you do if confidential information leaks?

A confidentiality breach can cause harm that money alone may not fix, so agreements often allow the harmed party to seek an order to stop the breach as well as claim damages. This template makes that remedy mutual, applying equally to both sides.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away