Every trade secret program I've ever seen has the same shape on paper. There's a policy. There are NDAs. There are acknowledgments. There's training. From a compliance standpoint, the program looks complete.
Then someone reshares a confidential design document with a vendor's vendor. An NDA expires and nobody notices for eight months. A senior engineer leaves and the company realizes they never actually reacknowledged her exposure to the latest set of trade secrets. None of these are policy failures. They're enforcement failures — small gaps where the gap between "what the program says" and "what's actually happening" widens unnoticed until something goes wrong.
Most of the recent features we've shipped at Tangibly are aimed at exactly these gaps. Trade secret protection isn't a one time setup. It's an ongoing operational discipline. Our job is to make that discipline easy to maintain, hard to ignore, and visible when it's being skipped.
Here's what we've built recently and why each piece matters.
Visibility into what happens after you share
When you share a trade secret asset with someone, an employee, a contractor, or a partner, you're trusting them to understand the boundaries of that share. But what happens when they reshare it with someone else? In most systems, you'd never know.
We now notify the asset owner when their shared asset is reshared. The owner gets an email and an in app notification with the relevant context: who reshared it, with whom, and when. This isn't about restricting collaboration. Sometimes resharing is appropriate and necessary. It's about making sure the original owner is in the loop on the actual reach of the asset, not just the initial share.
This is a small change with a real impact: trade secret owners get visibility where there used to be silence.
Acknowledgments that don't get stale
A one time acknowledgment that "I have read and agree to protect the company's trade secrets" is a starting point, not an ending point. People forget what they signed. Roles change. New trade secrets get added to the protected list. A signature from two years ago is, at best, weak evidence of current understanding.
We've built two things to address this. First, periodic reacknowledgment. The system can be configured to ask employees, contractors, and partners to reacknowledge their obligations on a schedule that fits your program, whether annually, on role change, or when material new assets are added. Second, manual reacknowledgment for situations that don't fit a schedule: a sensitive project ramping up, a personnel event, or a change in the relationship.
Both flows are designed to be lightweight on the user side and complete on the audit side. You get a clean record of who acknowledged what, and when, with full version history and defensible documentation.
NDAs that don't quietly expire
This one I find particularly important because it's the failure mode that's hardest to detect manually. NDAs have terms. Terms expire. And in most companies, the way you find out an NDA expired is when someone notices much later, often after sensitive information has continued flowing under what everyone assumed was an active agreement.
We now alert NDA owners one month before expiration, both via email and in the platform. After expiration, the NDA's status visibly turns red in the UI. There is no ambiguity about whether the agreement is still in force. The result: NDAs get renewed before they lapse, and when they do lapse, the people working with the counterparty know immediately rather than weeks or months later.
This is the kind of feature that doesn't get noticed when it's working, until you compare it to what you used to do, which was nothing.
Permissions that match how trade secrets actually flow
Trade secrets don't have uniform sensitivity. An asset shared internally with the engineering team needs different controls than one shared with an outside law firm preparing a filing or a partner under a specific NDA. Generic share controls force you to either over restrict, which slows legitimate work, or under restrict, which creates exposure.
We now offer full permission controls at both the asset level and the sharing level. You can specify who can view, edit, share, or download, both as a property of the asset itself and as a property of each individual share. The difference matters: an asset might be broadly viewable internally, but every external share needs explicit per share controls. Both layers are now explicit and auditable, supporting stronger trade secret governance.
The pattern, not just the parts
What ties these features together is a shift in how trade secret protection is treated.
The old model is event driven: someone joins, they sign an NDA. Someone leaves, you remind them of their obligations. An incident happens, you investigate.
The new model, and the one our customers are increasingly asking for, is continuous. Trade secret protection is something the system maintains in the background, surfacing decisions to humans when they need attention and creating an audit record for everything else. The features above each close a specific gap, but together they're moving Tangibly toward a model where running a trade secret program doesn't depend on someone remembering to run it.