Privacy Policy
Last updated · November 10, 2026
MCPify is designed to know as little about you as possible: no email, no password, no KYC form, no ad trackers. Your public wallet address is your account — this page lists exactly what we keep and what we never see.
What we store
Your account record: wallet address, account settings (such as whether agent trading is armed), a hash of your personal MCP key if you created one — never the key itself — and the trade-only Hyperliquid agent key you approved, stored encrypted. For each AI app you connect with a sign-in we keep the app’s name, the address its access is sent to, whether it may trade, and when it was connected and last used.
Your audit trail: every order request — from the browser or an agent — with its parameters, outcome and source; position events; TP/SL triggers; security-relevant account events; and a log of every MCP tool call with the client that made it. This is the same history your Portfolio page shows you.
If you use deposit addresses: the addresses issued to you — derived from your wallet address, with no key ever stored — and a record of each deposit (amounts, conversions, network transaction hashes and status), so you can follow it into your account. Transfers to those addresses are public on their blockchains, as all on-chain activity is.
If you sign in with Google: your Google account ID and the verified email address Google shares with us, used to sign you in and to derive your managed account (its key is computed when needed and never stored), plus your two-factor settings if you turn them on.
What we never have
Your private key and seed phrase stay in your wallet and are never transmitted to us. We never hold your trading balance — a transfer to a deposit address is held only while it is forwarded to you — and we collect no name, email address, phone number or identity documents. Your on-chain activity is public by the nature of blockchains — that is true with or without MCPify. Google sign-in changes two of these: MCPify then holds the key to the managed account it creates for you, and keeps the email address Google shares.
Operational logs
Like nearly every web service, our servers and edge infrastructure keep short-lived technical logs — IP address, user agent, request timing — used for security, rate limiting and abuse prevention. Web-server logs mask request URLs specifically so connector keys can never land in them.
Browser storage
The app uses your browser’s localStorage for session tokens and interface preferences (selected wallet type, leverage per market, chart layout). It stays on your device; clearing site data removes it. There are no advertising cookies. With your consent — asked once, and off by default in the EU, the UK and Switzerland — Google Analytics counts page views (the page, approximate location, device and browser) with its own cookies; its advertising features are off and nothing tied to your wallet or account is sent to it. Change your choice any time with “Analytics preferences” in the footer.
Third parties
Your browser talks to Hyperliquid directly for market data, deposits and withdrawals, so Hyperliquid sees your IP address and on-chain activity under its own privacy practices. The site is delivered through Cloudflare and loads fonts from Google Fonts; as infrastructure providers they process standard request metadata. We embed no social widgets and no ad networks.
Sharing and retention
We do not sell or rent data, and we disclose records only where the law requires it. Order and call records are retained as your account’s audit history. Disconnecting an app, revoking a personal key or revoking the agent key takes effect immediately and ends the corresponding access.
Your controls
You can disconnect apps, revoke a personal key or disarm agent trading on the AI · MCP page, revoke the agent key from the terminal or on Hyperliquid itself, disconnect your wallet at any time, and clear localStorage to remove everything the app kept in your browser. This policy may change; the date above reflects the latest revision.