Signalbound is wallet-first and public-chain aware.
The site does not need your name, email, or password to browse. Wallet interactions may reveal public wallet addresses, token ownership, signatures, transaction hashes, and chain activity. Blockchain data is public by design.
Wallet data
If you connect a wallet, the site or tool endpoints may process your public wallet address, selected network, token ownership status, signed messages, and transaction hashes. Private keys are never requested by the website and should never be shared.
Operational logs
Hosting providers, API routes, security systems, and infrastructure services may collect standard technical logs such as IP address, user agent, timestamp, requested URL, error state, and response metadata. These logs are used for reliability, abuse prevention, and debugging.
Tool requests
ERC-8257-compatible tools may process token IDs, wallet addresses, signatures, and request parameters required to return a result. Market-related tools may query external marketplace APIs or public chain data.
Some tool calls may record non-sensitive mission activity on-chain when a token ID is supplied and the caller is authorized. On-chain records are public and may be indexed by explorers, marketplaces, and other third parties.
Browser storage
The site may use browser storage for interface state such as selected token IDs, cached viewer preferences, or temporary wallet/session state supplied by wallet libraries. Clearing browser data or disconnecting your wallet may remove local state.
External providers
Signalbound may link to or rely on wallets, OpenSea, Ethereum, RPC providers, block explorers, hosting providers, analytics or abuse-prevention services, and other external infrastructure. Those providers process data under their own policies.
On-chain data cannot be deleted by us.
Transactions, ownership records, contract events, token metadata, and registration records written to public blockchains or public registries may be permanent, public, and independently indexed by third parties. Signalbound cannot erase or control copies of public-chain data.
Retention and contact
Operational logs are retained as needed for security, debugging, compliance, and service reliability. Public blockchain data follows the retention behavior of the underlying network and indexers.
For privacy requests, use the contact method published by the project owner or the official project domain. Do not send private keys or seed phrases.