Privacy policy

Last updated: 11 November 2026 (server logs)

KemLock is a self-custody wallet made by Kotav Labs. This policy covers the KemLock Android and iOS apps, the browser extension, the web wallet at kemlock.com/app and this site. In short: your keys and your recovery phrase stay on your device (and, only if you link one, in your own Google account), we run no analytics or advertising, and we do not sell or rent data.

Data kept on your device

• Your wallet, encrypted with your wallet password (PBKDF2-SHA-256 key derivation, 600,000 iterations), or in the Android and iOS apps with a random device key that only your phone's screen lock (biometrics, or its PIN, pattern or passcode) releases.
• If you link a Google account: the account's e-mail address and name as Google gives them, the time the wallet's copy was last saved and an identifier of that copy, so the wallet can show "Linked to …" and offer "Sign in with Google" on the lock screen. They are shown on this device only and never sent anywhere.
• Your saved contacts and the record of the operations you made, encrypted with a key derived from your wallet, and your display settings.
• In the extension: the sites you connected (their origin, the public address and network you shared with them, and when), the sites you blocked, and the wallet mode (mainnet or testnet).
• In the Android and iOS apps: the device key is kept in the Android Keystore or the iOS Keychain, on this phone only, and opens only after your phone's own authentication (biometrics, or its PIN, pattern or passcode); it approves every transaction the same way. The Android app is excluded from Android's cloud backup; on iOS the device key never leaves the phone, so a copy of the app's data in a device backup cannot open the wallet. An encrypted backup you export is saved only where you choose (a file, or the Google account you link, below).

Removing the wallet ("Use a different wallet"), clearing the site's or extension's data, or uninstalling the extension or the Android app deletes this data from the device. Kotav Labs has no copy and cannot recover a wallet: keep your recovery phrase and an encrypted backup safe.

Data the wallet sends, and to whom

A wallet has to talk to blockchain networks. When you use KemLock, these requests leave your device:

• Blockchain nodes. To show balances and send transactions, the wallet sends your public address, the transactions you approve and read requests to public RPC providers for Base, Ethereum and Arbitrum One (base-rpc.publicnode.com, mainnet.base.org, ethereum-rpc.publicnode.com, eth.drpc.org, arb1.arbitrum.io (Offchain Labs), arbitrum.drpc.org; sepolia.base.org in testnet mode). Like any server, they see your IP address. When you review an app's transaction, the wallet simulates it on the network's two public endpoints, which see that transaction and your address, even if you then reject it. Transactions you send become public on the blockchain, permanently.
• kemlock.com. The extension asks kemlock.com for token lists and token logos (to show the tokens you hold), sending the network and, for logos, the logo address. The web wallet and the Android app ask kemlock.com for token logos and, for swaps and bridges, for LI.FI quotes (below). If you are a referral partner, your partner credential and payout requests go to kemlock.com. The wallet downloads public phishing lists from kemlock.com and checks sites and addresses on your device. kemlock.com and its API routes keep no logs of your requests. The relayers never record your IP address; their job log, which holds no addresses, is deleted after 7 days.
• Sites you connect. The extension makes a wallet available to the websites you visit, so they can ask to connect. A site learns nothing about your wallet until you approve its connection; it then sees your public address and the network in use, and can ask you to sign messages or transactions. Each signature and transaction needs your approval on a review screen. You can disconnect or block a site at any time (Connected sites).
• WalletConnect. Only if you pair an app with WalletConnect: the pairing and the requests of that app go through WalletConnect's relay and verification services (walletconnect.org, walletconnect.com), under WalletConnect's privacy policy.
• The private balance, swaps and bridges. In the web wallet and the Android app: private operations go to the KemLock relayer of the network (relayer.kemlock.com for Base, relayer-eth.kemlock.com for Ethereum), which sees the proof and the public data it puts on chain, never your keys; to find your private notes, the wallet reads the private pool's public events from a block explorer (base.blockscout.com for Base, eth.blockscout.com for Ethereum), which, like any server, sees your IP address but not which notes are yours; swaps and bridges are quoted by LI.FI through kemlock.com, and the quote request carries the tokens, the amounts and the addresses involved.
• QR scanner (Android app). Only when you scan a QR code: the app uses the Google Play services code scanner. The camera image is processed on your phone and the app receives only the decoded text; it holds no camera permission. Google's scanner sends Google diagnostic and usage data (device model, Android and app version, performance, error codes and a per-installation identifier), under Google's privacy policy. Kotav Labs receives none of it.
• The pool figures on this site. The Status section of kemlock.com shows the private pools' caps and state only when you press "Read from the chain". Your browser then asks the same public RPC providers and the block explorers base.blockscout.com and eth.blockscout.com directly, for the pools' public figures. No wallet address is sent, because the site has none; like any server, they see your IP address. Until you press the button, the site makes no request to anyone but kemlock.com.

