Privacy Policy
Last updated — November 14, 2026
Polyrank is operated by DefiScout LLC ("we", "us"), the data controller for the personal data described below.
What we collect
- Wallet address (when you sign in with Ethereum) — stored as your account identifier.
- Email address (when you sign in with an email code or a sign-in link) — stored as your account identifier.
- Sign-in method. You can sign in with an email code, a sign-in link sent to your email, a passkey, an Ethereum wallet, or your Google or X account. Email codes, passkeys and Google and X sign-ins are handled by our wallet provider Turnkey, which creates the wallet tied to your account. From Google or X we ask only for what confirms it is you (from Google also your email address and basic profile); we never see your password there, and we cannot post for you.
- Session metadata (IP, user agent) — stored alongside session tokens for security audit.
- Saved rankings — your private and (optionally) public ranking configurations.
- Audit log — every authentication and sensitive action is recorded for 2 years.
Analytics
- Two choices, kept apart. Analytics (how the site is used, so we can fix what is slow or confusing: an analytics cookie and recordings of visits) and ad measurement (whether our ads lead to sign-ups).
- Where each one starts. In the European Economic Area, the United Kingdom, Switzerland and California, and wherever we cannot tell your region, both are off until you say yes; saying no changes nothing about how the site works. Everywhere else, analytics is on from your first page: a notice says so on every visit until you answer it, and its Turn off button ends it in one press. Ad measurement is off in every region until you say yes. We tell the region from the country (in the United States, also the state) that our network provider Cloudflare derives from your IP address. We use it for this decision only. The site keeps which rule applies (the cookie below), not the place; our server's access log holds the country code with each request for about two months.
- We use Google Analytics 4 to count visits. While analytics is off, GA runs cookieless (aggregate, modeled counts only) and sets no analytics cookie; while it is on, GA sets one first-party analytics cookie.
- We use PostHog (PostHog Inc., USA — US Cloud) for product analytics: which features are used and where the signup flow drops off, so we can improve the product, here and on docs.polyrank.app. While analytics is off it runs cookieless: it counts page views and clicks, where on the page your pointer moves and clicks, and how far you scroll, under a random id that lives only for that page load, sets no cookie, stores nothing on your device, hides the text of what you click, and records no session replay. This cookieless count also applies if you say no or turn it off: that stops the cookie and the recordings, not the cookieless count. Like any web request it receives your IP address and browser type, and before anything is sent we strip sign-in tokens from page addresses. In both states it also reports errors a page runs into: the error's message and where in our code it happened, with any email address or wallet address removed. While analytics is on, PostHog sets one first-party cookie (shared across polyrank.app subdomains) so visits link up, and may record a session replay of your visit: what the pages showed, where you moved, clicked and scrolled, and the messages the pages wrote to the browser console, so we can see where the site is hard to use. What you type into a field is masked in a replay, and your account's email and wallet, a new API key and a webhook signing secret are blanked out. While it is on and you are signed in, Google Analytics and PostHog also link your visits to your Polyrank account id (a random identifier, never your email or wallet) and to your plan, so a purchase or an AI Lab run recorded by our servers joins the same visit; a checkout then also carries Google Analytics' own random visitor id to our billing service for the same purpose. Turning it off keeps every feature working identically, stops the recording at once and removes both analytics cookies.
- Advertising measurement only with your consent. If you say yes to ad measurement we load the TikTok pixel (TikTok Inc., USA) and the X pixel (X Corp., USA) to measure ad-campaign conversions such as sign-ups, searches, profile views, checkouts and purchases. They share a limited set of event data — your IP address, user agent, the page URL, the event name, and (for checkouts and purchases) the order value, currency and an order reference — with TikTok and X for that purpose only. Until you say yes, it never loads, sets no cookie, and sends nothing; saying no keeps every feature working identically, and we never use it for cross-site ad targeting.
- You can change your mind anytime. Use Cookie preferences in the footer to turn either choice on or off: withdrawing is as easy as granting, and takes effect at once. Your choices are remembered in this browser, and in two small preference cookies (
polyrank_consent,polyrank_consent_ads) so docs.polyrank.app honors them too. One more cookie (pr_consent_mode) holds which of the two regional rules applies to you: one of two words, no identifier, gone when you close your browser. - One strictly functional cookie for sign-in state. After you sign in, a first-party cookie (
pr_access) remembers whether this browser last had a paid or a free account, so pages do not briefly show the logged-out view while your session loads. It holds one of two words (paidorfree) and no identifier, it gives no access to anything (your session and plan are always checked again), it is removed when you sign out, and it expires after 30 days. It is not used for analytics or advertising. - A short-lived sign-in note in this browser tab. When you start signing in with Google or X, your browser's session storage keeps the page to return you to and which button you chose (
polyrank:auth_return). It holds no token or password, it is never sent to us, it is used once, and it is ignored after 10 minutes and gone when you close the tab. - A note that this browser signed you in through our wallet provider. Your browser's local storage keeps your Polyrank account id (
polyrank:turnkey_account) so the Account page can show your sign-in methods. It holds no token, password or email, it is never sent to us, and it gives no access to anything. - The plan you chose before signing up. When you pick a paid plan while signed out, your browser's local storage keeps that plan and its billing period (
polyrank:chosen_plan) so that signing up, by any method, leads back to its checkout. It holds no identifier and no payment detail, it is never sent to us, and it is removed when checkout starts, when you dismiss it, or after 24 hours. - We never sell your personal data.
AI Lab assistant
- What is sent, and to whom. When you ask the AI Lab assistant a question, the text you type, the strategies you attach and the results of the tools it runs for you (your backtests, paper runs and the public market data it reads) are sent to Anthropic PBC (USA), our AI model provider, to produce the answer. We send no name, email address or wallet address of yours, and no account identifier: the provider sees the conversation, not who you are. Anthropic processes this data for us under its commercial terms (standard contractual clauses for the transfer), keeps API inputs and outputs for up to 30 days for abuse monitoring, and does not train its models on them.
- What we keep. Your chats are stored with your account so you can come back to them, together with the credits each answer used. They are deleted when you delete a conversation or your account (below).
- Improving the assistant. We may use conversations to improve the assistant: to see where it answers badly, to measure its proposed strategies against what happened afterwards, and to test prompt changes. For this we use conversation content under our legitimate interest (GDPR Art. 6(1)(f)), pseudonymised (no account identifier travels with it), for at most 12 months, and content tied to a specific wallet is left out unless you agree otherwise. You can opt out, in advance or at any time, by emailing hello@polyrank.app; opting out never limits the assistant. We do not train a model of our own on your chats.
Payments
Paid plans and AI credit top-ups are billed by Stripe (Stripe, Inc., USA, and Stripe Payments Europe Ltd. for EU customers). Checkout happens on Stripe's pages: your card number never reaches us. Stripe receives your email address, the billing address and tax id you enter, and your Polyrank account id as the order reference; we keep your Stripe customer and subscription ids, the plan, its status and a record of each purchase as our financial records, which we retain for as long as tax law requires, after account deletion too. Stripe is an independent controller for the payment itself; see its privacy policy.
Public on-chain data
Polyrank surfaces public Polygon blockchain data. We do not own or control on-chain data, and we cannot remove it from the blockchain. The wallet → display-name and wallet → P&L associations we publish are derived from public sources (the blockchain and Polymarket's public Data API).
Where data is stored
Polyrank runs on servers in Germany (EU). Encrypted backups are stored in the US. Product-analytics data (cookieless while analytics is off) is processed by PostHog Inc. (USA), through a proxy on our own domain; if you consent to ad measurement, conversion-event data is also transferred to TikTok Inc. (USA); AI Lab assistant conversations are processed by Anthropic PBC (USA) and payments by Stripe, as described above; apart from that, we do not transfer your data to third parties for commercial purposes.
Your rights
You can delete your account at any time — this removes your auth account, saved rankings, session history, and your AI Lab strategies, backtests, paper runs and assistant chats (the billing records above are kept as the law requires). We cannot delete on-chain trade data associated with your wallet (it's on the blockchain). Email hello@polyrank.app for deletion requests.