Wallet Follow LLC
WalletFollow privacy policy
This policy explains the information used to run WalletFollow, the choices available in the product and how to contact Wallet Follow LLC about your data. Privacy requests can be sent to info@walletfollow.ai.
Information the service uses
Creating an account provides an email address, authentication information and account settings. Password sign-in stores a password hash. Google sign-in, when selected, supplies the account information needed to authenticate and link your account. We also retain session, verification, security and access records.
Features you choose can add connected public wallet addresses, proof-of-ownership records, API and MCP authorizations, portfolio definitions, subscriptions, risk settings, consents and related activity. Support messages include the information you send us.
Hyperliquid wallet addresses, balances, positions, fills and market observations come from public venue interfaces and retained market history. A public address can become personal information when it is connected to an identifiable person. Connecting it to your account creates an additional association.
- WalletFollow does not ask for your wallet seed phrase or private key.
- Browser research watchlists, wallet names and notes are stored locally in your browser.
- Published portfolio definitions and their public creator information can be visible to other visitors.
Why information is processed
We use account and feature information to provide the services you request, authenticate you, manage permissions and respond to support requests. Public market information supports wallet research, portfolio statistics and the documented Data API.
Network addresses, browser information, request details and security signals are used to operate and protect the service, enforce usage limits, diagnose failures and prevent abuse. Research limits and security checks can automatically allow, challenge or refuse a request; contact support if you believe a refusal is incorrect.
Where data protection law requires a legal basis, requested account services rely on performance of the service agreement; service security and reliability rely on legitimate interests; optional browser matching relies on your consent; and records required by law rely on the relevant legal obligation.
Cookies and browser storage
Necessary cookies maintain sign-in sessions, protect requests against forgery and enforce research access limits. The anonymous research cookie has a 30-day lifetime. Consumer sign-in sessions have a seven-day inactivity limit and a 30-day absolute limit; session expiry does not itself delete account records.
Local storage holds your research watchlist and preferences. Clearing browser storage can remove these local records. WalletConnect, if you choose it, also maintains its connection state in the browser.
Optional browser matching is off until you enable it in Browser preferences. It computes a browser hash to help associate research usage; the application sends the hash only with consent, rather than the individual fingerprint components. You can turn it off from Browser preferences in the page footer. Turning it off stops future optional matching and clears the cached browser hash; existing security and usage records may remain until their expiry.
Providers and integrations
Cloudflare provides website delivery, hosting and security checks, including Turnstile. Resend delivers account verification and security emails. These services receive information needed to perform their functions, such as network and browser signals or email recipient details.
Google receives information when you choose Google sign-in. Hyperliquid receives account or market requests and any venue action you explicitly approve. If you select WalletConnect, its relay and your wallet provider handle the connection. WalletFollow disables telemetry in its WalletConnect client.
An AI assistant or other external client you authorize receives the data returned under its granted API or MCP permissions. Its own privacy policy governs what it does with that data. Review those permissions and revoke a connection from your account when you no longer need it.
Service providers and integrations may process information in countries other than your own. Their locations and processing depend on the service used. Contact us for information about the providers and transfer arrangements relevant to your account. We may also disclose information when required by applicable law or to investigate abuse and protect the service.
Retention and security
Account and service records are kept for the operation of your account and selected features. Expiring verification, session and research-limit records have their own lifetimes. Public market history is retained separately from your account.
When you request deletion, we assess the records associated with you and any need to retain limited security, dispute or legally required records. Closing an account does not erase public venue history or transactions recorded outside WalletFollow. Ask us about the retention applicable to a specific record rather than assuming every category expires with a cookie.
The service uses access controls and encrypted transport. No online service can promise absolute security. Protect your account, review active sessions and permissions, and never send private keys or recovery phrases to support.
Your choices and privacy requests
You can manage account security, sessions, API keys and MCP connections in your account. Browser preferences control optional browser matching. Local watchlists and notes can be edited in the product or removed by clearing the relevant browser storage.
Depending on the law applicable to you, you may have rights to access, correct, erase, restrict or transfer personal information, object to certain processing, withdraw consent and complain to a data protection authority. Withdrawal does not undo processing that was lawful before withdrawal.
Email info@walletfollow.ai to exercise a right or ask about processing. Describe the request and the account or public address concerned. We may verify ownership and explain any applicable exception before acting. We respond within the deadlines required by applicable law.
Changes to this policy
The date on this page identifies the current version. We update this notice when the service or its data practices change and provide additional notice where applicable law requires it.