The core answer
An employee confidentiality agreement can prohibit disclosure of information that is genuinely the company's secret: identifiable, not public, and worth protecting, such as formulas, costs, customer-specific terms, unreleased plans and source code. A clause covering "everything the employee knows from work", or banning disclosure "forever", is usually too broad to enforce and tends to cause the disputes it was meant to prevent.
Keep a second point separate: an employee's rights under the law. A private contract cannot validly take away a right the law gives. Generally, a clause whose purpose is contrary to law or to public order or good morals is void (Civil and Commercial Code section 150). Complaining to a labour inspector, giving evidence to a court, reporting to the police or consulting one's own lawyer should therefore be written into the agreement as exceptions to the ban, not left for the confidentiality clause to override.
This guide explains how to draft and review an agreement so both points sit together. It does not promise that any particular complainant or whistleblower will be protected under any particular statute; that depends on the facts and the agency involved.
Where are you?
| Stage | Read first |
|---|---|
| Not yet signed (employer drafting, or employee handed an agreement) | Sections 1 to 6 and the pre-signing checklist |
| Signed and in use | Sections 5 to 8, to see whether existing clauses go too far and how data is handled on exit |
| Dispute already started (employer alleges breach, or employee threatened over a complaint) | Sections 4, 5 and 8, then collect the documents listed before replying or disclosing more |
1. What is an employee confidentiality agreement for?
It gives the company a document showing that the employee knows which categories of information are confidential, may use them only for company work, and must not disclose them. The benefits:
- the employee knows the boundaries from day one rather than guessing what can be said;
- the company has evidence that it told staff and took protective steps, which matters when relying on trade-secret protection;
- fewer arguments later about who owns what information.
A good agreement therefore answers four questions: which information, for what purpose, to whom it may be disclosed, and what happens on exit. It is not a tool to silence staff about pay, safety or how they are treated.
2. How to define confidential information narrowly and concretely
The most common weakness is a definition that is too wide. "All information the employee learns during employment" sweeps in general knowledge, skills the employee has built up and facts already public. Courts tend to read blanket restrictions strictly, and the employee cannot tell when they are in breach.
| Too broad | Narrow and clear |
|---|---|
| "Everything the employee knows from work" | A list of categories, for example formulas or production methods, customer-specific costs and prices, customer lists and terms not made public, unannounced product plans, source code |
| "Information the company regards as confidential" | Information on the list, or marked "confidential", or which a reasonable recipient would understand to be confidential from its nature |
| "All company information" | Information the company owns or must keep confidential for third parties |
| No statement of purpose | Use only for the company's work; no disclosure to anyone without a need to know |
A two-layer drafting approach helps: a general principle (information not generally known that the company has reason to protect), then a list tailored to the role. Sales staff may need customer data and pricing; developers may need source code and system architecture.
Personal data about customers or other employees that the employee can access is a separate layer governed by data protection law. See the guide on PDPA and employee data for HR.
3. Standard exclusions to include
- Publicly known information, in publications, on the company's website or common in the industry, without the employee having caused it to become public.
- Information the employee knew before joining, which the employee can show, for example from earlier work.
- Information the employee developed independently without relying on the company's confidential information.
- Information that law, a court or an authority requires to be disclosed. Here the employee may be asked to notify the company where that is possible and to disclose only what is required, unless notifying would itself be prohibited or conflict with the employee's rights in section 4.
Draft who must prove an exclusion with care. Some agreements put the burden on the employee in every case, which makes the exclusions meaningless. A balanced approach, supported by records, is better.
4. Disclosures the law requires or permits: keeping them apart from the secrecy clause
The principle is that a private contract cannot strip a person of rights the law gives. Generally, a clause whose purpose is contrary to law or to public order or good morals is void under Civil and Commercial Code section 150. Whether a given clause is caught depends on its wording and the facts, so it is not an argument to be assumed in every case.
In practice, a well-drafted agreement states that the ban does not apply to an employee doing the following as the law permits or requires:
| Action | Note |
|---|---|
| Complaining to or giving information to a labour inspector or labour authority | A channel employment law provides for employees |
| Giving evidence or filing documents in the Labour Court or another court | When the court requires it or as evidence in a case |
| Reporting to the police or investigating officers | Where the employee believes an offence has occurred |
| Giving information to a regulator with legal authority | For example the authority supervising that business, or the data protection authority |
| Consulting one's own lawyer or an adviser bound by confidentiality | To get advice on rights and the agreement |
| Discussing one's own pay and employment terms | Information about oneself should not be treated as the company's secret |
Points for both sides:
- An employer should not require employees to "get permission first" every time they contact a government agency; that has a blocking effect.
- That the law allows a complaint does not mean an employee can send every confidential company file with it. Disclose what is needed for the matter and let the receiving body assess it.
- This guide does not state that a specific whistleblower-protection statute applies to private employers, and does not promise that a complaint will protect anyone from dismissal or a lawsuit. If it happens, take advice before disclosing documents.
5. Over-broad clauses and why they invite disputes
| Clause | Why it causes problems |
|---|---|
| Disclosure banned "for life" for all information | Much information goes stale or becomes public. A term with no stated reason is exposed as excessive. A trade secret that stays secret may justify longer protection, so separate it from ordinary information |
| Ban on speaking about or complaining about pay, workplace safety, harassment or unfair treatment | These are matters employment and other law give channels for. Such a clause risks being treated as contrary to law and void |
| Treating everything the employee knows, including general skills, as company property | Stops the employee working in their field and works like a non-compete without meeting the tests for one |
| Very high penalty unrelated to real loss | A court may reduce a penalty, and the dispute becomes an argument about the figure |
| Waiver of any right to complain or sue the company | An over-wide waiver risks being void and puts the whole document under attack |
| No point at which information stops being confidential | The employee cannot tell when the duty ends |
Overbroad clauses also hurt the employer. In a real dispute the other side will argue that a document mixing sweeping and legitimate terms should not be enforced. Drafting narrowly from the start makes the parts that matter stronger.
6. How a confidentiality agreement differs from a non-compete
The two are often combined in one employment contract but they restrict different things.
| Confidentiality agreement | Non-compete | |
|---|---|---|
| What it bans | Disclosing or using identified information | Working for or running a competing business |
| Effect on finding a new job | Does not stop working elsewhere; stops use of the secrets | May directly limit job choices |
| What a court looks at | Whether the information is really secret and whether it was disclosed or used | Duration, area, type of work and whether it protects a legitimate interest |
| Risk if drafted too wide | Read narrowly or not enforced | The whole clause may fail |
Do not use a broad secrecy clause to stop someone taking another job by the back door. If you want a non-compete, write it as a separate clause with its own justification. See the guide on non-competes after resignation.
If a former employee has already taken customer lists or information, see the guide on former employees and customer lists. For secrecy agreements with business partners before negotiations, see the post on NDAs before business negotiations, which is a different situation.
7. The Trade Secrets Act in plain words
Thailand's trade secrets legislation asks three things when deciding whether information is a trade secret: it is not generally known, it has commercial value because it is secret, and its owner has taken reasonable steps to keep it secret. The third point is why confidentiality agreements, restricted access and telling staff matter: they are evidence that the company really guards the information.
The Act does not make everything a company holds a trade secret, and it does not take away an employee's right to use their skills, general knowledge and accumulated experience. Drafting to match these ideas, by identifying the information, showing the measures taken and not claiming more than is truly secret, makes an agreement easier to enforce. Check the official text, for example on the Office of the Council of State database, before relying on specific provisions or penalties in a real document.
8. Returning and deleting data on exit, and keeping evidence
Return and deletion
The agreement and exit form should set steps that can actually be done:
- return company documents, equipment and storage media;
- delete company data from personal devices, personal email and personal cloud storage, with written confirmation from the employee;
- close system and account access on the last day;
- state what the employee may keep, such as their own employment contract and pay records;
- allow a realistic time, not deletion within an hour with no way to check.
Personal data of customers and colleagues on a device also engages the PDPA. See the PDPA and employee data guide.
Keeping evidence of what was disclosed to whom
- Employer: keep the signed agreement, the list of confidential information handed over, access history, and records of return or deletion on exit.
- Employee: keep a copy of what you signed. If you must disclose to an agency or a lawyer, note what was disclosed, to whom, on what date and by what channel. Keep only documents about your own matter; do not collect confidential company files beyond what is needed.
- Both sides should keep notices, emails and meeting notes on the issue together.
Hypothetical example: an old clause when an employee wants to complain about overtime
This example is invented to illustrate and is not a real case. The figures are illustrative only.
A parts manufacturer uses an agreement saying "the employee shall not disclose any company information to outsiders at any time and shall pay a penalty set by the company." An employee believes overtime was underpaid and wants to complain to a labour inspector with copies of their own time records, but worries about breaching the agreement.
| Issue | How to approach it |
|---|---|
| Own time records and payslips | Information about the employee's own pay and work; should not be treated as the company's secret |
| Ban on disclosing "any information" forever | So broad that it protects real secrets poorly, and risks being treated as conflicting with the right to complain |
| Penalty "as set by the company" | No predictable limit; a court has discretion over reasonableness |
| Customer price and formula files unrelated to overtime | Should not be attached to the complaint; these remain confidential |
A workable course here: the employee files with only the documents about their own situation and records what was filed and when. The company revises the agreement to a narrow list of confidential categories, adds an exception for disclosures the law permits, removes the open-ended penalty and drops wording that suggests complaining is forbidden.
Documents and checklists
Before signing or adopting a new template
- Confidential information is defined by identifiable categories, not "everything learned at work"
- The four standard exclusions are present (public, already known, independently developed, required by law or court)
- The ban expressly does not apply to complaints, information or evidence given to government agencies, courts and police, or to consulting one's own lawyer
- No ban on discussing one's own pay, safety, harassment or treatment
- Duration has a reason and differs by type of information
- Any penalty has a sensible framework
- Any non-compete is a separate clause
- Personal data the employee can reach matches the company's privacy notice
During employment
- Keep the signed agreement and the list of information accessed
- Limit access to what each role needs
- Review the agreement when an employee moves to a role with new access
On exit
- Return form for documents and equipment
- Written confirmation of deletion from personal devices and accounts
- Record that system access was closed
- State what the employee may keep copies of
If a dispute has started
- Gather the signed agreement and any amendments
- Relevant emails and notices
- A record of what was disclosed to whom and when
- Hold off sending further documents until you have advice
Common misunderstandings
| Misunderstanding | Correction |
|---|---|
| "Once I sign a confidentiality agreement I cannot complain to anyone" | Generally a private contract cannot strip a person of legal rights, and a clause contrary to law or public order is void. The outcome depends on the wording and facts |
| "The wider I draft it, the safer" | Overbroad clauses are harder to enforce and expose the whole document to attack |
| "Confidential means confidential for life" | Some information goes stale or becomes public. Set terms by type and reason |
| "A confidentiality clause can replace a non-compete" | They are tested differently. Using secrecy wording to stop someone working elsewhere is risky |
| "An employee can send every confidential file with a complaint" | Disclose what is needed for the matter; do not take unrelated confidential files |
| "Complaining guarantees protection" | This guide gives no assurance of any outcome or protection; it depends on the law involved and the facts |
Limits of this guide
This guide does not cover negotiating confidentiality agreements between companies, non-competes in detail, trade-secret litigation, or whistleblower protection under sector-specific laws. The answer changes with the contract wording, the role, the type of information and the agency that receives the complaint. Information as of 21 November 2026; check the official text at krisdika.go.th before relying on it.
Further reading
- Joining a competitor after resigning: non-compete clauses for non-competes and how they differ from confidentiality clauses
- Former employee using customer lists: trade secrets when secrets have already been used
- PDPA and employee data for HR for personal data employees can access
- NDA before business negotiations for confidentiality between business partners
A good confidentiality agreement protects information that is truly secret through a narrow, clear definition and standard exclusions, and writes an employee's legal rights in separately instead of using secrecy to block complaints.
We help adjust employment contracts and confidentiality policies to protect the business without blocking lawful use of rights, review clauses that go too far, prepare exit forms for returning data, and advise employers or employees who have been handed an agreement to sign or are already in a dispute. We cannot promise the result of a complaint or a case. Fees depend on the stage of the matter and the work needed; send us your documents first and we will confirm the scope and fees in writing before starting. For an initial consultation, call +66 92 254 2045 or send us the details. See also HR documents and PDPA compliance.
This guide is published by Suwanvara Law Firm — a Khon Kaen law firm established in 1986. General information only, not legal advice on a specific matter.

