NDA guide for founders: types, clauses, risks, and international use

Learn how to choose NDA types, draft key clauses, reduce disclosure risks, and address cross-border enforcement. Use this practical guide to protect secrets.

TL;DR

An NDA is a contract that controls how defined confidential information may be used and shared. We recommend setting clear boundaries around covered information, permitted use, access, exclusions, duration, and remedies. The agreement should be supported by practical controls such as limited permissions, access logs, secure payroll systems, and prompt offboarding. International teams also need local advice on privacy, worker rights, classification, and enforcement.

Table of Contents

What is an NDA, and what does it mean in business?

What is an NDA, and what does it mean in business?

An NDA, or non-disclosure agreement, sets rules for accessing, using, and disclosing specified confidential information. It may also be called a confidentiality agreement, proprietary information agreement, or secrecy agreement.

Signing an NDA does not usually transfer ownership of information or grant unrestricted permission to use it. One party discloses information, while the recipient accepts defined limits on its use and disclosure.

NDA meaning in common business situations

Businesses use NDAs during vendor reviews, contractor onboarding, client projects, acquisitions, partnerships, product demonstrations, and some hiring discussions. Penn State’s research guidance also describes NDAs as agreements that may protect one or both parties during preliminary collaboration discussions.

NDA vs confidentiality agreement vs non-compete

“NDA” and “confidentiality agreement” commonly describe the same type of contract. We focus on the operative clauses rather than the title.

A non-compete restricts competitive activity, while an NDA should focus on information. However, an NDA may contain additional terms covering intellectual property, non-solicitation, indemnification, exclusivity, or competitive employment. Those provisions deserve separate review.

The three types of NDA

The appropriate format depends on who will disclose information:

  • Unilateral NDA: One party is the primary discloser.
  • Mutual or bilateral NDA: Both parties disclose protected information.
  • Multilateral NDA: Three or more parties participate.

The label does not determine whether the terms are balanced or enforceable.

When a unilateral NDA fits

A unilateral NDA may suit an employer giving a worker access to customer records, source code, or payroll information. It can also cover confidential data shared with a service provider.

The agreement should limit access to people who need the information and address the recipient’s responsibility for employees, advisers, or subcontractors.

When a mutual NDA fits

We recommend a mutual NDA when both sides expect to share sensitive information during partnership, acquisition, integration, or client-vendor discussions.

Definitions, permitted disclosures, duration, and remedies should apply fairly. A document described as “mutual” can still impose unequal liability.

When a multilateral NDA fits

A multilateral NDA can cover several businesses working on the same project. It may reduce duplicate paperwork, but each participant’s permitted use, access rights, security duties, and responsibility for further disclosure must be clear.

What an NDA should protect and exclude

What an NDA should protect and exclude

Confidential information may include:

  • Payroll, compensation, banking, and tax records
  • Customer lists, pricing, and sales pipelines
  • Source code, credentials, datasets, and product plans
  • Tenant records and building-access information
  • Internal forecasts, reports, and financial information

We favour concrete definitions over language that labels every file, fact, and conversation confidential indefinitely.

Trade secrets vs ordinary confidential information

Trade secrets generally depend on information remaining secret and on reasonable efforts to preserve that secrecy. Whether source code, a process, or another asset qualifies depends on the facts and applicable law.

Other information may lose sensitivity sooner. Pricing, forecasts, and launch plans can therefore require different protection periods from qualifying trade secrets.

Standard exclusions from confidentiality

Common exclusions apply when the recipient can demonstrate that information was:

  • Already known without a confidentiality obligation
  • Independently developed
  • Lawfully obtained from another source
  • Publicly available without a breach
  • Approved for release in writing

Dated records can help support these exclusions if a dispute arises.

Sensitive information that needs more than an NDA

An NDA does not replace privacy notices, data-processing terms, security controls, or breach-response procedures. Payroll, banking, health, identity, tax, and tenant information may carry separate legal duties.

When planning an offshore development center, we treat confidentiality, data access, payroll, classification, and security as connected but distinct workstreams.

Essential NDA clauses to review before signing

Before signing, we recommend reviewing:

  • Covered information and permitted purpose
  • Authorized recipients
  • Contract term and confidentiality period
  • Legally required disclosures
  • Return and deletion requirements
  • Remedies, indemnity, fees, and liability limits
  • Governing law and dispute venue
  • Non-compete, IP, or non-solicitation provisions

Enforceability varies by jurisdiction and circumstance, so material risks may require qualified legal advice.

Definition, purpose, and permitted use

The NDA should identify what is protected and why the recipient may use it. If oral disclosures require written confirmation, the process and deadline should be clear.

Access should be limited to representatives who genuinely need the information and are subject to suitable confidentiality duties.

Term, confidentiality period, and survival

The contract term and the period for which confidentiality obligations survive are not necessarily the same. Both should be stated.

Long-term protection may suit genuine trade secrets, but it can be disproportionate for information that quickly loses commercial sensitivity.

Required disclosure, return, and deletion

The agreement should permit disclosure when required by law, a court, or an authorized regulator. Advance notice should be required only where giving notice is lawful.

Return and deletion provisions should address copies, extracts, credentials, shared links, and backups while allowing restricted retention where records must legally be preserved.

Remedies, liability, governing law, and venue

Review injunctions, damages, indemnities, legal fees, and liability caps. Also consider whether the selected law and venue make enforcement realistic.

Uncapped indemnities, distant proceedings, or one-sided fee clauses may create significant exposure even when the confidentiality obligations appear reasonable.

When an NDA may be illegal, void, or unenforceable

