Skip to main content

NDA Framework — Idea Protection

Information only — not legal advice. This document describes the Platform's confidentiality architecture and provides structural guidance on how idea protection works here. It is not a substitute for legal counsel and does not create legal obligations. Nothing in this document constitutes an attorney-client relationship. Consult a qualified attorney before drafting or executing any legal agreement. The Platform and its operators expressly disclaim any liability for reliance on this document. Structural guidance and checklists are provided as general educational context only and are not tailored to any user's specific facts or circumstances.

Purpose​

This document describes how confidentiality and trade secret protection intersects with the Platform's marketplace model. It explains what the Platform's Terms of Service can and cannot commit to regarding idea protection, and what supplementary agreements users may need for bilateral coverage.

NDA Structural Elements​

A binding NDA typically includes (this is a structural checklist, not a substitute for attorney review):

  1. Definition of confidential information — what is covered; what is excluded (public domain, independently developed, received from a third party without restriction, required to be disclosed by law)
  2. Obligations of the receiving party — do not disclose; do not use except for permitted purpose; protect with at least the same care used to protect the receiving party's own confidential information (no less than reasonable care)
  3. Permitted disclosures — required by law, court order, or regulatory body (with notice to disclosing party where legally permitted)
  4. Term — how long the obligations last; trade secret obligations are often perpetual
  5. Remedies — injunctive relief; damages; specific performance (courts regularly grant injunctions in trade secret cases because monetary damages are difficult to calculate)
  6. Return or destruction — what happens to confidential materials on termination
  7. Governing law and jurisdiction

For marketplace transactions, a unilateral NDA (seller discloses → buyer receives) is typically appropriate before sharing non-public idea details during due diligence. Mutual NDAs are appropriate when both parties exchange sensitive information.

Defend Trade Secrets Act (DTSA) — 18 U.S.C. § 1836​

The DTSA provides a federal civil cause of action for misappropriation of trade secrets. A trade secret under DTSA requires:

  1. The information derives economic value — actual or potential — from not being generally known or readily ascertainable to persons who could obtain economic value from its disclosure or use
  2. Reasonable measures were taken to keep the information secret

DTSA protection is automatic — no written agreement is required. However, a DTSA civil claim has a threshold requirement: the trade secret must be related to a product or service used in, or intended for use in, interstate or foreign commerce (18 U.S.C. § 1836(b)(1)). For most digital marketplace transactions this is satisfied, but purely local intrastate arrangements may warrant analysis.

Beyond the nexus requirement, a DTSA claim requires proving misappropriation: theft, breach of duty to maintain secrecy, or acquisition through improper means. It does not cover disclosure by parties who received the information legitimately without confidentiality obligations.

Practical implication: If you share idea content with another user without a confidentiality obligation in place, DTSA alone may not protect you — there is no duty of secrecy to breach. A written NDA creates that duty.

Contract-Based Confidentiality​

A written NDA creates contractual obligations independent of DTSA. Advantages:

  • Covers parties who learned the information legitimately
  • Defines scope, term, and permitted uses explicitly
  • Creates breach of contract remedies (typically easier to prove than DTSA misappropriation — plaintiff need only show duty, breach, and damages, not "improper means")
  • Can restrict use, not just disclosure
  • Can include liquidated damages clauses

The Platform's Terms of Service create contract-based obligations running platform↔user only. They do not create bilateral obligations between users.

UTSA (State Law)​

The Uniform Trade Secrets Act has been adopted by most U.S. states (with modifications) and provides a parallel state-law cause of action. Requirements and remedies are broadly similar to DTSA. State law typically preempts common-law misappropriation claims in UTSA states.

DTSA does not preempt UTSA. A plaintiff may bring both DTSA and UTSA claims simultaneously. Federal district courts have jurisdiction over DTSA claims, which can be a practical advantage when interstate discovery is needed.

Platform Relationship Types​

Type 1: User ↔ Platform​

Coverage: The Platform's Terms of Service and Privacy Policy govern this relationship. The Platform commits not to disclose non-public idea content to other users, not to sell your data, and not to use your content for targeted advertising.

Legal basis: Contract (Terms of Service) + applicable privacy law.

Privity: Obligations run between each user and the Platform only.

Gap: The Platform's ToS does not make the Platform a party to any user-to-user confidentiality obligation. The Platform is the marketplace operator, not a co-party to user-to-user deals.

Type 2: User ↔ User (via Platform)​

Coverage: None under the Platform's ToS. If you share commercially sensitive idea content with another user — in messages, off-platform, during due diligence — the Platform's ToS does not bind that other user to any confidentiality commitment.

