Vraimony
Trust Center

Concrete answers about storage, privacy, and verify.

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.

No tracking on reviewers No behavioural analytics Read-only verify surface Ed25519 + SHA-256
Data & Storage

What is stored. What is not.

✓ WHAT VRAIMONY STORES
  • The sealed record: structured case data (timeline, claims, evidence references)
  • File hashes (SHA-256) — not the files themselves unless you upload them
  • The ed25519 signature over the canonical record
  • Timestamp of sealing
  • The reviewer-facing record page (no-login access)
  • Purchase/billing data — handled by WooCommerce + your payment processor
✕ WHAT VRAIMONY DOES NOT STORE
  • Reviewer identities or browsing behaviour
  • Cookies or tracking pixels on verify.vraimony.com
  • Analytics profiles on either side of the review
  • The truth or accuracy of claims — only structure and integrity
  • Legal identity of sender unless provided explicitly
  • Session data beyond what is needed to serve the review page
Retention: Sealed records are stored for the duration of your subscription or one-case access period. Export a copy in PDF / JSON format before your access period ends. Vraimony does not currently offer a public retention SLA beyond active account access.
No-tracking stance

What no-tracking means in practice.

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.

Verify surface

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.

Sender side

The platform uses minimal analytics (page load, purchase events) for product improvement only. No behavioural scoring. No hidden profiling. No resale of data.

What Verify means — and does not mean

Verify checks integrity. It does not certify truth.

✓ WHAT VERIFY CONFIRMS
  • The record has not changed since sealing (tamper-evidence)
  • The canonical hash matches the sealed record
  • The ed25519 signature is valid
  • The sealing timestamp is as recorded
  • Which evidence items were PASS, Declared, or Unverified at sealing
✕ WHAT VERIFY DOES NOT CONFIRM
  • That the underlying facts are true
  • That the sender is who they say they are
  • Legal admissibility in any jurisdiction
  • That the reviewer's decision will be favourable
  • Compliance with any specific regulatory standard
PASS / Declared / Unverified explained: PASS = content was hashed and the hash matches. Declared = stated by the sender, not independently hashed. Unverified = referenced but not provided or hashable. These labels describe what Vraimony can structurally confirm — not whether the claim is factually true.
Structural guarantee

What the guarantee covers. What it does not.

"If your file is not structurally review-ready after sealing, we revise the package structure once at no extra cost."
✓ Covered
  • Missing timeline anchor
  • No clear ask for reviewer
  • Reviewer path not set
  • Structure revision — once
✕ Not covered
  • Content accuracy or legal admissibility
  • Reviewer's decision or outcome
  • Multiple revisions
  • Legal advice or representation
Technical integrity layer

How sealing works.

🔢
SHA-256 hashing

Every evidence file is hashed before sealing. The hash is recorded in the sealed record.

🔑
Ed25519 signing

The canonical record is signed with an ed25519 private key held on the sealing server.

📅
Timestamp anchor

Sealing time is recorded. Tampering with the record after sealing breaks the signature.

🔍
Offline-verifiable

The ed25519 signature can be verified without Vraimony infrastructure using the public key.

Public key: available at /keys/ · Algorithm: Ed25519 (RFC 8032) · Hash: SHA-256 · Canonical JSON: Vraimony profile (keys sorted, no whitespace)
Engine status — 2026-03-31

Infrastructure tested and operational.

VERDICT ENGINE

6 WooCommerce chargeback cases tested (2026-03-31). All 4 layers operational: Structural, Integrity, Policy, Readiness. Rules Registry v4.

SIGNING KEYS

Ed25519 signing key active (ed25519_2026-03-11). All sealed records carry a tamper-evident signature verifiable without Vraimony infrastructure.

VERIFY SURFACE

verify.vraimony.com is read-only. No tracking on reviewers. No account required. Domain separated from the sealing surface.

EXAMPLE RECORDS

Documented example cases available. Each shows evidence structure, engine verdict, and review path. See examples →

Questions?

Start with the product. Then come back here if needed.

Need the storage and export policy in plain English?

Review the record lifecycle page for access period, exports, and what remains verifiable after access ends.

Open record lifecycle