Key Notes
- AppLovin initiated arbitration and sought California court intervention over alleged Ad Quality data collection and competitive model training, claims Unity disputes.
- Unity offered a five-business-day shutdown for MAX-related collection, but AppLovin rejected a settlement it said left past data use and alleged model training unresolved.
- The court has refused temporary restrictions without deciding the underlying claims, leaving mobile studios watching for changes to their advertising tools and contracts.
AppLovin has taken Unity to court over allegations that its Ad Quality SDK collected advertising information without permission, opening a legal battle over data generated inside mobile games. The dispute involves both a California court application and separate arbitration, with AppLovin challenging how a competing advertising provider can use information about the ads it serves.
The proceedings began in late September. Unity denies wrongdoing and says publishers choose to share data through a product intended to keep harmful ads out of games. The conflict has since produced an initial court decision: AppLovin was refused the temporary restrictions it requested, while the underlying claims remain unresolved.
AppLovin Challenges Access to Its Advertising Data
According to Digiday’s reporting, AppLovin alleges that Unity’s software accessed information about AppLovin-served advertisements, including creative assets, audience engagement, user and device details, and revenue from individual impressions. AppLovin also claims that Unity could use those signals to train models that anticipate its bidding decisions and compete against it in advertising auctions.
The alleged model training has not been established. It is part of AppLovin’s case, rather than a finding that Unity copied a rival’s bidding strategy. That distinction is central to a dispute in which the companies disagree about both permission to collect information and the purposes for which it can be used.
The legal routes also serve different functions. PPC Land’s filing analysis dates the JAMS arbitration demand to September 27 and the San Francisco court petition to September 28. The arbitration raises contract, trade-secret, business-interference, and California unfair-competition claims. AppLovin sought court intervention to restrict collection while those claims proceeded.
Unity Rejects the Claims as Settlement Talks Fail
Unity describes Ad Quality as a free product that helps publishers identify inappropriate or harmful advertising. Its response to Digiday characterized AppLovin’s actions as an attempt by a dominant incumbent to slow a growing competitor. Unity maintains that developers authorize the data sharing and disputes the suggestion that Ad Quality explains its improved advertising performance.
Attempts to settle preceded the filings. AppLovin sent a demand in August, and Unity later offered to remotely disable collection relating to auctions on AppLovin’s MAX platform within five business days. The offer was tied to AppLovin agreeing that the dispute had been resolved.
AppLovin rejected that proposal because it did not resolve its concerns about information already collected or models allegedly trained on it. AppLovin also disputed the scope of a MAX-only solution, since its ads can be served through other mediation systems. A prospective shutdown and a remedy for past data use were therefore separate points of contention.
Mobile Studios Sit Between Ad Quality and Auction Competition
For game developers, mediation is the infrastructure that brings multiple advertising networks into an app. AppLovin’s MAX platform describes a real-time auction in which networks bid for an impression. It supports formats such as rewarded video, where a player chooses to watch an ad for an in-game benefit, and interstitials shown between parts of the experience.
Ad inspection addresses another need. Unity’s documentation describes reviewing creatives, analyzing player journeys, reporting problematic ads, and setting content rules. Its documented metrics include impression-level revenue, clicks, ad sources, and creative identifiers. Those capabilities explain why a studio might install the product; they do not establish whether any disputed collection was authorized.
Our reading is that the conflict exposes overlapping roles in mobile monetization: providers help studios evaluate advertising while also competing to sell it. A developer can want visibility into disruptive ads and competitive bidding for revenue at the same time. The legal question is where contracts place the boundary around information available inside that shared environment.
The refusal of AppLovin’s temporary restraining order does not decide that boundary or require studios to change their SDK integrations. It leaves the broader dispute to continue, with any later restrictions or software changes potentially affecting how game publishers combine monetization and ad-quality services.
