78/100

High evidence

ProblemPublished recordSportsProblem Space

LeBron Sues AI Sports-Betting Analytics App Alleging Bogus Endorsement

Truvace record
TRV-2026-3024raw data (JSON)
Version
v3Sources changed
First published
Evidence type
Regulatory or legal action
Sources
3 sourcesJournalism ×3
sha256
daee72cca054…check it

Lebron James sued PlayVision, alleging the company stole his name and likeness to make consumers believe he endorsed a sports-betting analytics app. NBA legend LeBron James is taking an AI sports-betting analytics app dubbed Bron to court, accusing the startup behind the tool of stealing his name and likeness to make consumers believe he endorsed it. James' lawsuit, filed Tuesday in Manhattan fed

The problem

LeBron James sued PlayVision in Manhattan federal court, alleging its Bron betting app used an AI-generated version of him, speaking in his voice, in an ad that drew a million views in a day and falsely implied his endorsement.

What this doesn’t fix

The claims are allegations in a complaint; PlayVision had not responded to requests for comment and no ruling has been reported.

Sources

3 on file
  1. Business Insiderbusinessinsider.com
    Journalism2026-11-17
  2. KABC-TVabc7.com
    Journalism2026-11-18
  3. Essentially Sportsessentiallysports.com
    Journalism2026-11-18

Cite this record

v3

Truvace Impact Record TRV-2026-3024, v3: “LeBron Sues AI Sports-Betting Analytics App Alleging Bogus Endorsement.” Truvace, 2026-11-19. /record/TRV-2026-3024 (accessed on the day you copy it). sha256 daee72cca05473f4…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Sources changedv3daee72cca054…

    Corroborated: Essentially Sports reported the same story.

  2. Sources changedv27f6c998012ca…

    Corroborated: KABC-TV reported the same story.

  3. Publishedv1e103131fb188…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3024 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.