SOLKEEPYOUR KEYS. YOUR WORLD.Enter your world ↗
YOUR WORLD, WITH CLARITY

Privacy policy

What stays on your device. What is shared to make your wallet work.

Last updated: 21 October 2026

Your wallet stays local

SOLKEEP creates and restores wallets in your browser. Your password encrypts your recovery material with AES-GCM using a PBKDF2-derived key. The encrypted vault, its public address and encryption parameters are saved in IndexedDB. The unlocked signer exists in memory. The app does not send your password, recovery phrase or private signing key to its API routes.

SOLKEEP cannot recover lost keys or reset your vault password. Keep a private offline recovery backup. An encrypted browser vault does not protect against every threat, including a compromised device or malicious code running in the page.

Browser storage and removal

In addition to the encrypted vault, the app uses local storage for address-scoped token watchlists and activity read checkpoints. Lock clears the active signing session. Sign out / use another wallet removes the primary encrypted vault from this browser; public watchlists and checkpoints can remain. You can remove all site storage through your browser settings. Back up your recovery phrase before removing a vault or clearing browser data.

Public blockchain and service requests

To show balances and activity, prepare transfers and request quotes, SOLKEEP’s server routes forward relevant public addresses, token mints, amounts, RPC requests and transaction data to the configured Solana RPC provider or Jupiter. Signed transactions are submitted to Solana when you approve a supported withdrawal. Blockchain transactions and account activity are public; removing browser storage does not erase them.

The SOL/USD display requests public prices directly from Coinbase Exchange. That provider receives ordinary connection information, including your IP address. Clicking a blockchain explorer link sends you to that provider. These services handle requests under their own policies.

Hosting and technical information

Accessing the site and API routes exposes normal web request information to the hosting infrastructure, such as IP addresses, requested paths, browser headers and request times. Hosting and upstream providers may retain technical logs under their own settings and policies. SOLKEEP’s API routes return sanitized service errors; the wallet does not require a name, email address or hosted user account.

Google Analytics

SOLKEEP uses Google Analytics to understand how visitors use the site. The Google tag can use cookies and collect page views, browser and device information, and other usage information according to the property’s settings. The initial page-view configuration excludes URL query strings, fragments and the referrer, and disables Google signals and ad personalization signals. No custom analytics events containing wallet addresses, balances, passwords or recovery words are added by SOLKEEP.

Analytics cookies are separate from the encrypted wallet vault. You can block analytics requests or manage cookies in your browser. For Google’s processing practices, see Google’s privacy policy and how Google uses information from partner sites.

Sentry error and performance monitoring

SOLKEEP uses Sentry to report application errors and sampled performance timings from the browser and server. Reports retain error types and stack locations. Arbitrary error messages, user context, cookies, request headers, request and response bodies, URL queries and fragments, breadcrumbs, and local variable values are removed or disabled. Performance reports use a small allowlist of technical attributes. Session replay is not enabled, and Sentry logs and custom metrics are not sent.

Browser telemetry connects directly to Sentry, which receives ordinary network connection information. Reporting filters reduce application data sent by the SDK; they do not hide the connection from the service. See Sentry’s privacy policy for its processing practices. Monitoring is separate from your encrypted vault.

Changes to this policy

This page describes the current implementation. We will update the date and text when the way this site handles information changes. Review this page before using newly introduced services. For wallet behavior and recovery guidance, visit the FAQ.