Privacy Policy

Last updated: September 24, 2026

Summary: HyperPerps AI is designed with privacy in mind. We do not collect names, phone numbers, government IDs, or your main-wallet private key. Hosted bots store their configuration, activity, and an encrypted copy of the trade-only agent key in a wallet-scoped Cloudflare Durable Object so they can keep running while your browser is closed. We also collect aggregated funnel analytics (Google Analytics 4) with limited event parameters.

1. Introduction

This Privacy Policy describes how HyperPerps AI ("we," "us," "our," or "the Operator") collects, uses, stores, and protects information when you use the HyperPerps AI trading application and marketing site (the "Service"). This policy applies to all users of the Service, including the landing site at hyperperps.app and the trading app at trade.hyperperps.app.

By using the Service, you agree to the collection and use of information as described in this policy. This Privacy Policy is incorporated into and subject to our Terms of Service.

2. Data We Collect

2.1. Browser and Hosted-Runtime Data

The application uses browser storage for session continuity. Data needed for 24/7 hosted execution is also sent to the wallet-scoped bot runtime as explicitly noted:

Data	Storage	Purpose
Wallet address	localStorage	Identify your session and connect to Hyperliquid
Agent-wallet key	IndexedDB; encrypted copy in Durable Object SQLite	Authorize the hosted strategy runtime to place and cancel Hyperliquid orders
Strategy preferences	IndexedDB / localStorage	Restore your local workspace and forms
Bot configuration	localStorage; Durable Object SQLite after deployment	Persist the reviewed rules and run deployed bots while the browser is closed

You can delete all locally stored data by clearing your browser's site data for the HyperPerps AI domains.

2.2. Data Collected by Our Cloudflare Worker Backend

When the Service communicates with our backend, we collect the following:

Data	Storage	Purpose
Bot activity and trading event logs (ticks, rule outcomes, order events)	Cloudflare D1 / Durable Object SQLite	Activity timeline, reliability analysis, and audit history
Deployed bot configurations and state	Durable Object SQLite	Run and recover deterministic strategies 24/7
Encrypted agent-wallet key	Durable Object SQLite	Sign orders for the hosted strategy runtime; the key cannot withdraw funds
Wallet address (as account identifier)	Cloudflare D1	Associate events with your account, leaderboard
Referral associations	Cloudflare D1	Track referral relationships for fee sharing
Gas-sponsorship record (grant time, confirmation time, bridge transaction hash, amount)	Durable Object SQLite	Limit how often a wallet can use sponsored gas for the deposit bridge
Request metadata (rate limiting)	Cloudflare KV (ephemeral)	Prevent abuse and enforce rate limits

2.3. Analytics Events (Google Analytics 4)

We use Google Analytics 4 (GA4) for funnel analysis — measuring how visitors move from the landing site through wallet connection, funding, bridging, and bot deployment. GA4 is delivered via Cloudflare's edge tag service (a server-side proxy that batches events). We tag specific user actions and emit them as events to the dataLayer; downstream tools (GA4, Cloudflare Zaraz) receive them.

The events we fire are listed below. Each event carries only the parameters listed — no other data is attached.

Event	Parameters	Where it fires
`section_view`	section name (e.g. "hero", "pricing")	Landing site, on scroll
`cta_click`	cta_location, cta_label	Landing site CTAs
`nav_click`	target, link_location	Landing site nav anchors
`faq_open`	faq_question (verbatim text)	Landing site FAQ accordion
`hl_referral_click`	link_location	Hyperliquid affiliate links
`social_click`	platform, link_location	Twitter, Discord links
`legal_click`	doc, link_location	Terms / Privacy links
`welcome_modal_shown`	—	App, on first paint pre-connect
`welcome_get_started_click`	—	App, Privy login attempted
`welcome_advanced_*`	connector_name (for connect events)	App, external-wallet path
`welcome_browse_click`	—	App, dismiss without connecting
`wallet_connected`	provider, wallet_short ("0x1234…abcd")	App, after auth completes
`onboarding_step`	from, to (state-machine label)	App, on each onboarding transition
`onboarding_funding_provider`	provider ("card" / "manual")	App, funding picker
`onboarding_bridge_*`	amount_usdc (rounded integer), error_class	App, bridge tx attempt
`onboarding_complete`	from (previous step label)	App, end of onboarding
`bot_start_click`	preset, has_custom_prompt, risk_pct, leverage	App, Start Bot button
`bot_start_*`	error_class (on failure only)	App, after start attempt

