Hidden Tokens / Academy / Lesson 6
Prove what the AI received
Ask Claude Desktop to show what it received: Hidden Tokens writes a local page, "What Claude saw", that lists every answer the AI got and re-checks them against your key, showing any value found in clear by its code, never in clear. The page is signed, so you or your DPO can verify offline that nobody edited it; during the trial it is signed by your computer, which proves its integrity but not your firm's identity.
Before you start
You need the conversation from lessons 3 and 5 in Claude Desktop: the page lists what the AI received through Hidden Tokens, so it needs at least a few exchanges.
Step by step
-
Ask Claude what it received
In Claude Desktop, in the same conversation, ask: Show me what you received. Hidden Tokens writes the page
CE-QUE-CLAUDE-A-VU.htmlinto theHidden-Tokenssubfolder and gives Claude only the verdict and the counts. -
Open the page and read the counts
Open
CE-QUE-CLAUDE-A-VU.htmlin your browser. At the top: the answers the AI received, the distinct codes it saw, the numbers in clear (amounts, dates) and the real values found in clear. On the sample folder, that last count should be 0. A value found is shown by its code, never in clear, so the page itself can be shared. -
Verify it in the app
In the Hidden Tokens menu, choose Verify a proof…, pick the page and click Verify. The app answers Proof verified when the signature holds and nothing in the page has changed since it was produced.
-
Verify it in a browser, offline
Anyone can do the same check without the app: on hiddentokens.com/verify-seal, drop the page. The check runs in the browser and nothing is sent. During the trial, the page is signed by a key created on your computer: it proves the page is intact and comes from one computer, not which firm produced it.
-
Keep the page for the badge
Keep
CE-QUE-CLAUDE-A-VU.html: the final exercise (lesson 8) asks for it, checks it in your browser and issues the badge. A subscriber can go one step further and give clients a seal certified by Hidden Tokens; it needs a paid licence, so the Academy shows it without making you produce one.
What can go wrong
- The page shows values found in clear. Look at their codes: often a word was coded somewhere and appears in clear elsewhere. On a real folder, decode the code on your computer to see what it was, and tell us: each case becomes a test of the engine.
- "Proof not verified". The file was edited or re-saved by another program (some browsers rewrite a page when you "save as"). Use the page exactly as Hidden Tokens wrote it.
- The page says it is signed by a trial workstation. That is expected during the trial: it proves integrity, not identity.
Check yourself
Three questions, answered on this page. Nothing is sent anywhere.
✓ Lesson done: every step ticked and every answer right. Your progress stays in this browser only.
Frequently asked questions
Does this page cover what I typed into ChatGPT in the browser?
It covers what went through Hidden Tokens: the connector's answers to Claude and the messages the extension coded. Text typed into an AI without the extension, or files attached directly, are not in it.
Can someone edit the numbers in the page?
They can edit the file, but then its fingerprint no longer matches the signed one and the verification fails. That is the point of the signature.
What is the seal, then?
A seal is a short code or QR a subscribing firm gives its client: it says that over a period, the client's data reached the AI only as codes, and it names the firm, certified by Hidden Tokens. It requires a paid licence.
Written for app 0.14.4 and connector 2.42.0 on . Not yet replayed on screen on Mac and Windows: if a label differs from what you see, trust your screen and tell us.