Download Markdown

EventheOdds.ai - Legal Briefing Document

Prepared for: Legal Counsel Confidential

Date: February 2026

Re: Platform Overview, Liability Analysis, and Compliance Review

Executive Summary

EventheOdds.ai is an educational sports analytics platform that teaches statistical analysis, probability theory, and data-driven decision-making using historical sports market data. The platform explicitly does NOT provide betting picks, gambling facilitation, or financial advice.

Key Legal Positioning:

1. Business Model

1.1 What We Sell

TierPriceWhat User Gets
Pro$20/moAI-powered backtesting, strategy simulation, historical data analysis
Elite$200/moAll Pro features + API access, custom data feeds, real-time market data
Enterprise/ShellCustomDirect database access via restricted shell account for data science education

1.2 The "Shell Account" Feature (Enterprise)

For advanced users (typically data science students, researchers, or analytics professionals), we provide:

Technical Restrictions:

1.3 What's In The Database

Data TypeRecordsPurpose
Historical games180,000+Backtesting simulations
Historical odds2.3M+ player propsLine movement education
Final scores95,000+Strategy validation
Team/player metadata50,000+Context for analysis

Critical: All odds data is historical (games already completed). We do NOT provide real-time odds for games that can still be bet on.

2. Competitive Differentiation

2.1 What Competitors Do (and why we're different)

Competitor TypeTheir ModelOur Difference
Tipsters/CappersSell "picks" for upcoming gamesWe don't provide picks - we teach methodology
Prediction sites"Lock of the day" guaranteesWe explicitly disclaim all guarantees
Data vendorsSell real-time odds APIsWe focus on historical data for education
Betting toolsCalculators for active bettingWe provide simulation only

2.2 Our Target Audience

We target analytically-minded individuals who want to:

We explicitly do NOT target: Gamblers looking for "hot picks," people seeking guaranteed returns, or anyone looking to "beat the books."

3. Existing Legal Safeguards

3.1 Disclaimer Page (/disclaimer)

Prominently displayed, includes:

3.2 AI Chat Guardrails

Our AI system has built-in pattern detection that automatically:

TriggerSystem Response
User asks for "picks"Refuses, explains why, redirects to education
User shows signs of chasing lossesStops conversation, provides gambling hotline
User asks about betting with savings/loansRefuses, warns about dangers
User asks about evading betting limitsRefuses, explains illegality
Multiple problem gambling signsEmergency intervention response

All guardrail triggers are logged for compliance review.

3.3 Terms of Service

Users must acknowledge:

4. Data Sources & Licensing

ProviderData TypeLicense Status
SportsGameOdds APIHistorical odds, propsPaid API subscription (Pro tier)
Public sports dataScores, schedulesPublic domain
Kaggle datasetsHistorical research dataOpen license

We do NOT: Scrape sportsbook websites without permission, use data obtained through ToS violations, or resell real-time odds feeds.

5. Potential Liability Concerns

5.1 Risk Areas

RiskMitigation
User loses money bettingDisclaimers; we don't recommend bets; educational framing
Gambling addiction claimsGuardrails detect & redirect; NCPG resources; we don't facilitate bets
"Prediction accuracy" claimsAll marketing says "hypothetical"; no win rate guarantees
Underage usersAge verification at signup; ToS requires 18+/21+
Restricted jurisdictionsGeo-blocking for certain states/countries if needed

5.2 Questions for Counsel

  1. Shell account liability - If a user learns SQL from us, then uses that skill to build betting models elsewhere, are we liable?
  2. Educational vs. gambling service line - At what point does "teaching sports analytics" become "providing gambling tools"?
  3. State-by-state compliance - Do we need different disclaimers or restrictions for states with strict gambling laws (Utah, etc.)?
  4. Affiliate/advertising risk - If we later add sportsbook affiliate links, does that change our educational positioning?
  5. International users - What disclaimers needed for UK (Gambling Commission), EU (GDPR + gambling), Australia (ACMA)?

6. Technical Architecture

[User Browser]
      |
      v
[Next.js Web App] -- eventheodds.ai
      |
      |---> [AI Chat Service] <-- Guardrails filter all messages
      |
      |---> [Backtesting Engine] <-- Historical data only
      |
      \---> [PostgreSQL Database]
              |
              |-- SportsGame (180K games)
              |-- PlayerPropLine (2.3M props)
              |-- GameOdds (32K records)
              \-- 110+ analytics tables

[Enterprise Shell Users]
      |
      v
[Restricted Shell] ---> [Read-Only DB View]
      |
      \-- Jailed environment, no write access, logged queries
    

7. Sample User Journey (Educational Framing)

User Goal: Learn if "fading the public" is a valid strategy

Platform Experience:

  1. User logs in, opens Strategy Builder
  2. Enters hypothesis: "Bet against teams with >70% public backing"
  3. System runs simulation on 5,000 historical games
  4. Results show: "52.1% win rate, -1.2% ROI (statistically insignificant)"
  5. AI explains: "Your hypothesis shows no edge. Here's why..."
  6. User learns: Public sentiment alone doesn't predict outcomes

What did NOT happen:

8. Recommended Legal Actions

Immediate

Before Shell Access Launch

Ongoing


Platform: https://eventheodds.ai
Support: support@eventheodds.ai

This document is confidential and prepared for legal consultation purposes.