What event parameters do NOT contain:

Your full wallet address — we send only a privacy-safe stub (e.g. 0x1234…abcd). The same wallet always produces the same stub, so cohort analysis works, but the stub alone cannot be reversed back to a full address.
Your agent-wallet private key — never included in analytics events or sent to an AI provider. Hosted execution stores only an encrypted server-side copy.
Raw error messages — only a short error class (e.g. UserRejectedRequestError). We strip free-form error text because it can contain transaction hashes, RPC endpoints, or other identifiers we don't want in analytics.
Dollar amounts in your account — only rounded USDC integers at funnel steps where amount is relevant for cohort analysis.
Trade-by-trade P&L, position sizes, signed messages, or any market data you've evaluated.

GA4 sets first-party cookies (_ga, _ga_<property_id>) on your browser to maintain a session identifier. These cookies persist for up to 2 years per Google's defaults. You can opt out — see Section 4.4.

2.4. Data Processed During Requests

The following data may be processed during requests:

AI provider keys: The Service no longer accepts your own AI API keys. The AI advisor runs on keys we provide. If you entered an AI API key in an earlier version of the Service, it was stored encrypted in your wallet's Durable Object and is no longer used; you can ask us to delete it (Section 11.2).
AI advisor messages: Strategy configurations, bot activity, and compact market/liquidity context may be sent to the configured AI provider. Conversation messages may be persisted in the wallet-scoped Durable Object so multi-turn chat works. They are not execution instructions and do not contain agent-wallet keys.
Signed transaction payloads: EIP-191 wallet signatures used for authentication and the bridge ERC-20 transfer signatures are forwarded to Hyperliquid / Arbitrum and not retained beyond the request.

3. What We Do NOT Collect

We explicitly do not collect, store, or process:

Your name, email address, phone number, or physical address (Privy may collect these if you sign in via email — see Section 5.5)
Government-issued identification documents
Your main wallet private key or seed phrase
Your agent-wallet private key in plaintext on our servers — our server copy is always encrypted (see Section 10.3)
IP addresses (we do not log IP addresses in our application layer; see Section 8 regarding Cloudflare infrastructure)
Browser fingerprints or cross-site tracking identifiers
Browsing history outside of HyperPerps AI
Your full wallet address in analytics events (only the privacy-safe stub described in Section 2.3)

4. Cookies and Tracking

4.1. The Service uses the following cookies and storage mechanisms:

Cookie / Storage	Purpose	Set by	Expiry
`_ga`, `_ga_<id>`	GA4 session + visitor identifier (analytics)	Google Analytics 4 (via Cloudflare edge tag)	2 years
`__cf_bm`	Bot management (essential security)	Cloudflare	30 minutes
`localStorage` / `IndexedDB`	Wallet address, local agent-key copy, strategy preferences (see Section 2.1)	HyperPerps AI	Until cleared
Privy authentication tokens	Maintain your authenticated session if you sign in with email/passkey	Privy	Per Privy session policy

4.2. Analytics framing: We use Google Analytics 4 to understand how visitors move through the funnel — what CTAs convert, where users drop off in onboarding, which strategies get deployed. The events we fire are listed exhaustively in Section 2.3. We do not share GA4 data with advertisers or third parties beyond Google Analytics itself.

4.3. No advertising trackers: We do not embed Facebook Pixel, TikTok Pixel, LinkedIn Insight Tag, or any advertising network's tracker. We do not engage in retargeting.

4.4. Opt out of analytics: You can prevent GA4 from collecting your data by:

Installing the Google Analytics Opt-out Browser Add-on
Using a privacy-focused browser (Brave, Firefox with Strict tracking protection) that blocks GA4 by default
Enabling "Do Not Track" — we honor DNT signals where technically feasible
Using browser-level cookie blocking for the googletagmanager.com and google-analytics.com domains

Opting out does not affect your ability to use the Service. None of our trading or onboarding functionality depends on analytics events firing.

5. AI Model Data Handling

5.1. When you use the AI strategy advisor, your message, a bot configuration you ask it to review, relevant bot activity, and compact market/liquidity context may be included in the prompt sent to the AI model provider. The advisor cannot deploy a bot or place an order.

