Privacy Policy

Who we are

OddsHub (oddshub.io) is operated by Outlier AS, a company registered in Norway, which is the data controller for the processing described here. For anything related to your data, contact hello@oddshub.io. OddsHub is an information service about betting odds; it is intended for users aged 18 or over and does not accept or place bets.

What we collect and why

• Launch and product emails (consent). If you reserve access on the Terminal launch page (or joined the earlier waitlist), we store the email address you enter and when. We use it to tell you the Terminal is open and for occasional product updates. Every email carries an unsubscribe link, and the address is deleted on request at any time.
• Account data (contract). Sign-in is handled by Kinde, our authentication provider; we receive your account id, email and name. Your product data, such as favourites, muted matches, preferences, feed profiles and tracked bets, is stored against your account id so the product works across devices.
• AI analysis (contract). If you use the bet tracker's AI analysis, aggregated statistics about your tracked bets (markets, odds, results; never your name or email) are sent to Anthropic, our AI provider, to generate the report. Anthropic does not use this data to train models.
• Bookmaker requests (legitimate interest). If you ask us to enable a bookmaker for value bets in the Terminal, we store your account id against that bookmaker and send the bookmaker, your email address and your plan to our internal team chat on Telegram, so we can decide what to add and tell how many accounts want it. The record is kept while your account exists and is deleted on request together with your other account data.
• Money-back guarantee requests (contract and legal obligation). If you ask for a refund under the Terminal money-back guarantee, we store a request record with your account id, email address, Stripe customer and subscription ids, the payments covered and the amount owed, and send the same details to our internal team chat on Telegram so a person can make the refund. If you add a note, it is stored only on the request record, never sent to the chat, and is deleted once the refund is made. The rest of the record is kept for five years, like the invoice it corrects (Norwegian bookkeeping rules), and is used for one more thing during that time (legitimate interest): checking that the guarantee is used once per person, by matching later requests and subscriptions against the account, email address and Stripe customer on it.
• Value bet reports (legitimate interest). If you report a value bet in the Terminal, we store your account id, the bet and bookmaker price you reported, the reason you chose, its expected value, and the price freshness and your plan tier at that time. We use this to remove the stale price for you, mark it for other users, and improve how we judge price freshness. Reports are stored by our odds data provider, odds-api.io, which we operate. A report affects what users see for 24 hours; the record is kept while your account exists to improve accuracy, and is deleted on request together with your other account data (email hello@oddshub.io).
• Shared bets (contract). If you share a value bet from the Terminal, we store a snapshot of it against your account id: the match, market, bookmaker, price, fair odds, value and the time it was shared. Anyone with the link can see that snapshot on a public page, and apps such as Telegram, X and WhatsApp show a preview image of it. The fair odds and value are only shown publicly if you leave them switched on. If you choose to show your name, the page and preview also show the display name and link of your public betting record. Removing a link takes effect once our caches refresh: within a minute for the page, and within a day for the preview image. Previews already posted in a chat may stay visible longer, because those apps keep their own copy. A removed link is kept, marked as removed, while your account exists. Shared bets are deleted on request together with your other account data (email hello@oddshub.io).
• Feedback on changes (legitimate interest). If you give a change in the Terminal's What's new panel a thumbs up, we store your account id, which change it was, your choice and the time. We use it to show how many accounts found a change useful and to decide what to build next. Taking a thumbs up back switches it off; the record itself stays. It is kept while your account exists and is deleted on request together with your other account data (email hello@oddshub.io).
• Push notifications (consent). If you switch on notifications on a device, we store that device's push subscription address and browser user agent against your account. Notifications for odds drops, bet results, goals and value bets are delivered through your browser vendor's push service (Apple, Google or Mozilla), and the notification text contains the match and the bet. Switching a device off deletes its subscription.
• Usage analytics (legitimate interest). We use Plausible Analytics, an EU-based, cookie-free analytics service. It collects no personal data and cannot identify you; we only see aggregate page statistics. Plausible keeps this data for as long as our Plausible account exists, which we close once the move below is complete. We are moving to Umami, which we host ourselves on our own servers in Amsterdam, and run both side by side for now. Umami sets no cookies and uses no browser storage. At the moment of your visit, your IP address is used to derive your country, region and city and, together with your browser's user agent and a secret salt that changes every month, a pseudonymous visitor id. The IP address is not stored. We store the page path, campaign (utm) parameters, the referring site's domain, your device, browser and operating system, and these named events: opening, dismissing and reading guides, clicks on links to other sites, and form submissions. We use Umami on the basis of our legitimate interest in understanding how the site is used (GDPR art. 6(1)(f)). Umami keeps visit-level data (page views, events and the pseudonymous visitor id) for 26 months; after that it is deleted. Statistics from before we moved to Umami are imported from Plausible's aggregated counts; they contain no information about individual visitors and are kept. Separately, we store account-linked timestamps for registration, Terminal visits, saved alert profiles, matching-feed views, approved trials, and first payments to understand where setup stalls. These records contain no bet selections or payment-card details, are not sent to Plausible or Umami, and expire after 12 months without activity.
• Referrals and creator codes (contract). If you arrive through a partner link or enter a creator code, we store the link between your account and that partner so their discount applies and their commission can be paid. This uses Dub, our referral platform, which sets a first-party attribution cookie (dub_id) when you arrive via a partner link.
• Technical logs (legitimate interest). Server logs and rate-limiting counters, including IP addresses, are kept briefly to keep the service available and prevent abuse and scraping. They are deleted or expire automatically on short timescales.

