FICTIONAL DEMO Synthetic people, ads, records, and trust keys. No live ad-platform connection or commercial certification.
THE ANATOMY OF A VERIFIED CLICK

One tap.
A whole chain
of trust.

Steve sees a racing shoe. Taps the ad. Lands at Kuma.
Now, can anyone show what actually happened
and whether the charge follows the rules?

A 10-second synthetic replay. Evidence you can inspect.

THE MOMENT IT BEGINS
9:41
kuma.running The feeling of the front row.
Meet your next starting line.
↗
YOUR FIRST PIECE OF EVIDENCEIt starts with a tap.
STEVE’S FEED · LOOP, A FICTIONAL SOCIAL APP

From attention to accountability.

TAP THE AD TO TRACE THE EVIDENCE
  1. 01Ad delivered

    Steve sees the creative

    Awaiting event
  2. 02Click captured

    A synthetic tap is recorded

    Awaiting event
  3. 03Merchant confirms

    A landing receipt is linked

    Awaiting event
  4. 04Claims disclosed

    Policy + decision declaration

    Awaiting event
  5. 05Evidence checked

    Signatures, links, and rules

    Awaiting event
  6. 06Billing decision

    Accept, reject, or hold

    Awaiting event

This is the order we inspect the evidence, not the targeting decision’s chronology. The decision declaration predates the ad impression.

THE EVIDENCE WORKBENCH

Don’t trust the story.
Test the records.

What happens when the receipt changes?
Choose a scenario. Same click, different evidence.

A complete, unchanged evidence bundle. The declared use matches the agreed policy, and the $0.42 click charge matches the terms.
01 THE CLAIMSIMULATED SOURCES

A click worth
$0.42 USD

Loop declares a billable click for Kuma’s Apex 01 campaign. Kuma pays the ad fee, not Steve.

Shopper
Steve synthetic persona
Merchant
Kuma Shoes
Buying platform
Loop Ads simulated
Agreed rate
$0.42 / valid click
Declared context
Motorsport interest synthetic declaration
↳

The platform’s declared reason is evidence of a claim, not proof that the claim is true.

02 THE CHECK BROWSER-RUN VERIFIER

READY WHEN YOU ARE

The evidence decides.

?

Tap the ad or run a scenario. The verifier checks the actual bundle, not a prewritten result.

INTEGRITYNot runUnchanged + signed
POLICY & BILLINGNot runWithin declared rules
COVERAGENot runRequired records present
SOURCE ASSURANCESIMULATED ONLYDemo keys do not establish real-world authority.
Your local verification session is ready.
SESSION KUMA-DEMO-001 · FIXED SYNTHETIC CLOCKRuns locally in your browser. No personal data collected by the demo.
A SMALL CLICK. A BIGGER IDEA.

Less “take our word.”
More “here’s the record.”

01

Portable evidenceOne linked bundle that the platform, advertiser, and a separate verifier can inspect.

02

Specific, bounded answersUnchanged records, declared policy, and a correctly calculated charge. Each checked separately.

03

An honest edge of proofNo claim of causal sales lift, true targeting motives, real-world identity, or live independent certification.

OPEN THE RECEIPTS

The evidence bundle

Every record below is synthetic. Signatures bind demo records to demo keys, not to real-world companies or events.

THE EDGE OF THE EVIDENCE

What this proves.
And what it doesn’t.

✓

What the code checks

Signature validity against pinned demo keys, record hashes, cross-record links, policy version, allowed declared context, fixed-clock freshness, and the charge against an agreed integer-cent CPC rate.

×

What it cannot establish

That a real person clicked, that the platform actually used its declared targeting reason, that a sale happened, or that advertising caused incremental revenue. A click cannot prove why an earlier ad was selected.

↗

Independent code, simulated trust

You can rerun the verifier separately. All source roles, events, and trust keys are controlled by this demonstration, so it is not independent commercial certification. Real deployment would need authenticated sources, governance, privacy controls, and independent key custody.

Kuma Shoes, Apex Racing, Loop, and Steve are fictional. This is not connected to or endorsed by Meta, Instagram, Puma, McLaren, Formula 1, IAS, or DoubleVerify.