Caemso Nexus
GVP — GhostVerify Protocol •
Trust infrastructure for AI-era introductions Pitch Pilot Contact
GVP v0.1 • Consent-first • Privacy-first • Cross-platform

Exchange trust before you exchange data.

GVP is a protocol that lets professionals verify authenticity and consent in a secure introduction — without sending raw documents, IDs, or sensitive files around.

Request a Founding Partner Pilot Open the Pitch How it works
✅ Verifiable integrity (tamper-evident) 🔐 Encrypted payload (token + key separation) ⏱ Expiry + consent scope built-in

What a “GhostVerify Package” looks like

GVP1 meta: scope=professional_intro | expires=14d | shareable=false payload: AES-GCM encrypted attributes (no raw files) signature: device-signed (tamper-evident) sharing: token via QR/link + key via separate channel
No raw files Consent-scoped Device-signed

The problem

Professional intros often start with over-sharing: CVs, decks, IDs, screenshots, chat logs. That data gets copied, forwarded, trained on, or misused.

The gap

In 2026, bots and synthetic profiles make “looks legit” meaningless. You need verifiable authenticity + explicit consent — without centralizing sensitive data.

The fix

GVP enables a verifiable handshake: encrypted attributes, signed by the issuer device, scoped by consent, with expiration. Share trust — not raw data.

Demo story (plain language)

A 16-year-old should get this. No jargon.

Meet Sara (recruiter) and Tom (candidate). Sara wants to introduce Tom to a company. Normally she emails a CV, LinkedIn screenshots, maybe even an ID scan. That stuff gets forwarded, copied, stored in random inboxes, and sometimes used as training data. Tom hates that — but he also wants the introduction.

What they do with GVP:
  • Sara goes to caemsonexus.com/gvp and clicks “Generate Package”.
  • She selects only what’s needed: role, skills, availability, and “verified contact”.
  • GVP creates two things: a code (the token) and a key (like the key to a lock).
  • Sara sends the token to the company (email/QR/link).
  • Sara sends the key to the same contact via a different channel (WhatsApp/SMS).
  • The company opens the token + key on the verify page.
  • The page checks: “Is this package real?” “Has it been changed?” “Is consent OK?” “Is it expired?”
  • If everything is valid, the company sees only the agreed info — not a pile of raw documents.

Result: Tom stays in control, Sara can still introduce him, and the company gets a verified package instead of “trust me bro” PDFs.

Why this is safer:
  • Token alone is useless (without the key you can’t open it).
  • It expires (so it can’t live forever in inboxes).
  • It’s signed (so edits/fakes get detected).
  • Consent is embedded (what it may be used for).
One-liner:

“GVP lets you send a locked box + a separate key, with a tamper-proof seal and an expiry date.”

How it works

Simple flow. Strong guarantees.

1) Create a package

  • Issuer selects which attributes to share (e.g., role, domain expertise, verification status).
  • Consent scope + expiration are embedded (what it may be used for, and for how long).
  • The payload is encrypted so only the intended recipient can open it.

2) Sign it (tamper-evident)

  • The issuer device digitally signs the package.
  • Recipients can verify it was not altered.
  • No “trust me bro” PDFs required.

3) Share token + key

  • The package token can be shared via QR or secure link.
  • The decryption key is shared out-of-band (separate channel).
  • Token without key = useless to attackers.

4) Verify & reveal

  • Recipient verifies signature, consent scope, and expiry.
  • If valid, the payload is decrypted locally.
  • Only the allowed attributes are revealed.
Note: v0.1 focuses on integrity + consent + encryption. Advanced attestation/ZKP can be added later.

Founding Partner Pilot

Get early access + shape the protocol.

What you get

  • Access to GVP v0.1 verification flow (generate → share → verify).
  • Custom consent scopes for your workflow.
  • Priority roadmap influence (partner, not a ticket).
  • Early pricing (locked).

Price (pilot)

Pilot fee: €500 (one-time) • Includes 3 months access • Limited seats.

Email for pilot Open pitch

We keep the MVP simple: verifiable packages + consent + expiry. Advanced features come after the first paying pilots.

Contact

If this resonates, let’s talk pilots.

Email

Use-case + your current flow + what “trust gap” hurts most.

hello@caemsonexus.com Back to top

What we’ll show

  • Generate → Share → Verify demo flow
  • Consent scopes & expiry
  • How to embed into existing tools
  • Pilot terms