How we handle data
NavoSwap is built around a privacy-first experience: no KYC for ordinary swaps, no wallet connection required to use the public swap UI, and minimal tracking compared to typical Web3 products. The binding legal text is in our Privacy Policy and Terms & Conditions (aligned with the NavoSwap app).
Standard swap users
You are not required to create an account to swap. The system uses order IDs and single-use deposit addresses to process flows; the public whitepaper describes a design where internal services work on order IDs, not long-lived user profiles, and where logs are minimized where possible.
You (swap user)
No account required; destination address only where needed.
Order & deposit layer
Single-use deposit addresses; work tracked by order ID, not a long-lived profile.
Routing (optional)
With is_anonym, paths aim to reduce trivial on-chain linkability between in and out.
Settlement
Liquidity aggregation and payout; minimal retention of correlation data per policy.
Privacy features reduce unnecessary exposure but are not a guarantee against all analysis. See Architecture for the full lifecycle.
Partner accounts
If you register as a partner, NavoSwap stores credentials needed for authentication (e.g. email, password hash), optional 2FA settings, API key metadata, payout instructions for affiliate settlements, and related audit data. That is separate from anonymous end-user swaps.
Cookies & local storage
The app uses minimal browser storage for session state, recent orders, and UI preferences, not third-party ad trackers as described in project policies.
Routing & anonymous mode
When enabled (API field is_anonym), swaps can use privacy-oriented execution paths so that input and output are not trivially linkable on-chain. This is a product feature, not a guarantee against all forms of analysis; see Architecture & lifecycle for the trust and state model.