Google account (optional): "Sign in with Google"

If you link a Google account to your wallet (Settings → Google account → Link Google account), or choose Sign in with Google on the first screen or the lock screen, the wallet keeps a copy of itself in your own Google Drive, so that signing in with that Google account opens the wallet on any device without a backup password. Your recovery phrase still restores it anywhere.

• What is stored, and where. Two files per wallet, in the hidden app-data folder of your Google Drive, which only KemLock can see: the wallet's copy (your recovery phrase, your saved contacts and operation records, and your wallet password in encrypted form, the same record that protects the wallet on your computer), encrypted on your device with AES-256-GCM under a random key; and that key. The copy is kept up to date automatically while you are signed in. Neither file contains your address or your e-mail address in readable form; they carry an identifier that only your wallet can compute, a key identifier, the time they were saved and the KemLock version (web, extension, Android or iOS) that saved them.
• Who can open the copy. Because the key is in the same Google account, the copy is protected by your Google account, not by a password: anyone who gets into that Google account, and Google itself, could open it and control your wallet. Turn on Google 2-Step Verification. If you also turn on Also protect with a password, the copy is instead encrypted with a backup password you choose (Argon2id key derivation, 64 MiB, and AES-256-GCM), no key is stored, and Google cannot open it; every new device then asks for that password, and nobody, including Kotav Labs, can reset it.
• Signing is separate. Signing in with Google opens the wallet. In the web wallet and the extension every transaction and signature still asks for your wallet password; in the apps, for your phone's screen lock.
• Google user data the wallet accesses. Only the files KemLock itself creates in that app-data folder, and your Google account's e-mail address and name as Google Drive reports them to the app, through the permission https://www.googleapis.com/auth/drive.appdata. The wallet does not ask for your contacts or any other Drive file, and cannot read them. The e-mail address and name are shown on your device only ("Linked to …").
• How it is used. Only to save, list, download and delete your wallet's copy and its key, on your device. The Google access token stays in your device's memory (in the Android app, in Google Play services) for at most an hour and is never stored or logged by KemLock; in the iOS app, the token Google returns for renewing access is discarded at once.
• Who receives it. Nobody but Google, which stores the files in your account under Google's privacy policy. Kotav Labs' servers never receive the files, the token, your Google account, your e-mail address or the link between your Google account and your wallet. We do not transfer or sell Google user data, use it for advertising, or let anyone read it.
• Removing it. Unlink in Settings deletes the key first, then the copy, from your Drive, revokes KemLock's access and forgets the link on the device. You can also revoke access at myaccount.google.com/connections, and delete the hidden app data in Google Drive (Settings → Manage apps → KemLock → Delete hidden app data). Uninstalling KemLock does not delete the files in your Drive.

KemLock's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

What we do not do

• No analytics, tracking pixels, advertising or fingerprinting, in the Android app, the extension, the web wallet or this site.
• The Android app asks only for internet access and biometric authentication. It has no camera, location, contacts or storage permission, and it blocks screenshots of its screens.
• The extension does not read the pages you visit or your browsing history. Its page script only passes a site's own wallet requests to the wallet, with the site's address as reported by your browser.
• We do not sell, rent or share your data with third parties, and do not use it for creditworthiness, lending or any purpose unrelated to running the wallet.
• The extension and the Android app run no remotely hosted code: all of their code is in the package you install.

Chrome Web Store user data policy

The use of information received through the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Your rights

Most data stays on your device, under your control. For anything Kotav Labs holds (such as server access logs or partner records), you can ask for access, correction or deletion, and you may complain to your data protection authority (in Portugal, the CNPD). There are no KemLock accounts: to ask for deletion, write to support@kemlock.com. Data on public blockchains cannot be deleted by anyone.

Children

KemLock is meant for adults and is not directed at children. On Google Play, the Android app is listed for ages 18 and over.

Changes

We will update this page when the wallet's data handling changes, and change the date above.

Contact

Kotav Labs · support@kemlock.com