What we hold, and what we never ask for.

A ledger is only as trustworthy as the access it needs. DEFISCAN reads public chain data and never holds the means to move anything.

The controls we can evidence

Four properties of the system, each one checkable from the product itself rather than from a promise.

S1
Read-only by construction
Watching an address requires no key material. DEFISCAN never asks for private keys, seed phrases, or signing rights, and has no code path that could use them. The product cannot move funds because it is never given the means to.
S2
Raw data is kept, not overwritten
Provider responses land in an immutable raw store before anything interprets them. Cleaning and netting produce new layers on top; if a rule changes, the layers are rebuilt from the same raw events rather than from a previous interpretation of them.
S3
Workspaces are separated
Each tenant is its own workspace with its own wallets, dimensions, reports, and audit log. Roles decide who may change settings, invite members, or trigger a run, and the audit log records who did what.
S4
Your data leaves when you want it to
Reports and balances export to CSV, JSONL, or XLSX with a manifest. There is no lock-in format and no export that only opens inside this product.

Stated plainly, because the alternative is a compliance-shaped page with nothing behind it.

This page is not a certification. We do not claim SOC 2, ISO 27001, or any other attestation here, and a page that implied one without the report behind it would be worse than saying nothing.
It is not a custody product: keys, signing, and wallet UX are explicitly out of scope.
It is not an AML or KYC screening service, and it does not classify taxable events.

Security questionnaires, data-flow questions, or a scoped pilot. Tell us what your review needs and we will answer it in writing.