Reviewer page
The verify.vraimony.com reviewer page does not set cookies, load ad pixels, or track IP addresses beyond what is needed to serve the static HTML page. The reviewer is not identified.
What Vraimony stores. What it does not. What the verify link means. What no-tracking means in practice. What the structural guarantee does and does not cover.
The verify.vraimony.com reviewer page does not set cookies, load ad pixels, or track IP addresses beyond what is needed to serve the static HTML page. The reviewer is not identified.
verify.vraimony.com is domain-separated from the sealing surface. It is read-only. It cannot modify records. Visiting it does not create a user session or log browsing behaviour.
The platform uses minimal analytics (page load, purchase events) for product improvement only. No behavioural scoring. No hidden profiling. No resale of data.
"If your file is not structurally review-ready after sealing, we revise the package structure once at no extra cost."
Every evidence file is hashed before sealing. The hash is recorded in the sealed record.
The canonical record is signed with an ed25519 private key held on the sealing server.
Sealing time is recorded. Tampering with the record after sealing breaks the signature.
The ed25519 signature can be verified without Vraimony infrastructure using the public key.
6 WooCommerce chargeback cases tested (2026-03-31). All 4 layers operational: Structural, Integrity, Policy, Readiness. Rules Registry v4.
Ed25519 signing key active (ed25519_2026-03-11). All sealed records carry a tamper-evident signature verifiable without Vraimony infrastructure.
verify.vraimony.com is read-only. No tracking on reviewers. No account required. Domain separated from the sealing surface.
Documented example cases available. Each shows evidence structure, engine verdict, and review path. See examples →
Review the record lifecycle page for access period, exports, and what remains verifiable after access ends.