Dashboard overview
The main dashboard shows:- Verifications this month — total successful verifications across all workers
- Verification rate — the percentage of attempts that result in a successful proof
- Activity by worker — breakdown per site/domain
Worker-level stats
Clicking into a worker shows:- Monthly totals — total, passed and failed verifications, each with a daily activity sparkline for this worker.
- Configuration summary — the worker’s current age requirement, automated and manual trigger settings, whether the popup is dismissible, and the session length. An Edit configuration button takes you to the full settings.
- Verification history — a paginated list of this worker’s verifications (25 per page), filterable by result (all, passed, or failed). Each row shows the date, the domain it ran on, the claim that was checked (e.g.
18+), the on-chain blockchain anchors, and the result. To export records in bulk across workers, use Exporting Audit Records.
Verification detail
Expand any row to see the full record for that verification. For the concepts behind the on-chain anchors and why they matter, see On-Chain Anchoring.- Summary — the claim, the date-of-birth upper bound used, the session ID, the audit record ID, and links to the on-chain request anchor (CCDVRA) and audit anchor (CCDVAA).
- Verification request — the exact signed request that was shown to the visitor.
- Proof — the zero-knowledge proof the visitor submitted. No personal data is contained in the proof — it only attests that the claim was satisfied.
- Audit record — the full cryptographic audit record (CCDVAA) for the verification. Hashing this record reproduces the on-chain audit anchor exactly, so anyone holding it can independently confirm the stored proof is what was anchored at verification time. Audit records exist for passed verifications from June 2026 onwards; failed verifications are never anchored.
Verify against chain
The Audit record tab includes a Verify against chain button. It recomputes the audit record’s hash in your browser and compares it with the anchor registered on the Concordium blockchain, fetched directly from a public Concordium node. No Veriox servers are involved in the check, so the result is independent of Veriox: a green check means the stored record is byte-for-byte what was anchored on-chain at verification time. A link to the CCDScan explorer is included if you want to inspect the raw transaction on a third-party site.The verification request and proof are stored so you have a complete, self-contained audit trail for each verification. They contain no directly identifying personal data.