Create a business NDA

Last checked Aug 17, 2026 Free service

Create one confidentiality agreement for an ordinary business relationship between two organizations. Use it when only your business will share confidential information, only the other business will share, or both businesses will share.

This tool is for a confidentiality-only business-to-business NDA. It is not designed for employee or individual-freelancer confidentiality, M&A or investment diligence, settlement terms, restrictive covenants, substantive IP or software licensing, regulated-data security terms, or other specialist agreements.

Create my NDA
Built for ordinary organization-to-organization confidentiality Private by design Free to create and download

Sign together or separately

Two organization representatives can sign electronically on the same device, or one signer can create a Secure Relay link for the other. The signing state stays in the browser and the handoff is carried in the link itself; LegalDocsBuilder does not email or store the NDA for you.

Create a Secure Relay signing link

  1. Which organization is signing first?
    The second signer role is fixed after the first organization signs.
  2. Signature
    After the first organization signs, LegalDocsBuilder’s signing workflow treats the NDA’s material facts and that completed signing record as read-only. If an organization name, purpose, information-flow choice, timing treatment, governing law, or another material agreement fact needs to change, restart from a newly created NDA; the existing signature does not carry over.
  3. Send the other organization its signing link
    This client-only Secure Relay link contains the partially signed NDA state in its URL fragment and is targeted to the remaining organization’s signer. The fragment is not sent to LegalDocsBuilder with the page request, and LegalDocsBuilder does not email or store the handoff for you. The embedded state includes client-side consistency checks, but LegalDocsBuilder does not retain an independent origin record for the link.
    Sign together on one deviceRelay by link or QR
  4. Sign and finish NDA
    This link contains a prior signing record and NDA facts that pass LegalDocsBuilder’s internal consistency checks, and the supported signing workflow treats them as read-only. LegalDocsBuilder does not keep a separate server or cryptographic origin record that proves this recipient-held link is the exact historical bundle created by the first signer. If anything material is wrong or you need stronger provenance, do not sign this state; obtain a fresh handoff or confirm the signing state independently.
  5. Download signed NDA PDF
    Download and keep the signed PDF. LegalDocsBuilder does not store the signed agreement in an account or document repository for you. Each organization should retain a copy it can reproduce later.

Treat the complete link as sensitive. Anyone who receives it may be able to open the partial signing state it carries. Because the handoff is self-contained and uses public client-side validation, LegalDocsBuilder cannot independently prove that a recipient-held link has not been replaced with a different self-consistent bundle. Share it only with the intended signer using a communication method that gives you appropriate confidence in the handoff.

A title can identify the representative’s role, but LegalDocsBuilder does not verify that it gives authority to bind the organization.

Before you start

Have the legal names of both organizations, a short description of why confidential information will be shared, and the states connected to the organizations or business relationship. We will first check whether this general business NDA fits your situation. Missing or uncertain facts stop the form until they are resolved; specialist scenarios are routed out rather than forced into a general NDA.

Common questions about business NDAs

What is this General Business NDA for?

It is a confidentiality agreement for an ordinary commercial relationship between two organizations. It can cover a one-way exchange where only one business shares confidential information or a mutual exchange where both do. It is intentionally narrower than “any NDA”: workforce, individual-contractor, M&A, investment, settlement, restrictive-covenant, substantive IP/licensing, regulated-data/security, and other specialist scenarios are routed out.

Do I need a different form for a mutual NDA or a one-way NDA?

No. This product uses one agreement engine. Choose “Only my business,” “Only the other business,” or “Both businesses” when asked who will share confidential information. The first two are one-way or unilateral orientations in opposite directions; the third is the mutual orientation. The rest of the confidentiality core remains the same.

Who are the parties to the NDA?

The contracting parties are the two organizations named in the agreement. A human representative may sign for an organization, but the representative does not become the contracting party merely by signing. This v1 tool does not support a natural person or sole proprietor acting personally as one of the parties, and it does not treat a name, title, email address, or signature as independent proof of authority to bind an organization.

What counts as Confidential Information under the generated NDA?

The agreement uses a contextual definition for nonpublic business, technical, financial, operational, commercial, customer, supplier, product, planning, research, and similar information. Information can qualify when it is identified as confidential or when a reasonable person would understand from its nature and the circumstances that it is confidential. The agreement also excludes information that becomes public without recipient breach, was already lawfully known without a confidentiality duty, is lawfully received from a third party without such a duty, or is independently developed without using the Confidential Information. Contractual Confidential Information is not automatically a trade secret under law.

What if confidential information was already disclosed before the NDA is signed?

The generated agreement’s Effective Date is the date of the last signature, and its ordinary contractual Confidential Information treatment is prospective from that date. If meaningful future or ongoing sharing remains, the tool can continue with the accepted mixed-past/future treatment, which states that the NDA does not by itself establish contractual protection for an earlier disclosure. Rights concerning earlier disclosures may arise from applicable law or another agreement. If the main objective is only to protect disclosures already completed and no meaningful future sharing remains, this product routes out rather than backdating the NDA or promising a retroactive cure.

How can the receiving business use the confidential information, and who can see it?

The agreement limits use to the business purpose entered in the form. It permits disclosure to specified representatives—such as directors, officers, employees, attorneys, accountants, consultants, and contractors—only when they reasonably need the information for that purpose and are subject to sufficient confidentiality duties. The receiving organization remains responsible under the agreement for a representative’s use or disclosure that would violate the agreement if done by the receiving organization.

How long does the confidentiality obligation last?

