How Robin processes wallet, blockchain, authentication, metadata and interface data.
This Privacy Policy describes how the Robin interface processes information when users connect wallets, authenticate private Portfolio views, create Tokens, trade and use Robin's website and supporting services.
Blockchain activity is public by nature. Public wallet addresses, contract events and confirmed transactions may be visible to anyone through blockchain infrastructure, indexers and explorers.
Robin is non-custodial. Robin does not require or request your wallet seed phrase or private key.
Connecting a wallet allows the interface to read the active public address and public blockchain state. Transaction requests are presented to your wallet, and the wallet decides whether to sign and submit them.
Certain wallet-specific Portfolio data uses a signed-message authentication flow. Robin issues a time-limited challenge containing information such as the wallet address, origin and nonce. The connected wallet signs that message, and Robin verifies the signature.
A signed authentication message is not a blockchain transaction and does not transfer Tokens or ETH. Successful authentication creates a time-limited wallet session backed by server-side Redis state and a session cookie.
Challenge and session records include expiration controls. Logging out removes the server-side session registry entry used to authorize the private session.
Transactions submitted to Robinhood Chain become public blockchain records. Robin cannot erase a confirmed public blockchain transaction by removing information from the website.
Robin indexers and databases process public onchain information to provide market prices, trading history, Token information, wallet Holdings, Created Tokens, Activity, fee views and protocol statistics.
Indexed copies may be rebuilt from public blockchain history and are used to operate Robin's interface; the blockchain remains authoritative for onchain state.
Creators may upload a custom Token image through Robin. Supported images are authorized for upload through Robin's server and sent to Pinata/IPFS infrastructure. Robin's Pinata credential remains server-side and is not provided to the browser.
Token metadata and content-addressed files intentionally published for a Token may be publicly accessible and may continue to be available through IPFS gateways or other systems independently of Robin's website.
Robin uses browser-side state for interface and wallet-session behavior. A private wallet-authentication session may also use a cookie so the server can associate requests with an authenticated wallet session.
Browser storage or cookies used for Robin functionality are separate from the public blockchain records created when you submit onchain transactions.
Robin may send requests to infrastructure required to operate the service, including blockchain RPC providers, hosting infrastructure and Pinata/IPFS services. Those providers may process network or request information under their own policies.
Robin's private wallet-authentication service uses Redis for time-limited challenge and session state, while Robin's application and archive databases store indexed blockchain-derived data needed by the interface.
Robin may disclose or transmit information to infrastructure providers when necessary to operate the service, such as blockchain RPC, hosting and IPFS providers.
Robin may also disclose information where required by applicable law, valid legal process or to protect the security and integrity of Robin and its users.
Robin does not receive your wallet seed phrase or private key through its normal wallet connection or authentication flows.
Wallet-authentication challenge and session records are time-limited by the authentication service. Other operational records may be retained as reasonably necessary for service operation, security and legal requirements.
Public blockchain records and content intentionally published to content-addressed networks may remain available independently of Robin and therefore cannot necessarily be deleted by Robin.
Robin uses technical controls intended to protect non-public service data, including signed-message verification, time-limited authentication state and server-side credentials. No internet service or blockchain application can guarantee absolute security.
Users remain responsible for securing their devices, wallets, private keys and transaction approvals.
This Privacy Policy may be updated as Robin's functionality, infrastructure or legal requirements change. The 'Last updated' date identifies the version currently presented through the interface.
Material changes should be reflected in the interface or other appropriate Robin communication channels.