Why Blind Detection Matters: Privacy-First AML at Scale

Traditional AML tools require you to submit raw wallet addresses to a third-party service. This creates a fundamental privacy contradiction: by checking if an address is safe, you reveal your trading activity, counterparty relationships, and portfolio composition to the AML provider.

For high-volume traders, this exposure is a competitive intelligence risk. For compliance-sensitive organizations, it's a data processing liability under GDPR and similar frameworks. For privacy-conscious individuals, it's a non-starter.

Most AML providers store your raw queries indefinitely. Their databases contain a complete map of who is trading with whom. A breach of such a provider would expose the trading relationships of every user.

Sanctuary's privacy model minimizes raw address retention wherever the product flow permits it:

1. Checks use privacy-preserving identifiers for long-term intelligence records where possible. 2. Compliance records retain the data required for billing, reports, audits, reconciliation, and customer-configured retention. 3. Address-handling controls are separated from the evidence review layer. 4. Sensitive implementation details remain in security and customer governance material, not public marketing copy.

The result: compliance teams get usable wallet risk context without turning public pages into an infrastructure diagram.

The key insight: we don't need to store YOUR address to score it. The privacy model keeps raw wallet data out of long-term intelligence storage wherever the product flow allows it:

1. The address is transformed into a privacy-preserving identifier. 2. The identifier is checked against intelligence records. 3. External evidence is queried only where the review requires it. 4. The final verdict is computed from governed evidence classes. 5. Long-term records avoid retaining raw addresses unless required for compliance, billing, reconciliation, or customer-configured audit trails.

Fast screening is designed to reduce unnecessary data exposure while still returning a usable risk posture for operational flows.

For compliance teams evaluating AML solutions, the key questions should be:

• Which product flows retain raw addresses, and why? • Can query history be minimized without breaking reports or audits? • How are customer records separated from shared intelligence workflows?

Sanctuary is designed around data minimization, auditability, and clear retention boundaries. A full Data Processing Agreement (DPA) is available on request.