- No accounts, no tracking cookies, no analytics beacons.
- Your theme choice and tour progress stay in your own browser.
- Kerb's servers do not keep a list of wallets that connect.
- Paid agent calls are recorded as public evidence: payer, amount, transaction.
01What stays in your browser
Two small preferences, saved by your own browser: your theme (Night, Day or Market time) and whether you have seen the guided tour. Clearing site data removes them. Nothing else is written.
02Wallets
Connecting a wallet shares its public address with the page running in your browser, so the page can read your balances and positions from X Layer. Kerb's servers do not receive or store a list of connected addresses. The account page reads the same public data anyone can read on OKLink.
03What the servers see
Like any web server, the Kerb web and API servers receive the IP address, time and path of each request. These are used to serve the page and to enforce rate limits, and are kept only in short-lived operational logs, never sold or shared.
04Public blockchains
Transactions you send are public on X Layer by design and cannot be erased by anyone. Kerb only reads what the chain already shows.
05Paid agent calls
For each settled x402 call Kerb records the payer address, the amount, the settlement transaction, the time, and a hash of the answer it returned. These records are evidence that the service was paid for and delivered; the payment itself is already public on chain.
06Contact
Questions about privacy: open an issue at github.com/Franlinozz/Kerb.
Effective 23 September 2026. Questions: open an issue. See also the FAQ.