Privacy Policy
Last updated 14 November 2026
KerbTape is built to need as little about you as possible: there are no accounts, no names, no ad trackers and no analytics scripts. This page lists what we do store, why, for how long, and who else sees data when you use the board, the terminal, our bots and notifications.
The short version
- Visiting the board: we count page views and clicks as daily totals. We don’t store your IP address, browser details or a visitor id in our app.
- Trading in the terminal: your keys and settings stay on your device. Your trades are on Hyperliquid’s public ledger, as they would be with any Hyperliquid app.
- We store a wallet address only where a feature needs it (referral credit, free-game entries, Founding invites, opt-in leaderboards, server-side automation you turn on), and we never publish addresses tied to you.
- Bots and notifications store only what they need to send what you asked for, and you can stop or delete them.
Visiting the board
- Counts. Page views and clicks (for example a click on a Trade button) are stored as daily totals per event type, referral code and market. No IP address, user agent, cookie or visitor id is stored with them.
- Rate limits. Your IP address is held in memory for a few minutes to stop abuse, and then forgotten. For the terminal’s usage counts (below) we also keep, in memory only, a keyed hash of it until the end of the day (UTC), to cap how many counts one address can send.
- Country. Our network provider tells our server which country a request comes from. We use it on the spot to show regional notices and to hide trade links where trading isn’t offered; we don’t store it with anything about you (the free games are the one exception, below).
- Server logs. Our web server keeps standard technical access logs (time, page requested, status, browser user agent, and the connecting address, which is our network provider’s rather than yours) for troubleshooting and security, for about 14 days.
Using the terminal
- On your device only: the trading key (encrypted in your browser, valid 30 days), your settings, layouts, hotkeys, saved commands, journal and local alerts. We can’t see them. Clearing your browser’s site data removes them.
- Sent to Hyperliquid, not us: your orders and account reads go straight from your browser to Hyperliquid’s API. Hyperliquid is a public blockchain: your address, positions and trades are visible to anyone, whichever app you use.
- Usage counts: the terminal sends us anonymous events, each at most once per browser (flags in your browser’s storage record what was already sent):
- with the referral code and market: trading set up, first order, deposit started or sent, a share, and WalletConnect failing to connect;
- if you opened the terminal from one of our links (a share card, a post, a group or partner link): opened, wallet connected and first trade (with the time it took), with the id of that link;
- as daily totals only: the terminal opened, a wallet connected, your Hyperliquid account had funds, your first trade, which deposit route was shown or opened, a deposit sent or arrived, the “Your weekend” card shown, the Monday reminder turned on or opened (push or Telegram), and coming back in week 1 to 12 after your first trade. The week counts carry the calendar week of that first trade, which you share with everyone who started that week.
- Your fee tier: to show your fee tier, the terminal asks our server for it with your wallet address when you connect and about every 5 minutes after. The server looks up that address’s 14-day Hyperliquid volume and keeps the answer, with the address, for up to 6 hours (at most 20,000 addresses; the oldest are dropped first). The usage counts above stay separate and carry no address. The address is also part of the request’s web address, so it appears in our server access logs (about 14 days).
- Builder-fee records: Hyperliquid publishes the fills routed with our builder code, including the trader’s address. We read them to work out fee tiers, waivers and partner payouts.
- Signing in: some features (share cards, your calls on the “Your weekend” card, your own referral code) ask you to sign a sign-in message; it costs nothing and is not a transaction. We then keep the one-time code you signed, with your wallet address, for up to a day; give your wallet its own referral code; and, if you sign in from a country where trading isn’t offered, note that fact against the address (not the country). On the board, your browser keeps the sign-in token for that tab for up to 12 hours; in the terminal, for up to 7 days for that wallet on this device, until you switch wallets or disconnect.
- Referral credit: if you arrived through a partner’s or group’s link and approve the builder fee, or sign in (share cards, the “Your weekend” card), the terminal sends us your wallet address and that referral code, so the partner can be credited. Visitors without a partner code are not recorded this way (the fee-tier lookup above is separate). Totals are published per code, never addresses.
- Founding members: redeeming an invite stores your wallet address with the invite code and your signed confirmation that you are not a US person.
- Server-side automation (only if you turn it on): we store your wallet address, the trade-only key you approved for it (encrypted), and the automated orders you set up, until you stop and revoke them.
- Execution reports (only if you upload them): we keep a keyed hash of your address, not the address.
Free games and leaderboards
Entering “Call the reopen”, “Call the first print” or an opt-in leaderboard stores your wallet address, the message you signed, your picks, and the alias you chose (if any). For the games we also store the two-letter country code at entry (for regional prize rules) and a keyed hash of your network’s address range, to spot duplicate entries; the IP address itself is not stored. Addresses are never shown publicly: leaderboards show your alias or an anonymous label. Entering sets a random cookie for the entry form (see Cookies). You can leave an opt-in leaderboard by signing an opt-out.
Telegram and Discord bots
- Personal alerts (Telegram): your chat id, when you opted in, quiet hours, the alerts you set, the wallet addresses you link, and a log of messages sent to you (to enforce limits). Not stored: your name, username, phone number, profile, or what you type to the bot.
/stopstops all messages at once;/deleteerases your alerts, linked wallets and message log. - Weekend message (Telegram): if you turn it on, the Monday message counts the graded “Call the reopen” calls made by the wallets you linked, read from the game’s own records.
- Groups and channels: the group or channel id and the settings its admins chose. When members use group features such as calls, mutes or the contest, the member is stored only as a keyed hash of their user id, never the id, name or messages. For Discord the server is stored as a keyed hash too.
- The bot never messages anyone first.
Push notifications
If you turn on browser notifications, we store the push address your browser gives us (and its public keys), the time zone and quiet hours you pick, and the alerts you create. No wallet or IP address. Turning notifications off (or the push service telling us the address is gone) erases the push address and switches your alerts off. If you follow a public Hyperliquid address, that address sits in a watch list for 24 hours after its last use, not linked to you.
Cookies and local storage
| Name | What it does | Kept for |
|---|---|---|
kt_ref | Remembers the partner or group link you arrived from, so trade links credit them. Set only when you arrive with such a link. | 30 days |
kt_sr | A random value for the free-game entry forms, to stop strangers using up your entry attempts. Sent only to our entry endpoints. | 30 days |
kt_admin | Signs in the site’s operators. Visitors never get it. | 30 days |
| Browser storage | Your theme, dismissed notices and last tab on the board; your settings and trading key in the terminal. These stay on your device, with two exceptions: the board sign-in token (kept for the tab, up to 12 hours; in the terminal, up to 7 days for that wallet) is sent to our server with requests that need you signed in, such as your calls on the “Your weekend” card and share cards; and the usage-count flags decide which counts are sent (the flags themselves are not sent). | Until you clear it (the sign-in token: until the tab closes or 12 hours; in the terminal, 7 days or until you switch wallets or disconnect) |
We use no advertising or analytics cookies, and our network provider’s analytics beacon is turned off.
Who else sees data
- Cloudflare carries all traffic to KerbTape (security, caching and country detection) and processes connection data under its own policy.
- Hyperliquid receives your orders and account reads directly from your browser. Trades and positions on Hyperliquid are public.
- WalletConnect (Reown) relays messages between the page and your wallet app if you connect that way; your wallet provider sees what you sign.
- Your wallet app and the network provider it uses see balance reads: the “Fund your account” sheet asks your wallet for your USDC and gas balance on the chain it is on, so that provider sees a read for your address. “Open in” links on phones go through that wallet maker’s link service.
- Bridges and other deposit sites (Relay and others) see your visit when you open them from the funding sheet. The link opens their own site with no referrer, and they see your wallet if you connect it there.
- Google Fonts serves the terminal’s fonts, so Google sees a request from your browser. The board hosts its own fonts.
- Telegram and Discord carry bot messages; X sees a share only if you click Post on X.
- Push services run by your browser’s maker (Apple, Google, Mozilla or Microsoft) deliver notifications.
- Our server runs on Amazon Web Services in Japan. Public data sources (Hyperliquid, the BLS, the BEA, SEC filings) receive no data about you.
Personal data is never sold or rented, and we don’t share it with anyone else unless the law requires it.
How long we keep it
| Data | Kept |
|---|---|
| Daily counts | Kept as totals; they contain nothing about a person |
| Bot message logs and finished alerts | 30 days; everything at once with /delete |
| Group send logs | 30 days |
| Sign-in codes (one-time, with the wallet address) | Up to a day |
| Referral bindings and Founding invites | While needed for fees, payouts and waivers; removed on request |
| Free-game entries | Kept as the game’s permanent record (entries can’t be edited after the deadline); removed on request where the rules allow |
| Push subscriptions | Until you turn notifications off |
| Followed public addresses | 24 hours after last use |
| Server access logs | About 14 days |
| Emails you send us | As long as needed to answer, then deleted |
Data on Hyperliquid’s blockchain can’t be deleted by anyone.
Your choices
- Use the board without any of the above: just browse.
- Stop or delete bot data with
/stopand/delete; turn notifications off in the page or your browser. - Ask us to see, correct or remove data tied to your wallet address at [email protected]. We may ask you to sign a message with that wallet to prove it is yours.
Age
KerbTape is not for anyone under 18.
Changes and contact
We will update this page when what we store changes; the date at the top shows the latest version. Questions: [email protected].