OnPitch — Privacy Policy
Effective date: 2 November 2026 · Version: 2.1 · Last updated: 2 November 2026 · Contact: support@onpitch.gg
Available in: English · Español · Português (Brasil). English governs in the event of any discrepancy (section 17).
What changed in version 2.1: we added how we process data when you take part in the Spin-to-win welcome bonus (new section 3.7, and changes to sections 3.3, 3.6, 4, 5.5, 6.1, 8.8 and 11). This processing applies only if you spin the wheel or take part in the promotion. We also now explain that we store your Polymarket API credentials, encrypted, to submit your orders and read your orders and fills (sections 3.2, 3.4, 4, 7.1, 11 and 12.2). This is not new processing: it is how the Service has always placed your orders. We never hold your wallet's private keys.
This Privacy Policy explains how we collect, use, share, and protect personal data when you use https://onpitch.gg, its subdomains (including https://app.onpitch.gg), and any related application or API (the "Service"). It also explains your rights under the EU General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR"), and, for users in Brazil, under the Brazilian General Data Protection Law (Lei nº 13.709/2018, "LGPD") (section 16), and how to exercise them.
Please read this alongside our Terms of Service.
In short: we ask for your email, we see your wallet address, and we look up your country from your IP to apply access restrictions. We count page views without cookies. Only if you consent through our cookie banner do we also use Google Analytics and Amplitude to understand how the Service is used, and the Meta Pixel to measure and improve our advertising. Support conversations run through Mava. If you spin the Spin-to-win wheel, we use a cookie and a hashed form of your IP address to make sure each person spins only once, and we keep a record of your boost and any bonus we pay you. To submit your orders, we store your Polymarket API credentials, encrypted; we never hold your wallet's private keys. We do not sell your data, we hold none of your money, and you can change your cookie choices at any time.
1. Who we are
Data controller:
OnPitch — https://onpitch.gg Email: support@onpitch.gg
We are the controller for the personal data described in this Policy, except where section 7 says otherwise.
Data protection officer. We have not appointed a data protection officer. Our processing does not meet the criteria in Article 37(1) GDPR: our core activities do not consist of regular and systematic monitoring of data subjects on a large scale, and we do not process special category data on a large scale. All privacy questions, requests, and complaints go to support@onpitch.gg and are handled by our management.
EU representative. Not applicable — we are established in the European Union (Republic of Lithuania).
2. Scope, and what this Policy does not cover
2.1. This Policy covers processing carried out by us, as controller, in operating the Service.
2.2. It does not cover:
(a) Polymarket. When you place an order, you transact directly with the Polymarket protocol and its operators. They are independent controllers of any data they process about you, under their own privacy policy. We do not control what they collect or how they use it. (b) Privy. Our wallet infrastructure provider, Privy (Horkos, Inc. d/b/a Privy), processes data about you under its own privacy policy and security model. See https://www.privy.io. (c) Card funding providers. If you fund your wallet by card, the purchase is handled inside the wallet widget by third-party payment and on-ramp providers: Meld routes the transaction, and depending on your currency it is completed by Stripe (EUR) or MoonPay (USD and GBP). Each is an independent controller and processes your data under its own terms and privacy policy. MoonPay in particular performs its own identity verification and may ask you for identity documents. Card details, identity documents, and verification data go to those providers, not to us. Their policies are at stripe.com/privacy, meld.io/policy/privacy-policy, and moonpay.com/legal/privacy_policy. (d) Meta's own processing. If you consent to the Meta Pixel, we and Meta are jointly responsible only for collecting that data on our Service and transmitting it to Meta (section 7.4). What Meta does with it afterwards — including combining it with your Facebook or Instagram account and using it for its own ad products — is governed by Meta's own privacy policy, at https://www.facebook.com/privacy/policy. (e) Discord and Telegram. If you contact our support through Discord or Telegram, those platforms process your messages and account data under their own terms and privacy policies. (f) Public blockchains. Data written to a public blockchain is public, permanent, and controlled by no one. See section 6. (g) Third-party sites and platforms. News outlets, X, Reddit, and other sites we link to or embed from have their own policies. Following a link takes you outside this Policy.
We encourage you to read those policies before using the Service.
3. What personal data we collect
3.1. Data you give us
| Data | Detail | When |
|---|---|---|
| Email address | Your registration email | Account creation |
| Account settings | Display name, notification and alert preferences, watchlists, saved filters, theme | While using the Service |
| Support correspondence | Content of emails to support@onpitch.gg and of support chats and tickets through Mava (in-app chat, Discord, or Telegram), including your Discord or Telegram username and anything you volunteer in them | When you contact us |
| Marketing preferences | Whether you have consented to, or opted out of, marketing email | On signup or in settings |
| Cookie preferences | Which categories of cookies you have accepted or rejected, and when | When you respond to the cookie banner or change your settings |
| Feedback | Survey answers, bug reports, feature requests | Voluntarily |
| Age confirmation | Your confirmation that you are 18 or over | Account creation |
We do not ourselves collect identity documents, government identifiers, payment card details, or bank account details, and we do not perform identity verification (KYC). If you fund your wallet by card, that purchase and any identity check it involves are carried out by the third-party providers described in section 2.2(c), under their own terms; the data goes to them, not to us. If we ourselves begin to collect any of this data, we will update this Policy and notify you before it applies to you.
3.2. Data generated when you use the Service
| Data | Detail |
|---|---|
| Wallet address | The public address of the wallet you connect or provision, and its association with your account |
| Order and routing metadata | Orders you compose and submit through our interface: market, side, size, price, timestamps, our builder code attribution, submission and error status |
| Polymarket API credentials | An API key, secret and passphrase that Polymarket issues for your wallet, created with your wallet's signature when you first trade, and stored encrypted on our server. We use them to submit the orders you instruct and to read your orders and fills, including for the welcome bonus (section 3.7). They are not private keys: they cannot sign an order or move your funds, and we never hold your wallet's private keys |
| Position and portfolio views | Positions we read from public on-chain state and display to you |
| Cookieless usage data | Aggregate page and news-item views, referrers, and feature usage, measured without cookies (section 5.2) |
| Analytics data (only with your consent) | Pages and screens viewed, features and buttons used, events (for example, sign-up, wallet connected, order submitted), session duration, referring site and campaign parameters (UTM tags), a pseudonymous user ID and device or cookie identifiers, browser, device type, operating system, language, and approximate location (country and city) derived by the provider from your IP address (section 5.3) |
| Advertising measurement data (only with your consent) | Pages viewed and actions taken on the Service (for example, sign-up or wallet connected), the Meta browser identifier, the ad-click identifier if you arrived from a Meta ad, your IP address, and browser and device information (section 5.4) |
| Device and technical data | IP address, browser type and version, operating system, language, and a server-side session identifier |
| Derived country | The country resolved from your IP address (section 3.3) |
| Diagnostic data | Application error logs, stack traces, and performance timings, stored on our own servers |
| Communications metadata | Delivery and bounce events for transactional and marketing email |
3.3. Data we derive
| Data | Detail |
|---|---|
| Country determination | Your country, derived from your IP address, used to apply the access restrictions in Annex A of the Terms. See section 8 — this is an automated decision. Country-level only: our own geolocation does not derive your region, province, city, or precise location. |
| Restriction status | Whether your session is Full access, Read-Only, or Blocked, and the reason |
| Abuse signals | Indicators of multi-accounting, circumvention attempts, bot traffic, scraping, or market-abuse patterns, and, for accounts taking part in a promotion, the promotion checks in section 3.7 |
| Aggregated statistics | Non-identifying totals and trends about usage of the Service |
3.4. Data from third parties
- Privy: authentication events, wallet provisioning status, and the public wallet address.
- Polymarket: your orders and fills, which we read using your Polymarket API credentials (section 3.2).
- Public blockchains: on-chain activity associated with your wallet address.
- DB-IP database: a country code, returned by a local database file (no data about you is sent anywhere — see section 8.3).
- Google, Amplitude, and Meta (only with your consent): reports about how the Service and our advertising campaigns perform. Meta and Google provide these to us in aggregated form.
- Mava: the history and status of your support tickets, and your Discord or Telegram username where you contact us through those platforms.
3.5. What we do not collect
We do not collect or process:
- identity documents, national identifiers, or biometric data;
- payment card, bank account, or IBAN details (card funding is handled by the providers in section 2.2(c), who receive that data directly);
- precise location data or GPS data. Our own geolocation is country-level only. If you consent to analytics, Google Analytics and Amplitude may derive an approximate location (city level) from your IP address; we use it only in aggregate;
- special category data under Article 9 GDPR (health, ethnicity, political opinions, religion, trade union membership, genetic or biometric data, sex life or sexual orientation) or criminal offence data under Article 10.
Please do not send us special category data. If you volunteer it in a support message, we will process it only as necessary to answer you and will delete it when no longer needed.
3.6. We do not screen wallets
We do not currently perform wallet-address screening, blockchain analytics, or transaction-risk scoring, and we do not send your wallet address to any screening vendor. The only exception is the limited promotion checks in section 3.7: for accounts that receive a Spin-to-win boost, we compare the public addresses that deposited funds to, and received withdrawals from, those accounts' wallets, to detect one person claiming more than one bonus. We do this ourselves, from public on-chain data, without any vendor. If we introduce screening, we will update this Policy first.
3.7. Spin-to-win welcome bonus
If you spin the wheel or take part in the Spin-to-win promotion (see clause 23 of the Terms and the Promotion Terms), we process the following. The wheel does not ask you for your email, phone number, or any other contact details, and spinning does not sign you up for marketing.
| Data | Detail | When |
|---|---|---|
| Spin identifier | A random identifier stored in a first-party cookie on .onpitch.gg (section 5.5), so that the same browser gets the same result back instead of a new spin |
When you click Spin, whether or not you are signed in |
| Hashed IP address | A keyed one-way hash (pseudonymised form) of your IP address. We never store the IP address itself for this purpose. It is used only to give the same result back to the same internet connection for 24 hours, and is deleted after 24 hours | When you click Spin |
| Boost record | The boost you won, when you spun, when it expires, and its status (for example, active, used, expired, won, paid) | From the spin; linked to your account when you sign in or sign up |
| Qualifying trade data | The first buy order placed within the boost period, and its fills, shares, cost, fees, market, and outcome. We read your own orders and fills from Polymarket using your stored API credentials (section 3.2). We use public data (Polymarket's public data and the public blockchain) only to check whether your account has traded before, whether the boosted shares were sold, and the claim of your winnings | When you trade and claim |
| Bonus and payout data | The bonus amount, the wallet address it is paid to, the transaction hash of the payment, and its status (Paid, Sending, Under review, Rejected), shown in your History | When you claim |
| Promotion checks | Whether your account has already received a boost or bonus; whether the address that funded your wallet (for crypto deposits not made through Privy) also funded another boosted account; whether withdrawal addresses are shared with other boosted accounts; and, if a payout is held, the reason and the reviewer's decision | At claim, and afterwards for pattern review |
4. Why we process your data, and our legal basis
| # | Purpose | Data used | Legal basis (GDPR Art. 6) |
|---|---|---|---|
| 1 | Create and operate your account; authenticate you | Email, account settings, session data | Contract (Art. 6(1)(b)) |
| 2 | Provide the news service, alerts, and personalised views | Account settings, usage data | Contract (Art. 6(1)(b)) |
| 3 | Let you compose and submit orders, and display your positions and your orders and fills | Wallet address, order metadata, on-chain data, Polymarket API credentials | Contract (Art. 6(1)(b)) |
| 4 | Attribute orders routed through the Service using our builder code | Order metadata, wallet address | Legitimate interests (Art. 6(1)(f)) — accounting for activity our Interface originates |
| 5 | Send transactional email (verification, security, service and legal notices) | Email, communications metadata | Contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)) for legally required notices |
| 6 | Enforce jurisdictional restrictions (Blocked / Read-Only) | IP address, derived country, restriction status | Legal obligation (Art. 6(1)(c)) for sanctions-driven blocks; legitimate interests (Art. 6(1)(f)) for the remainder — complying with regulatory expectations and with our counterparty's requirements, and protecting the lawfulness of our operations |
| 7 | Enforce the age requirement (18+) | Age confirmation, session data | Legal obligation (Art. 6(1)(c)); legitimate interests (Art. 6(1)(f)) — protecting minors |
| 8 | Detect and prevent fraud, abuse, circumvention, market abuse, bots, and scraping | Usage, technical, abuse signals, order metadata | Legitimate interests (Art. 6(1)(f)) — protecting the Service, other users, and market integrity |
| 9 | Secure the Service; investigate incidents; keep audit logs | Technical, diagnostic, access logs | Legitimate interests (Art. 6(1)(f)); legal obligation (Art. 6(1)(c)) where applicable |
| 10 | Provide support, including through Mava (in-app chat, Discord, Telegram) | Support correspondence, Discord/Telegram username, account data | Contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)) — answering questions from people who are not yet users |
| 11 | Measure and improve the Service using cookieless, non-identifying analytics (Plausible) | Aggregate usage data | Legitimate interests (Art. 6(1)(f)) — understanding which features are used, with minimal privacy impact and no tracking |
| 12 | Product and marketing analytics: understand how people find and use the Service, measure sign-up and feature adoption, and improve the product (Google Analytics, Amplitude) | Analytics data | Consent (Art. 6(1)(a)), withdrawable at any time |
| 13 | Advertising measurement and optimisation: measure the results of our ads on Meta platforms, and show our ads to people who have visited the Service or who resemble our users (Meta Pixel) | Advertising measurement data | Consent (Art. 6(1)(a)), withdrawable at any time |
| 14 | Remember your cookie choices | Cookie preferences | Legal obligation (Art. 6(1)(c)) — demonstrating valid consent (Art. 7(1) GDPR) |
| 15 | Debug faults | Diagnostic and error data | Legitimate interests (Art. 6(1)(f)) |
| 16 | Send marketing email and product updates | Email, marketing preferences, communications metadata | Consent (Art. 6(1)(a)), withdrawable at any time |
| 17 | Handle notices about content, and comply with the Digital Services Act where applicable | Notice content, contact details | Legal obligation (Art. 6(1)(c)); legitimate interests (Art. 6(1)(f)) |
| 18 | Establish, exercise, or defend legal claims; respond to lawful requests; comply with court orders | As relevant | Legal obligation (Art. 6(1)(c)); legitimate interests (Art. 6(1)(f)) |
| 19 | Corporate transactions (merger, acquisition, financing, sale of assets) | As relevant | Legitimate interests (Art. 6(1)(f)) |
| 20 | Run the Spin-to-win promotion: give you a spin result, link the boost to your account, apply it to your qualifying trade, calculate and pay your bonus, and show it in your History | Spin identifier, boost record, qualifying trade data, bonus and payout data, wallet address (section 3.7) | Contract (Art. 6(1)(b)) — performing the Promotion Terms you accept by taking part |
| 21 | Make sure each person receives only one boost and one bonus, and detect and prevent promotion abuse (holding a payout for human review where a check fails) | Spin identifier, hashed IP address, promotion checks, on-chain deposit and withdrawal addresses (section 3.7) | Legitimate interests (Art. 6(1)(f)) — protecting the promotion's budget and fairness to other users |
| 22 | Keep accounting records of bonuses we pay | Bonus and payout data | Legal obligation (Art. 6(1)(c)) — Law on Accounting of the Republic of Lithuania |
Legitimate interests balancing. Where we rely on legitimate interests, we have assessed our interest against your rights and freedoms and concluded that our processing is necessary, proportionate, and within your reasonable expectations. You may object at any time (section 10.6), and you may ask us for a summary of the relevant assessment.
5. Cookies, analytics, and advertising measurement
5.1. Your choice, through our cookie banner
When you first visit the Service, we show a cookie banner. Non-essential technologies — Google Analytics, Amplitude, and the Meta Pixel — do not load and set no cookies until you accept them. You can:
- Accept all, Reject all (as easily as accepting), or choose by category (Analytics, Marketing);
- change or withdraw your choice at any time through the Cookie settings link in the footer of every page. Withdrawing is as easy as giving consent, and stops further collection from that point; it does not affect processing before withdrawal.
If you reject or ignore the banner, only the strictly necessary cookies in section 5.5 and cookieless Plausible analytics (section 5.2) are used. Rejecting cookies does not affect your ability to use the Service.
Where your browser sends a Global Privacy Control signal, we treat it as a rejection of the Marketing category.
5.2. Cookieless analytics (no consent needed)
We use Plausible Analytics, provided by Plausible Insights OÜ (Estonia, European Union), hosted in the EU. Plausible sets no cookies, stores nothing on your device, does not track you across sites or sessions, and does not collect or retain personal data or your IP address. It produces aggregate counts only. We therefore rely on legitimate interests, not consent.
5.3. Analytics cookies (only with your consent)
- Google Analytics 4, provided by Google Ireland Limited (with Google LLC, United States). We use it to measure traffic sources, campaigns, page views, and conversion events. Google acts as our processor. We have disabled Google signals and data sharing with Google for advertising purposes, and Google Analytics 4 does not log or store full IP addresses. Google's information on how it processes this data: https://policies.google.com/technologies/partner-sites.
- Amplitude, provided by Amplitude, Inc. (United States). We use it for product analytics: understanding which features are used, where users drop off, and how changes affect usage. Events may be linked to a pseudonymous user ID associated with your account, so that we can understand usage across your sessions and devices. Amplitude acts as our processor. We do not send your email address, name, or wallet address to Amplitude.
5.4. Marketing cookies (only with your consent)
- Meta Pixel, provided by Meta Platforms Ireland Limited (with Meta Platforms, Inc., United States). We use it to measure whether our ads on Facebook and Instagram lead to visits and sign-ups, and to show our ads to people who have visited the Service or who resemble our users. The Pixel sends Meta the page you view, the actions you take (for example, sign-up), your IP address, browser information, and Meta's cookie identifiers. We do not send your email address, phone number, or wallet address to Meta, in hashed or any other form (we do not use Meta "Advanced Matching"), and we do not send Meta order sizes, positions, or other trading data. Meta may link this data to your Facebook or Instagram account if you have one. See section 7.4 for how responsibility is shared with Meta, and https://www.facebook.com/privacy/policy for Meta's own processing. You can also manage ad preferences in your Meta account settings.
5.5. Cookies and similar technologies we use
| Name | Set by | Purpose | Category | Lifetime |
|---|---|---|---|---|
onpitch_session |
onpitch.gg (first party) | Maintains your signed-in session | Strictly necessary | Session, expiring on logout or after inactivity |
XSRF-TOKEN |
onpitch.gg (first party) | Protects against cross-site request forgery | Strictly necessary | Session |
onpitch_consent |
onpitch.gg (first party) | Stores your cookie choices so we do not ask again on every visit | Strictly necessary | 12 months |
onpitch_boost |
onpitch.gg (first party, on .onpitch.gg, shared by the website and the app) |
Set only when you click Spin. Contains only a random, encrypted identifier. Remembers your spin result and its 2-hour timer so that refreshing the page, or opening the wheel again, shows the same result instead of a new spin. Used only for the promotion, never for analytics or advertising | Strictly necessary | 30 days from the spin |
privy-token |
Privy | Short-lived authentication token for your wallet session | Strictly necessary | Approximately 1 hour |
privy-refresh-token |
Privy | Renews your wallet session so you are not signed out constantly | Strictly necessary | Up to 30 days |
| Local storage: interface preferences | onpitch.gg (first party) | Remembers your theme, watchlists, and display settings | Strictly necessary / functional | Until you clear it |
| Local storage: support chat | Mava (Noosa Labs, Inc.) | Keeps your support chat conversation open between pages, only once you open the chat | Strictly necessary / functional | Until you clear your browser storage |
_ga |
Google Analytics (first-party cookie) | Distinguishes visitors | Analytics — consent | 2 years |
_ga_* |
Google Analytics (first-party cookie) | Maintains session state | Analytics — consent | 2 years |
AMP_* |
Amplitude (first-party cookie) | Stores a device ID and session ID for product analytics | Analytics — consent | 12 months |
_fbp |
Meta Pixel (first-party cookie) | Identifies browsers for ad measurement | Marketing — consent | 90 days |
_fbc |
Meta Pixel (first-party cookie) | Stores the ad-click identifier when you arrive from a Meta ad | Marketing — consent | 90 days |
Strictly necessary cookies and storage are exempt from the consent requirement under Article 5(3) of the ePrivacy Directive (Directive 2002/58/EC) as implemented in Lithuanian law. The spin cookie falls into this category: it is set only when you ask to spin, and the promotion you asked for cannot work without it. Analytics and marketing cookies are set only with your consent. If you consent to analytics, Google Analytics also records wheel events (for example, that the wheel was opened or spun, and the boost won) as part of the analytics data in section 3.2.
5.6. Blocking cookies
Most browsers let you block or delete cookies. Blocking the strictly necessary cookies above will prevent you from signing in and using the Service. Blocking analytics or marketing cookies has no effect on your ability to use the Service.
6. Blockchain data — read this carefully
6.1. When you transact, data is written to a public blockchain. This includes your wallet address, the market, the size, the price, the timestamp, and the builder-code attribution associated with the order. If we pay you a Spin-to-win bonus, the payment is also a public on-chain transfer from a promotional wallet controlled by onPitch to your wallet, which shows anyone that your wallet received a bonus from us.
6.2. This data is:
- public — visible to anyone in the world, permanently, without needing your permission or ours;
- immutable — it cannot be altered, corrected, or deleted, by us or by anyone;
- outside our control — it is replicated across independent nodes we do not operate; and
- potentially linkable to you — chain-analysis techniques may associate a wallet address with a real-world identity, particularly if you have used that address on a verified exchange or disclosed it publicly.
6.3. Consequences for your rights. Because on-chain data is immutable and outside our control, we cannot erase, rectify, or restrict it, and your rights of erasure, rectification, and restriction (section 10) cannot be exercised against the blockchain. Those rights apply to the data we hold in our own systems — your account record, our off-chain logs, our analytics — and we will honour them there in full.
6.4. Please treat any decision to transact on-chain as a decision to publish that transaction permanently. If pseudonymity matters to you, consider carefully which wallet address you connect.
7. Who we share your data with
We do not sell your personal data and we do not disclose it to data brokers. With your consent only, we share limited browsing and event data with Meta for advertising measurement (section 5.4).
7.1. Recipients
| Recipient | Role | Location | Why | Data |
|---|---|---|---|---|
| OVHcloud (OVH SAS) | Processor | European Union | Hosting, servers, databases, storage, application and error logs, and email infrastructure for our domain | All data we hold, in transit and at rest |
| Privy (Horkos, Inc. d/b/a Privy) | Processes your data under its own terms and privacy policy (section 2.2(b)); independent controller for its own operations | United States | Wallet provisioning, authentication, and signing | Email, authentication events, wallet address |
| Google Ireland Limited / Google LLC (Google Workspace) | Processor | EU / United States | Our support mailbox — receiving and sending email to support@onpitch.gg | Your email address and the content of your correspondence |
| Noosa Labs, Inc. (d/b/a Mava) | Processor | United States | Customer support platform: in-app support chat, and support tickets raised through Discord and Telegram | Support messages and attachments, Discord or Telegram username, your email address if you provide it, ticket history |
| Plausible Insights OÜ | Processor | Estonia, EU | Cookieless, aggregate analytics | Aggregate page-view counts. No cookies, no IP retention, no personal data |
| Google Ireland Limited / Google LLC (Google Analytics 4) | Processor — only with your consent | EU / United States | Traffic, campaign, and conversion analytics | Analytics data (section 5.3) |
| Amplitude, Inc. | Processor — only with your consent | United States | Product analytics | Analytics data, linked to a pseudonymous user ID (section 5.3) |
| Meta Platforms Ireland Limited / Meta Platforms, Inc. (Meta Pixel) | Joint controller for collection and transmission; independent controller for Meta's subsequent processing — only with your consent | EU / United States | Advertising measurement and audiences | Advertising measurement data (section 5.4) |
| Polymarket | Independent controller | Outside our control | Receiving your signed order and our builder code, and reading your positions, orders and fills; our requests are authenticated with your Polymarket API credentials | Wallet address, order data, builder code |
| Public blockchain networks | No controller | Global | Settlement and record of your transactions | On-chain transaction data (section 6) |
| Professional advisers (lawyers, accountants, auditors) | Processor or independent controller | EU | Advice, compliance, defence of claims | As relevant |
| Authorities (courts, regulators, law enforcement, financial-intelligence units) | Independent controllers | As applicable | Where legally required, or necessary to establish or defend legal claims | As relevant |
| An acquirer or investor | Independent controller | As applicable | In a merger, acquisition, financing, insolvency, or sale of assets | As relevant, under confidentiality |
7.2. No geolocation vendor
Our IP geolocation for access restrictions uses a local database file installed on our own servers (section 8.3). No third party receives your IP address for this purpose — there is no geolocation API call, no lookup service, and no vendor involved at request time.
7.3. Processors
OVHcloud, Google (Workspace and Google Analytics), Mava, Plausible, and Amplitude act on our instructions as processors under written terms meeting Article 28 GDPR, are bound by confidentiality, and may not use your data for their own purposes. Privy processes your data under its own terms of service and privacy policy (section 2.2(b)).
7.4. Meta — joint controllership
Where you consent to the Meta Pixel, we and Meta Platforms Ireland Limited are joint controllers, within the meaning of Article 26 GDPR, for the collection of Pixel data on the Service and its transmission to Meta. This arrangement is set out in Meta's Controller Addendum (https://www.facebook.com/legal/controller_addendum). Under it, we are responsible for obtaining your consent and for informing you, as this Policy does; Meta is responsible for enabling your rights in respect of the data it holds after transmission. You may exercise your rights with either of us; we will forward requests that concern Meta's processing to Meta. Meta is an independent controller for any processing it carries out after the data has been transmitted.
7.5. Independent controllers
Polymarket, Meta (for its own processing), and public blockchain participants act as independent controllers or as no controller at all. Once data reaches them, this Policy no longer governs their processing.
7.6. Lawful requests
We will disclose data where compelled by valid legal process, or where we reasonably believe disclosure is necessary to comply with law or sanctions, to protect our rights or property, to protect the safety of any person, or to investigate fraud or market abuse. Where lawful and practicable, we will notify you first. In some cases we are legally prohibited from doing so.
8. Automated decision-making: how geo-restriction works
8.1. We use automated processing to determine which access category applies to you: Full access, Read-Only (you may view the news feed only), or Blocked (no access). This is applied automatically, without human involvement, each time you access the Service.
8.2. The logic. Your IP address is read from the request. It is looked up against a country-level IP geolocation database to produce a two-letter country code. That country code is matched against the lists in Annex A of the Terms of Service. The resulting category is applied to your session. Signals suggesting deliberate circumvention may also result in restriction.
8.3. Where the lookup happens — and what does not leave our servers. The geolocation database is the DB-IP "IP to Country Lite" database, distributed by DB-IP (https://db-ip.com) as a single file of approximately 8 MB. That file is bundled inside our application and installed on our own servers. The lookup is a local, in-process file read. Consequently:
- your IP address is never transmitted to any third party for geolocation;
- there is no external API call, no lookup service, and no vendor that receives or logs your request;
- the database contains no data about you — it is a static mapping of IP ranges to countries; and
- it is refreshed only when we deploy a new version of our application. It does not connect to the internet or update itself.
8.4. Country-level only. The database resolves to a country and nothing more. We do not determine, and cannot determine, your region, state, province, city, postcode, or coordinates from it. Where a legal restriction applies only to part of a country, we apply it to the whole country rather than attempt finer resolution — which is why the whole of Ukraine and the whole of Canada are restricted. See clause 4.5 of the Terms.
8.5. Client IP determination. Our application runs behind our own ingress infrastructure, and we read your originating IP address from the forwarded request headers so that the restriction is applied to you rather than to our own load balancer.
8.6. Significance and consequences. A Blocked determination prevents you from using the Service. A Read-Only determination limits you to the news feed: you cannot view or use markets, trading, positions, or portfolio features, or open, increase, reduce, or close a position through the Service. Neither affects positions you already hold on-chain, which remain yours and remain accessible directly through Polymarket or your wallet.
8.7. Legal basis and safeguards. We consider this processing necessary for entering into and performing our contract with you, and necessary for compliance with legal obligations to which we are subject, within Articles 22(2)(a) and 22(2)(b) GDPR. In any event, and regardless of whether Article 22 applies, we give you these safeguards:
- You may contest the determination and request human review by emailing support@onpitch.gg with your account email and the country you are actually in.
- A person will review the determination and correct it where it is wrong. IP geolocation is imperfect and mistakes happen, particularly with mobile networks, corporate VPNs, and satellite connections.
- Correcting a geolocation error does not grant access where the restriction genuinely applies to you.
8.8. Profiling. Apart from geo-restriction, we make no automated decision that produces legal or similarly significant effects for you. In the Spin-to-win promotion, the spin result is random, and the promotion's rules (for example, one boost per account, and no boost for accounts that have already traded) are applied automatically, as the Promotion Terms you accept say, which is necessary to perform them (Art. 22(2)(a) GDPR). The payout checks in section 3.7 can only hold a payout for review. They never refuse it on their own: a person decides, and you can ask us to explain or reconsider that decision at support@onpitch.gg. If you consent to analytics or marketing cookies, Amplitude and Google Analytics group usage data to help us understand how the Service is used, and Meta may use Pixel data to include you in, or exclude you from, audiences for our ads. This is profiling for analytics and marketing purposes. It does not affect your access, eligibility, or pricing, and you can stop it at any time by withdrawing consent (section 5.1).
8.9. Attribution. IP Geolocation by DB-IP, used under the Creative Commons Attribution 4.0 International licence.
9. International transfers
9.1. We are established in the European Union (Republic of Lithuania). Our hosting, databases, logs, and cookieless analytics are located in the European Union (OVHcloud and Plausible).
9.2. The following providers involve a transfer to the United States or another country outside the EEA:
| Provider | Purpose | Safeguard |
|---|---|---|
| Privy (Horkos, Inc. d/b/a Privy) | Wallet infrastructure and authentication | No adequacy decision covers this recipient. Where you choose an embedded wallet, we rely on the derogation in Article 49(1)(b) GDPR: the transfer is necessary to perform our contract with you, because an embedded wallet cannot be provisioned or used without it. If you connect your own external wallet instead, we transfer no data to Privy. Privy applies its own technical and organisational measures, described in its privacy policy |
| Google LLC (via Google Ireland Limited) | Support mailbox; Google Analytics (with consent) | The EU–US Data Privacy Framework adequacy decision of 10 July 2023, under which Google LLC is certified, and, additionally, Standard Contractual Clauses |
| Amplitude, Inc. | Product analytics (with consent) | The EU–US Data Privacy Framework adequacy decision, under which Amplitude, Inc. is certified, and, additionally, Standard Contractual Clauses |
| Meta Platforms, Inc. (via Meta Platforms Ireland Limited) | Meta Pixel (with consent) | The EU–US Data Privacy Framework adequacy decision, under which Meta Platforms, Inc. is certified, and, additionally, Standard Contractual Clauses |
| Noosa Labs, Inc. (d/b/a Mava) | Customer support | Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module 2: controller to processor), Article 46(2)(c) GDPR |
9.3. Blockchain networks are global by design. On-chain data is replicated worldwide across nodes we neither operate nor select. This is inherent to the technology and cannot be constrained by contract. By transacting, you accept that on-chain data will be published globally.
9.4. You may request a copy of the Standard Contractual Clauses we rely on by emailing support@onpitch.gg.
10. Your rights
Subject to the conditions and exemptions in the GDPR, you have the following rights. Users in Brazil also have the rights set out in section 16.
10.1. Access — obtain confirmation of whether we process your data, a copy of it, and information about the processing.
10.2. Rectification — have inaccurate data corrected and incomplete data completed.
10.3. Erasure ("right to be forgotten") — have your data deleted where it is no longer needed, where you withdraw consent and there is no other basis, where you successfully object, or where processing is unlawful. This does not extend to blockchain data (section 6.3), or to data we must retain to comply with a legal obligation or to establish or defend legal claims.
10.4. Restriction — have processing limited, for example while you contest accuracy or an objection is being considered.
10.5. Portability — receive the data you provided to us, and data generated by your use, in a structured, commonly used, machine-readable format, and have it transmitted to another controller where technically feasible. This applies to processing based on consent or contract and carried out by automated means.
10.6. Objection — object at any time, on grounds relating to your particular situation, to processing based on legitimate interests (Art. 6(1)(f)). We will stop unless we can demonstrate compelling legitimate grounds that override your interests, or the processing is for legal claims. You may object to direct marketing, including profiling for marketing, at any time, for any reason, and we will stop unconditionally.
10.7. Withdraw consent — withdraw consent at any time where processing is based on it. This covers analytics and marketing cookies (withdraw through Cookie settings in the footer — section 5.1) and marketing email (use the unsubscribe link or your account settings — section 14). Withdrawal does not affect the lawfulness of processing before withdrawal.
10.8. Human review of an automated decision — see section 8.7.
10.9. How to exercise your rights. Email support@onpitch.gg from your registered email address, or from another address together with enough information for us to identify you. We will:
- respond within one month, extendable by two further months for complex or numerous requests, in which case we will tell you within the first month;
- act free of charge, except where a request is manifestly unfounded or excessive, in which case we may charge a reasonable fee or refuse and tell you why; and
- ask for additional information only where we genuinely cannot identify you, and only to the extent necessary.
10.10. Complaints. If you are unhappy with how we handle your data, please tell us first at support@onpitch.gg so we can put it right. You also have the right to lodge a complaint with a supervisory authority — in Lithuania:
Valstybinė duomenų apsaugos inspekcija (State Data Protection Inspectorate) L. Sapiegos g. 17, LT-10312 Vilnius, Lithuania Telephone: +370 5 271 2804 Email: ada@ada.lt · Web: https://vdai.lrv.lt
You may also complain to the supervisory authority in your EU country of residence or place of the alleged infringement. Users in Brazil may complain to the ANPD (section 16.6).
11. How long we keep your data
We keep personal data only as long as necessary for the purpose it was collected for, and then delete or anonymise it.
| Data | Retention | Rationale |
|---|---|---|
| Account record (email, settings) | For the life of the account, then 90 days after closure | Reversal of accidental closure, then deletion |
| Wallet address ↔ account association | For the life of the account, then 5 years | Defence of claims; responding to lawful requests |
| Order and routing metadata (off-chain records) | 5 years from the order | Attribution, dispute handling, record-keeping |
| Polymarket API credentials (encrypted) | For as long as needed to provide the Service to you | Submitting your orders and reading your orders and fills |
| IP address in application logs | 12 months, then deleted | Demonstrating that access restrictions were correctly applied; incident investigation |
| Country code derived from IP | Retained with the session and restriction record for 5 years | Evidence of compliance with sanctions and access rules. The country code alone is far less identifying than the IP address it came from |
| Security and access logs | 12 months | Incident investigation |
| Diagnostic and error data | 90 days | Debugging |
| Cookieless analytics (Plausible) | Aggregate, non-identifying counts only — no personal data is retained | Plausible stores no personal data or IP addresses |
| Google Analytics data (with consent) | 14 months from collection, then deleted by Google | Year-on-year comparison of traffic and campaigns |
| Amplitude data (with consent) | 12 months from collection, then deleted | Product analytics over a full year of releases |
| Meta Pixel data (with consent) | Audiences we create expire after a maximum of 180 days of inactivity. Meta's own retention is governed by Meta's privacy policy | Advertising measurement |
| Cookie consent records | 12 months from your last choice, then 3 years as proof of consent | Demonstrating valid consent (Art. 7(1) GDPR) |
| Support correspondence (email and Mava) | 3 years from resolution | Service quality; defence of claims |
Welcome bonus: spin identifier cookie (onpitch_boost) |
30 days from the spin (section 5.5) | Replaying your spin result |
| Welcome bonus: hashed IP address from a spin | 24 hours, then deleted | Giving the same result back to the same connection for 24 hours |
| Welcome bonus: spin records never linked to an account | 30 days from the spin, then deleted | No longer needed once the boost has expired; matches the life of the spin cookie |
| Welcome bonus: boost record, qualifying trade data, and promotion checks for your account | For the life of the account, then 5 years | Showing that the promotion's rules were applied correctly; defence of claims; preventing the same person from claiming again |
| Welcome bonus: bonus payment (payout) records | 10 years | Accounting records under the Law on Accounting of the Republic of Lithuania. A boost that was paid is kept for this longer period |
| Marketing consent and opt-out records | Until withdrawn, then 5 years as a suppression record | Proving we honoured your opt-out |
| Content notices and our decisions | 5 years | Digital Services Act record-keeping, where applicable |
| Accounting records | 10 years, as required by Lithuanian law | Statutory retention under the Law on Accounting of the Republic of Lithuania |
| Records subject to a legal claim, investigation, or legal hold | Until the matter is finally resolved plus the applicable limitation period | Establishing or defending legal claims |
| On-chain data | Permanent — outside our control | See section 6 |
Where a retention period expires but the data is still needed for a specific, documented legal claim, we retain only what is necessary for that claim and delete the rest.
12. Security
12.1. We implement technical and organisational measures appropriate to the risk, including encryption in transit (TLS), encryption at rest at our hosting provider, access controls on a need-to-know basis, environment separation, secrets management, logging and monitoring, dependency management, and supplier due diligence.
12.2. We do not hold your private keys or your funds. Key material is handled by Privy or by you. We do store your Polymarket API credentials (section 3.2). They are encrypted at rest, and access to them is restricted to the systems and staff that need it to submit and read your orders. They are not private keys and cannot be used to move your funds. This meaningfully limits what an attacker could obtain from us — but it also means we cannot restore access to a wallet, reverse a transaction, or recover lost assets.
12.3. We hold no payment card or bank data, because we do not process payments ourselves. Card funding is processed by the providers in section 2.2(c).
12.4. No system is perfectly secure. We cannot guarantee absolute security, and transmission over the internet is at your own risk.
12.5. If a personal data breach is likely to result in a risk to your rights and freedoms, we will notify the State Data Protection Inspectorate within 72 hours of becoming aware of it, and will notify you without undue delay where the risk is high. Where a breach may cause relevant risk or damage to users in Brazil, we will also notify the ANPD and affected users as required by Article 48 LGPD.
13. Children
The Service is not intended for anyone under 18, and we do not knowingly collect data from anyone under 18. If we learn that we have, we will close the account and delete the data promptly. If you believe a minor is using the Service, contact support@onpitch.gg.
14. Marketing
14.1. We send marketing email only with your consent, or where permitted by law to an existing customer about similar services, with a clear opt-out in every message.
14.2. Every marketing email contains a one-click unsubscribe. You can also change your preferences in your account or email support@onpitch.gg.
14.3. Opting out of marketing does not stop transactional and service messages (security alerts, account notices, changes to these documents), which are part of providing the Service.
14.4. We do not share your email address with any third party for that party's own marketing, and we do not upload it to Meta, Google, or any other advertising platform for ad targeting.
14.5. Advertising on Meta platforms that uses Pixel data is governed by your cookie choices (section 5), not by your marketing email preferences. You can turn it off through Cookie settings.
15. Changes to this Policy
15.1. We may update this Policy. The current version is always at https://onpitch.gg/privacy with a version number and effective date.
15.2. Where a change is material, we will notify you by email or prominent in-Service notice at least 15 days before it takes effect, unless a shorter period is required by law.
15.3. Where a change requires your consent — for example, introducing a new analytics or advertising technology — we will ask for it before the change applies to you.
16. Users in Brazil (LGPD)
This section applies when the LGPD applies to our processing of your personal data — in particular, where you are located in Brazil when we collect your data. It supplements the rest of this Policy. Where this section conflicts with another part of this Policy for such processing, this section prevails.
16.1. Controller and contact. The controller is OnPitch (section 1). For the purposes of Article 41 LGPD, requests and communications about your personal data, including those from the ANPD, may be sent to our privacy contact channel: support@onpitch.gg.
16.2. Legal bases. The legal bases described in section 4 correspond to the following legal bases under Article 7 LGPD: performance of a contract (GDPR "Contract") — Art. 7, V; compliance with a legal or regulatory obligation (GDPR "Legal obligation") — Art. 7, II; legitimate interests (GDPR "Legitimate interests") — Art. 7, IX; consent (GDPR "Consent") — Art. 7, I; and the regular exercise of rights in judicial, administrative, or arbitration proceedings — Art. 7, VI. We do not process sensitive personal data (Art. 11 LGPD).
16.3. Your rights under Article 18 LGPD. You have the right to:
- confirmation that we process your personal data;
- access to your data;
- correction of incomplete, inaccurate, or out-of-date data;
- anonymisation, blocking, or deletion of unnecessary or excessive data, or of data processed in breach of the LGPD;
- portability of your data to another service or product provider, subject to ANPD regulations and our trade secrets;
- deletion of data processed on the basis of your consent, except where the LGPD permits retention (Art. 16);
- information about the public and private entities with which we share your data (section 7);
- information about the possibility of not giving consent and the consequences of refusing (section 5.1 — refusing analytics and marketing cookies has no effect on your use of the Service);
- revoke your consent at any time (sections 5.1 and 14); and
- object to processing carried out on a basis other than consent, where it does not comply with the LGPD.
16.4. Review of automated decisions (Article 20 LGPD). You may request a review of decisions taken solely on the basis of automated processing that affect your interests, including the geo-restriction determination in section 8. You can request this, and clear information about the criteria and procedures used, at support@onpitch.gg (see section 8.7).
16.5. How to exercise your rights and response times. Email support@onpitch.gg as described in section 10.9. Requests are free of charge. We will confirm whether we process your data, and provide access to it, in simplified form immediately, or in a clear and complete declaration within 15 days of your request (Art. 19 LGPD). Where we cannot act on a request immediately, we will tell you why.
16.6. Complaints to the ANPD. You have the right to petition the Autoridade Nacional de Proteção de Dados (ANPD) regarding our processing of your data: https://www.gov.br/anpd. We ask you to contact us first so that we can try to resolve your concern.
16.7. International transfers. Your data is transferred outside Brazil — to the European Union, where we are established and host the Service, and to the other countries listed in section 9. We carry out these transfers on the bases permitted by Article 33 LGPD, including standard contractual clauses approved by the ANPD where required, and, where applicable, where the transfer is necessary to perform a contract with you (Art. 33, IX, read with Art. 7, V).
16.8. Security incidents. See section 12.5.
17. Language
This Policy is published in English, Spanish, and Portuguese (Brazil). The Spanish and Portuguese versions are translations provided for convenience. The English version is the authoritative text and governs in the event of any discrepancy, except where mandatory law requires otherwise.
18. Contact
Questions, requests, or complaints about privacy:
OnPitch — https://onpitch.gg Email: support@onpitch.gg
OnPitch (onpitch.gg) aggregates news published by third parties and provides a non-custodial interface to Polymarket: you submit your own signed orders, we hold no funds, take no other side, and exercise no discretion over your trades. IP Geolocation by DB-IP.