How it works
The protection lives in the process: each participant accepts the NDA before the meeting link is shown, and a visible witness records what happens next.
Every participant receives a personal link, verifies their identity and accepts the NDA. The meeting link is shown only after acceptance.
A visible bot named “C-NDA Protocol” joins the call. It records the audio and keeps the event log: who joined, who left, and when. Everyone can see it is there.
After the call, the recording is transcribed automatically. The evidence package (participants, acceptances, transcript, event log) is sealed and secured with blockchain anchoring.
Five steps, always in the same order: identity and agreement come before access, and the evidence is sealed before it can be verified.
An evidence product is only as strong as what it admits about itself.
It joins with the name “C-NDA Protocol” and appears in the participant list. Covert recording is not what this is: the visibility is part of the evidence.
If the bot loses connection during the call, the gap is stated in the certificate. An evidence product that hides its blind spots is not an evidence product.
Corrections produce a new certificate in a revision chain, never a silent edit. The original fingerprint stays anchored.
The bot delivers the audio; the transcript is generated automatically afterwards, declared as automatic, then sealed into the evidence package.
C-NDA is a progressive web app: from your browser menu you can install it on desktop or add it to your phone's home screen, and it opens like a native app. No store, no separate download: the same portal, the same evidence engine.
C-NDA Protocol
Install from your browser menu
A verifiable confidentiality protocol. It links identity, the NDA, access, evidence and blockchain anchoring in one fixed sequence, and produces a certificate anyone can check.
Confidential information shared in two settings: documents and other material you disclose after an NDA, and online meetings on Google Meet, in early access. Microsoft Teams and Zoom are coming.
Each party is identified and accepts the NDA. Access follows acceptance. The evidence is sealed with a cryptographic fingerprint, secured with blockchain anchoring and summarised in a certificate.
The set of original records behind a certificate: NDA terms, each party's identification and acceptance, and, for meetings, the event log, recording fingerprint and transcript. You download it as a ZIP alongside the PDF.
Each party receives their own link by email. Opening it proves control of that mailbox; the party can then identify further (one-time email code, passkey or Google account) and accept.
In a scheduled meeting the Google Meet link is encrypted and revealed only after the participant has accepted. Anyone in the call who has not accepted is flagged to the host and recorded in the event log; admitting people to the call remains the host's decision.
Only the cryptographic fingerprint of the evidence package, through blockchain anchoring. No names, no documents, no meeting content.
Yes, on Google Meet, in early access. A visible C-NDA witness joins the call and the session becomes part of the evidence. In a call that is already running, the protection covers the recorded phase from the moment it starts.
No. Signing is one step. C-NDA also ties access to acceptance, records what happens and makes the record verifiable by third parties.
No. Enforceability depends on the agreement and on the applicable law. The blockchain lets anyone check that the evidence has not changed and when it was sealed.
Enter the certificate code on the verification page, no account needed. Or recompute the fingerprint of the evidence package yourself and compare it with the blockchain anchor.
You schedule a Google Meet through C-NDA and invite the participants. Each one verifies their identity and accepts the NDA before the link is revealed; a visible C-NDA witness joins the call, and the session evidence is sealed and anchored after it ends.
You send an NDA to one or more parties. Each one verifies their identity and accepts; the acceptances are sealed into a certificate anchored on blockchain, which you have before you share the confidential material.
No. Only a cryptographic fingerprint is anchored. Documents, names and meeting content stay off-chain, and the fingerprint reveals nothing about them.