What the app keeps in your browser
Everything visionscan writes to your device goes to localStorage under the respawn, vision and visionscan prefixes listed below. Nothing else is written by the terminal, and none of it leaves your browser on its own.
- respawn.access.v1
- Session access token. Written when a session is created, removed on logout.
- respawn.refresh.v1
- Session refresh token. Written and removed at the same points.
- respawn.order.*
- Trade-size preferences: quick SOL amounts, last amount, slippage. Interface preference only; no order surface uses them yet.
- respawn.focused-token.v1
- The token you last opened, so it survives a route change.
- vision.intro.v1
- One flag marking the first-visit walkthrough as seen, so it never replays.
- vision.slippage-tier.v1
- The slippage tier selected for copy-return figures. Interface preference only.
- visionscan:comment-draft:*
- Unposted comment text, keyed to your account id and the thread it was typed in. Written while you type, removed when the comment posts. It stays on your device until then.
The two session keys are written when you sign in, with email or with a Solana wallet, and removed when you log out. Reading the roster, the profiles and the trade history still requires no account.
What an account stores
Sign-in exists, by email or by signing a message with your Solana wallet. An account keeps one account row (your email address or wallet public key), the comments you post, including edits, likes and replies, the traders you follow, and the session records that keep you signed in.
None of that is written until you sign in. Without an account the terminal is read-only and stores nothing about you beyond the browser keys above.
What is true whatever the document says
Trades are signed by your own wallet. There is no custody and no delegated signing, so visionscan never holds a key and no stored token can move funds.
The wallet activity on the board is public on-chain history, observed through Helius. visionscan reads what the chain already published about those 553 wallets. It does not make anything public that was not.
What you can do in the meantime
Clearing site data for this origin removes every key listed above. Logging out removes the two session keys on their own.
Until the policy is published, treat anything not stated on this page as unwritten rather than implied. No commitment has been made here that is not printed above.