NavoSwap
App

Security & compliance

Security & compliance map
Non-custodial design: execution is coordinated across partners; no traditional custodial account model for user balances.

Security measures

  • Isolated execution environments
  • Deterministic execution windows
  • Continuous monitoring
and

Compliance principles

  • No mandatory KYC for standard usage
  • Automated sanctioned-address detection
  • Policy-based action on prohibited activity

Legitimate user discretion and compliance are framed as complementary: privacy does not imply tolerance for sanctioned or illicit use.

Illustrative layout of themes from project documentation. Binding terms are in the Privacy Policy and Terms & Conditions.

Non-custodial

NavoSwap doesn't run a classic custodial wallet for swap users. We coordinate execution across providers; funds move through deposit addresses and settlement flows tied to each order—not a pooled "NavoSwap balance" you log into.

What we invest in operationally

Whitepaper and ops docs call out (high level):

  • Isolated execution environments where it matters
  • Deterministic windows so orders don't hang in limbo
  • Monitoring on the paths that move money

Compliance stance

  • No mandatory KYC for the standard anonymous swap
  • Automated sanctions screening where we're required to
  • Freezes or blocks when policy says we have to—not because we enjoy it

Privacy for regular users and blocking bad actors aren't opposites in our book. We want the first group to have a sane experience and the second group to get stopped at the door.