What we do not do

We do not sell personal data, we do not run advertising or cross-site trackers, we set no marketing cookies, and we do not send marketing email beyond what you explicitly asked to receive.

Cookies

OddsHub sets cookies that are strictly necessary for signing in and keeping your session secure (provided by Kinde), and, only if you arrive through a partner link, a first-party referral cookie (dub_id) used solely to apply your discount and credit the partner. Our analytics is cookie-free, and we set no advertising or cross-site tracking cookies.

Payments

Paid software subscriptions are processed by Stripe. Every payment to us is a subscription fee for software and data tools; we never receive, hold or pay out gambling stakes or winnings. Card details never touch our servers; we receive only what is needed to know your subscription status. Stripe's own privacy policy governs payment data.

At checkout Stripe collects your billing address and, if you buy for a business, your VAT or tax number and legal business name. Stripe uses them to work out whether VAT applies and at what rate; we use them on invoices and for tax reporting (legal obligation). They stay on your Stripe customer record for as long as tax law requires us to keep invoices (five years under Norwegian bookkeeping rules) and are deleted with it after that.

Who processes data for us

We use a small number of service providers under data processing agreements: Vercel (web hosting), Railway (application and database hosting; our databases are hosted in the EU), Kinde (authentication), Stripe (payments), Anthropic (AI analysis), Plausible (analytics, EU), DigitalOcean (hosting for our self-hosted Umami analytics, Amsterdam), Dub (referral and partner attribution) and Sanity (content management for the blog; no personal data). Where a provider processes data outside the EEA, transfers rely on the European Commission's Standard Contractual Clauses or an adequacy decision.

How long we keep data

Waitlist entries are kept until you receive access or ask to be removed. Account and product data are kept while your account is active and deleted on request. Technical logs and rate-limit counters expire automatically within days. Umami analytics data is deleted after 26 months; statistics imported from Plausible's aggregated counts contain no information about individual visitors and are kept. Plausible analytics data is kept until our Plausible account is closed.

Your rights

Under the GDPR you can request access to, correction of, deletion of, or a portable copy of your personal data, ask us to restrict processing, object to processing based on legitimate interest, and withdraw consent at any time. Email hello@oddshub.io and we will respond within a month. You also have the right to complain to a supervisory authority; in Norway that is Datatilsynet (datatilsynet.no).

Changes

If this policy changes materially we will update this page and the date above, and for significant changes affecting account holders we will notify you by email.