Customer Lists as Trade Secrets in Nepal: What the Law Protects and How to Keep It
Customer lists as trade secrets in Nepal: when a client database qualifies, how Nepalese law reaches its misuse, and the contracts and controls that hold.
A Nepali business's customer list is often its most valuable asset and its least protected one: years of relationships in a spreadsheet, copied to a laptop, walked out the door, and working for a competitor next quarter.
Whether that copying is legally actionable in Nepal depends on what the list actually is — and what the business did to keep it secret. This guide sets out the customer-list trade secret question as Nepalese law answers it.
In short
Customer lists can qualify as trade secrets in Nepal — not automatically, but when they meet the secrecy test: compiled through effort, not publicly available, valuable because they are secret, and kept confidential by real measures. Nepalese law protects them through contract and confidence (NDA enforceability, employment terms, breach remedies) rather than a trade-secret statute — statutory protection is proposed in the Bill 2082. The protection that works: written confidentiality and non-solicitation terms, access controls, dated evidence of the list's development, and enforcement consistency. A list circulated freely or compiled from public sources is legally naked.
Customer list trade secrets: when the claim is strong
The qualifying test is functional, and Nepalese practice applies it through the general law: a customer list is protectable when it is not publicly available, carries commercial value from its secrecy, and is subject to reasonable secrecy measures. A distributor's database of 400 named accounts with volumes, pricing history and contact persons — compiled over years — clears that bar easily. A list of shops anyone can photograph in New Road does not.
The middle cases turn on the effort and the measures: a list compiled from public registers is weak; the same registers compiled, filtered, verified and enriched with pricing and relationship data is strong. What the business added — and what it kept confidential — is the difference.
| Factor | Weak claim | Strong claim |
|---|---|---|
| Source | Public directories, observable market | Compiled relationships, verified data, pricing history |
| Availability | Circulated to staff freely, emailed around | Access-controlled, need-to-know, logged |
| Value | Duplicate of what competitors can build | Years of goodwill and intelligence competitors cannot copy |
| Measures | No NDAs, no policy, no marking | Contracts, confidentiality policy, marking, exit protocols |
How Nepalese law reaches misuse
Nepal has no trade-secret statute yet — protection runs through contract and confidence. The working instruments: NDAs and confidentiality clauses (enforceable as contracts; breach claims for damages and injunctions), employment contracts with confidentiality and non-solicitation terms, and the general law against taking or using confidential information in breach of confidence. What the law does not do — absent statute — is police a secret nobody contracted to keep.
The proposed Industrial Property Bill 2082 would change this: statutory trade-secret protection is among its headline additions, aimed squarely at startups and the knowledge economy. Until enactment, the contracts are the system — which makes the drafting quality the whole legal position.
The contracts: what to paper with whom
The protection map is role-by-role, because the leakage routes differ:
- Employees — confidentiality clauses in every contract; non-solicitation terms for customer-facing roles, drafted to be enforceable and proportionate
- Sales staff with CRM access — access controls and logged permissions, not just paper obligations
- Distributors and agents — confidentiality plus return-or-destroy obligations at termination; the agreement is also what makes their use of your marks and relationships authorised
- Contractors and consultants — NDAs before access, not after; scope-limited to the data they need
- Partners in deals — mutual NDAs signed before data rooms open, with survival terms that outlast failed negotiations
The controls: secrecy is a process
Courts and counterparties both assess what the business actually did. The measures that make a claim credible: the master list held centrally with access restricted and logged; exports disabled or monitored on CRM systems; documents marked confidential; exit protocols that collect devices and reconfirm obligations on the last day; and a written confidentiality policy staff have actually been trained on. A business that cannot show its measures is asking a court to protect a secret it never kept.
The evidence habit completes the position: keep dated records of the list's compilation and maintenance — when accounts were added, verified, priced. The development history is what distinguishes your compiled asset from a directory anyone could have typed.
When a list walks out the door
The response sequence for suspected misuse: secure the evidence first — the departing employee's access logs, the files taken, the contract terms signed; then the demand letter asserting breach and seeking return or destruction; then the remedies — damages and injunctions under contract law — if the demand fails. Two things decide these cases in practice: the quality of the contracts signed before the departure, and the consistency of the measures shown after it. The case built on a signed NDA, logged access and a marked list is a case; the one built on suspicion is a negotiation.
Prevention remains the only cheap option — and its cheapest form is the exit protocol: the ten-minute conversation, the device collection and the written reconfirmation of obligations that most Nepalese businesses skip and later wish they had not.
Want this handled for your brand?
IP Watch monitors new trademark publications in Nepal and alerts you to potentially conflicting marks — with the context needed to review them.
This article is general information, not legal advice.