Hookr reads public Robinhood Chain records such as wallet addresses, launches, swaps, hook configuration, fee credits and claims. That information is already public and can be copied or indexed by anyone. Disconnecting a wallet or deleting Hookr profile metadata cannot remove a blockchain record.
We use wallet addresses to render the product and to prove ownership. We do not ask for seed phrases or private keys. A wallet signature can authenticate a Hookr profile or approve a transaction, but Hookr never signs on your behalf.
Never enter a seed phrase or private key into Hookr.
If you create a Hookr profile, we store the display name, bio, avatar reference and wallet address you choose to publish. Public Hookr profile fields are visible to anyone. Private session and provider identifiers are kept out of the public response.
Linking X confirms control of an X account at that moment. Supabase's X provider requests users.read, tweet.read, users.email andoffline.access. X and Supabase Auth process the OAuth authorization, and Supabase Auth stores the linked identity metadata, which can include an email address. Provider access or refresh tokens can be returned in the browser auth session; Supabase documents that it does not intentionally store those provider tokens in the project database.
Hookr copies the stable X account ID, username, display name and avatar URL into the private Hookr profile record. Hookr's server-mediated public Hookr profile response exposes only the linked username and display name; the stable ID, email, avatar URL, exact link time and OAuth credentials stay private. Hookr does not persist provider tokens in its Hookr profile tables, send them to analytics, or use the permission to post.
Unlinking X removes the linked identity from the Hookr auth account and immediately clears the X fields Hookr exposes. A linked account is provenance, not identity verification, KYC, endorsement or a quality guarantee.
Hookr uses Vercel Web Analytics for aggregate page measurement, Vercel Speed Insights for route-level Core Web Vitals, and a small set of Hookr profile lifecycle events such as edit started, completed or failed. EVM addresses in telemetry URLs are replaced with a generic address marker before an event is sent. We do not attach wallet addresses, balances, signatures, calldata, holdings, Hookr profile-form content or OAuth credentials to those events.
If error monitoring or product analytics is expanded, sensitive wallet and RPC payloads must remain scrubbed and session replay must mask Hookr profile inputs by default. This page will be updated before a material change is enabled.
You can disconnect your wallet at any time. Hookr profile owners can edit public metadata, unlink X, and request deletion of offchain Hookr profile data. Security, abuse-prevention and audit records may be retained for the minimum period needed to protect the service.
Onchain transactions, IPFS content, explorer copies and third-party caches are outside Hookr's ability to erase. Before publishing, assume public content may be permanent.
For a privacy or deletion request, contact the official Hookr account at @hookrfun on X. We may ask you to sign a fresh, domain-bound message to prove control of the relevant wallet before changing its Hookr profile data.