Where the evidence comes from.
A file is only as defensible as its sources. Peloryn screens against official authorities, records the version it saw, and seals the result — so months later you can still show exactly what was known, and when.
Sources in. Governance through. A sealed record out.
Official & observed
- Seven official sanctions authorities
- AIS behaviour & movement
- Ownership & UBO records
- Vessel registry & identity
Checked & stamped
- Source permission verified before use
- List version recorded on every screen
- Freshness gated — stale data is flagged
- Full audit log of what ran, when
Defensible record
- Timestamped, UTC, server-side
- List-version watermark
- SHA-256 hash (Verify)
- Retained 5–10 years
Seven authorities, every screen.
The vessel and its associated entities are checked against each, and the list version is recorded — hit or no hit. A “no match” is itself evidence, and we keep it.
Three rules that keep a file holding up.
Version & time
Every screen records which list version it saw and the exact UTC moment. Sanctions lists change daily; your file remembers the one in force when you decided.
Freshness, not assumptions
If a source hasn’t refreshed within its window, the file says so rather than pretending it’s current. Stale is a state we show, never one we hide.
Permission before use
A governance layer checks each source is legally permitted for customer-facing use before it ever reaches a report — so what you rely on, you’re allowed to rely on.
On Verify, the file is sealed.
Every Enhanced Due Diligence report is fingerprinted with a SHA-256 hash and stored in your Evidence Vault, retained for up to ten years. Re-run a saved record and Verify flags what changed.
Your data stays yours. EU-based, access-controlled, kept for evidence — not resold.
9f2c8e51b3d0a2f4…6c1e904a71b6
See the provenance behind a real file.
Start free on Protect, or request a sample Verify report and inspect every source and version.