Not by policy. Not by permission. By math.
You had a car accident. You file a claim. Today, every adjuster, every contractor, every fraud analyst reads everything — your damage estimate, your fault assessment, your medical details, your entire claims history. It gets forwarded, stored, sometimes breached.
In this demo, you'll file a claim. Your data gets encrypted on your device. The server that processes it has no secret key and is mathematically incapable of reading your data. It runs six policy gates on encrypted values — coverage, deductible, fault, fraud, injury, jurisdiction — and produces a binding decision. Approve, deny, or flag. Route to fast-track, standard review, or special investigation. Set a payout band. All without seeing a single number.
Pick any numbers. This prevents the demo from being pre-generated.
Your claim was encrypted here. The server received scrambled bytes. It cannot read them — even if it wanted to.
Six policy gates ran on your encrypted claim. Each produced a single bit: pass or fail. The server never saw the values behind them.
This decision was made on data the system cannot see.
74 bytes. Binds the claim, the ciphertext, all six gate results, the routing, and the timestamp. Signed under three independent hardness assumptions. The insurer proves the decision was correct. You prove your data was never exposed.
A separate verifier checks every binding. If anything was tampered with — your claim, the decision, the server binary — the proof fails. This is what a regulator, auditor, or reinsurer would see.
Try to break it