Explain the scope of the check
Keep selected coverage, source references, and dataset, engine, and policy versions with the screening. Make clear what the result describes.
Sanctions screening evidence and recordkeeping
Keep the screening result and its source context together.
Retain the scope, matched evidence, and version identifiers behind a check. Export structured screening records so your organization can preserve the evidence in its approved recordkeeping process.
API and compliance dashboard included in every plan.
SanctionsKitIllustrative workflow
SCREENING EVIDENCE
A result with its context
01What was screened
02Which sources were selected
03Matched fields & conflicts
04Dataset, engine & policy versions
Export retained evidence as structured JSON.
What this helps your team do
Give the next reviewer a result they can understand.
Export a structured evidence file
Download retained evidence as JSON with a format version, the original result, and its supporting context. Keep the screening reference with your own internal record.
Choose retention deliberately
Use the organization’s retention controls to decide what remains available. Select a policy before relying on the dashboard as part of a longer recordkeeping process.
A practical use case
A colleague needs to understand a screening after the original review.
A useful screening record shows the sources and versions checked, the evidence behind the match, and your team’s decision.
- 01
Inspect the retained result
Open its source records, selected coverage, match explanations, and dataset, engine, and policy versions.
- 02
Read the decision in context
Distinguish the original screening outcome from later analyst decisions. Retrieval timestamps stay separate from genuine source publication dates.
- 03
Export into your approved process
Download the structured JSON record while it is retained. Store the exported file under your organization’s access and retention controls.
For the people behind the process
One capability. Useful to the whole team.
Compliance teams
Source context stays within reach
Use retained evidence to explain the identity review and distinguish it from later decisions.
Explore your workflowOperations
Retention is an explicit choice
Plan how long results must remain available and where exported files should be stored.
Explore your workflowDevelopers
A structured export for internal systems
Work with format-versioned JSON and stable result references rather than a screenshot of the dashboard.
Explore your workflowEvaluate the details
Evidence exports: practical questions.
What is included in the screening evidence export?
Retained evidence exports include a format version, the original result, selected coverage, source references, and dataset, engine, and policy versions. Available details depend on the selected retention policy and underlying source record.
How long is evidence retained?
Standard retention defaults to 90 days and is configurable for the organization. Minimal mode does not save the submitted subject and keeps a reduced result for 24 hours. Inputs removed by that policy cannot later be reconstructed from a digest.
Is an exported file a tamper-proof archive?
No. Access inside the application requires tenant authorization and is audited, but a downloaded file leaves those controls. Store it according to your own policies. Ordinary hashes can support comparison against a trusted value; they do not create a tamper-proof archive.
See SanctionsKit in action
Explore the evidence behind an example screening.
Try the interactive demo with synthetic examples. Compare plans for your team’s screening volume.