Privacy

What Kalyx stores. What it never receives.

This policy covers kalyx.si, the public testnet, the wallet on the explorer, and the Kalyx browser extension. Effective 26 October 2026.

Kalyx does not sell personal information. It does not build an advertising profile. It does not ask for your name, email, or phone number to open a wallet. The terms are the rules for using the software. This page is what happens to information.

The website

kalyx.si serves pages. A request can show the host your IP address, the time, and the path you asked for. The host may keep ordinary server logs for as long as that host keeps them. Those logs are not a product.

The theme switch stores one value in this browser, under the name kalyx-theme. It is light or dark. Clearing site data removes it. The site does not set an account cookie.

Pages load typefaces from Google Fonts. That request goes to Google and can include your IP address and the fact that you opened kalyx.si. Google’s own policy is at policies.google.com/privacy.

The public pages do not load an analytics product. The admin page is for the operator of this site. It is not a visitor account. It uses Privy to check one operator wallet. Privy’s policy is at privy.io/privacy.

The chain is public

A public send is public. The explorer shows the account, the amount, the fee, and the block. Validator duties are public. That record is the chain. Kalyx does not delete it on request, because a later block cannot be edited to forget an earlier one.

A private note is a second balance of the same KALYX. It is not full anonymity, and it is not a hidden sender.

  • Shield is public. The account and the amount show. That is the last public view of those coins.
  • A private payment does not put the amount on the transaction value. The transaction still names the account that holds the note, and the account that will hold it next.
  • Unshield is public. The coins return to a public balance.
  • The account that pays the network fee is named.
  • The chain stores a commitment. It does not store the note. Lose every copy of the note and the coins cannot come back. There is no recovery desk.

The check is built from hashes. It is not an elliptic-curve proof, and it is not a replacement for the ML-DSA-87 validator signature or the XMSS account signature. The private payments page is the full description.

The explorer and the faucet

testnet.kalyx.si shows blocks, accounts, and validators. Looking up an address is a request to that server. The address is already a public chain record.

A send from the explorer wallet, a faucet request, and a send from the browser extension pass a person check. The check is Google reCAPTCHA. The browser talks to Google, and the explorer verifies the result with Google. The check is there so a script cannot drain the public submit path. It is not an account, and it is not a backup of a seed. Google’s policy is linked above.

The faucet asks for a KAL address and that check. It does not ask for a name. It pays test coins, with a daily cap.

The wallet on the explorer

The dashboard wallet creates a spending account in the browser. The seed stays in the tab. The server does not receive the seed, the passphrase, or the opened key.

  • You can save an encrypted file, kalyx-wallet.json. Encryption uses argon2id. The file and the passphrase stay on your machine.
  • Refresh the page and the tab forgets the seed until you open the wallet again.
  • Private notes for that wallet stay in this browser, locked by the wallet seed. Clearing site data does not bring them back. Another computer does not have them.
  • If you pay someone else, the page shows a note code once. That code is the note. Give it only to the person who holds the named account. The chain never receives it.

The browser extension

The Kalyx extension is a spending wallet for chain 21520. It runs in Chrome, Firefox, and Brave. It does not create a Kalyx account on a server. Private notes are not in the extension.

What stays on the computer

  • The keystore. Each wallet is one seed, encrypted with argon2id under a passphrase you choose. The encrypted record is stored by the browser, on that computer. The passphrase is not sent to Kalyx.
  • The open session. While the wallet is unlocked, the browser holds the opened account in session storage. Lock clears that session. Closing the browser ends it.
  • Connected sites. After you choose Connect, the extension remembers that site’s origin so it can show the address again. A site does not see the address before that choice. Reset, or removing the extension, clears the list.
  • Tokens you add. A contract address you paste is stored so the wallet can read the name, the symbol, and the balance again.
  • A display choice. Popup or sidebar is stored on the computer.

What the extension is allowed to do

The extension asks the browser for storage, so it can keep the encrypted keystore. It asks to open its own window, as a popup or a sidebar. It asks to run on http and https pages so it can offer window.kalyx to a site built for this chain.

That permission does not mean the extension reads your pages for a profile. It does not read your other wallets. It does not sell what a page contains. A site learns your address only after you connect, and only that site. A send still waits for you to confirm it.

What leaves the computer

Balances, token reads, and submitted transactions go to testnet.kalyx.si. That request can show your IP address to that server. The seed, the passphrase, and the opened key do not travel with it. A submitted transaction is public chain data, as described above. The person check is the same reCAPTCHA the explorer uses.

A signature spends one XMSS leaf. The extension does not offer a signature of an arbitrary message, because that signature would spend a leaf.

Reset and removal

Reset asks you to type RESET. It deletes the wallets, the keystore, and the connected sites stored in that browser. It does not delete coins from the chain. A forgotten passphrase cannot be recovered from the extension. Removing the extension from the browser removes what the browser stored for it. A seed you wrote down can be imported again. A seed you did not write down is gone.

What this policy does not cover

A site you connect can keep its own logs. A contract you call can record what you send. A browser store that lists the extension has its own policy. Those parties are not this page.

Kalyx does not sell personal information. It does not share a seed, a passphrase, or a note with a buyer, an advertiser, or a data broker. It does not have those secrets on a server to share.

Children

This project is not made for children. The software does not ask a child’s age, because it does not ask who you are.

Changes

This page can change. The date at the top is the version on the site. A change does not give Kalyx a copy of a seed it never received.