Skip to content

Legal

Privacy policy

What QHooks stores, who processes it, and how to delete it. QHooks runs qhooks.com. Questions go to team@qhooks.com.

Last updated 16 Nov 2026

Your keys and your funds

QHooks never holds your keys or funds. Trades and launches are signed in your own wallet.

Email, Google and X sign-in and embedded wallets are provided by Privy, which holds those wallet keys under its own terms.

What we store

Only when you use these features:

  • public profile fields you choose: name, bio, picture, links and handle;
  • accounts you link and verify (X, Discord, Farcaster), which you can hide or unlink;
  • your follows, calls, posts and thanks;
  • token profiles creators publish: icon, banner and links;
  • your wallet address or addresses;
  • trade-sharing settings, if you opt in;
  • web push subscriptions, if you turn alerts on;
  • your Telegram user id, if you link @qhooks_bot.

What is public

Wallet addresses and on-chain activity are public on the blockchain. Profiles, calls and posts are public.

Who processes requests

These service providers handle requests for us:

  • Cloudflare, for hosting. Request logs are sampled.
  • Privy, for sign-in.
  • Blockchain RPC providers, including Alchemy and public RPCs, for balances and transactions.
  • DexScreener, for market data.
  • 0x, Jupiter, Meteora and Hyperliquid, for the quotes and trades you request.
  • Telegram, if you use the bot.
  • Your browser’s push service, if you turn alerts on.

MCP and API requests

QHooks processes the tool name and the inputs needed for the request, such as a chain, public token or wallet address, amount, counterparty or agreement terms. Public market and wallet reads need no QHooks API key. This endpoint needs only the selected tool’s inputs; do not include unrelated conversation content. Do not send keys, recovery phrases, passwords or authentication tokens in tool inputs, feedback or support.

Read and preparation tools return public information, an unsigned plan, link or wallet-signing message. Preparation does not sign, send a transaction, publish a post or enter a competition. If you separately sign and submit a profile, post or competition message, its public content, wallet address and verification signature are stored for that feature. On-chain records are public and cannot be erased by QHooks.

We measure requests and prepared results as daily aggregates by tool/route, a normalized client name and user-agent family. Raw user-agent strings, tool arguments, wallet addresses and IP addresses are not stored in those aggregate rows. Approximate distinct-client counts use a daily-derived hash of a client-held MCP session or an optional random client ID. They are estimates of client-days, not people. Referral-source counts use bounded campaign labels and a daily sketch. Client names are self-reported.

To limit abuse, the service processes the connecting IP and derives a visitor identifier that changes by UTC day. Rate-limit records use that identifier rather than a raw IP. This is a pseudonymous identifier, not a claim that a hash makes someone anonymous. Hosting providers can process request metadata and sampled operational logs under their own terms.

send_feedback runs only when you explicitly ask to send feedback. It stores the text you supply (up to 2,000 characters), optional tool/client labels, a category, timestamp, status and the daily visitor identifier. The team uses it to investigate your report; it is not a public feed or an instruction to act automatically. Keep secrets and unrelated personal information out of it.

Requests are processed by Cloudflare hosting/database services. Public wallet/token inputs needed for a read or simulation may be sent to configured public RPCs, Alchemy and the market/venue providers named elsewhere in this policy. Your chosen AI client separately handles your conversation under its own policy. QHooks does not promise control over third-party or blockchain retention.

Retention schedule

RecordRetention
MCP usage aggregatesToday plus the previous 8 UTC dates; delete expired rows within 24 hours
Campaign/source aggregatesToday plus the previous 7 UTC dates; delete expired rows within 24 hours
Client-held MCP session24-hour validity
Abuse-limit counters48-hour expiry; remove within the following 24 hours
Feedback text and labels90 days after submission
Feedback visitor identifierRemove after 48 hours
Cloudflare sampled operational logs7 days, or a shorter available retention
Controlled backups/exportsDelete or age out within 30 days after source deletion
Wallet-verified public profile/post/competition recordsUntil deletion/withdrawal is requested; begin handling within 30 days

Controls and contact

For a data-access, correction or deletion request, contact team@qhooks.com with enough public context to identify the record. Do not email a key or recovery phrase. Response target: acknowledge and begin handling within 30 days.

No selling, no advertising trackers

We don’t sell personal data. We do not use advertising trackers. We measure aggregate API usage as described above.

Deleting your data

To delete your profile data, email team@qhooks.com. On-chain data can’t be deleted.

Age

QHooks is not for people under 18.

Contact

QHooks, team@qhooks.com. See also the terms of use.

Your wallet

No wallet extension needed. Your QWallet quantum key stays separate.

Connect your phone with a QR code.

Uses MetaMask Connect, copyright ConsenSys. License

Choose an EVM wallet.

No wallet detected in this browser.

Open qhooks.com in Chrome with your wallet extension enabled, or in your wallet app’s built-in browser.

The in-app preview cannot access Chrome’s wallet extensions. Use MetaMask Mobile above to pair your phone.

Connecting does not authorize spending. Every signature and transaction needs your approval. Never enter your recovery phrase here.