Make employee NDAs more robust with a verifiable record of confidential knowledge
When an employee joins a company, they need access to knowledge that makes their work possible. When they leave, confidentiality obligations need to remain connected to the information they received and helped develop.
An NDA establishes obligations. Bernstein helps give those obligations an identifiable reference: preserved project files, certified versions, and sharing under expressly accepted conditions. This connection matters at three moments: onboarding, project development and departure.
Consider Alex, a hypothetical employee joining Acme to work on a technical project.
Onboarding: certify the knowledge that already exists
Before giving Alex access, Acme collects the confidential project materials relevant to their role. These might include source code, technical specifications, experimental results or a documented manufacturing process.
The company uploads and certifies a baseline revision in Bernstein before Alex joins the project.
Files are encrypted client-side before transmission. Their cryptographic fingerprints are anchored to the Bitcoin blockchain and timestamp authorities, creating independently verifiable evidence of the certified content’s existence and integrity at a particular time. The confidential content itself is not published on the blockchain.
Acme now has a preserved reference for the project knowledge that predates Alex’s involvement. If Alex later claims that particular material originated with them during their employment, the company can produce the earlier files and their corresponding certificate. The baseline supports that factual distinction; employment agreements and contribution records establish the surrounding rights.
Refer to confidential collections without reproducing them
The same certified revision can serve as a reference in Alex’s confidentiality agreement. Acme prepares a collection of the materials it intends to cover. The agreement identifies that collection by its project name and Bernstein certificate ID, and defines the confidentiality and permitted-use obligations attached to it.
The technical content remains in the encrypted repository. There is no need to reproduce formulas, source code or experimental details in the employment paperwork merely to identify the collection.
This is useful when the protected knowledge spans hundreds of files or contains information that should not circulate with ordinary contracts. Those contracts may later pass through legal reviews, audits or due diligence. A certificate reference allows them to point to a fixed collection without carrying its sensitive contents.
Where the intended scope is the entire certified collection, the agreement can say so expressly, subject to its exclusions, such as information already public or independently developed. A dedicated collection makes this simpler than referring to a mixed project archive and trying to describe confidential subsets in the agreement.
Where detailed verification is needed, the underlying materials can be made available to authorized reviewers through controlled sharing. The certificate provides the reference against which those files can be checked.
Share the baseline under explicit conditions
Acme then shares the certified collection with Alex through Bernstein. Sharing can require recipient verification and in-app acceptance of confidentiality terms before access. Those terms can define the permitted purpose, restrictions on further disclosure, and responsibilities for handling the information.
Acme keeps the certified collection, the applicable terms and the record of Alex’s acceptance connected in its documentation. Each element serves a distinct purpose:
- The certified revision fixes the content of the collection and provides verifiable evidence of when it existed.
- The confidentiality terms define the obligations attached to that collection.
- Alex’s acceptance documents their agreement to those conditions.
The resulting arrangement is more concrete than a standalone NDA referring broadly to company information. Alex is given access to an identifiable body of knowledge under explicit conditions, and Acme preserves the version to which those conditions refer.
During employment: keep the record current
A project changes as people work on it. The onboarding baseline should therefore become the first entry in an ongoing record.
Acme establishes a certification routine around meaningful updates: design changes, development milestones, new experimental results or other significant additions. Bernstein’s immutable revisions preserve successive states of the documented content.
This history helps distinguish the knowledge that existed before Alex joined from developments made during their employment.
The company can use these certified references in project acknowledgements, updated confidentiality schedules or agreements concerning new work. When needed, contribution records can be preserved alongside the technical materials.
When additional material is shared, its certified reference can be connected to the confidentiality terms governing that disclosure. The benefit is continuity. The company’s agreements and its documented knowledge remain connected as the project evolves.
Departure: refer to an identifiable body of confidential information
When Alex leaves, Acme prepares a current certified revision and a confidentiality schedule for the departure documentation. The schedule identifies the project and the Bernstein certificate IDs corresponding to the covered collections. The departure agreement or acknowledgement refers expressly to that schedule when restating continuing confidentiality and permitted-use obligations.
This provides a fixed reference for the documented project knowledge at departure. If the scope is later disputed, the company can retrieve the preserved files and verify that they match the referenced certification.
Relevant earlier revisions should also be included. Alex may have received an abandoned design, an earlier formulation or a historical analysis that no longer appears in the latest project files. The revision history allows the company to account for that information without relying solely on the project’s final state.
As at onboarding, these references avoid reproducing sensitive technical details in the departure paperwork. The detailed content stays securely preserved, while the agreement identifies the collections to which the continuing obligations apply. The departure record reinforces the obligations established during employment and makes their subject matter more specific.
Keep the evidence confidential and available
Preserving evidence should not require unnecessary disclosure of the information being protected. Bernstein combines client-side encryption, immutable revisions and sharing with recipient verification and acceptance of terms. Acme can preserve its confidential project materials and make them available to Alex under defined conditions.
This separation is central to the workflow: agreements refer to identifiable certified collections, detailed content remains protected, and the originals are preserved for verification when required.
Certification fixes the reference. The confidentiality agreement defines the obligations. Neither requires the company to expose its technical knowledge in paperwork that may circulate more widely.
Give confidentiality obligations a concrete reference
With Bernstein, Acme can connect Alex’s employment to a documented sequence:
- Certify the project baseline before onboarding.
- Share the relevant collection under expressly accepted conditions.
- Preserve certified revisions as the project develops.
- Reference the relevant certified collections in departure documentation.
The result is a clearer connection between the company’s knowledge, the information made available to the employee, and the obligations attached to it.
That is how Bernstein can make employee NDAs more robust: by giving confidentiality agreements a precise, verifiable reference while keeping the underlying knowledge securely preserved.
