Privacy · PayHole

PayHle

Creators Developers Token Sinkhole Trust

Effective 2026-09-04

Privacy

PayHole has no accounts, no analytics, and no servers that see your keys or your browsing. This page lists exactly what the website and the browser extension store, what they send, and to whom.

The website

payhole.org is a static site. It sets no cookies and loads no analytics or advertising scripts. The web server keeps standard access logs (IP address, requested path, browser user agent, time) for security and debugging; these are rotated automatically and are not shared.

Pages read public data from Robinhood Chain (chain id 4663) directly from your browser through the chain's public RPC endpoint, for example the total burned or the tier prices. The RPC operator can see your IP address, as with any public endpoint.

The Creators page sends the domain and wallet address you enter to the PayHole verifier at payhole.org/api. The verifier performs a DNS lookup of that domain, checks the TXT record, and returns a signed attestation. It stores nothing beyond its access logs.

The extension

Everything the extension knows lives in your browser's extension storage on your device: the encrypted vault with your seed, the keys derived from it, per-site spending policies, the payment ledger, tips, the tracker blocklist, and settings. PayHole never receives any of it. There is no sync, no account, and no telemetry.

The extension sends network requests only to do its job:

To the website you are visiting, when that site answers with an HTTP 402 payment request: a signed USDG transfer authorization for the amount the site asked for, within the cap you set for that site.
To the payment facilitator named by that site in its 402 response, if the site asks the client to submit the authorization there instead of to the site itself.
To the Robinhood Chain public RPC endpoint, to read balances and contract state and to submit the on-chain transactions you approve, such as funding a pocket, topping up a site address, tipping a creator, or unlocking a tier.
To a Sinkhole DNS resolver, only if you configure one yourself: the list of domains you chose to block. Sinkhole is self-hosted software; PayHole runs no resolver for you.

Payments settle on a public blockchain. Addresses, amounts, and transaction times are public by nature. The extension derives a separate address for every site so that one site cannot see what you paid another.

Why the extension asks for each permission

Access to all websites: a 402 can come from any site, so the extension has to be able to see responses and answer them anywhere. It reads only responses with status 402 and the headers those responses carry.
webRequest and webNavigation: to notice 402 responses and page loads so the site card can show what a page cost.
declarativeNetRequest: to block tracker and drainer domains from your blocklist before the browser connects to them.
tabs: to know which site is in the active tab so the popup shows the right pocket and address.
storage: to keep the vault, ledger, and settings on your device.
alarms: to refresh balances and the blocklist on a schedule while the extension is idle.

Deleting your data

Remove the extension, or use Reset in the extension dashboard, and everything it stored is deleted from your browser. Your funds stay on chain under the keys derived from your seed; keep the seed if you want to reach them again.

The website keeps no data about you to delete. Access logs expire on their own rotation.

Changes and contact

If this page changes, the effective date above changes with it. Questions go to the PayHole account on X, x.com/payhole_x402.

Robinhood Chain, chain id 4663, settlement in USDG onlyPrivacy x.com/payhole_x402payhole.org