Privacy Policy

Account information. When you sign in (email/password or a provider like Google), we receive your email address and display name from our authentication provider, Neon Auth (Stack Auth).

Bet slip screenshots and the data extracted from them. When you upload a screenshot, we send the image to Google’s Gemini API to read it, and store both the image and the extracted details (teams, league, market, selection, odds, stake, and similar) in our database, tied to your account.

Financial figures you enter. Stakes, payouts, deposits, and withdrawals you record — this is bookkeeping data you type in or that we extract from your own screenshots; we never see or touch your actual bank or bookmaker account.

Optional public profile. If you choose to set a username and turn on a public profile (the “Tipsters” feature), your win-rate/ROI statistics and that username become visible to other users. This is off by default and entirely opt-in — your individual bet slips are never made public this way, only aggregate stats and any single slip you separately, explicitly choose to post.

Preferences and settings. Currency, point-value conversion, UI language, notification preferences, and any responsible-gambling loss limits you set.

Push notification subscription. If you enable push notifications, your browser gives us a delivery address for your device (through your browser’s own push service — Google, Mozilla, Apple, or Microsoft, depending which browser you use) so we can send you an update when a bet settles or a followed match starts.

Social features. Teams you follow, groups you’re a member of, and who you follow or are followed by, if you use those features.

We don’t sell your data. It’s shared only with the services that make the app work:

• Neon Auth (Stack Auth) — handles sign-in and identity.
• Google (Gemini API) — reads the bet slip screenshots you upload to extract their contents. Only the image itself is sent, for that one extraction request.
• API-Football — we look up public match/team/league information from them (scores, fixtures, odds) to match against your slips. We never send them anything about you personally — only team names and dates.
• Neon (database) and Vercel (hosting) — the infrastructure BetScanr itself runs on.
• Your browser’s own push service (Google/Mozilla/Apple/Microsoft) — delivers push notifications you’ve opted into; only reachable if the message came from BetScanr’s own server in the first place.
• PostHog (product analytics, EU-hosted) — only if you accept the analytics-cookie banner. Sees which pages/features you use and when, tied to a random account ID, never your email or name. See Section 5 below for the full opt-in details.

Other BetScanr users only ever see what you explicitly choose to make visible: a public Tipster profile if you opt in, a slip you choose to post to the feed, or your standing inside a private group you joined. Your email address is never shown to other users.

These aren’t just policy promises — they’re real, working buttons in the app today:

• Export everything. Settings → Privacy & Account → Export my data downloads a complete copy of your account as a file, on demand.
• Delete everything. Settings → Privacy & Account → Delete my account permanently removes your bet slips, transactions, and every setting, and closes the account itself — not just a deactivation. This can’t be undone. If you created a private group, deleting your account deletes that group for its other members too — the in-app confirmation warns you about this specifically before you confirm.
• Correct or change anything. Every setting, and most extracted slip fields, can be edited directly in the app.
• Opt out of anything public. The public profile, notifications, and posting to the feed are all separately opt-in — off by default.

For as long as your account exists. Deleting your account (see above) deletes it immediately and permanently — we don’t keep a backup copy around “just in case” once you’ve asked us to remove it.

We use a session cookie (set by our authentication provider) to keep you signed in, and your browser’s local storage to remember your language preference and a few other settings. We don’t use any advertising cookies, and never sell or share data for advertising purposes.

We do use one analytics cookie — PostHog, hosted on EU servers — to understand how BetScanr is actually used (which features get used, where people drop off) so we can improve it. This is entirely opt-in: you’ll see a banner the first time you visit asking you to accept or reject it, and nothing loads until you accept. It never sees your email, name, or any bet-slip content — only which pages/features you use, tied to a random account ID. You can decline it at any time and the app works exactly the same either way.

BetScanr isn’t intended for anyone under 18, given its subject matter. We don’t knowingly collect data from anyone under that age.

If this changes in any meaningful way, we’ll update the date at the top of this page. Continuing to use BetScanr after a change means you’ve accepted the update.

Questions about your data, or want help with something the in-app export/delete tools don’t cover? Reach out at support@betscanr.com.