NDA Clause Checklist Generator
An NDA works only when its language fits the direction in which information actually moves.
Run — free
This generator turns the selected NDA type and the names of the disclosing and receiving parties into a structured drafting checklist. It covers the definition of confidential information, handling duties, standard exclusions, duration, compelled disclosure, return or destruction, ownership, remedies, and core operating terms. The result is a planning aid for reviewing a draft or preparing instructions for counsel, not a completed agreement or a substitute for legal advice in the relevant jurisdiction.
Choose the NDA structure before reviewing individual clauses
Start with the real flow of information. A one-way NDA is appropriate when one side expects to disclose protected material and the other side mainly receives it. A mutual NDA is appropriate when both sides expect to exchange sensitive information and should carry equivalent duties when acting as recipients. This choice affects more than the heading. It changes how the parties are defined, whose information receives protection, who must restrict use, and how obligations are expressed throughout the document. Enter the legal names or clear role names for both parties, then confirm that the generated role summary matches the planned relationship. If a project contains several entities, affiliates, advisers, or contractors, decide whether they are parties, representatives, or neither. Avoid treating a mutual form as automatically fair: matching words can still impose unequal practical burdens if one side shares trade secrets while the other shares routine material. The checklist gives a reliable structure, but the commercial facts should determine which provisions need negotiation, added detail, or removal.
Test the definition, exclusions, and duration together
The definition of confidential information determines the agreement's reach, while the exclusions and time limits keep that reach defensible. Check whether the definition covers the formats the parties will actually use, including demonstrations, conversations, prototypes, source materials, financial records, and electronic files. Decide whether every item must be marked, whether context can make confidentiality obvious, and whether oral disclosures require written confirmation. Then read each exclusion as an evidence rule: information already known, independently developed, publicly available without breach, or lawfully obtained from another source is commonly outside the duty, but the draft should say who must establish those facts. Review the agreement term separately from the confidentiality period. The first controls when covered disclosures can occur; the second controls how long duties survive. A single expiration date can create an unintended gap. Trade secrets may need protection for as long as they retain that status, subject to applicable law, while other commercial information may justify a defined period. These provisions should work as one system rather than as isolated boilerplate.
Turn the checklist into a practical legal review
Use each check as a question to answer from the draft, not as language to paste without review. Confirm that use is limited to a stated purpose, access is restricted to people who need the information, and representatives carry compatible duties. Examine the process for legally compelled disclosure, including notice, cooperation, protective orders, and allocation of costs. Return-or-destruction language should account for backups, legal retention, and surviving duties for retained copies. Ownership and no-license wording should prevent an exchange of information from becoming an accidental transfer of intellectual property. Remedies deserve particular care: injunctive relief may be important, but availability depends on law and facts, while damages limitations or indemnities elsewhere in the contract can change the result. Finally, align governing law, venue, notices, assignment, signatures, and the entire-agreement clause with the wider transaction. Record decisions and unresolved issues beside the checklist, then give the draft and those notes to qualified counsel. The API price is $0.002 per request, but the checklist remains general information rather than legal advice.
What you can do with it
Prepare instructions for counsel
Organize the parties, information flow, standard protections, and open commercial questions before requesting a tailored NDA draft.
Review a counterparty's NDA
Compare an incoming mutual or one-way draft against a consistent list of common clauses and flag omissions for legal review.
Standardize an intake workflow
Give procurement, partnerships, or sales teams a repeatable first-pass checklist without presenting the output as legal approval.
FAQ
Does this generator create a complete NDA?
No. It creates a clause checklist for planning and review. It does not draft an agreement, decide enforceability, or replace advice from qualified counsel.
What is the difference between mutual and one-way?
In a mutual NDA, both parties may disclose protected information and each carries recipient duties when receiving it. In a one-way NDA, the named disclosing party provides protected information to the named receiving party.
Which standard clauses are included?
The checklist covers parties and purpose, confidential-information definitions, protection duties, exclusions, compelled disclosure, term and survival, return or destruction, ownership, remedies, and general operating terms.
Can confidentiality obligations last indefinitely?
That depends on applicable law, the information, and the drafting. Trade secrets are often treated differently from other confidential information, so qualified counsel should review the chosen duration.
Why does the checklist include remedies?
A draft should address what may happen after a breach and how that language interacts with damages limits, indemnities, notice requirements, and remedies available under applicable law.
What does each request cost?
The API price is $0.002 per request. The same deterministic logic can also run in the browser.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/doc/nda-clause-checklist \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"type":"one_way","disclosing_party":"Northstar Labs","receiving_party":"Riverbend Consulting"}'const res = await fetch("https://api.kit.forhosting.com/doc/nda-clause-checklist", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"type": "one_way",
"disclosing_party": "Northstar Labs",
"receiving_party": "Riverbend Consulting"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/doc/nda-clause-checklist",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"type": "one_way",
"disclosing_party": "Northstar Labs",
"receiving_party": "Riverbend Consulting"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/doc/nda-clause-checklist", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"type":"one_way","disclosing_party":"Northstar Labs","receiving_party":"Riverbend Consulting"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"type":"one_way","disclosing_party":"Northstar Labs","receiving_party":"Riverbend Consulting"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/doc/nda-clause-checklist", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"type": "one_way",
"disclosing_party": "Northstar Labs",
"receiving_party": "Riverbend Consulting"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "doc.nda_clause_checklist",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_chars | 200 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |