Inventors and creators

The description has to be detailed enough to be judged, and that is the problem

A prototype, a process, a formulation. To get an opinion worth having, you have to say enough that the person could use it. The conversation in which you say it is the one that should be protected, and it almost never is.

The moment

The call with the engineer, the manufacturer, the potential partner or the fund's technical advisor: the one where you stop being vague, because a vague description gets a vague answer.

What goes wrong today

  • In many places what was public before a filing matters to whether an invention can still be protected. What counts as public is a question for a patent attorney, not for us, but whether a specific conversation happened under an obligation of confidence is a question of evidence, and evidence is what people usually do not have.
  • The obligation, when it exists, is a PDF signed at some point. It does not say which conversation it covers, and reconstructing that months later means email threads and calendar entries.
  • The people who most need the detail (a supplier, a lab, a specialist) are often the ones you have never met before the call.

What happens with C-NDA

  1. 01

    The obligation comes first

    In a scheduled meeting the link is shown only after each participant has identified themselves and accepted. There is no exception for an important guest.

  2. 02

    The description is recorded as it is given

    In a protected meeting the transcript is produced automatically from the recording and sealed with the evidence, declared as automatic. A correction creates a new linked certificate, never a silent edit.

  3. 03

    The package is sealed and anchored

    One evidence package, one cryptographic fingerprint, secured with blockchain anchoring. The date is the blockchain's, not ours.

  4. 04

    It stays checkable without us

    Whoever needs to be convinced later (a counsel, a court-appointed expert, a counterparty) recomputes the fingerprint from the file and finds it on the chain. They do not have to believe C-NDA exists in good faith, or at all.

What ends up in the certificate

  • who was in the conversation and how each of them was identified
  • the moment each of them accepted the confidentiality obligation
  • for a protected meeting: the automatic transcript of what was described
  • the fingerprint of the whole package, and the public transaction that carries it
  • the blockchain timestamp: from that moment on, any change to the package is detectable

We do not tell you whether to file first or talk first. We make the version where you talk leave behind something better than a memory.

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