Comment by lazide
5 months ago
For a company with any decent number of people with access to the code base, extremely difficult to maintain that type of protection.
5 months ago
For a company with any decent number of people with access to the code base, extremely difficult to maintain that type of protection.
I mean trade secret as a legal protection: code is declared as trade secret. Then if employee leaks it, and other company uses it, it can be sued.
It is not that simple. To have that protection, it needs to be treated (and protected) like an actual secret.
It’s why the nominal ‘top secret’ coke formula is stored in a giant vault.
If everyone at the company has access (and it’s a big company), good luck having that protection.
https://www.wipo.int/web-publications/wipo-guide-to-trade-se... is likely a good source for the "what constitutes trade secret"
One of the things there though is that trade secrets don't have exclusive rights. If you write code and then distribute the application, trade secrets don't protect it anymore.
There's also a section on trade secrets and digital objects... which includes code ... and that gets into other challenges.
https://www.wipo.int/web-publications/wipo-guide-to-trade-se...
... it also has guidance on trade secrets and LLMs.
https://www.wipo.int/web-publications/wipo-guide-to-trade-se...
7 replies →
claude says one needs to take "reasonable steps", which includes asking employee to sign NDA, setting access control, and putting TRADE SECRET disclosure in source files: https://ipwatchdog.com/2025/12/02/fourth-circuit-clarifies-r...
That hinges on whether you can convince a judge that your LLM's slop meets the requirement of being inaccessible to other professionals of the same field, and that committing it to your repo meets the bar for keeping it secret.
I wouldn't hold my breath.