Ink Ink Wallet
Download Soon

Updated 28 September 2026

Privacy Policy

This policy describes how Ink Wallet handles information. It matches how the software works today, not a generic template.

Who we are

Ink Wallet is a self-custody wallet for Ink (chain IDs 57073 and 763373). The Chrome extension is the product that exists today. Android and iOS builds will use the same local-vault model when those listings go live. There is no user account with us. Contact: info@inkonwallet.com.

Ink Wallet is an independent build. It is not the Ink Foundation and not Kraken.

No accounts

We do not ask you to register. We do not operate a backend that stores your wallet, balances, or recovery phrase.

What stays on your device

The encrypted vault, settings, custom tokens, RPC overrides, connected dapp permissions, and language stay on this device. In the Chrome extension they live in chrome.storage.local, and the session unlock flag uses chrome.storage.session. On forthcoming Android and iOS apps they will live in on-device app storage. Those stores are not synced to us.

What leaves the device

To show balances, quotes, and activity, the wallet calls public infrastructure: the Ink RPC (rpc-gel.inkonchain.com on mainnet, rpc-gel-sepolia.inkonchain.com on testnet), DexScreener and GeckoTerminal for some prices, token icon CDNs, and Ink explorer pages (explorer.inkonchain.com / explorer-sepolia.inkonchain.com) for transaction links. Those operators can see IP addresses and the on-chain requests you make (addresses you query, transactions you broadcast). We do not receive a copy of that traffic.

Custom RPC

If you set a custom RPC in Settings, that node can see addresses you query and transactions you send. Chrome will ask permission for that host. Only use a node you trust.

Dapps and WalletConnect

In Chrome, Ink Wallet injects a provider into pages you open so a dapp can request accounts and signatures. That site can see the address you approve and the messages or transactions you sign.

On forthcoming Android and iOS apps, a WalletConnect session (QR, pasted wc: link, or inkwallet://) is handled by WalletConnect / Reown infrastructure so the dapp and the wallet can talk. Those operators can see the connection metadata and your wallet address for that session. We do not receive your keys through that path.

Camera

Forthcoming Android and iOS apps may use the camera only when you scan a WalletConnect QR code. Frames are processed on the device to read the QR. We do not upload or store camera images. The Chrome extension does not use the camera.

This website

The marketing site does not use analytics pixels, advertising cookies, or an account system. The host that serves the pages may keep ordinary web logs (IP address, user agent, requested URL) for operations and abuse prevention. We do not sell that data.

Email

If you write to info@inkonwallet.com, we receive whatever you put in the message so we can reply. Do not send a recovery phrase, private key, or password. We do not need them to help, and we will not ask.

Recovery phrases

The phrase is generated and stored only on your device. Ink Wallet cannot read it from here. Anyone who has the phrase can move the assets.

Children

The product is not directed at children. Do not use it if you are not old enough to enter a software agreement in your region.

Changes

We will update this page when the software starts collecting something new. The date at the top will change.

Contact

Questions about this policy: info@inkonwallet.com.