NDA (Non-Disclosure Agreement)
An NDA (Non-Disclosure Agreement) is a contract in which a party commits not to disclose or use for its own purposes confidential information received from the other party.
In plain words
A document in which a person or company promises: what I learn from you stays with you. NDAs are signed by employees, contractors, partners and sometimes candidates, before they see internal materials.
What it usually contains
- what counts as confidential: the customer base, deal terms, scripts, internal reports;
- what may and may not be done with that information;
- how long the obligation lasts, including after the work ends;
- what happens in case of breach.
Why it matters to a manager
For sales and collection departments, the main asset is the base and knowledge of customers. Without a written agreement it is hard to prove that the customer list was a secret and not public information. An NDA makes the rule explicit: the employee knows the limits, and the company knows its rights.
The strength of an NDA depends on national law. In some places protection requires a formally introduced trade-secret regime; elsewhere the text of the contract decides. Rules depend on the country, so check with a lawyer.
A common mistake
Treating the signature as protection. An NDA does not stop an employee from physically taking the base. It only gives grounds for a claim afterwards. If everyone has access to customers and nobody controls exports, the company will be proving the breach after the losses.
A second mistake is a generic template without specifics. “Do not disclose commercial information” with no list of what that means works poorly in a dispute.
More in Signals
- Client base security in messaging apps: who sees the conversations and how to prevent a leakA client base in messaging apps leaves quietly: with a rep who quits, in a spreadsheet “for myself,” in screenshots, on a personal phone. Protection starts with the owner’s decisions: the number and account belong to the company, the contract has an NDA, the client has consented, access is minimal, and departures follow a clear procedure.
- CRM for messengers: 12 questions to ask before you buyChoosing a CRM for messengers starts with your company, not with a vendor. Twelve questions an owner asks themselves: whose numbers and conversations they are, what happens when someone leaves, who owns promises made to clients, what an hour of silence costs, who actually brings revenue, where the law allows your data to sit, and who decides on access. Until you have the answers, any purchase is a blind bet.