A record you can prove, months later.

The moment a source answers, its result is written with a fingerprint of its content. The fingerprint covers the search inputs, the list date and every candidate, so any later edit to any of them changes the fingerprint and shows.

• Fingerprint written at collection time, not at export
• Covers inputs, list dates and candidates together
• Shown in the report and in the exported bundle

RECORDEDThe fingerprint of every evidence item and the time it was written.

Each record includes the fingerprint of the record before it. Remove one, reorder two, or change any content, and the chain no longer verifies. The chain runs across checks, so a whole month of screening stands or falls together.

• Every entry links to the previous entry's fingerprint
• Gaps and reorders are detected, not just edits
• One chain per organisation, across checks and reviewers

RECORDEDThe previous fingerprint on every entry and the chain position.

The chain is re-verified on a schedule and after every export. If a verification fails, an alert goes to the administrators with the first entry that did not match, so a problem is found in hours rather than during an examination.

• Scheduled verification across the whole chain
• The first failing entry named in the alert
• Verification results are themselves recorded

RECORDEDEach verification run, its result and the first mismatch if any.

A bundle holds the reports, the evidence and a small verifier program. Your auditor runs the verifier on their own machine, with no account and no network, and sees the same pass or fail you see.

• Reports, evidence and manifest in one file
• Offline verifier included, no login needed
• Scope and limits stated inside the bundle

RECORDEDThe bundle manifest, its fingerprint, who exported it and when.

Replay runs a past decision again. Against stored evidence, it shows the decision is reproducible. Against today's lists, it shows what changed: a new listing, a delisting, a renamed alias, line by line.

• Same inputs, stored evidence: the result must match
• Same inputs, today's lists: the difference is shown
• Both runs are recorded as replays, never as new checks

RECORDEDThe replay, which mode it used and the line-by-line difference.

When a dispute or an investigation starts, an administrator places a hold. Retention schedules stop for the records in scope, erasure requests are answered with the hold on file, and the hold itself is part of the record.

• Hold by subject, case or date range
• Retention and erasure paused while the hold stands
• Start, scope and reason recorded with the hold

RECORDEDThe hold, its scope, who placed it, when, and when it was lifted.