How OriginStats collects, uses, and protects your data.
We collect information you give us — your email address, username, name if provided, password credentials, date of birth, and subscription status — and information generated by your use of the service, including page views, feature and signal interactions, device and browser details, and IP address. When you arrive from a marketing link we also capture campaign parameters and advertising click IDs (such as utm_* values, gclid, fbclid, ttclid, twclid, and msclkid) together with the referring site and landing page. If you choose "Continue with Google", Google sends us your Google account identifier, your email address and whether Google has verified it, and your name and profile picture where available; we store the identifier and your email address so the same Google account signs you back in to the same OriginStats account. Payment details are handled by our payment processors — Stripe, for some accounts Coinflow, and Settlane when you pay in cryptocurrency; we do not intentionally store full card numbers. Before your first withdrawal or your first redemption in the OriginStats shop we ask you to verify your identity through Settlane, our payment and verification processor, whose identity-verification provider, Didit, checks a government photo ID, a live selfie, and whether the same face is already registered to another account. Settlane keeps only the result and its review: whether you were verified and why, the country and type of the document, whether its date of birth matches the one on your account and shows the minimum age, which other OriginStats accounts matched, and whether a sanctions screen raised a match. To check the date of birth we send Settlane the one on your account, which it keeps only until the check is decided. We read from Settlane whether you are verified, and where another OriginStats account matched we record which accounts did; if your account has no date of birth, we record the one shown on an approved document. For a verification completed before Settlane ran our checks, we keep a copy of its result (the decision, the document's country and type, and whether its date of birth matched and a sanctions screen raised a match) with our compliance records. Neither we nor Settlane keep the images, your name as read from the document, or the document number. If you ask to withdraw, we collect the wallet address and network you give us and send them to Settlane, which pays you from our wallet; we record the blockchain transaction it sends, Settlane's answer on each withdrawal, and each withdrawal request we refuse, with the address it named. Settlane checks the address against sanctions and blocking lists and against addresses given by other OriginStats accounts, and keeps a record of those checks. If you redeem a shop item that is delivered, we collect the delivery name, address and, if you give it, phone number. When you register, pay, redeem in the shop or ask to withdraw, we also record technical signals about your connection, such as whether it appears to come from a hosting provider or proxy, to help prevent fraud.
We use data to provide and secure the service, manage accounts and subscriptions, send transactional emails, respond to support requests, operate analytics, measure our marketing campaigns, and improve product quality. We also check comments for spam and abuse, partly by automated means, and may hide a comment that breaks our rules. Everyone who visits Community can read the threads and replies you post there and the wins you share, with your username, until you delete them or we hide them. We check Community posts in the same way as comments, and on Community swearing also breaks our rules. A post you delete leaves Community at once; we keep a record of it so we can look into reports. If you send private messages on Community, we store them until you delete them or your account is deleted. Each message is checked automatically, in the same way as Community posts, and we may hide one that breaks our rules. Our staff read a conversation only when one of its two people reports it, and then only its last 10 messages up to the report. If you block someone, they can no longer send you messages.
We use Google Sign-In as an optional way to create an account and log in; Google acts as an identity provider and tells us only the details listed in section 1. It is not used for advertising or measurement. We use Google Analytics and PostHog for product and site analytics, and Meta (Facebook) Pixel, TikTok Pixel, X (Twitter) conversion tracking, the OpenAI (ChatGPT ads) pixel, and Google Ads conversion tracking for marketing measurement. We also send conversion events to Meta and TikTok server-side (Conversions/Events API); those events can include a hashed (SHA-256) version of your email address and of your OriginStats account identifier, your IP address, and your browser user agent. When you are signed in, the Meta and TikTok tags in your browser also carry that hashed account identifier. When you are signed in, the conversion events we send to Google Ads from your browser can also include a hashed (SHA-256) version of your email address; Google calls this "enhanced conversions" and uses it to match the conversion to a Google account. That hashed address is attached only to those Google Ads conversion events, not to our general analytics. We do not intentionally send raw email addresses, reset tokens, or verification codes to analytics or advertising tools, and analytics page-view URLs are stripped of parameters we have not allow-listed.
We use a session cookie to keep you signed in. Signing in with Google sets one further short-lived cookie, for up to ten minutes, that carries the security tokens protecting that sign-in; it is removed as soon as the sign-in finishes. If you arrive through a friend's referral link or a partner's link, we set a cookie that remembers that link for 30 days, so an account you open can be attributed to it, and we remember your language choice in a cookie. The analytics and advertising tools above set their own cookies or identifiers; our PostHog analytics runs in memory-only mode and does not set cookies. We store marketing attribution (campaign parameters and click IDs) in your browser's local storage for up to 90 days so a later registration can be attributed to the campaign that brought you here, and short-lived flags in session storage. Local storage also keeps settings and progress on your device, such as your display preferences and the choices you have made but not yet sent.
We share data with service providers who help us run OriginStats, including our payment processors (Stripe, for some accounts Coinflow, and Settlane when you pay in cryptocurrency, verify your identity or withdraw; we send Settlane your account's identifier and the date the account was created), Settlane's identity-verification provider (Didit) when you verify before a withdrawal or a shop redemption, blockchain data providers, to which Settlane sends a withdrawal wallet address to check it against stablecoin issuers' lists of frozen addresses, Google where you choose to sign in with it, and the analytics and advertising platforms listed above. When you post a comment, we send its text, with the names of the two teams in the match, to Anthropic, whose AI model checks it for spam, abuse, threats, sexual content and other people's personal details on our behalf. We do not send your name, email address or any other account details with it. When a post or reply, a poll, a comment, an Expert's note or a match analysis appears on OriginStats, we send its text, as written and including any @names in it, to Anthropic so that its AI model can translate it into the site's other languages. We send no account details with it. When you post on Community, we send the title and text of your post and the choices in any poll it carries, with the names of the two teams in any match it is about, to Anthropic in the same way, and its AI model also checks it for swearing, scam links and links to pornography. We send no account details with it. We also send the title and text of a Community thread, the choices in any poll it carries and the text of its visible replies to Anthropic, so that OriginStats' own accounts can write replies on Community. We send no names, usernames or account details with them. When you send a private message, we send its text to Anthropic in the same way as comments, so that its AI model can check it as it checks public posts. We send no names, usernames or account details with it. If you turn on browser notifications for Community, your browser's push service (Google, Apple, Mozilla or Microsoft, depending on your browser) gives us an address and keys for your browser, which we store. When someone replies to you, mentions you or sends you a private message, we send a notice to that address through the push service. The notice says who it was and what happened, never the words of their post or message, and it is encrypted so that only your browser can read it. We delete the address when you turn the notifications off in that browser or sign out there, or when you delete your account. We do not sell personal data for money. Some privacy laws treat sending data to advertising platforms as a "sale" or "sharing" of personal data — you can object to this at any time by contacting [email protected].
You may request deletion of your account and data from your account page. After a verification is decided, Settlane asks its identity-verification provider to delete the images and the data it read from your document; the provider keeps an image-free face template, linked to your account, for up to 5 years, so that the same person cannot open a second account. When you delete your account, we close it at once and erase it 30 days later. Until then you can get it back by logging in. We may keep limited records after that for security, legal, tax, billing, dispute, or compliance purposes. Erasing your account also removes the link to your Google account; you can disconnect Google at any time from your account page without deleting anything, provided you have set a password to log in with. When an account is deleted, the private messages it sent are deleted with it. If a conversation was reported, the messages our staff need to review it are kept until the review is done, and never longer than 90 days, then deleted.
We show ads on OriginStats. Some of them come through Awin, an affiliate network that connects websites with advertisers.
Our pages load a small piece of code (a "tag") from Awin. When you click an ad, or visit a page that carries this tag, Awin and the advertiser may set cookies or use similar technology to record the visit and, if you then buy something, to credit that purchase to us.
Awin explains what it does with this information in its own privacy notice: www.awin.com/gb/privacy.
Some ads come from BAMify, an ad exchange. They load from BAMify's own website inside a sealed-off box on our page, so BAMify receives your IP address and browser details, as any website you load does, and may set its own cookies. When you click one of them, BAMify records the click before it sends you to the advertiser.
Some ads come from Adsterra, an ad network. They load from Adsterra's own servers inside the same sealed-off box, so Adsterra receives your IP address and browser details, as any website you load does, may set its own cookies, and counts the times its ads are seen and clicked. When you click one of them, Adsterra records the click before it sends you to the advertiser.
We keep our own count of the ads we show for advertisers. For each day, we store only which of those ads was shown or clicked, where on the page it was, your country (worked out from your connection), your type of device (phone, tablet or desktop) and the hour on your own clock. These counts carry no name, account, IP address or cookie. Our own OriginStats promotions are recorded like any other use of the site (see section 1).
When an advertiser's ad is seen or clicked, we also send that to Google Analytics and Google Tag Manager, with the ad and the advertiser's name.
Privacy questions: [email protected]