The generated NDA uses a three-year disclosure window beginning on the Effective Date and, for ordinary Confidential Information, duties lasting three years after each disclosure. Information that qualifies as a trade secret under applicable law remains subject to the agreement’s applicable confidentiality and use duties for as long as it continues to qualify for trade-secret protection. The three-year periods are product drafting choices, not a claim that every state requires three years and not the federal DTSA limitations period.

Why can’t I simply choose any state’s law?

The tool offers governing-law choices only from real U.S. connections you provide, such as an organization’s formation state, principal place of business, or a state where the relationship or performance is mainly centered. It does not use an unrestricted 50-state preference picker or ask users to self-qualify for special no-relation statutes. Choosing governing law also does not choose a court, venue, or federal jurisdiction.

What does this NDA not replace?

It does not create the main commercial terms of a services, licensing, employment, acquisition, investment, ownership, development, data-processing, cybersecurity, settlement, or other substantive agreement. An in-scope NDA can sit alongside a separate agreement when confidentiality is only one layer of the relationship. If the NDA itself is being asked to supply those other rights or obligations, the form routes out.

Can the organizations sign this NDA electronically?

Yes, when the electronic-signing feature is enabled for this product. One human representative signs for each organization. Each signer must expressly intend to sign electronically and represent that they are authorized to sign for the named organization. LegalDocsBuilder records that representation as part of the signing state but does not verify the person’s identity or actual authority merely from a name, title, signature, browser session, or link possession. Federal E-SIGN provides that qualifying contracts and signatures generally cannot be denied effect solely because they are electronic, while underlying authority, assent, and other substantive requirements remain separate.

How does Secure Relay work for this NDA?

Secure Relay is a client-only signing handoff, not an email-delivery, server-storage, identity-verification, authenticated-custody, or historical-origin service for this product. The first organization’s representative signs, then the browser creates a link containing the partial signing state in the URL fragment for the other organization’s signer. LegalDocsBuilder can check whether the state is structurally valid and internally consistent, and the supported continuation treats prior agreement and signing facts as read-only. Because the whole handoff is self-contained and its validation rules are public, LegalDocsBuilder has no independent origin record that can prove a recipient-held bundle is the historical original if someone deliberately remints a different self-consistent bundle. Treat the complete link as sensitive and share it only through a method you consider appropriate. If the state is too large for the supported link transport, the product falls back to same-device signing or print rather than truncating the record.

What should the organizations keep after creating or signing the NDA?

Keep a reproducible copy of the agreement with the records for the business relationship. For an unsigned or manually signed path, download and retain the PDF rather than relying on the ready-page browser session. When site electronic signing is enabled and completed, download and retain the fully signed PDF; LegalDocsBuilder does not store the signed NDA in an account or document repository for the parties.

Tell us about the confidentiality relationship

Legal sources and scope

This tool uses a nationwide common NDA core together with a connected-state governing-law choice. Relevant federal sources include 15 U.S.C. § 7001 on electronic records and signatures and 18 U.S.C. §§ 1833 and 1839 on trade-secret and protected-reporting rules, together with state contract, trade-secret, electronic-transactions, and choice-of-law authorities reviewed for all 50 states and the District of Columbia as of Aug 17, 2026. The agreement does not make every confidential item a trade secret, guarantee a remedy, or choose a court or forum for a dispute.

First, check whether this NDA fits

Choose the relationship the NDA itself is supporting. This general tool is limited to ordinary confidentiality between two organizations.

An NDA can sit alongside a separate services, licensing, vendor, collaboration, or other agreement. This tool does not use the NDA to create those substantive relationship terms.

Do you need the NDA itself to include any of these specialist protections? *

Select “None of these” only if ordinary confidentiality is the job. “None of these” cannot be combined with another option.

Confirm the two contracting parties

Your business name, job title, email address, or signature does not by itself establish that an organization is the contracting party.

The other organization must itself be the contracting party; a representative’s name, title, email address, or signature does not establish that by itself.

When will confidential information be shared?

Do not answer based on a date you hope to put in the NDA. We need the actual disclosure timing.

This general NDA is built for prospective or continuing confidentiality. It does not use backdating to promise protection for a completed past disclosure.

Who will share confidential information?

The first two choices create a one-way NDA in opposite directions. “Both businesses” creates the mutual orientation. All three use the same General Business NDA engine.

Name the organizations

Enter the organization that will be a party to the NDA, not the representative’s personal name.

Enter the other organization that will be a party to the NDA.

Add a person’s name if you want it prefilled in the signature block. The organization remains the contracting party.

A title can identify the signer’s role, but it does not prove authority to bind the organization.

Add a person’s name if you want it prefilled in the signature block. The other organization remains the contracting party.

A title identifies a role only; LegalDocsBuilder does not treat it as proof of authority.

Describe the business context and purpose

This describes the setting; it does not create separate vendor, software, licensing, or collaboration NDA products.

Use a short, concrete business purpose—for example, evaluating a supplier relationship, discussing a proposed project, or exploring a commercial collaboration. The agreement uses this purpose to limit how confidential information may be used.

Identify the states connected to the relationship

This tool does not offer an arbitrary 50-state governing-law picker. It first collects real connections to the organizations or business relationship, then lets you choose from the connected U.S. states it can support.

If you do not know, choose “I’m not sure.” An unknown answer does not create a governing-law option.

If you do not know, choose “I’m not sure.” An unknown answer does not create a governing-law option.

Choose a state only when it reflects a real relationship or performance connection.

The listed states come only from the connections you provided. Choosing governing law does not choose a court, venue, or federal jurisdiction.

Review the NDA facts

Check the material facts below before creating the agreement. The NDA is generated only from the current confirmed version of these facts.

Contracting organizations
Representatives, if provided
Business context
Confidentiality purpose
Disclosure timing
Who shares confidential information
Selected governing law
Why that state was available
General-business NDA fit