- Who does what in the confidentiality system
- What makes information confidential: the legal trigger
- The contractual overlay: NDAs and employment clauses
- Creating and marking documents: why the paperwork matters
- Day-to-day protection and what it proves
- The privacy overlay: when documents contain personal information
- Departures and disputes: where confidentiality bites
- Where a lawyer helps
- Confidentiality is a proof problem
Most businesses hold documents they would rather not see published: customer lists, pricing models, product roadmaps, financial forecasts, source code, supplier terms. The practical question is not whether you have them. It is what the law actually does when someone who should not have them gets hold of them.
In Australia, the answer comes from three layers that work together. Equity protects confidential information as a matter of conscience, even when nothing has been signed. Contract adds express terms through non-disclosure agreements and employment clauses. And where the documents contain personal information, the Privacy Act 1988 (Cth) stacks statutory duties on top.
This article walks through how that machinery operates: the people in the system and what each one does, the legal trigger that makes information confidential, the contracts and documents that support it, the privacy overlay, and where the protection comes apart.
Who does what in the confidentiality system
Confidentiality protection is not a single rule. It is a set of relationships, and each participant has a different role:
- Your business: the owner and controller of the information. You decide what is confidential, who may see it, and how it may be used.
- The people you share it with: employees, contractors, investors, suppliers, partners and advisers. Each one receives the information on terms, and each one is the person who might leak it.
- The courts: the enforcers. If information is misused, a court decides whether it was confidential in the first place and what remedy follows.
- The Office of the Australian Information Commissioner (OAIC): the regulator where the documents contain personal information, with its own powers to investigate and act.
The tension in the system sits between the first two players. You must share information to grow the business, but every disclosure is a chance for it to escape. The law's job is to make that trade-off workable.
What makes information confidential: the legal trigger
The foundation of confidentiality protection in Australia is the equitable doctrine of breach of confidence. Courts apply the classic test from Coco v AN Clark (Engineers) Ltd [1969] RPC 41, which has been adopted and applied in Australia, including in the New South Wales Court of Appeal in Filby v TEG Live Pty Ltd [2023] NSWCA 320 and Del Casale v Artedomus (Aust) Pty Ltd [2007] NSWCA 172.
Three things must be established before information is protected:
- The information must have the necessary quality of confidence: Information that is already public property or public knowledge cannot be confidential. The more closely guarded the information, the easier this element is to prove.
- It must have been imparted in circumstances importing an obligation of confidence: This is where the relationship matters: an NDA, a marked document, a private meeting, or a contract clause all signal that the recipient knew the information was not theirs to use.
- There must be an unauthorised use of the information to the detriment of the person who communicated it: The recipient must actually have used or disclosed it beyond the permitted purpose.
The third element is where many claims fail, as Filby v TEG Live shows. The plaintiff pitched an idea for a promotional concert to a promoter, and later argued the promoter had used his confidential idea. The claim was dismissed because the idea was found to be inherently unspecific, the information had not been received in circumstances importing an obligation of confidence, and there was no misuse.
Two consequences follow from the way the trigger works. First, protection does not depend on a signed document. Oral information disclosed in a private meeting can be protected, and equity can bind a recipient who simply knew the information was confidential. Second, because every element turns on what you can prove, documents and systems are not bureaucracy. They are evidence. A marked document, a signed NDA, and a restricted folder are each pieces of proof that the information had the necessary quality of confidence and was imparted in circumstances importing an obligation.
The contractual overlay: NDAs and employment clauses
Equity protects you by default, but it has limits. The information must qualify, and the obligation must arise from the circumstances. A contract removes most of that uncertainty by defining the deal in advance.
A well-drafted non-disclosure agreement (NDA) does more than say "keep this secret". It defines what counts as confidential information, sets out the permitted purpose for which it can be used, identifies who it can be shared with, states how long the obligations last, and requires return or destruction of the material when the relationship ends. It also records carve-outs, such as information that enters the public domain or that must be disclosed by law.
Employment contracts and contractor agreements serve the same function for the people closest to your information. Standard provisions include confidentiality obligations that survive the end of the relationship, and intellectual property assignment clauses so work created for you is owned by the business rather than the person who created it. Where founders and co-owners are involved, a shareholders agreement can set expectations about how confidential information is handled and what happens on exit.
None of this replaces equity. Contract and equity run alongside each other, and a court can enforce either. But a contract lets you define the scope precisely, which is especially valuable for information that might not qualify for equitable protection on its own.
Creating and marking documents: why the paperwork matters
The way you create and label documents feeds directly into the legal trigger. Consistent marking, such as "Confidential", "Commercial-in-confidence" or "Confidential, do not distribute" on documents you share externally, creates the record that you treated the information as confidential. Ownership statements, such as a note that the document and its contents are the property of the business, serve the same purpose.
A simple classification system can make the whole thing operational without an enterprise security budget:
- Public: fine to share, such as website copy and brochures.
- Internal: for staff and contractors only, such as procedures and team updates.
- Confidential: strict need-to-know, such as customer lists, financials, product roadmaps and legal documents.
Once the tiers exist, the rules write themselves: where each tier can be stored, who can access it, whether it can be emailed, and whether it must be password-protected. Version control matters too, because drafts often contain more sensitive detail than final versions. Negotiation notes, redlines and internal commentary should sit in restricted folders, not on a shared drive.
The legal point is simple. Conduct inconsistent with confidentiality, such as treating information casually or circulating it widely, makes it harder to argue later that the information had the necessary quality of confidence. The reverse is also true: a disciplined paper trail is what you would show a court to prove the first two elements of the claim.
Day-to-day protection and what it proves
Most leaks are not dramatic. They are a team member downloading the wrong file, a contractor still holding access after the project ends, or a document forwarded to a personal email account. Practical controls close those gaps:
- Limit folder access: Give access only to people who genuinely need it, and use role-based permissions rather than open access.
- Remove access immediately: Cut off access the moment someone leaves or a contract ends.
- Turn on multi-factor authentication: Require it for cloud accounts that hold sensitive material.
- Avoid personal email: Do not use it as a channel for confidential documents.
- Keep a simple internal policy: Set out what is confidential, where it can be stored, who approves external sharing, and what to do if a document goes to the wrong person.
An offboarding checklist is worth particular attention, because confidential information often leaves the business when a person does. Access removal, device return, and confirmation that material has been returned or deleted should all be standard steps.
These controls have two legal effects. They reduce the chance of a leak in the first place. And if a leak happens, they demonstrate the reasonable steps you took to protect the information, which strengthens both an equitable claim and, where personal information is involved, a statutory defence.
The privacy overlay: when documents contain personal information
Some confidential documents are confidential for a different reason: they contain personal information about identifiable individuals. Customer lists, employee files and CRM exports are the obvious examples. When that is the case, the Privacy Act 1988 (Cth) applies, and the Australian Privacy Principles (APPs) impose duties that exist independently of equity and contract.
Two principles matter most for document handling. APP 6 provides that if you hold personal information collected for one purpose, you must not use or disclose it for a secondary purpose unless the individual has consented or an exception applies. APP 11 requires you to take such steps as are reasonable in the circumstances to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure, and to destroy or de-identify it once it is no longer needed.
The key question for a small business is whether the Act applies at all. Under s 6D of the Privacy Act, a business with an annual turnover of $3,000,000 or less in the previous financial year is generally a small business and exempt from most of the Act. But the exemption has exceptions, and they are broader than many owners assume. It does not apply to businesses that provide health services and hold health information, that disclose personal information for a benefit, service or advantage, that act as contracted service providers for Commonwealth contracts, or that are credit reporting bodies.
If the Act does apply, the OAIC can investigate and the business can face regulatory action, including civil penalties for serious or repeated interferences with privacy. For a business handling customer or employee data, that makes the day-to-day protections in the previous section a legal duty, not just good practice.
Departures and disputes: where confidentiality bites
The moment of maximum risk is when a relationship ends. A departing employee takes knowledge of your business to a competitor or a new venture, and the question becomes what they can lawfully use.
Australian courts, including the Court of Appeal in Del Casale v Artedomus, draw a line between categories of information. True trade secrets, such as a secret supplier source or a proprietary formula, remain protected after employment ends. General skill and knowledge, the competence and experience an employee has built up, travels with them and cannot be restrained. Between the two sits a category of confidential information that may be protected where the contract says so, or where the circumstances of disclosure imported an obligation. This is why the express confidentiality clause in the employment contract matters: it can turn information that equity might not protect into something the employee is contractually bound not to use.
Directors and employees also owe statutory duties. Section 183 of the Corporations Act 2001 (Cth) prohibits directors, secretaries, other officers and employees from improperly using information acquired through their position to gain an advantage or cause detriment.
When a dispute does reach court, the remedies available include injunctions to stop further use, orders for delivery up or destruction of material, damages, and an account of profits. But every one of these depends on the claimant proving the three elements. Information that was vaguely expressed, disclosed without any signal of confidentiality, or never actually misused will not support a claim, no matter how valuable the business thinks it is.
Where a lawyer helps
The system only works if the pieces line up. A lawyer is most useful at four points:
- Drafting the contracts: Define confidentiality in NDAs, employment and contractor terms, intellectual property assignment, and shareholders agreements, shaped around how information actually flows in your business rather than a generic template.
- Assessing what qualifies: Identify which documents genuinely qualify as trade secrets or confidential information, so you know which need the highest level of protection and which employees or contractors should sign what.
- Enforcing quickly: Act fast when a leak happens, because injunctions are urgent applications and the evidence gathered in the first days often decides the outcome.
- Checking privacy compliance: Build the APP obligations into the same systems that protect your commercial secrets where the documents contain personal information.
Engagement letters or written authorities for advisers who coordinate disclosures, such as during fundraising or due diligence, are another area where a short document can prevent a costly dispute over what someone was entitled to share.
Confidentiality is a proof problem
Read the three elements of breach of confidence again and notice what they have in common. Every one of them is about what you can demonstrate: that the information was genuinely confidential, that the recipient knew it, and that they used it. The contracts, the markings, the classification tiers and the access logs are not administrative decoration. They are the evidence you would rely on if the worst happened.
Businesses that treat confidentiality as a process problem early, with a signed NDA before the first pitch, an employment contract that protects both confidentiality and ownership of work product, and a folder structure that matches the classification, rarely need to test their system in court. Businesses that skip the paperwork discover the cost of an injunction application and a forensic review of shared drives is many times the cost of a lawyer drafting the wrappers in the first place. A consultation to map which documents are confidential and which contracts need updating is inexpensive, and it is the point at which the system is cheapest to fix.