Privacy for a public-chain utility
Solana addresses and transactions are public by design. NOXR still minimizes what it retains about who used the product and why.
Public wallet addresses used for scans
When you run a recovery, Wallet Health or dust scan, the public wallet address is sent to NOXR's server so it can query Solana data and calculate supported results. Wallet Health does not persist the scanned wallet address. Recovery product analytics store aggregate counts and amounts rather than the full audited wallet address.
Token Risk scans
A Token Risk scan sends the public token mint to NOXR's server for Solana and Jupiter lookups. Token Risk analytics record aggregate scan characteristics such as signal level and data coverage, not the scanned mint address.
Prepared recovery transactions
For a prepared recovery, NOXR stores a one-time build identifier and a SHA-256 digest of the wallet address, plus transaction metadata needed for secure confirmation. The full wallet address is not stored in the authoritative recovery-build record.
Dust Cleaner
Dust discovery is read-only. If you choose cleanup, server-only build metadata can include token account, mint, expected output, fee account, message hash, expiry height and the public transaction signature.
Visit analytics
NOXR uses a random browser-session UUID to estimate unique visits. Product analytics do not intentionally persist raw IP addresses as user identifiers.
Confirmed transactions
Solana transaction signatures are public blockchain data. NOXR may retain confirmed signatures, action counts, fee amounts and other operational transaction metadata for reliability, accounting and abuse prevention.
Server logs and providers
Hosting, RPC, Jupiter and database providers may process technical request data needed to operate the service. NOXR does not ask for or intentionally collect seed phrases, private keys or wallet recovery phrases.
Public blockchain data
NOXR cannot delete or make private information already recorded on Solana. Public addresses, account state and transaction history remain part of the blockchain itself.
Retention
Prepared build records are intended for transaction verification, product measurement, accounting and abuse prevention and are subject to bounded cleanup.
Effective: 2026-09-25.