Wojak Wallet — browser extension for WojakCoin (WJK-20 tokens & inscriptions)
Last updated: June 11, 2026
This policy describes the privacy practices of the Wojak Wallet browser extension (the “Wallet”) for the WojakCoin network. The Wallet is free, open-source software. This policy applies to the extension itself, not to any third-party website, decentralized application (dApp), or blockchain node you may choose to interact with.
We want to be explicit. The Wallet does not collect or transmit any of the following:
The Wallet contains no third-party analytics or tracking SDKs of any kind.
To function as a wallet, the extension stores the following locally on your device only, using your browser’s extension storage. This data is never sent to us or to any server we control:
nintondo-browser-passworder library (AES via the browser’s Web Crypto API). Only an encrypted blob is stored; the password is never saved.This data persists until you remove it — for example by locking, resetting, or uninstalling the extension, or clearing your browser’s extension data. If you lose your recovery phrase, no one (including us) can recover your funds.
Like any cryptocurrency wallet, the Wallet must communicate with the blockchain to be useful. To show balances, fetch token/inscription data, estimate fees, and broadcast transactions, the Wallet sends requests to public WojakCoin infrastructure APIs. These requests can include:
These are public by the nature of any blockchain. No private keys, recovery phrase, or password are ever included in these requests. By default the Wallet contacts WojakCoin endpoints such as:
api.wojakcoin.cashexplorer.wojakcoin.cashord.wojakcoin.cashwjk20.wojakcoin.cashwojakcoin.cash / testnet.wojakcoin.cashWhen you connect the Wallet to a third-party website or dApp, that site may see your public address and may request transaction signatures, which you must approve. Your interaction with such sites is governed by their privacy policies, not this one.
| Permission | Why it’s used |
|---|---|
storage / unlimitedStorage | To save your encrypted wallet and preferences locally on your device. |
sidePanel | To let you open the wallet in the browser’s side panel. |
| Content script on pages | To inject a standard wallet provider so websites/dApps can request a connection and transaction signatures — only after you approve. The Wallet does not read, collect, or transmit page content or browsing history. |
For clarity and to match the Chrome Web Store “Privacy practices” disclosures:
| Data type | Collected / transmitted by us? |
|---|---|
| Personally identifiable information | No |
| Health / financial / payment info | No |
| Authentication information (passwords, keys) | No — stored encrypted on-device only |
| Personal communications | No |
| Location | No |
| Web history / user activity | No |
| Website content | No |
| Analytics / tracking | No |
We also affirm: we do not sell or transfer user data to third parties, we do not use or transfer data for purposes unrelated to the wallet’s core functionality, and we do not use or transfer data to determine creditworthiness or for lending.
Your secrets are encrypted at rest using your password before being written to local storage. Because the Wallet is non-custodial and self-contained, the security of your funds depends on keeping your recovery phrase and password private and your device free of malware. Never share your recovery phrase with anyone.
The Wallet is not directed to children under 13 (or the minimum age required in your jurisdiction) and does not knowingly collect any data from them.
We may update this policy from time to time. Material changes will be reflected here with an updated “Last updated” date. Continued use of the Wallet after an update constitutes acceptance of the revised policy.
Questions about this policy or the Wallet’s privacy practices can be raised via the project’s public repository: