Transparency · Live data
Everything we publish about ourselves. In one place.
Corpus depth is the moat. We publish the live numbers so customers, regulators, journalists, and acquirers can verify what we claim. Updated every 30 minutes from the production database.
Generated at Fri, 25 Sep 2026 06:45:07 GMT
Pre-Deal checks ever
153
12 in last 30 days
Cluster entities
226
2 confirmed · 27 countries
Verified counterparties
0
0 document-backed
Defense packs signed
1
0 cryptographically bound
Live surfaces
Every public-facing trust artifact
Live corpus metrics
Refreshes every 30m
Decision corpus depth, cluster intelligence breadth, verified-network density, defense-pack ledger, contribution queue throughput. Every number aggregated live from production tables. No editorial.
Cluster directory
226 active entities
Every first-party investigated fraudulent counterparty, ordered by severity then recency. None of these entities are on any sanctions list. They are caught only by cluster intelligence with the routing layer mapped.
Verified counterparty directory
0 approved
Document-backed counterparty opt-ins. Approved profiles get a +15 clearance probability lift on Pre-Deal verdicts. Embeddable SVG badge for the counterparty's own site.
Public verified lookup
Anyone can check
Free anonymous lookup against the verified directory + cluster blocklist. Paste a counterparty name, get a recommendation tier (block / caution / verified / unknown). No signup, no API key.
Defense-pack verification
SHA-256 + canonical JSON
The cryptographic binding between MLRO signature, evidence pack, and decision basis. The published algorithm lets a regulator recompute the digest, an internal consistency check that the pack matches its stored canonical rows, not proof the rows were not rewritten.
Simar Chahal cluster teardown
Flagship teardown
The Chevron-CEO impersonation chain. Full evidence chain and fictional-entity catalog. The launch story for the customer-contribution flow.
Customer cluster contribution
Anon-rate-limited
Anyone can report a fraudulent counterparty pitch. OilFlow's named investigator triages within 72 hours. Confirmed cases enter the public blocklist; submitter is never named publicly.
Get verified (counterparty side)
Document-backed
Counterparty self-serve onboarding for the verified network. UBO disclosure + company registration + reference letter + trade-history sample. Approval gives the +15 Pre-Deal lift.
Compliance Intelligence Digest
Hourly · RSS
Public weekly compliance signal stream: sanctions deltas, adverse-media findings, cluster additions. Cross-jurisdiction. Free for everyone.
Pre-Deal Copilot live surface
30s verdict · No signup
The front-office Pre-Deal surface. Paste a deal description, get a sub-30s clearance probability + restructure suggestion. Sells to RMs, deal originators, brokers, not compliance.
Data rights
The contractual lock-in for customer-contributed cluster intelligence, Pre-Deal outcome telemetry, and MLRO defense-pack attestations. Published in the Terms of Service.
Read §§ 18 (3A, 5A, 6A) →Security + compliance
SOC 2: not started. No report of any type exists, no auditor is engaged, no engagement letter is signed, no penetration test exists. A self-assessed control mapping (CSA CAIQ v4) is available under NDA. GDPR compliant · CCPA compliant · 8-list sanctions screening. Encryption, key rotation, sub-processor list.
Investor data room
Live metrics snapshot, updated daily. Revenue, customers, corpus depth, sales pipeline.
Investor surface →FCA, MAS, FinCEN, OFSI, and other regulator engagement
OilFlow has built three surfaces with regulator review in mind. No regulator has been engaged and no submission has been made. (1) The cross-regulator Defense Pack format (FinCEN SAR, FCA SYSC 6.3, FATF Rec 10, MAS Notice 626) renders the same decision-level evidence bundle in regulator-specific narratives. (2) The MLRO signoff chain stores a SHA-256 over the pack's canonical rows; a recompute is an internal consistency check that shows the pack matches those stored rows, and does not prove the rows were not rewritten. (3) The cluster intelligence corpus is written so that it could be submitted to OFAC SDN candidate intake or an FATF Recommendation 10 typology working group; nothing will be submitted to any regulator before an OilFlow legal entity exists.
Regulators reviewing OilFlow for sandbox / innovation-hub inclusion can verify all of the above directly from the public surfaces linked on this page. No NDAs required for any of the corpus metrics, the cluster directory, or the defense-pack verification algorithm. For a guided walkthrough, contact [email protected].