#01Overview
Last updated: October 8, 2026 (UTC).
Bansun does not require an app account for its core tools. Local processing is used for private device tools and downloaded browser AI. Online AI and Ethereum or price lookups necessarily send the submitted information to a server or data provider.
“Private” does not mean anonymous to your internet provider, hosting service or an external endpoint. Public wallet addresses can identify people when combined with other information.
#02Data kept on your device
The app stores preferences, saved wallets and watchlists, journal and prediction records, credit tokens and vault data in browser storage. Browser AI model and engine files use browser caches. Data is scoped to the browser profile and site origin, with no automatic cross-device synchronization.
Ordinary device storage is unencrypted. Records moved into the Vault use AES-256-GCM encryption. Vault backups are encrypted; exported journal CSV files are not. A passphrase or enough recovery shares can grant access to an encrypted backup.
#03Information sent by online features
- Server AI: chat messages, compare questions, simplification text and requested AI explanations go to the Bansun backend and its configured model server. This installation uses local Ollama server models, not a Hugging Face hosted-inference service.
- Agent tools: addresses, hashes, symbols and other lookup inputs explicitly included in a request can be sent to Ethereum and market-data providers.
- Portfolio and market: the addresses and tokens needed for a requested refresh are sent online. Saved labels and the rest of your local journal are not automatically supplied to the agent.
- Browser AI download: the browser contacts model hosts to download public weights. Local prompts are processed on the device after loading.
- Credits: issuance and redemption use blinded values, signatures and spent-token state. Blind signatures do not conceal transport metadata.
A tool may offer an explicit action to copy or save text; that action does not make the text public. Never submit secrets to an online AI mode.
#04Operational metadata and hosting
The backend uses request identifiers, timestamps, endpoint paths, response status and timing for operational logs. Its structured request logs do not intentionally include chat bodies, vault contents or recovery shares. IP-based rate limiting and credit-issuance quotas are used to reduce abuse.
Hosting and network providers may process IP addresses, user agents, traffic and other connection information under their own policies. This page does not promise a universal retention period or zero logging by third parties. Credit keys and spent records are server-side state, not private-record backups.
#05Permissions, cookies and browser controls
Bansun's own app code does not set tracking cookies or install advertising analytics. Browser local storage and caches are still used and are not the same as cookies. Hosting-platform features may have separate processing policies.
The privacy tool can inspect permission states. Optional camera-dependent features request browser permission when used; a permission grant is not required for the core Ethereum tools. Any face/camera processing built into the current app stays on the device. Revocation uses your installed wallet provider, whose own permissions and policies apply.
#06Export, deletion and retention
Local records remain until you delete them, the app's relevant erase control clears them, or the browser evicts storage. Export supported records and encrypted backups before using the Privacy tool's erase action. Browser storage settings can also remove the site's local data and caches.
Clearing this device does not delete downloads, clipboard contents, backups held by trusted people, another browser's records or information already processed by a provider. Blockchain transactions and public on-chain addresses cannot be removed by deleting app data. Auto-erase affects chat memory, not every copy of an answer.
#07External services and transfers
Model downloads can use Hugging Face and the browser engine's documented hosts. Ethereum RPC and price sources receive the information needed for online lookups. Visiting X, a model source, a block explorer or another external site subjects that visit to its policies. Requests may cross national borders depending on the hosting and provider locations.
Bansun does not embed the official X feed on these pages; following the link is your choice.
#08Privacy requests and policy changes
Depending on applicable law, you may have rights relating to access, correction, deletion, objection or other processing controls. Bansun cannot retrieve local-only records from your browser for you. Use the app's exports and deletion controls for those records; for server-side concerns, contact the project without posting sensitive information publicly.
Use the official Bansun X profile, @bansun_ai, for project contact. Do not publish private records, passphrases, seed phrases, recovery shares or wallet keys. For privacy requests, describe the request without posting the underlying sensitive data.
Material changes will be reflected in this page and its update date. This description is not a claim of certification or compliance with every privacy law.