Skip to content

Privacy

Last updated 2026-11-14.

Sagitta is a website (sagitta.broker), these docs, a public API (api.sagitta.broker) and two command-line clients for programs on Solana. There are no accounts: no sign-up, no names, no email addresses, no passwords. This page lists everything that passes through our systems and what we keep of it.

  • Sagitta sets no cookies, and runs no analytics, advertising or tracking scripts on the site or the docs.
  • The API sees your IP address, to count your calls against its limits. The counts live only in the server’s memory.
  • The API keeps no access log. Its log never records callers’ IP addresses, what they asked for, or API keys.
  • For a free API key, we store your wallet address, a hash of the key, and the IP address it was requested from.
  • To read the chain, your browser asks Solana’s public endpoints directly, so they see your IP address. See Reading the chain.
  • Your trades are on a public blockchain. Anyone can read them, and so can we.

Every call to the API reaches our server through Cloudflare, which tells it the caller’s IP address. The API uses it for these things only:

  • Counting calls. Each limit counts calls per IP address (an IPv6 address by its /48 block) in a short window: 60 seconds for the API’s limits, 10 seconds for the calls that make it read the chain on your behalf (a wallet’s holdings, a coin’s pools, a transaction to sign, a search). The counters are held in the server’s memory, are never written to disk or to a log, and are lost whenever the server restarts.
  • The site’s check. When a page of sagitta.broker opens, it runs Cloudflare Turnstile, an invisible check that the visitor is a browser and not a script. The page sends the check’s result to the API, and the API asks Cloudflare to confirm it, with your IP address. The API then gives the page a site token that lasts 30 minutes. The token holds your IP address (an IPv6 address by its /48 block) and a random number, signed by the API, so it only works from the address that asked for it. The API stores nothing about it.
  • Issuing keys. See API keys below.

The API’s log records the server’s own events and errors. It does not record who called, from where, or with what. Before a line is written, any web address and anything shaped like an API key is removed from it.

A free API key costs a Sign-In With Solana signature from your wallet. Signing costs nothing and sends no transaction. The API stores:

  • the wallet address that signed;
  • a SHA-256 hash of the key, and its first characters (sk_sag_ and 8 more) so a key can be looked up. The full key is shown to you once and never stored;
  • the IP address the key was requested from (an IPv6 address by its /48 block). It is there to hold new keys to 3 a day for each IP address;
  • when the key was made, when it was last used (to within a minute), and whether and why it was revoked.

The message you sign is not stored until you use it. Then its one-time code is kept until it expires, five minutes later, so the same signature can’t be used twice.

You can revoke your key at any time with a fresh signature, and asking for a new key revokes the old one at once. A key we revoke for abuse also stops its wallet address from getting another, and we keep the address and the reason for as long as that block stands. Key records stay after a key is revoked or replaced. Write to us if you want the records for your address removed. See API keys for how keys work.

Connecting a wallet shows the site your wallet’s public address, nothing else. Your wallet signs every transaction itself. Sagitta never sees your seed phrase or your wallet’s private key, and nobody from Sagitta will ever ask for them.

  • Browser wallets talk to the page directly, through the Wallet Standard. The site loads no wallet service of its own.
  • Phone wallets. On Android, the Mobile Wallet Adapter connects the page to a wallet app on the same phone over a local connection, with no relay in between. A deep link to Phantom, Solflare or Backpack opens the site inside that wallet’s own browser, which is covered by that wallet’s own policy.
  • The burner wallet is made in your browser. Its private key is kept in your browser’s local storage, on that device only, and never sent to us. If you clear the site’s data, switch browsers or lose the device, the key and anything it holds are gone, and anyone who can use that browser can use the burner. You are responsible for it. Use it for small amounts and move what you win to a wallet of your own. When the browser refuses to store it, the key lives in the tab’s memory and is gone when the tab closes.

The site, and the wallet libraries it runs, keep a few small records in your browser. None of them is a cookie, and none is sent to us, except the site token, which goes with each call to the API.

Name Where What it holds
hype local storage Whether the trade pop-ups (hype toasts) are on
ref local storage The referrer address from a ?ref= link, which your mints then carry
pins local storage The markets you pinned or unpinned
cat local storage The category filter you last chose
lastMarket:v1 local storage The last market you opened, for the Trade button
view local storage Whether you chose the Simple or the Pro view
onboarded local storage That you have seen the card shown before your first wallet connection
sagitta:wallet local storage Which wallet you connected, so a reload reconnects you
SolanaMobileWalletAdapterDefaultAuthorizationCache local storage On Android with the Mobile Wallet Adapter: the wallet app’s authorization for the site and the connected account, so a reload reconnects
sol-burner:v1 local storage The burner wallet’s private key, if you made one
sol-burner:connected local storage Whether the burner is the connected wallet, so a reload reconnects it
sagitta:site:… session storage and local storage The site token, good for about 30 minutes. Each tab keeps its own, and the newest any tab got is kept for a new tab to start with

Clearing the site’s data in your browser removes all of it. Move anything out of a burner first.

Cloudflare serves docs.sagitta.broker (Cloudflare Pages) and carries every request to sagitta.broker and api.sagitta.broker to our server (Cloudflare Tunnel). Cloudflare handles each request, your IP address included, to deliver and protect it. Turnstile, the site’s invisible check, is the only outside script the site loads, from challenges.cloudflare.com. It reads signals from your browser, such as your IP address and browser type, to tell people from bots. Cloudflare’s own policies cover what it does:

Search on these docs runs inside your browser and sends nothing anywhere.

Most of what a page shows comes from the API. Where a number has to be current, your browser reads Solana itself, from its public endpoints: Solana’s own and PublicNode’s, when the first doesn’t answer, both listed on the Solana page. That covers the open market’s accounts, a wallet’s tokens and tickets, and your own balance before you trade. Both endpoints see your IP address and what your browser asks them, such as the wallet it looks up, and their own policies cover what they keep. The site sends them nothing of its own: no site token, no cookie, and not the address of the page you are on.

Your wallet sends your transactions through its own provider. A burner sends them through the same public endpoints. The API never passes your browser’s calls on to the chain.

When you search for a coin to list, the API looks your search up with Jupiter, GeckoTerminal and DexScreener from our server. They see the search, not you.

Solana is a public blockchain. Every commit, fill, cash-out, delivery, claim and referral is recorded there for good, with the wallet addresses involved, and anyone can read it. The site and the API show this public record: the board, the live feed, the leaderboard, each wallet’s page and share cards. Sagitta’s Telegram channel and X account may post public activity too, such as large trades, new markets and wins, naming wallets by a short form of their address. Nobody, including Sagitta, can change or delete anything on chain.

Each night the API’s databases and the keeper’s are copied, compressed and stored in Cloudflare R2, and each copy is deleted after 14 days. They hold the chain data the API has read, the API key records described above, and the services’ own working state. The API’s host, DigitalOcean, also keeps a daily backup of its whole disk, and deletes each one after 7 days.

sagitta.mjs and nash.mjs run on your own computer. They keep your wallet key and your API key in ~/.sagitta on that computer, sign locally, read the chain through Solana’s public endpoint (or one you choose), and call the API with your key.

When what we collect or keep changes, we update this page and its date, and note the change in the changelog.

Write to [email protected]. The same address takes security reports and privacy questions. If you write to us, we use your message and address only to answer you.