Wallet data
If you connect, the site may process your public address, selected network, wallet provider state, token ownership, signatures, and transaction hashes.
This Privacy Policy explains what data may be processed when you browse Signalbound, connect a wallet, use holder tools, register an agent, or interact with public blockchain infrastructure.
If you connect, the site may process your public address, selected network, wallet provider state, token ownership, signatures, and transaction hashes.
Hosting and API infrastructure may retain IP address, user agent, timestamp, requested URL, response metadata, and error events for security and reliability.
Agent tools may process token IDs, wallet addresses, signatures, clearance checks, market parameters, and request payloads needed to return holder-gated results.
The browser may store interface choices such as theme mode, selected token IDs, temporary session values, and wallet-library state.
Data may be used to operate the website, display token state, verify ownership, run holder tools, prevent abuse, debug errors, maintain security, measure reliability, and comply with applicable obligations.
Wallets, marketplaces, RPC providers, block explorers, hosting providers, analytics or abuse-prevention services, and API providers may process data under their own privacy policies and terms.
Operational logs are retained only as reasonably needed for reliability, security, debugging, abuse prevention, legal compliance, and service operations. Public blockchain data follows the retention behavior of the network and indexers.
Signalbound does not ask for private keys or seed phrases. You should never share them. Wallet connection does not give the site custody over your assets, but transactions you sign can affect them.
Transactions, ownership records, token metadata, registry entries, public signatures, and tool-related on-chain writes may be visible to explorers, marketplaces, indexers, analytics services, and other third parties. Signalbound cannot erase public blockchain history.
If you want to reduce public association between a wallet and your identity, use a wallet strategy that fits your privacy needs before interacting with public contracts or marketplaces.
You can disconnect your wallet, reject signature requests, clear local browser storage, block cookies where supported, or use a different wallet or browser profile.
For privacy requests, use the official project contact path published by Signalbound. Do not send private keys, seed phrases, or unnecessary sensitive information.
This Privacy Policy may be updated as the site, tools, infrastructure, or legal requirements change. The updated date reflects the latest published version.