Trade Secret Records: Presenting the Evidence to Counsel
How a timestamped, confidential record can support a claim of prior possession of unpatented technology, source code, or trade secrets — while keeping the underlying material undisclosed. Outcomes depend on the facts; this scenario guide is general information, not legal advice.
Compliance under US Defend Trade Secrets Act (DTSA) & EU Directive 2016/943
To qualify for trade secret protection, owners are generally expected to demonstrate they took "reasonable steps" to keep information secret. Encrypting AES-256 archives and registering SHA-256 hashes can be part of demonstrating such steps; whether the standard is met depends on the specific facts.
When a departing employee or competitor is suspected of taking a trade secret, matching cryptographic hashes can evidence that you possessed the exact material before the apparent leak — without revealing the source code publicly.
Pre-NDA / Investor Pitch: Documenting the Record
- Timestamp baseline deck & code: Generate an Intellectual Property Vault certificate prior to sending confidential decks or code to potential partners or investors.
- Reference Registration ID in NDA: Insert the unique Vault Registration ID into Schedule A of non-disclosure agreements so the record remains traceable; the weight given to it depends on the specific facts.
- Audit trail in dispute: In case of breach, present both the eIDAS RFC 3161 Qualified Timestamp (.tsr) and the Bitcoin OpenTimestamps anchor (.ots) — automatically issued by IP Vault on every run — to prove the confidential information originated from your organization at a specific time.