Trade Secret

The oldest way of protecting technical knowledge trades disclosure for exclusivity. The problem is that some things lose their value the moment they are written down for the public: a customer list, the internal rules for setting prices, a cost structure, a calculation method nobody outside has worked out yet.

Simply hiding those things without any legal footing leaves a company with nothing to say when they walk out the door. The usual scene: someone who ran sales for three years resigns, taking a file of customer contacts and the terms each one is on. A month later they join a competitor, and the month after that those same customers start receiving similar offers. The list took three years to build, and there is nothing obvious to reach for.

Trade secret law fills that gap. There is no registry and nothing to apply for. Instead the law asks whether the company actually treated the information as secret, which turns everyday handling into the condition that creates the right. Nothing goes on a calendar, but the access settings and the paperwork of ordinary weeks become the evidence. That is a harder discipline than a filing deadline, because it has to hold continuously rather than once.

Among the four kinds of intellectual property, this one arises without registration, which makes it look like copyright. One difference matters. Copyright survives neglect; a trade secret does not. Stop managing the information as confidential and it drops out of protection at that moment.

Three requirements have to hold at once: the information is not publicly known, it has economic value because of that, and the company has managed it as a secret.

1. Not publicly known — this is where most claims fail. Describe the system architecture in detail in a job posting, or put the pricing formula in a deck that circulates outside, and that part is already public.
2. Economic value — holding the information has to produce some advantage. Three years of per-customer churn reasons qualifies; a list of restaurants the team likes does not. The working test is whether a competitor learning it would leave you worse off.
3. Managed as a secret — almost every dispute turns on this requirement alone. There has to be a trail showing the information was handled as confidential.

What counts as that trail is usually some combination of the following.

1. Documents and files marked confidential.
2. Access restricted to the people who need it. Information sitting in a folder the whole company can open is hard to protect no matter how valuable it is.
3. A confidentiality undertaking signed at hire, and a return-and-delete check at departure.
4. A non-disclosure agreement in place before anything goes outside.
5. Logs showing who opened what, and when. A tool that records downloads is worth more here than one that only records views.

Unlike the other rights, this one has no time limit. It lasts as long as the secrecy does, and once the information is out there is no route back. That runs in the opposite direction from a patent, which becomes free for anyone to use after twenty years, so deciding what to file and what to keep quiet is a real choice rather than a formality.

The places where the trail actually gets built are predictable.

1. Onboarding and offboarding — a confidentiality undertaking on day one, a return checklist and revoked access on the last day. What was written down at the exit interview is often the only evidence that exists later, and the checklist should ask whether copies remain in personal accounts or on personal devices.
2. Conversations with outsiders — the agreement goes in place before internal figures are shown to an investor or a partner. Reverse that order and the conversation itself is the disclosure.
3. Permissions in document tools — who can open the file holding the customer list or the pricing policy is the management evidence. Leaving it open to everyone and labeling it confidential does not satisfy the requirement.
4. Deciding where technology lives — whether to file an application and publish, or keep the method quiet. If a competitor cannot infer the method from the output, secrecy holds up well; if taking the product apart reveals it, secrecy was never available. Pricing logic and customer data usually fall on the secrecy side; anything a user can observe in the interface usually does not.

"This doc is open to the whole company. If we want to call it a trade secret, the permissions have to come down first."

Without a management trail there is no claim to make.

"Did we get a signed return confirmation from the person who left? We need that to say anything later."

Building the evidence before there is a dispute to use it in.

"Let's not file on this one. Publishing it hands them the method."

Declining the disclosure-for-exclusivity trade.

At Pagedeck the issue surfaced over a document Sofia had maintained for three years, holding the terms each customer was on. It sat in a folder all 45 people could open, with the word confidential appended to the filename.

Grace checked and found four people actually used it for their work. Access came down to those four, view logging was switched on for the file, and Theo confirmed download activity could be audited. The whole change took half a day, and a confidentiality undertaking joined the onboarding steps afterward.

The most common assumption is that important information is automatically a trade secret. The company decides what is important, so that judgment feels like it should carry protection with it. What the law examines is not importance but the management trail. The single most valuable document in the company, sitting in an open folder, is not a trade secret; a less significant document kept behind narrow permissions is. Tightening access after a dispute starts only establishes management from that point forward, and it does nothing about the state of things on the day the file left. The cheap version of this is narrowing permissions once a quarter, before anyone has a reason to.

The second misreading is that a signed non-disclosure agreement covers it. There is a document with a signature on it, so something has clearly been done. But that agreement binds only the party who signed. It does not reach someone who saw the information without signing anything, and it does not fix a folder that everyone inside the company can open. The agreement is one of the five kinds of trail, and the other four have to be built internally.