Overview
Kaspa Wallet is built around the principle that wallet-sensitive material belongs with the user. This page describes information that may be created while using the website, downloads, or wallet software.
Wallet and local data
Recovery phrases, private keys, wallet files, and signing material should remain local to the user's device. Kaspa Wallet should not ask users to send recovery material through email, forms, support chats, social channels, or direct messages.
- Wallet activity may be visible on the public Kaspa network.
- Local app settings may be stored on the user's device to keep the wallet usable.
- Removing the app may not remove every local backup or wallet file created by the user.
Website data
The website may receive ordinary technical information such as browser type, device information, referring page, approximate region, and request logs. These signals are commonly used for security, debugging, and reliability.
If analytics are used, they should be limited to aggregate product and site performance insights rather than wallet-sensitive information.
Third-party services
Links to explorers, GitHub, community platforms, release hosts, or Kaspa resources may lead to services operated by other parties. Their privacy practices are controlled by their own policies.
Your choices
- Backups: you control where recovery material and wallet backups are stored.
- Network activity: public blockchain activity cannot generally be made private by deleting local app data.
- External links: you choose whether to open third-party explorers, repositories, or community sites.
Policy changes
This page may be updated as the wallet, website, or release process changes. The production version should clearly identify its latest revision date.