Immutable decision log.

Every signal check and intelligence run is recorded automatically, signed with an integrity hash, and stored in an append-only log. Records cannot be deleted — only archived from your view. The full trail is always available for export.

What is recorded

Timestamp

Exact UTC date and time the intelligence run was completed.

Query

The name searched, plus any additional identifiers supplied (DOB, passport, country, IMO).

Source

Whether the search came from the [S/1] report, the Signals screen, or the API.

Result count

Number of matches returned above the configured confidence threshold.

Top match

Name, source registry, and confidence score of the highest-scoring result.

Integrity hash

SHA-256 of user ID + timestamp + query name + result count. Written at insert time and re-verifiable on export.

Decision context

CSDDD — EU Corporate Sustainability Due Diligence Directive

Article 8 of CSDDD requires companies to implement and document source-based risk processes. The decision log provides evidence that company intelligence and public-list signal checks were performed at a specific point in time. Exportable as CSV for filings, review packs, or external assurance.

FATF Recommendation 10 — Customer Due Diligence

FATF R.10 requires financial institutions and designated non-financial businesses to maintain adequate records of customer intelligence and identity verification measures taken for a minimum of five years. The append-only design means records accumulate without being overwritten — the history of every check is permanently preserved.

AML6D — EU 6th Anti-Money Laundering Directive

AML6D strengthens record-keeping requirements and introduces criminal liability for natural persons responsible for AML failures. The timestamped, integrity-verified decision log demonstrates documented risk analysis in the event of an investigation.

Integrity verification

Each record is written with a SHA-256 hash computed from:

hash = SHA-256(user_id + “|” + searched_at + “|” + query_name + “|” + result_count)

When you export the decision log with Verify integrity enabled, each row's hash is recomputed on export and compared to the stored value. A true in the integrity_ok column confirms the record has not been altered since it was written.

Note: archiving an entry (hiding it from your view) does not affect its integrity hash. Archived entries remain in the full export with is_archived = 1.

Exporting your decision log

1.

Go to Account → Decision Log.

2.

Optionally enable "Verify integrity" to add an integrity_ok column to the export.

3.

Click "↓ Export decision log". The file downloads as a CSV.

4.

The export covers all records for your account (and all team members, if on a Teams plan).

5.

Archived entries are included in the export. Active-only entries appear in the account view.