Your wallet is public. Your telemetry should not be.

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.

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. Hookr's first-party X authorization requests only users.read and tweet.read, reads the authorized account, and then asks X to revoke the temporary access token. Hookr does not request permission to post or request a refresh token.

Hookr keeps the stable X account ID private and publishes only the linked username and display name. OAuth credentials, wallet-auth session data and stable provider IDs are not included in public profile or token-presentation responses and are not sent to analytics.

A token creator may separately associate an X account with one token. They can reuse the account on their Hookr profile or authorize a different project account. This token-scoped choice does not replace the profile account. Unlinking a profile account does not erase a token association or its revision history; each public association states only that control was verified when it was linked.

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.

Creators may publish an optional website, GitHub URL, token-specific X account and Hookr display image. These fields are public creator content. Hookr stores the authenticated user and wallet needed to authorize changes, while public responses omit private auth identifiers and the stable X provider ID.

A creator-updated Hookr display image does not change the token's constructor-set onchain image. Hookr keeps immutable image objects and a revision history so the original launch image and later presentation changes remain distinguishable. Hookr may hide an unsafe display override without altering the token contract or its public chain record.

Hookr uses Vercel Web Analytics for aggregate page measurement, Vercel Speed Insights for route-level Core Web Vitals, and a small allowlisted set of profile lifecycle events such as 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.

Live pool and token-market pages lazy-load an embedded CoinGecko GeckoTerminal chart for the exact Robinhood Chain pool shown. When that chart loads, the browser connects directly to GeckoTerminal, which may receive ordinary request information such as the IP address, browser and device details, and may apply its own storage or cookie policy. Hookr suppresses the referring page URL and does not send the connected wallet, Hookr profile content, OAuth credentials, signatures or launch-form data to the embed. The separate external-chart link leaves Hookr and opens GeckoTerminal directly.

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.

If you submit a launchpad request, hook idea, or partner technical brief, Hookr stores the name, email, project or idea title, selected technical track when applicable, optional website and details, originating Hookr page, and keyed abuse-prevention digests in a private operator-only intake table. We use that information only to route and review the proposal, prevent repeated abuse, and reply about a possible fit. Rows are retained until a Hookr operator deliberately deletes them. Use the contact route below to request deletion; its current availability is stated there. Do not submit credentials, private keys, signatures, or confidential launch material.

Onchain transactions, IPFS content, retained token-presentation revisions, explorer copies and third-party caches are outside Hookr's ability to erase completely. 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.