EN
Appearance

To remember this theme on future pages, allow saved preferences. Cookie preferences

Could not save. Check that your browser allows cookies and try again.

Talk to sales
MenuClose
Talk to sales

Preferences

LanguageEnglish
AppearanceSystem
Appearance

To remember this theme on future pages, allow saved preferences. Cookie preferences

Could not save. Check that your browser allows cookies and try again.

Evidence and audit

Years later, how do I prove what the platform knew, when, from which publication, and what it answered?

Every fact served leads back to the publisher's file, stored with its SHA-256 before it was read, and every screening leaves a receipt naming the versions that answered it. Receipts, certificates and dossiers verify offline, and a screening can be rerun as it stood on a past date.

Illustrative example · invented data

Screening receipt

Query
SCR-DEMO-001
Made at
2026-11-03 09:05
Profile
example-profile v3
Publication
sha256 9f2c…e41a
Signature
Ed25519 · JWS

Verifiable outside the platform with the public key

What you get

  • An evidence chain per fact

    Record, publication, file and SHA-256 for every fact, from the publisher to the answer.

  • Screening receipt

    Who, when, versions, counts and parties reported, with the subject and the answer, kept six or ten years by the organization’s duty and read back with each source’s publication.

  • A signed certificate

    The receipt signed with Ed25519 as a JWS, bound to the request’s digest with a nonce only you hold, verifiable offline against the keys published at /.well-known/jwks.json.

  • Screening as of a past date

    A screening with asOf returns what a screening returned that day, and a party’s profile can be read as it stood. A lookback does the same for your book.

  • Regulator dossier

    A period’s receipts, the publications they rested on, profile versions, review events and policy versions in one signed JSON Lines file whose last line carries the SHA-256 of every byte before it.

  • What each publication changed

    Designations added, withdrawn and restated in each of a source’s publications, with their terms before and after.

The audit trail also records configuration changes: access and team, the review policy, what the organization contracted, every private list entry, every profile version with its thresholds and every batch sent, each event with its author.

How it works

  1. Every downloaded file is stored with its SHA-256 before any parsing and never altered.

  2. Every fact served points to the record, publication and file it came from.

  3. Every screening writes a receipt with the versions of the sources, the matcher and the profile.

  4. Receipts, certificates and dossiers are signed and verified against the public keys.

How it is delivered

  • API
  • Console
  • File

Related products

Talk to sales

Years later, how do I prove what the platform knew, when, from which publication, and what it answered?

Talk to sales