🔒 Privacy & Local Processing
How BagSensei protects your data by design
BagSensei is built with a privacy-first architecture, where all sensitive operations run directly in your browser. No external logging. No server-side tracking. No user profiling.
⚙️ How It Works
BagSensei performs all core analytics locally:
Wallet data stays in the client session
Token holdings and prices are computed in-browser
Risk calculations run through local processing
Portfolio & signal views are generated on your device
Your information is never uploaded, never stored, and never cached on our servers.
🚫 What We Do NOT Store
BagSensei never collects:
Wallet addresses
Portfolio balances
Token lists
Scan logs
Trading history
IP-based activity
Interaction patterns
We do not maintain user databases or persistent profiles.
🌐 Network Calls
When BagSensei fetches blockchain data, the request is:
initiated from your browser
sent directly to public Solana RPC endpoints
processed without passing through BagSensei servers
This keeps the entire flow user → RPC → user.
🧱 Architecture Overview
Client-side processing for wallet, risk, and analytics
Read-only RPC — never touches signing or private keys
Zero server persistence — no data storage or logs
Stateless sessions — close tab = no trace
🔐 Your Keys & Wallet
BagSensei:
cannot access private keys
cannot request approvals
cannot initiate transactions
operates 100% read-only
Your wallet is your wallet — we only read publicly available data.
📱 Mobile Privacy
The new mobile-friendly Web App keeps the same privacy model: all processing remains local, even in compact mode.
No changes in data flow. No additional permissions.
📌 Summary
BagSensei was built for traders who want powerful analytics without sacrificing privacy. Everything stays on your device — exactly where it belongs.
Last updated