5.2. AI prompts do not include your main-wallet or agent-wallet private keys. The advisor tool projection is limited to strategy, status, activity, account-relative validation values, and non-identifying market context. Your wallet address is not intentionally included in prompts.

5.3. Models: The default model is Kimi K2.6, run on Cloudflare Workers AI. Some accounts may use models from OpenAI, Anthropic or Google, sent through our Cloudflare AI Gateway using our own keys.

5.4. No trading AI: AI does not make or place trades. Deployed bots follow fixed rules you review before deploying.

5.5. Privy authentication: If you sign in with email, passkey, Apple, or Google via Privy, Privy may collect identifiers (email address, OAuth profile data) as part of providing authentication. Privy's privacy practices are governed by Privy's Privacy Policy, which we encourage you to review. We do not receive your email or OAuth profile from Privy — we only receive the wallet address Privy provisions for you.

5.6. We recommend reviewing the privacy policies of the respective AI providers:

6. How We Use Your Data

We use the data we collect for the following purposes:

Service operation: Executing trades, displaying your event timeline, providing core functionality
Product improvement: Bot activity and outcome data may be used to analyze strategy behavior and improve platform reliability; AI does not make live trade decisions
Funnel analytics: The GA4 events listed in Section 2.3 help us understand where users drop off (e.g. funding step, bridge step) so we can fix friction points
Leaderboard: Aggregated performance data associated with wallet addresses may be displayed on public leaderboards (you can opt out by requesting data deletion)
Abuse prevention: Rate limiting and request monitoring to prevent abuse of the Service. Gas-sponsorship limits stop abuse of sponsored deposit transactions.
Debugging and reliability: Event logs help diagnose issues and improve Service reliability

We do not sell, rent, share, or transfer your data to third parties for advertising, marketing, or any purpose unrelated to the operation of the Service. The Google Analytics relationship is a data-processor relationship — Google processes events on our behalf, governed by Google's Data Processing Terms.

7. Builder Fees and On-chain Activity

7.1. When the Service places a trade on Hyperliquid on your behalf, a 0.02% builder fee is routed to our builder address (0x79ce08822E57aa76EfBc2E3Ae813C055A9D1bdC1) by Hyperliquid's protocol. This is on-chain activity — your wallet address and trade size are publicly visible on the Hyperliquid blockchain by design. We do not control on-chain disclosure.

7.2. Hyperliquid maker/taker fees apply on top of the builder fee, the same as if you were trading manually. These are paid to Hyperliquid, not to us.

8. Cloudflare Infrastructure

8.1. The Service is hosted on Cloudflare's global network. Cloudflare provides CDN, DDoS protection, DNS, Workers runtime, Durable Objects (per-user state), and D1 (shared SQL).

8.2. Cloudflare may collect limited infrastructure-level data (e.g., IP addresses for security and performance purposes) as part of their standard service operation. This data is governed by Cloudflare's Privacy Policy, not ours.

8.3. Cloudflare's edge tag service is the proxy through which Google Analytics 4 events are routed. Events still go to Google's servers — Cloudflare's role is delivery and batching, not data processing of analytics events on our behalf.

9. Data Retention

9.1. Browser-stored data: Persists until you clear your browser's site data or uninstall the application. We have no control over or access to data stored solely in your browser.

9.2. Server-stored bot and event data: Deployed configurations, bot state, advisor messages, and trading event data are retained to operate the Service and maintain audit history, unless deleted under the controls and requests described below.

9.3. GA4 analytics events: Retained per the data retention setting on our GA4 property (default: 14 months). Aggregated reports may be retained longer.

9.4. Rate limiting data: Stored in Cloudflare KV with short TTLs (typically minutes to hours) and automatically expires.

9.5. Referral data: Retained as long as the referral relationship is active.

9.6. Gas-sponsorship record: Retained with your wallet's other server-side data, so sponsorship limits keep working. You can request deletion (Section 11.2).

10. Data Security

10.1. All communications between your browser and our backend are encrypted via TLS (HTTPS).

10.2. Server-side data is stored in Cloudflare's infrastructure, which provides encryption at rest and in transit, along with enterprise-grade physical and network security.

10.3. Your main wallet key never leaves your wallet; we never see it. Your trade-only agent key is kept in your browser's IndexedDB, and a copy is kept on our servers so bots can trade while your browser is closed. That copy is encrypted with AES-256-GCM using HKDF-SHA256-derived keys with random per-blob salt and fresh IV, inside a Cloudflare Durable Object. The encryption key is a server-side secret that never leaves the Cloudflare runtime.

