Mobile Privacy Policy

This Privacy Policy applies to KeepKey Wallet, the standalone Android software wallet with package name com.keepkey.wallet (the “App”). It does not apply to the KeepKey hardware wallet, the separate KeepKey Mobile hardware companion, the KeepKey ecommerce website, or third-party services that publish their own notices.

The App is provided by Key Hodlers, LLC, doing business as KeepKey, a Delaware limited liability company (“KeepKey,” “we,” “us,” or “our”). Questions and privacy requests may be sent to support@keepkey.com.

• The App is self-custody software. You can create or import a wallet without opening a KeepKey account.
• Recovery phrases and private keys are designed to remain encrypted on your device. KeepKey cannot recover them for you.
• Online wallet features necessarily send public wallet, transaction and technical data to blockchain and other service providers.
• Optional KeepKey usage analytics are off by default. The current release contains no advertising SDK.
• Public blockchain records are generally permanent and cannot be deleted by KeepKey.

Depending on the features you use, the App stores locally:

• recovery phrases, wallet passphrases, private keys, public keys and watch-only wallet information;
• wallet names, addresses, assets, balances, transaction history, contacts and preferences;
• App-lock, biometric-use, privacy, network and appearance settings;
• WalletConnect pairings and sessions, swap records and locally cached market or blockchain information; and
• custom node or RPC details that you choose to save.

Sensitive wallet fields are encrypted before being written to the App database using a key protected by Android Keystore. Android system backup is disabled for the App. You may create a password-encrypted backup file and choose where to save it; if you select a cloud or third-party storage provider, that provider handles the encrypted file under its own policy.

To show balances or history, estimate fees, resolve names, check network state or broadcast a transaction, the App may send the following to blockchain peers, nodes, RPC endpoints, light-wallet servers, explorers or indexers:

• public wallet, sender and recipient addresses;
• public keys or extended public keys when required by a network;
• chain, asset and token identifiers, balance and history queries;
• transaction hashes, payloads, amounts, fees, memos and status; and
• IP address, request time and ordinary network or protocol metadata.

The recipient depends on the asset and your settings. It can include a service selected by KeepKey, a decentralized-network participant, or a custom endpoint you enter. Raw recovery phrases and private keys are not required for these requests and are not intentionally sent. Public addresses and activity may still be linked to you by network observers or other parties. An IP address can also be used to infer an approximate location.

When you connect a decentralized application through Reown/ WalletConnect, the relay and connected dApp may receive pairing and session identifiers, dApp metadata, approved public account addresses, chains, requested methods, signing or transaction requests, your response, IP address and timing information. Signing occurs locally, but an approved request can still authorize a harmful transaction.

Reown SDK telemetry is disabled in the current release. The WalletConnect SDK initializes with automatic relay connectivity, so ordinary technical connection data may be exchanged when the App starts. Pairing, session, account and request data is exchanged when you use a WalletConnect feature.

The App performs automatic market and asset-metadata synchronization through Blocksdecoded infrastructure. Other features can contact NFT metadata, explorer, name-resolution, address-risk and swap providers when you open or enable them. A request can reveal the asset, contract, address, amount, route or feature context together with network metadata. Swap routing can use providers or protocols such as 1inch, Uniswap, PancakeSwap, THORChain and Maya Protocol. Their own terms and privacy notices apply.

Principal service categories in the current release include Reown’s WalletConnect relay, Blocksdecoded market and metadata infrastructure, public or configured blockchain RPCs and peers, OpenSea for supported NFT metadata, chain and address-risk services, and the swap provider selected for a quote. The precise recipient varies by chain, feature, region and your custom settings.

If you use a passkey wallet, Android Credential Manager and the credential provider you select may process a display name, random user identifier, credential identifier, cryptographic challenge and passkey metadata. Your provider may synchronize the passkey under its own terms. Removing a wallet from the App may not remove the passkey from that provider.

If you contact support, KeepKey and the channel you use receive the information you submit, such as your email or messaging identifier, message, attachments and technical details. Do not include wallet secrets in a support request.

KeepKey’s optional UI analytics are off by default. You can control them in Settings → Privacy → Share UI data. When enabled, the App may send events such as screens opened, features used, settings changed, selected chain or coin identifiers, wallet type, language, theme, App version, event time and a persistent random installation identifier generated by the App.

The current event design is not intended to include a recovery phrase, private key, raw wallet address or transaction amount. Turning the setting off stops new event collection and upload while it is off. Events already queued locally may remain until they are sent or you clear the App’s data.

Enabled events are sent through the configured production analytics endpoint at api.blocksdecoded.com. Successfully sent events are removed from the local queue. Server-side records are kept according to the analytics service’s operational, security and legal retention criteria. Because the identifier is pseudonymous and is not linked to a KeepKey account, KeepKey may be unable to locate a specific person’s analytics events without that identifier.

Information is used to:

• create, import, protect and display wallets;
• synchronize supported networks and process transactions you request;
• connect to dApps and provide optional swaps and market data;
• provide support, security and abuse prevention; and
• improve the App through optional analytics when you enable them.

Data may be shared at your direction, with the infrastructure needed for a feature, when required by valid legal process, or during a corporate transaction subject to applicable law. The current Android source for the current Android release contains no intentional advertising SDK, and its optional telemetry is not designed for targeted advertising.

Wallets, settings, sessions, contacts, caches and history generally remain on your device until you delete the relevant item, clear App data or uninstall the App. Manual backup files remain wherever you saved them until you delete them there. A credential provider may retain a passkey after you remove the corresponding wallet.

Retention depends on the record and purpose. Support messages are kept while a request is open and afterward only as needed for continuity, security, dispute resolution or legal compliance. Optional analytics are kept only while needed to measure and improve features; security records are kept while relevant to preventing or investigating abuse. Records are then deleted or de-identified unless law requires longer retention. Independent blockchain and third-party providers set their own retention practices. Public blockchain records generally cannot be altered or deleted.

To ask about deletion of support or optional analytics data that KeepKey can reasonably identify, use our privacy request page. Because there is no hosted wallet account, KeepKey may have no central wallet record to locate. We cannot remotely delete data stored only on your phone.

You can:

• leave optional analytics off or turn them off;
• choose custom network sources where supported;
• deny camera access and disconnect WalletConnect sessions;
• delete wallets, contacts, backups and local App data; and
• request access, correction, deletion, portability, restriction, objection or withdrawal of consent where applicable.

Rights can be limited where KeepKey does not control the data, cannot associate it with you, must retain it by law, or the information is on a public blockchain. We will not ask for your recovery phrase or private keys to verify a privacy request.

The App uses Android Keystore-backed encryption for protected local wallet fields, device authentication, an App lock and local signing. User-created backup files use separate password-based encryption. These measures reduce risk but cannot make a compromised, rooted or unlocked device invulnerable.

Many HTTPS services encrypt traffic in transit. Some decentralized blockchain peer-to-peer protocols do not provide transport encryption, so we do not claim that every transmission is encrypted. Protect your device, verify every address and approval, and store recovery material offline in a secure place.

Blockchain infrastructure and providers operate globally. Information may be processed outside your country, where privacy protections can differ. Data is handled under the terms and legal obligations that apply to KeepKey and the relevant provider.

The App is intended only for people who are 18 or olderand is not directed to children. If you believe a child submitted personal information to KeepKey, contact us so we can review the request.

We may update this policy when the App, providers or law changes. The current version and updated date will remain available at this URL. We will provide any additional notice required by applicable law.