Privacy Policy — pBank

Last updated: 3 August 2026

pBank is a portfolio tracker and block explorer for the PulseChain and Ethereum networks, available as a website at pbank.info and as a mobile app. This policy covers both. The pBank Simulator browser extension is a separate product with its own policy at /extension/privacy.

It is written from the actual behaviour of the software rather than from a template.

The short version

pBank has no accounts, no passwords and no sign-up. You use it by entering a wallet address — which is public information on a public blockchain. pBank cannot move your funds, cannot sign anything, and never has access to your private keys or seed phrase.

What pBank never has

What you enter, and where it goes

Wallet addresses. The addresses you track are stored on your own device, in browser local storage (or the app's local storage), along with any nicknames and groups you give them. They are sent to pBank's servers only as part of ordinary requests to look up their public on-chain data — balances, transactions, LP positions — because that lookup cannot happen without the address.

Portfolio value history. When a wallet is loaded, pBank records a row containing the address, a timestamp and the wallet's total value in USD. This is what draws the portfolio history chart, and it means the chart is already populated the next time that address is viewed — by you or by anyone. Wallet addresses and their balances are public blockchain data that anyone can compute from a public node; pBank stores its own copy so the chart does not require re-scanning the chain on every view. No name, email, device identifier or IP address is attached to these rows.

Cached chain data. Public on-chain data (transactions, transfers, token metadata) is cached against the address it belongs to so the app is fast and so we make fewer calls to public infrastructure. It is the same data any block explorer shows.

The mobile app specifically

Push notifications (optional). If you turn on wallet alerts, the app asks iOS or Android for a push token and sends that token to pBank along with the list of wallet addresses you want alerts for. Both are stored so the alert can be delivered when one of those wallets moves. The token identifies a device installation to Apple's or Google's push service; it is not a name, an advertising identifier, or anything that follows you between apps. Turning notifications off removes the token.

Camera (optional). The QR scanner uses the camera to read a wallet address from a QR code. The camera is opened only when you tap the scan button, frames are processed on the device, and no image or video is stored, uploaded or transmitted — the only output is the address text, which is then handled exactly like an address you typed.

Haptics, splash screen, status bar. Local device features; no data involved.

There is no advertising SDK, no tracking framework and no cross-app tracking in the app. pBank does not participate in the App Tracking Transparency prompt because it does not track you across apps or websites. The one analytics service in use is described below, and it does not track you either.

Optional features you have to opt into

Analytics

There are two counters, and neither uses a cookie.

pBank's own page counter. One row is written per visit containing only the page path and a timestamp — for example /screener. Paths that contain an address or a symbol are collapsed to a placeholder (/profile/[slug]) before the row is written, and query strings are removed both on the device and again on the server. No IP address, no device identifier, no user agent, no wallet address and no cookie is stored with it. It is not possible to reconstruct an individual's browsing from this data.

Vercel Web Analytics. pBank's host, Vercel, provides a cookieless analytics script that runs on every page, including inside the mobile app. It records the page path, the referring site, and — derived from the network request rather than from your device — your country, browser, operating system and device type. To count returning visitors within a single day it uses a one-way hash of your IP address and browser details combined with a salt that is discarded and replaced every 24 hours; the hash cannot be reversed, is not stored on your device, and cannot connect your visits across days or to any other site. Vercel's privacy documentation covers this service in full.

Neither counter is used for advertising, neither builds a profile of you, and no data from either is sold or shared with advertisers.

pBank sets no cookies and uses no advertising or cross-site tracking services.

IP addresses

Your IP address is visible to pBank's servers, as it is to any website you visit. It is used in memory to rate-limit abusive request volumes and is not written to any database. As with any web service, the hosting provider (Vercel) keeps standard short-lived infrastructure logs, which are discarded on their own schedule and are not used to build any profile of you.

Third parties

pBank reads public blockchain data through public infrastructure, and your requests reach those providers as ordinary API calls: PulseChain and Ethereum RPC nodes, Blockscout explorers, and market-data providers (DexScreener, GeckoTerminal, CoinGecko) for prices. Wallet addresses form part of these requests where the request is about that address. These providers have their own policies and are not controlled by pBank.

Data pBank stores itself is held in Supabase (Postgres) and served through Vercel, which also provides the analytics described above.

pBank does not sell your data, does not share it with advertisers, and does not use it for advertising.

Retention and deletion

Children

pBank is not directed at children and is not intended for use by anyone under 17.

Changes

Material changes to this policy will be reflected in the "last updated" date above. The app has no account system, so there is no mailing list to notify — check this page.

Contact

Questions, or a deletion request: tehironclad@gmail.com

← pbank.info