Privacy Policy — pBank Simulator (PulseChain tx preview)

Last updated: 6 July 2026

pBank Simulator is a browser extension (Manifest V3) for Chromium browsers (Chrome, Edge, Brave). This policy explains exactly what data the extension processes, what it sends off your device, and what it never touches. It is written to reflect the extension's actual, audited behavior.

What the extension does

Before you sign a transaction on the PulseChain network in any wallet (MetaMask, Rabby, etc.), the extension shows a pre-flight preview of what that transaction would do — balance changes, token approvals (unlimited approvals are flagged), emitted events and storage changes, the revert reason if it would fail, and gas. You can then Reject or Proceed. That is its single purpose.

What data is processed and sent off your device

The only data the extension sends off your device happens in one specific situation: when you are on the PulseChain network (chainId 0x171) and a website (dapp) asks your wallet to send a transaction (eth_sendTransaction).

In that case, the extension's background service worker sends a single POST request to https://pbank.info/api/explorer/simulate. The request body is a JSON object containing exactly these fields:

• from — your wallet address
• to — the destination address of the transaction
• data — the transaction calldata
• value — the amount being sent

The response is the simulation result, which is used to render the preview.

On any other network, nothing is sent. If you are not on PulseChain, no request is made to pbank.info.

To do its job the extension also reads two values from your wallet using the wallet's standard EIP-1193 request() method only:

• eth_chainId — to check which network you are on
• eth_accounts — to fill in from if the dapp did not supply it

These reads stay on your device except where the resulting from address is included in the simulation request described above.

What is stored locally (never transmitted)

• chrome.storage.local holds the last simulation summary shown in the toolbar popup (host, destination, revert status, and change counts) and the list of sites you have enabled. This data stays on your device.
• chrome.storage.sync holds your settings (the on/off toggle and the API base URL). Your browser syncs this across your own devices when you are signed in to the browser; it is not sent to us.

What the extension NEVER accesses

• Private keys and seed phrases. These are never exposed by the EIP-1193 API — your wallet keeps them sealed — and the extension never attempts to reach them.
• Signatures. The extension never signs anything and never sees your signatures. It does not intercept signing methods (eth_sign, personal_sign, signTypedData); it only reacts to eth_sendTransaction. On "Proceed", it forwards your original, unmodified request to the real wallet, which does all signing internally.
• Your browsing history. The extension does not run on any website by default and does not collect a record of the sites you visit.

Third parties

The only third-party destination for any data is the simulation endpoint at https://pbank.info/api/explorer/simulate, operated by the pBank operator, and only for the PulseChain transaction sends described above. The transaction details (from, to, data, value) are sent to pbank.info solely to compute the simulation and return the preview result.

pbank.info data retention: The simulation endpoint processes the transaction fields you send (from, to, data, value) in memory only, to compute the preview, and returns the result. pBank does not store these details in any database and does not log them. (Only non-personal token metadata — token symbols, names, and decimals — is cached; this contains none of your data.) As with any web service, the hosting provider (Vercel) may retain standard, short-lived request logs as part of normal infrastructure operation, after which they are discarded; pBank does not use these to build any profile of you.

Analytics and tracking

The extension contains no analytics, no telemetry, no tracking, no cookies, no eval, and no remotely-hosted code. This was verified by audit.

Your controls

• Per-site enable. The extension does not run on any website until you explicitly enable it for that site from the toolbar popup ("Enable on this site"). It then runs only on the sites you chose.
• On/off toggle. You can turn the extension off in its settings at any time.
• Uninstall. Removing the extension deletes its local data. Settings held in chrome.storage.sync are managed by your browser's sync.

Contact

Questions about this policy: tehironclad@gmail.com