Kieru Back to KieruBack

Privacy notice

Last updated 17 November 2026

Kieru has no accounts. We do not store your keys, your main wallet address, which one-time addresses are yours, IP addresses or chat transcripts. Some of our services see data while it passes through, and this page lists each one.

Contact

This notice covers Kieru: the website, the relayer, the balance reader and the assistant server.

For privacy questions, write to [email protected]. Kieru has no accounts, so we cannot tell who you are unless you tell us.

Back to contents

What stays in your browser

Your one-time keys are made in your browser from one signature of your main wallet. They never leave your device unless you export a backup.

  • The key signature. Your wallet signs the same message twice so Kieru can check that it signs the same way each time. Your browser turns the signature into keys and then drops it. It is never sent to us.
  • Your one-time keys and wallet connection. Held in memory until you close the tab. Sign again on any device to rebuild them. A phone wallet connection is kept in memory too. Its QR code window writes a few settings to this browser's storage, and Kieru deletes them when the QR step ends, when you disconnect and when you leave the page.
  • Chat history. Kept in this tab only.
  • A random token that counts your daily questions to the assistant. It is not tied to your wallet.
  • Your eligibility confirmation, asked once per session before you trade.
  • An encrypted backup, only if you export one. You keep the file. Anyone who can decrypt it controls your one-time addresses.

"Clear keys from this tab" in Portfolio clears your keys, the list of your one-time addresses and cached balances from this tab right away, instead of when you close it. It also ends a phone wallet connection. Nothing is saved on this device. Your funds stay where they are.

Back to contents

What each part receives

Kieru runs on Cloudflare. We switch request logs off on every one of our servers. Beyond the two counters listed under What we store, they keep nothing.

The website

Receives
Normal requests for the page and its files. The site loads no scripts, fonts or analytics from other servers. The phone wallet library is served from our own domain.
Keeps
Nothing. Hosting request logs are off.

The relayer

Sends your trade to the chain and pays the network fee, then takes it back from the trade.

Receives
The signed trade from one one-time address, until it is on-chain.
Keeps
Nothing. We count trades and fees per day from the relayer's public transactions on Robinhood Chain; the relayer itself keeps no records.
Never keeps
Which addresses belong together, IP addresses, request logs.

The balance reader

Reads balances, trade history and prices for the Portfolio and Trade screens.

Receives
The one-time addresses you ask about, all at once, for balances and trade history.
Keeps
Nothing. We do not log these requests.

This is the one place where the full list of your one-time addresses exists outside your browser, while the request is answered. You rely on our promise not to log it. Your main wallet's balance is read by your wallet app, never by our balance reader, so our server never sees it next to your one-time addresses.

The assistant

Our server passes your question to the model and the answer back to you.

Receives
Your question and the data you chose to share: tickers, quantities, average cost and current prices. Never addresses. The Ask AI screen shows the exact data, and you can switch positions off.
Keeps
Daily question counts, keyed by the random token in your browser.
Never keeps
Your IP address, the question, the answer, or analytics on the text.

To limit abuse, the server counts requests using a salted hash of your IP address that lives in memory only. The salt changes every day. The IP address itself is not written anywhere.

The model provider

Who
AWS Bedrock, with zero data retention switched on for the whole account.
Receives
Your question and the shared data, without your IP address.
Keeps
Nothing. AWS does not store the question or the answer.

Region check and address screening

Kieru blocks restricted regions and may check addresses against sanctions lists. Neither check stores your IP address or a link between your addresses.

Price quotes

The price you see comes from a quote for your trade size, compared with the Chainlink reference price. Quotes come from swap services run by others. Where one of them answers a request, it handles that request under its own privacy policy.

Back to contents

What we store

Never stored

  • Private keys or the signature they come from
  • Your main wallet address
  • Which one-time addresses belong together
  • IP addresses and chat transcripts

Passes through, not stored

  • Relayer: the signed trade, until it is on-chain
  • Balance reader: the one-time addresses you ask about, for balances and trade history
  • Assistant: your question and the data you chose to share

Stored

  • Daily question counts, keyed by a random token
  • Totals per day of trades and fees, counted from the relayer's public transactions

We say "we don't store", not "no one can see". The next section explains who else sees what.

Back to contents

What others can see

  • Everyone, on-chain. Robinhood Chain is a public blockchain. Anyone can see the one-time address that made a trade, the token, amount, price and time, that our relayer sent it and was paid back, and where the one-time address got its money.
  • Cloudflare and AWS. Our hosting provider and the model provider see traffic while it passes through. We turn off the logs we control; they still process traffic under their own policies.
  • Your wallet app. It reads your main wallet's balance and sends your wallet's own transactions through its own network provider, under its own privacy policy.
  • Phone wallets. If you connect a phone wallet, the site talks to WalletConnect's relay, to Reown's wallet list (api.web3modal.org) and to WalletConnect's site check (verify.walletconnect.org). They see your IP address and our project ID, and the relay passes messages between the site and your wallet. The messages themselves are encrypted between the site and your wallet. The connection is kept in this tab's memory only and ends when you disconnect, clear keys or close the tab. Wallets in your browser do not use these services.
  • The Privacy Pool. You deposit and withdraw in the Privacy Pool's own app, run by a third party (0xbow). Its app, its relayer and its deposit screening follow its own privacy policy, not this one. When you cash out, the pool's screening service sees the one-time address and your main wallet's pool account together.

Kieru keeps your main wallet out of your trades if you fund them through the pool. It does not hide your trades. Someone who studies the chain can still guess links from timing, amounts and how an address was funded. See the risk disclosure.

Back to contents

Your rights

Because we do not keep data that identifies you, we usually have nothing to show you, correct or delete. What sits in your browser is under your control: close the tab, or use "Clear keys from this tab".

You can still ask us about your data at [email protected]. Depending on where you live, you may also have the right to complain to a data protection authority.

Back to contents

Changes to this notice

If what we collect changes, we update this page and the date at the top before the change takes effect. We will not start storing anything listed under "Never stored" without saying so here first.

Back to contents