10.4. Despite our security measures, no system is perfectly secure. You are responsible for securing your own devices and browser environment.

11. Your Rights

11.1. Right to Access

You have the right to request a copy of the data we hold that is associated with your wallet address. Contact us to make an access request.

11.2. Right to Deletion

You have the right to request deletion of all server-stored data associated with your wallet address, including event logs, leaderboard entries, and referral associations. Browser-stored data can be deleted by you directly by clearing site data. GA4 analytics events can be deleted via Google's user-deletion request flow — see Google Analytics: Delete data.

11.3. Right to Rectification

If any data we hold about you is inaccurate, you have the right to request correction.

11.4. Right to Data Portability

You have the right to request your data in a structured, machine-readable format (e.g., JSON).

11.5. Right to Object

You have the right to object to the processing of your data for AI training purposes or analytics. Upon objection, we will cease using your data for that purpose, though we may retain it for core Service functionality. To opt out of analytics, see Section 4.4.

11.6. Exercising Your Rights

To exercise any of the above rights, contact us through the channels listed on the HyperPerps AI website or repository. We will respond to requests within 30 days. We may verify your identity by requesting a signed message from your wallet address.

12. GDPR Compliance (European Economic Area Users)

12.1. If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, the following applies:

Legal basis for processing: We process your data based on (a) your consent (by choosing to use the Service), (b) legitimate interest (improving the Service and preventing abuse), and (c) contractual necessity (providing the Service you requested).
Analytics consent: If you are subject to the EU ePrivacy Directive, you may be presented with a cookie consent prompt. Declining will prevent GA4 from setting analytics cookies; the Service still functions normally without analytics.
Data transfers: Your data may be processed outside the EEA on Cloudflare's global network and on Google's analytics infrastructure. Both providers maintain appropriate safeguards for international data transfers, including Standard Contractual Clauses.
Supervisory authority: You have the right to lodge a complaint with your local data protection supervisory authority.

12.2. All rights described in Section 11 are available to EEA, UK, and Swiss users in accordance with the General Data Protection Regulation (GDPR) and equivalent local laws.

13. CCPA Compliance (California Users)

13.1. If you are a California resident, the California Consumer Privacy Act (CCPA) provides you with additional rights:

Right to know: You may request disclosure of the categories and specific pieces of personal information we have collected about you (see Section 2).
Right to delete: You may request deletion of your personal information (see Section 11.2).
Right to opt out of "sharing": Under CCPA's expanded definition of "sharing," routing analytics events to Google Analytics may be considered cross-context behavioral advertising "sharing." You can opt out — see Section 4.4. We do not sell personal information for monetary or other valuable consideration.
Non-discrimination: We will not discriminate against you for exercising your CCPA rights.

13.2. For purposes of the CCPA, your wallet address (and the privacy-safe stub used in analytics events) are the primary "personal information" we associate with your use of the Service.

14. Children's Privacy

The Service is not directed to individuals under the age of 18 (or the age of majority in their jurisdiction). We do not knowingly collect data from minors. If we become aware that a minor has used the Service, we will take steps to delete associated data.

15. Third-Party Links and Services

The Service may contain links to or integrations with third-party services:

Hyperliquid: Trading venue. Trades you place are visible on the Hyperliquid blockchain.
Privy: Wallet provisioning and authentication.
Google Analytics 4: Funnel analytics (see Section 2.3).
AI providers (Cloudflare Workers AI, OpenAI, Anthropic, Google): LLM inference for read-only strategy advice.
Block explorers (Arbiscan): Linked from the app for transaction lookup; we do not control what they collect.
MoonPay: Card-purchase USDC funding (linked via Privy's fundWallet).

We are not responsible for the privacy practices of third-party sites. We encourage you to review the privacy policies of any third-party services you interact with.

16. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be reflected in the "last updated" date at the top of this page. Material changes (e.g. new third-party data processors, new analytics events) will be communicated through the Service interface. Your continued use of the Service after changes constitutes acceptance of the revised policy.

17. Contact

For privacy-related inquiries, data access requests, or deletion requests, please contact us through the channels listed on the HyperPerps AI website or repository. We will respond within 30 days.

← Back to HyperPerps AI | Terms of Service