Privacy notice

The short version

There are no accounts here, so there is almost nothing to collect. No signup, no email, no password, no analytics, no tracking pixels, no cookies from us. Your browser stores one key for Ponbond, and it holds which wallet you picked, not who you are.

The one thing worth reading in full is the section on our read proxy, because our server does see the requests your browser makes to the chain. That is stated below rather than skipped.

What we do not collect

• No accounts and no signup. There is nothing to register for and no profile to create.
• No email address, no phone number, no name, no password. We do not run a newsletter.
• No analytics or product telemetry. There is no Google Analytics, no Plausible, no Segment, no session recorder, and no A/B testing tool on any page.
• No advertising or conversion pixels, and no fingerprinting scripts.
• No cookies set by this site. Check for yourself in your browser's storage inspector.
• No selling or sharing of personal data, because there is no store of it to sell.

Your wallet address

Ponbond reads a wallet address only from the wallet you connect yourself, and only after you approve the connection inside the wallet's own window. We cannot see an address before that, and we never ask you to type one.

Once connected, the address is used in your browser to look up your balances and positions. It is not written to a Ponbond database, because there is no database and no server side account. It does leave your browser in one direction: as a parameter inside a public blockchain read, which is the only way to ask the chain what an address holds. That path is described in the next section.

Disconnecting in the app drops the address from the page immediately.

The read proxy, said plainly

Robinhood Chain's public RPC endpoint sends no CORS headers, which means a browser cannot read the chain directly from our site. Every read therefore goes to /api/rpc on our own origin, and our server forwards it to the chain and returns the answer.

So our server sees those requests. Concretely, it sees the method being called, the parameters (which include your wallet address whenever you are looking at your own balance or position), and the ordinary metadata that any web server receives from any HTTP request: your IP address, the time, and your browser's user agent string.

What we do with that: nothing beyond answering the request. We do not build a profile, we do not link requests to an identity, and there is no account for them to attach to. Our hosting provider processes the traffic and may retain short lived operational logs for reliability and abuse prevention, which is standard provider behaviour rather than something Ponbond adds on top.

Two properties of the proxy are worth knowing. It is read only, and it rejects any method that is not on a fixed allowlist of read calls, so it cannot be used to move funds or to relay a signed transaction. And signing never touches it: your wallet signs locally and broadcasts through its own connection, so a private key never reaches our server under any circumstances.

What your browser stores

One key in localStorage, named ponbond.wallet.rdns. It holds the identifier your chosen wallet publishes about itself, for example the reverse domain name of a browser extension, so that returning to the site reconnects to the same wallet instead of asking you to pick again.

That key does not contain your address, your balances, or anything about what you did. It never leaves your browser, and Ponbond has no way to read it from our side. If a display preference such as a light or dark theme is added later, it would be stored the same way and stay just as local.

To clear it, disconnect in the app, or clear site data for ponbond.app in your browser settings. A browser in a hardened privacy mode may block storage entirely; the app handles that and simply asks which wallet to use on each visit.

Who else your browser talks to

Ponbond has few third party dependencies, but it is not zero, and pretending otherwise would defeat the purpose of this page.

• Google Fonts. The page loads the Inter typeface from fonts.googleapis.com and fonts.gstatic.com, so Google's servers receive a request from your browser, including your IP address and user agent. This is the only third party asset on the page. If you block it, the site still works and falls back to your system typeface.
• Your wallet. Your wallet extension or app is separate software with its own privacy policy, and it may use its own RPC endpoint when it estimates gas, switches networks, or broadcasts a transaction. We do not control what it sends or to whom.
• Block explorer links. Links to the Robinhood Chain explorer are ordinary links. Following one is a normal visit to that site, which sees you the way any website sees a visitor.
• Outbound links. The same is true of any other link we point at, including the ponsfamily launchpad, our profile on X, and the fund fact sheets cited under the historical illustration, which sit on the issuers' own sites. Nothing is requested from any of them until you click.

The chain itself is public

Anything you sign is written to a public ledger. Your address, the amounts, the timing and the counterparties are visible to anyone who looks, permanently, and they can be analysed by people we have no relationship with. We cannot delete an onchain record and neither can you.

That is a property of using a blockchain, not a choice Ponbond made, but it is the single largest privacy consideration in using this app. If unlinkability matters to you, address hygiene is your tool, not a setting we can offer.

Children

Ponbond is not directed at children and we do not knowingly collect anything from anyone, including them.

Your choices

• Browse without connecting. Every page and every public number works with no wallet attached.
• Disconnect at any time, and clear site data to remove the stored wallet identifier.
• Use a fresh address if you would rather not link this activity to your main one.
• Block the font request at the network level if you prefer. Nothing breaks.

Because we hold no personal data about you, a request to access, correct, or delete such data has nothing to act on. If you believe we do hold something, ask and we will look.

Changes and contact

If this notice changes, the date at the top changes with it. Questions can go to Ponbond on X (opens in a new tab).