7.2 Privacy Mechanisms

• Minimal data collection: Only legally required data.

• Selective disclosure: Counterparties see only what they need.

• User-controlled permissions: Real-time grant/revoke and clear scopes for AI agents.

• Cryptographic verification: ZK proofs for compliance attestations, encrypted data, privacy pools where legal.

Architectural Principles

Veil’s system is guided by four core principles:

1. Minimal Disclosure by Default

Only the data strictly required for a given action is requested or processed. User activity is compartmentalized across services, ensuring no single system has full visibility into a user’s financial life.

2. Modular Trust

Instead of centralizing trust in one entity, Veil operates through a modular architecture:

• Wallets

• Cards

• On-ramps and off-ramps

• Offshore and virtual accounts

• Payment rails

Each component operates independently with clear boundaries, reducing systemic risk and data concentration.

3. User-Controlled Flow of Value

Users can move seamlessly between crypto, fiat, and spending tools without surrendering custody or transparency over fund movement.

Funds move:

• From wallet → card

• From wallet → bank

• From crypto → fiat

• From onchain → offchain

through deterministic, auditable flows rather than opaque black-box conversions.

4. Privacy-Preserving Compliance

Veil is designed to work with regulated infrastructure without exposing users to unnecessary friction or invasive processes.

Where identity verification or compliance checks are required by counterparties, they are:

• Scoped

• Isolated

• Purpose-limited

Veil does not monetize user data, sell behavioral insights, or aggregate financial profiles for secondary use.