Privity gap: Contracts bind their parties. A Terms of Service agreement between User A and the Platform does not bind User B. Bilateral coverage requires a direct agreement between User A and User B.

What you need: A separate written NDA executed between the parties before sharing sensitive information. This can be executed off-platform.

Recommended workflow for marketplace transactions:

  1. Use the marketplace listing for public teasers only (no proprietary technical details)
  2. Screen interested parties through the platform's messaging system
  3. Execute a unilateral or mutual NDA with serious buyers before full due diligence disclosure
  4. Complete purchase only after NDA is signed and retained

Type 3: Platform ↔ AI Subprocessors (Anthropic)​

Coverage: Anthropic processes user content under their Data Processing Addendum (DPA).

Retention: Anthropic retains inputs/outputs for up to 30 days under standard commercial API terms (per Anthropic's Privacy Center, "How long do you store my organization's data?" — updated 2026-03-16; this applies to commercial API customers and differs from the consumer product policy). Exception: Anthropic may retain content flagged for policy violations for up to 2 years, and trust-and-safety classifier metadata for up to 7 years. See Anthropic's Privacy Center for the current schedule.

Model training: By default, Anthropic does not use commercial API inputs or outputs to train their models. This is Anthropic's standard commercial API policy.

Privity: Users are not party to the Platform↔Anthropic DPA. The Platform is the data controller; Anthropic is a data processor acting on the Platform's instructions. Users' rights flow through the Platform as data controller.

EEA users: GDPR Art. 28 requires the Platform to use only subprocessors providing sufficient guarantees. The Anthropic DPA satisfies this requirement for EU users. Questions about Anthropic's processing may be directed to privacy@anthropic.com or your national data protection authority.

Non-Compete: Ancillary Restraint Framework​

Non-compete clauses may be included in a comprehensive idea sale agreement as an ancillary restraint. Under the Restatement (Second) of Contracts §§ 188-191, courts apply a proportionality balancing test — not a checklist — weighing four factors:

  1. Ancillary to a legitimate transaction — e.g., sale of a business, employment agreement, or IP transfer; not a standalone restriction
  2. Reasonable in scope — limited to the specific market, technology area, or customer set at issue
  3. Reasonable in duration — typically 1-3 years; longer periods face judicial scrutiny
  4. Reasonable geographically — proportionate to where the business operates

Even a facially reasonable non-compete may be unenforceable if the harm to the promisor or the public outweighs the legitimate interest of the party seeking enforcement (§ 188(1)(b)). Sale-of-business non-competes (§ 191) are generally afforded more judicial latitude than employment covenants — the most relevant context for marketplace transactions here.

Jurisdiction warning: Non-compete enforceability varies dramatically by state.

  • At minimum: California, Minnesota, Montana, North Dakota, Oklahoma, and Wyoming void or severely restrict non-compete agreements as against public policy (as of 2025). Additional states have enacted restrictions — verify current state law before drafting.
  • Other states — vary; some require independent consideration; some apply blue-pencil/reformation doctrines
  • Federal: The FTC's April 2024 final rule banning most non-competes was vacated nationwide by a federal district court in August 2024 (Ryan LLC v. FTC). The FTC abandoned its appeal in September 2025 (current as of March 2026 — verify regulatory status before relying on this). The rule is not in effect as of this document's publication. State law governs non-compete enforceability.

Geographic Scope​

This framework is based on U.S. law (DTSA, UTSA, Restatement). International users should be aware:

  • EU/EEA: Trade secret protection is governed by the EU Trade Secrets Directive (2016/943/EU). Requirements parallel DTSA in broad strokes but have EU-specific procedural rules and remedies. Notably, the Directive explicitly protects reverse engineering and independent discovery as lawful acquisition methods (Art. 3-4) — limiting the scope of protectable trade secrets compared to typical U.S. NDA practice.
  • UK: The Trade Secrets (Enforcement, etc.) Regulations 2018 implement similar protections post-Brexit.
  • Canada: Provincial law governs; the common-law tort of breach of confidence provides similar protection to contract-based NDA claims.
  • Other jurisdictions: Local law applies. Cross-border enforcement of U.S.-law NDA terms may be limited. Parties in different countries should consider choice-of-law and dispute resolution clauses carefully.

Platform users outside the United States should consult local counsel before relying on U.S.-law NDA templates for cross-border transactions.

Last updated: March 30, 2026 This document is reviewed and updated with each marketplace-readiness milestone.