C-NDAPROTOCOL
Join the waitlist
How it worksWho it is forSecurityPricingVerify
About usContact
Sign in

Language

English

Italiano Français Deutsch Español

Legal, M&A and diligence

Who was actually in the room, and what were they bound by?

A process NDA covers the process. It does not tell you who joined a specific session on a specific afternoon, whether each of them was inside the perimeter, or what they heard while they were there.

The moment

A diligence session over video. Several people on the other side, at least one of whom nobody on your team has met, and a calendar invitation that has been forwarded at least twice.

What goes wrong today

  • The attendance list is reconstructed afterwards, from memory or from an invitation that people forwarded. A forwarded invitation is not a record of who joined; it is a record of who was told.
  • The NDA covers the transaction. It does not name this session, these people or this date, and the link between the obligation and the disclosure is left to be argued about.
  • A participant nobody recognises is either awkward to challenge live or quietly ignored, and both outcomes end up in the same place, which is no record at all.

What happens with C-NDA

  1. 01

    Access starts at acceptance

    Each participant is invited individually. The meeting link is revealed only after they have identified themselves and accepted; a forwarded link carries no acceptance with it, and anyone in the call who has not accepted is flagged to the host.

  2. 02

    The room is observed, and the observation is declared

    In a protected meeting the witness records who joined and when. Someone it could not identify is written into the certificate as exactly that, an unidentified participant, because a gap you can see is evidence and a gap you cannot is not.

  3. 03

    The record is sealed after the call

    Transcript produced, package sealed, fingerprint anchored. The date on it belongs to a public blockchain, not to our database.

  4. 04

    It can be handed to the other side

    A certificate code lets anyone confirm existence, integrity and the anchor without seeing names or contents, so the fact of the record can be shared without sharing the record.

What ends up in the certificate

  • each party, with the identification method used and the moment of acceptance
  • the NDA text accepted, with its fingerprint
  • the event log of the session: entries, exits, and anyone who could not be identified
  • the automatic transcript and the fingerprint of the recording
  • the anchor, and any coverage gap, declared rather than omitted

The point is not surveillance of a meeting. It is that the perimeter of a confidential session should be a fact recorded at the door, not a reconstruction attempted a year later.

Where this stands today: registering an NDA with identified signatories, sealing it and anchoring it is live. The protected meeting (the witness that joins the call, the recording and the automatic transcript) is live on Google Meet in early access, and the feature list states each capability's status.

See the status of each capability

This page describes what our system records and how it can be checked. What that evidence is worth in your jurisdiction is a question for a lawyer, and we do not answer it.

Protect a meeting or a document

Every protection produces a certificate that can be verified later, without an account on the other side and without trusting us.

Join the waitlist

Where to go next

Why C-NDAHow verification worksPricing