Skip to content
{white}INTEL
/ Trust & methodology

Sourced, resolved, cited.

WhiteIntel fuses 24 public and licensed sources into one graph of 37.1M+ entities — every claim carries the record behind it. Here's exactly where the data comes from, how the same entity is resolved across sources, and how it's secured.

An armillary sphere of ownership ringsFive ledgers, one identity
/01 Provenance

Every source, what it contributes, and its licence. Commercial-safe sources are served openly; restricted registers are attribution-bound or gated behind an entitlement.

OpenOwnership
UK beneficial ownership (PSC)
CC0 — public domain
GLEIF
Global LEI registry + parent/child
CC0 — public domain
ACRA Singapore
SG company registry
Singapore Open Data — commercial-ok
ICIJ Offshore Leaks
Panama · Paradise · Pandora · Bahamas
ODbL — attribute ICIJ
SEC EDGAR
US filers, insiders (Forms 3/4/5)
US public domain
FAA
US aircraft assets
US public domain
OFAC · EU · UK OFSI · UN
Sanctions lists
Public / OGL / EU reuse
Gibraltar UBO
Gibraltar beneficial owners
Restricted — gated
OBRS Belize · Anguilla · St Vincent · Luxembourg
Offshore company registers
Restricted — gated
Resolution

The same entity, across sources

  • 1 · Identifier join — exact strong-id match (LEI, sanctions id, company number, NIP, UEN, SEC CIK).
  • 2 · Name-block — name + jurisdiction, only where a block spans ≥2 registries.
  • 3 · Sanctions bridge — links null-jurisdiction sanctioned parties onto same-name registry/leak records.

Matches collapse into one cluster_id; the dossier shows every record in the cluster.

Security

Locked down by construction

  • Row-Level Security on every table; the public API reads through a locked-down service role.
  • Input validation + rate limiting on every public endpoint; write functions execute-revoked from anon.
  • No secrets shipped to the client. Enforced security headers. Posture independently audited.
/02 Honesty by construction
A source on every claim

Every entity, edge and risk flag links to the registry or leak record behind it. Nothing is asserted without provenance.

Absent ≠ non-existent

A missing ownership edge means “not yet observed in our sources”, not “does not exist”. We never imply completeness we don't have.

Decision-support, not a verdict

Risk levels are heuristic investigative leads. WhiteIntel is not a legal determination of beneficial ownership.

Unscored shown honestly

Where an entity isn't yet risk-scored we say “Unscored” rather than defaulting it to low.

Corrections & removals

Spotted a sourced error, or need a lawful removal? Include the entity id or dossier URL.

intel@whiteintel.dev
/ FAQ

Questions, answered.

From 24 sources — OpenOwnership (UK PSC), GLEIF, ACRA Singapore, ICIJ Offshore Leaks, SEC EDGAR, FAA, offshore UBO registries and the OFAC/EU/UK/UN sanctions lists — cross-source-resolved into one graph, with live UK Companies House lookups on top. Each carries its licence; commercial-safe sources are served openly and restricted registers are gated.

In three precision-ordered passes: (1) exact strong-identifier join (LEI, sanctions id, company number, NIP, UEN, SEC CIK); (2) name-and-jurisdiction blocking, only where a block spans two or more registries; (3) a sanctions name-bridge that links null-jurisdiction sanctioned parties onto same-name registry/leak records. Matches collapse into one cluster_id — the same real-world entity across sources.

Heuristically, from graph connectivity (degree), presence in a secrecy jurisdiction, and sanctions signals — as an investigative lead, never a legal conclusion. Unscored entities are labelled as such.

Row-Level Security is enforced on every table; the public API reads through a locked-down service role with input validation and rate limiting; write functions are execute-revoked from anonymous callers; no secrets are shipped to the client. Security posture is audited.

Email intel@whiteintel.dev with the entity id or dossier URL. We correct sourced errors and honour lawful removal requests; corrections propagate on the next ingest.

/ Explore

See it for yourself.

Open any entity — every claim on the dossier links back to its source.

Search the corpus Read the API docs