Privacy policy

What we keep, part one: the till sticker

A seller may have a printed sticker on the counter. It carries no amount: the seller names the price on their own phone, and for ten minutes we hold it so the buyer can see it when they point a camera at the sticker. What is held is exactly this: the seller’s address, the till number, the amount, the currency, the item name, the order and invoice numbers, and the time. After ten minutes the record deletes itself.

Nothing about the buyer is kept: not a wallet address, not a device, not the payment itself — whether an invoice was paid we read from the blockchain. But to be honest about logs: while the buyer waits for the amount, their page asks our server every few seconds what the till is asking for, and that question contains the seller’s address and the till number. So the hosting logs (Cloudflare) keep an ordinary entry: such-and-such IP asked about such-and-such till at such-and-such time. The buyer’s name, wallet and amount are not in it. If a seller uses the on-chain charge instead of the sticker, we do not hold the amount either.

What we keep, part two: messages attached to tips

On the tips page (wallet.tavarov.com/d/name) a viewer can leave the creator a nickname and a short message. We keep it under the invoice number and show it to the creator only after a payment to that very creator arrives on the blockchain under that number; unpaid messages are erased after two hours, paid ones after 180 days. Stored with the message are the amount, the currency and the payer address — the same things that are already public on the blockchain. Nothing else about the viewer is kept. The message is not private: the creator sees it and may later show it on stream. A creator can also put a greeting and a fundraising goal on their page — we keep them until the creator changes them, and anyone who opens the page can see them.

What we keep, part three: shops using the API

A shop that connects payments to its website signs in to the developer dashboard by signing with its wallet. We keep: its wallet address; fingerprints of its API keys (not the key itself — only the shop sees it, once); its webhook address and the secret we sign webhooks with; the invoices it created through the API — amount, currency, order number, description, its own metadata and, once paid, the payer address from the blockchain. Invoices are kept for 90 days, a dashboard sign-in lasts 12 hours. Beyond the payer address, which is public anyway, we know nothing about the customer.

What we do not collect

The wallet does not ask for identity documents, contacts or advertising identifiers. Your API integration may include order metadata; do not include unnecessary customer information. Contacting the project by email shares your address and the contents of your message so we can reply.

What is stored on your device

• The wallet keys and the twelve-word phrase — encrypted, under your password.
• Settings: language, mode, the chosen network, tokens you added yourself, the site address used for invoices, your OBS alert settings.
• A journal of your own operations — so that history opens instantly and works without a connection.

All of it lives on the device only. It is not sent to our servers and not copied to any cloud. Delete the app and it goes with it, which is why a backup is worth making in advance.

The NoN Wallet browser extension works the same way: keys and settings are stored only in the extension's storage in your browser. The extension asks for access only to our server wallet.tavarov.com and does not read the pages you visit, your tabs or your history.

The website tavarov.com counts page views with Cloudflare Web Analytics — no cookies and no tracking across sites. The wallet, the app and the extension themselves have no analytics.

Where requests go

A wallet cannot work without asking the blockchain. These requests go straight from your device, bypassing us, and their recipients can see your IP address and what you asked about:

• BNB Chain, Ethereum, Base and Solana nodes (bsc-dataseed.binance.org, ethereum-rpc.publicnode.com, base-rpc.publicnode.com, solana-rpc.publicnode.com and similar) — balances, fees, sending operations. Some Solana requests go through our server (wallet.tavarov.com/api/solrpc), which passes them to a Solana node and does not store them.
• CoinGecko — coin rates, to show an approximate amount in dollars. Only coin names are requested; your address never goes there.
• Our site — the app page itself, the payment and tip pages, the developer dashboard. The web host’s logs (Cloudflare) then see what any site sees: IP, time, page address.
• Block explorers (BscScan, Etherscan, Basescan, Solscan) — only if you press "view in the explorer" yourself.
• Wallet apps (MetaMask, Trust Wallet, OKX) — only if you choose “open in an app” on the payment page yourself. Then the link to this payment — seller, amount and item — goes through their link service (metamask.app.link, link.trustwallet.com, web3.okx.com) so the page opens in their browser.
• Swap services (KyberSwap, Jupiter, Relay) — only when you open a coin swap yourself. They receive your address, the coins and the amount: without that they cannot quote a rate or build the transaction. You sign the transaction yourself, on your device.
• Phantom and Solflare — only if you press “pay in Phantom” or “in Solflare” on a Solana payment page. The link to that payment then passes through their link server (phantom.app, solflare.com) to open the page in the wallet’s browser.

None of these services receives your keys, phrase or password from us: we do not have them.

App permissions

• Internet — without it the wallet cannot see the network.
• Camera — only to read a payment QR code. The image is processed on the device, is never sent anywhere and is not saved. Permission is asked at the moment you press "scan", and refusing it breaks nothing but scanning.
• Face, fingerprint or screen lock — only if you turn on biometric unlock yourself. They then also confirm large payments and dangerous actions. The check is done by the device’s own system, which tells us nothing.

Backups

You create the backup yourself and it is encrypted with your password at once. The file stays with you: we never receive it and cannot recover a forgotten password. Keep the copy and the password apart from each other.

The blockchain is an open book

Everything that happens on the network is visible to everyone and stays forever: addresses, amounts, times. That is how a blockchain is built, not a decision of ours, and nobody can delete a record from it, ourselves included.

Children

The app is not intended for children and is not aimed at them in content.

Changes

If something changes, this page changes with it — starting with the date at the top.

Contact

Questions about this page: [email protected]. We never ask for keys, the twelve-word phrase or your password — whoever asks, it is a fraud.

Browser cashier and desktop app

The browser cashier keeps the API key in memory for the current page session. Checkout settings and payment history are saved in browser storage on that device. API requests pass through our cashier server to the invoice API. Closing or reloading the page may require entering the key again. The Windows app keeps checkout settings and history on the computer where it runs.

Project contact: [email protected].