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, how both sides can use and protect it, what’s excluded, how long the duty lasts, and what happens if there’s a breach.

Non-Disclosure Agreement template preview

Language:

en

Last updated:

October 2026

Share template

Exports get shared, credentials get issued, and a deal can’t move forward until both sides know the sensitive parts won’t leak. This non-disclosure agreement gives that moment clear wording, so pricing, customer lists, operating volumes, and technical material can be discussed without guessing where the line is. The pages sit under verdigris green headings in Raleway with Roboto body text, which keeps the document feeling like governance rather than a pitch.

The agreement opens by making the promise mutual, then defines What is confidential broadly enough to cover commercial details alongside schemas, queries, notebooks, runbooks, and access keys, even when nothing is stamped “confidential”. How we protect it limits use to evaluating, planning, or carrying out the work, and narrows sharing to people who need the information under matching obligations. The later sections spell out What is not confidential, how long protection continues, how return and deletion works, who owns what, and what the harmed side can ask for if something goes wrong.

  • This agreement is a mutual promise Opens by making the confidentiality duty two-way, so both sides protect what they receive.
  • What is confidential Defines the information covered, including commercial details and technical material like exports, code, notebooks, and credentials.
  • How we protect it Limits use to the work being discussed and restricts sharing to people who genuinely need access under equivalent obligations.
  • Returning and deleting Covers returning or deleting shared material and what limited copies can be kept for archiving, audit, or legal duties.
  • If something goes wrong Ends with remedies for misuse or leakage and includes the Signature block so both sides can sign.

In Plutio, you fill in the names, dates, and any terms that need to match how your work actually runs, then send the agreement for signature. Once both sides sign, you’ve got a dated record of what each side promised to protect and what uses are allowed.

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

States the duty is mutual, so both sides commit to protecting the other’s confidential information while discussions move forward.

What is confidential

Defines what counts as confidential, including pricing, customer and supplier lists, operating volumes, and technical artefacts like exports, schemas, queries, notebooks, and credentials.

How we protect it

Limits how information can be used and shared, and sets expectations around access control and handling, including when read-only access makes sense.

What is not confidential

Lists the main exclusions, like information that was already public, already known, independently developed, or lawfully obtained, plus what happens if disclosure is legally required.

How long this applies

Explains when the agreement starts, what kinds of sharing it covers, and that confidentiality continues after discussions or work end for the period agreed in writing.

Returning and deleting

Covers returning or deleting confidential information on request or at the end of work, and allows limited retention for backup, audit trails, or legal duties.

Who owns what

Clarifies that ownership stays with the original party and that sharing doesn’t grant a licence beyond evaluating or carrying out the agreed work.

If something goes wrong

Explains what the harmed side can seek if there’s a breach, and includes a Signature block so the agreement can be signed.

Who it is for

Consultants, agencies, founders, and in-house teams who need to share commercial or technical information with a counterparty before a project, partnership, or vendor engagement can start.

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 counts as confidential information in an NDA?

Confidential information usually includes anything a reasonable person would treat as private or commercially sensitive, even if it isn’t marked confidential. This agreement also names common examples like pricing, customer lists, operating volumes, and technical items such as exports, schemas, notebooks, and access credentials.

Does a mutual NDA protect both sides?

A mutual NDA sets the confidentiality duty both ways, so each side protects what they receive. This agreement starts by making that mutual promise explicit.

What information is excluded from confidentiality?

An NDA typically excludes information that’s already public through no fault of the receiving party, already known without a duty of confidence, lawfully received from someone else, or independently developed. This agreement also allows disclosure when required by a regulator, court, or legal process, with notice where allowed.

How long does an NDA last?

This agreement applies to confidential information shared from the date the last party signs it. The duty continues after discussions or work end for the period the parties agree in writing.

Do we have to return or delete data after a project ends?

This agreement says each side will return or delete the other’s confidential information when asked or when work ends, including copies. The agreement also allows keeping a limited copy for archiving, backup, audit trails, or legal or compliance duties, while keeping it confidential.

What happens if someone breaches an NDA?

This agreement says a leak or misuse can cause harm that money alone may not fix. The harmed side may seek an order to stop the breach or prevent further disclosure, and may also claim damages.

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