Last updated: 16 September 2026
1. Controller and website operator
Solana Web Wallet is owned and operated by FAR COAST LTD, Company No. 17441292, a private company limited by shares registered in England and Wales. Registered office: 167-169 Great Portland Street, London, England, W1W 5PF.
2. Private wallet data
The application is designed to process recovery phrases, private keys and JSON secret keys in the user's browser. These secrets are used locally to derive keys and sign transactions. They are not intentionally submitted to the site's RPC relay for transaction signing.
3. Browser storage
The application can store an encrypted wallet seed and a non-exportable browser encryption key in IndexedDB so the wallet can remain open after refresh or browser restart. It can also store the last successfully used RPC endpoint in localStorage. Selecting Exit removes the saved wallet session. Users can also clear site data through their browser.
4. Public blockchain requests
To show balances, token accounts and transaction history, the application sends public addresses and other public blockchain query parameters to Solana RPC infrastructure. Signed transactions are sent to an RPC endpoint for broadcast. These providers may process technical connection data according to their own policies.
5. Server and security logs
The website host and web server may process standard technical information such as IP address, request time, requested path, browser or user-agent information, status codes and security events. Such logging can occur at infrastructure level even when the wallet application itself does not create an account profile.
6. RPC relay data
The included RPC relay forwards permitted JSON-RPC requests to configured upstream providers. It maintains a temporary server-side cache of provider ordering for availability and response-time selection. That cache is not a wallet-account database.
7. Cookies and analytics
The current wallet package does not include advertising trackers, third-party analytics scripts or an application login cookie. If the production site later adds analytics, support tools or other tracking technology, this policy should be updated before or at the time those tools are deployed.
8. Market-price, token display data and QR services
To display an approximate SOL/USD value, the wallet may request public SOL market-price data from external price services. For token names, symbols, icons and approximate USD prices, the browser sends public token mint addresses to the same-origin token-data endpoint. That endpoint can request public market data from DEX Screener using the hosting server connection and temporarily cache the result. Token mint addresses are public blockchain identifiers, but a set of requested mints can indicate which asset types are being displayed in the wallet. Recovery phrases, private keys and JSON secret keys are not included in these requests.
Token icons obtained through the token-data endpoint are proxied by the website rather than loaded directly from the market-data provider. When the Receive QR code is opened, the public wallet address is submitted to the QR image service solely to render that address as a QR code. External SOL price and QR services may receive ordinary technical connection data such as an IP address.
9. Third-party sites
Links to Solana Explorer and other external resources open third-party websites. Once a user follows an external link, that site's own privacy practices and technical logging apply.
10. Security and retention
Non-custodial design reduces server-side exposure to wallet secrets, but no website or browser environment is risk-free. Browser-stored wallet data remains until Exit, site-data deletion, profile deletion or another browser action removes it. Server log retention depends on hosting and security configuration.
11. Changes
This policy may be updated when the wallet architecture, infrastructure or legal requirements change. The current version and update date are published on this page.