Privacy Policy
What the current BetTheGap application processes, why it is needed, and how to contact us.
Information we process
- Full name (when provided), account email, user identifier and authentication/session information. Email/password authentication is handled by Supabase Auth; application logs are designed to omit passwords and tokens.
- Your country/province or state, timezone, odds format, selected operator feeds, preferred leagues, bankroll, default stake, thresholds, reference books, weights and devig preference.
- Pinned opportunity identities, last-known price snapshots and timestamps.
- Subscription plan/status, billing period, cancellation state, billing interval and provider customer/subscription identifiers, where a billing integration has been used.
- Structured cancellation reasons, optional feedback, and account/subscription-linked cancellation-funnel events used to improve onboarding and support.
- Affiliate applications, versioned program-term acceptance, a first-party 30-day referral token and pseudonymous visitor identifier, referral attribution, commission and manual payout records where you participate. Referral visits are deduplicated; affiliates see anonymous referral labels rather than customer identities or payment information.
- Information you voluntarily include in a human support email.
- Operational/security metadata needed to serve and protect requests, such as request time, route, status and connection information processed by hosting providers.
BetTheGap does not accept betting funds, store raw payment-card details, connect to your sportsbook account, or collect your sportsbook passwords or wager history. Bankroll and stakes are values you choose to enter, not bank-account connections.
Why we use it
We use account information to personalize your private greeting, authenticate you, restore preferences across devices, restrict feature access, maintain pins, provide requested tools, synchronize verified billing state, respond to support and prevent misuse. Selected feed keys and markets determine which odds we request. We do not send your account email or user identifier to The Odds API as part of an odds request.
Services involved
- Supabase: hosted Auth and database storage for account preferences, pins and normalized subscription state; row-level security restricts access to your account data.
- Cloudflare: application hosting, network delivery and security, including Turnstile bot protection when enabled. Request/session data and challenge responses pass through this infrastructure.
- Stripe: hosted billing/payment interfaces and subscription events when billing is used. Standard Stripe processes payment details under its own privacy notices. We retain subscription/Checkout identifiers, terms acceptance/version and private hashed payment-identity history to enforce one-trial eligibility; we do not store raw card details.
- Resend: automated account email through Supabase SMTP, and trial-start billing confirmations. Private notification records retain delivery status and the message needed for safe retries.
- iCloud Custom Email Domain: human/business support mailbox delivery. Human support is separate from automated noreply emails.
- The Odds API: sportsbook/operator price data. Requests include selected sport/event/market and feed keys, not your Supabase account identity.
These services may process data in countries outside your residence according to their service terms and safeguards.
Cookies, sharing and analytics
Essential authentication cookies/session storage keep you signed in and restore access. You can sign out or clear browser storage; this removes the browser session but does not delete your account. The current application does not implement advertising trackers or a third-party marketing analytics SDK. Infrastructure providers may still process operational request metadata.
We do not sell personal information. We share necessary information with the services above to operate the platform, and may disclose information where legally required or necessary to investigate abuse and protect rights. We do not publish your saved settings or pins to other users.
Retention and your choices
Account settings, pins and subscription records remain stored while the account is maintained; unpinning removes the selected pin. An automatic deletion schedule for inactive accounts has not been implemented. Operational logs and backups follow the respective providers’ configured retention. We do not promise a fixed retention/deletion deadline that has not been verified.
You can update your name and settings, remove pins and sign out in the app. Contact support@betthegap.com to request access, correction, export or account deletion. We may need to verify ownership. Applicable legal, security and billing-record obligations may require retaining some records. Self-service account deletion/export is not currently available.
Security, age and contact
We use HTTPS, authenticated account access, database ownership policies and server-only privileged billing credentials. No system is completely secure. The service is intended for users who meet their jurisdiction’s legal gambling age, not children. Report suspected unauthorized access or send privacy questions to support@betthegap.com. Material policy changes will be identified with an updated date and appropriate notice where required.