NDAs are not inherently unlawful, but particular terms or uses may conflict with mandatory rights or public policy. Vague definitions, excessive restrictions, unlawful purposes, or missing contractual requirements can also weaken enforceability.

We avoid relying on generic templates because the rules vary by jurisdiction, worker status, and context.

Pay discussions and collective worker rights

Applicable law may protect discussions about wages, benefits, hours, or working conditions. An NDA should not appear to prevent workers from discussing their own terms or exercising protected collective rights.

A business may still restrict unauthorized access to another person’s payroll records.

Whistleblowing, misconduct reports, and regulator contact

Confidentiality terms should not obstruct legally protected reports of suspected fraud, harassment, discrimination, safety issues, or other misconduct. Communications with regulators, law enforcement, legal advisers, and authorized reporting channels may also be protected.

Why an NDA does not establish contractor status

Describing someone as an independent contractor in an NDA does not settle their legal classification. The actual working relationship remains relevant under applicable employment, tax, benefits, and payroll rules.

For example, UK contractor status and IR35 risk require analysis beyond contract labels.

International NDAs for employees, contractors, and vendors

Using one domestic NDA for every international worker or vendor can leave gaps involving local rights, language, privacy, and enforcement. We recommend aligning confidentiality terms with the broader onboarding, payroll, classification, and data-access process.

Governing law, venue, and enforcement

Governing law affects interpretation, while venue identifies where a dispute will be handled. Before choosing either, consider whether a judgment or injunction can realistically be enforced where the signer or relevant assets are located.

Language and local-law review

Bilingual agreements should state which version controls if the wording conflicts. Local rules may also affect contract language, electronic signatures, notices, worker rights, and confidentiality restrictions.

Local review is safer than assuming one global template will work unchanged.

Cross-border data and payroll workflows

Confidentiality obligations are separate from privacy, cybersecurity, and international data-transfer requirements. Access to identity, compensation, banking, and tax records should be limited by role and business purpose.

Shor’s international payroll platform helps founders centralize global payroll workflows. Controlled access and prompt permission removal can support the NDA, but they do not replace it.

NDA examples for startup and property-management workflows

No single NDA suits every relationship. Scope, duration, access, deletion, and permitted use should reflect the information being shared and the applicable law.

Employees and international contractors

An employee or contractor NDA may cover source code, credentials, customer information, payroll data, and internal financial records. It should preserve applicable reporting rights, lawful pay discussions, and the use of general skills and experience.

When learning how to hire a virtual assistant, we recommend planning system access before onboarding rather than granting broad permissions later.

Staffing firms and data-labeling companies

Staffing agreements may protect candidate records, client rates, contacts, and forecasts. Data-labeling terms may cover customer datasets, annotation instructions, model outputs, and subcontractor access.

Project-specific deletion, access, and incident-reporting provisions can strengthen these agreements, although they do not independently satisfy privacy law.

Property managers, vendors, and business discussions

Property-management NDAs may cover tenant records, access codes, owner reports, maintenance pricing, and vendor credentials. Public or independently developed information should be excluded.

For early sales discussions, staged disclosure and redaction may sometimes be more practical than requesting an NDA immediately.

Operational controls that make an NDA more effective

A contract cannot compensate for unrestricted access or weak offboarding. We pair confidentiality obligations with clear process owners and system controls.

Before access is granted

  • Classify information by sensitivity.
  • Provide only the data required for the role.
  • Confirm the parties and signing authority.
  • Complete the appropriate agreement.
  • Use redaction, staged disclosure, and least-privilege access.

While the relationship is active

Maintain appropriate access logs, approvals, version history, and security alerts. Review permissions whenever responsibilities change.

Sensitive payroll, identity, tenant, customer, and production data should remain in controlled systems rather than personal drives or unmanaged spreadsheets.

At offboarding or project completion

Disable accounts, rotate credentials, revoke links, recover devices, and document return or deletion. Records retained for legal, tax, payroll, or security reasons should remain restricted.

What to do if someone breaches an NDA

Begin with containment and evidence preservation. A signed agreement alone does not establish breach, loss, or entitlement to a particular remedy.

Contain the disclosure and preserve evidence

Restrict access, rotate credentials, remove exposed links, and preserve the agreement, communications, logs, and disclosed materials. Record what was shared, who received it, and whether it remains confidential.

Avoid changing or deleting potentially relevant evidence.

Evaluate notice duties and realistic remedies

Check contractual notices and any privacy, employment, insurance, client, or regulatory reporting duties. Possible responses may include return, deletion, settlement, damages, an injunction, or other claims, depending on the law and facts.

Prompt legal advice may be necessary when disclosure is ongoing or regulated data is involved.

Protect confidential data across international teams

Pair a precise NDA with controlled access, secure payroll workflows, and disciplined offboarding. Talk to Shor about international payroll when confidential worker and compensation data crosses borders.

FAQ

What does an NDA mean?

NDA means non-disclosure agreement. It restricts how defined confidential information may be used or shared for a stated purpose.

What are the three types of NDA?

The main types are unilateral, mutual or bilateral, and multilateral. The right choice depends on how information flows between the parties.

Is an NDA illegal?

No, not inherently. However, certain terms may be prohibited, void, or unenforceable if they conflict with mandatory law, public policy, worker protections, or reporting rights.

Is signing an NDA risky?

It can be. We look closely at vague definitions, indefinite obligations, one-sided remedies, uncapped liability, and hidden non-compete, indemnity, IP, or non-solicitation terms.

Should a founder use an NDA template or maker?

A template can organize standard clauses, but it cannot assess local enforceability, worker rights, cross-border data duties, or the facts of a specific relationship. Legal review may be worthwhile when the information or potential liability is significant.