What looks like a technical squabble over the phrase “data leakage” has turned into a courtroom fight between two mobile advertising heavyweights. On Sept. 29, it emerged that AppLovin had sued Unity in San Francisco, claiming Unity’s Ad Quality SDK improperly collected information generated when AppLovin won and served ads.
Unity denies the allegations and calls the lawsuit an attempt by a dominant rival to slow a growing competitor. The filings turn on a question the ad-tech industry is only beginning to answer: where does observation of an ad auction end and an opponent’s proprietary data begin?
What AppLovin alleges
AppLovin’s central claim is that Unity’s Ad Quality software extracted signals from auctions Unity did not win — and in some cases auctions in which it did not even participate. A bidder ordinarily learns how its own bid fared, but AppLovin says that does not create a right to assemble a record of the creative another bidder served, the user who saw it, the revenue tied to the impression and the engagement that followed.
The filing adds technical detail: AppLovin says Unity uses AppLovin-specific connector scripts, interacts with callbacks inside AppLovin’s SDK and subscribes to an internal channel for impression and revenue events. It also alleges the collection can be configured remotely on an app-by-app basis.
AppLovin further says, “on information and belief,” that Unity could use the data to train its advertising models and model AppLovin’s ad decisions. That claim is disputed and has not been adjudicated.
Unity’s response
Unity rejects the allegations and says Ad Quality gets information from publishers’ apps or users’ devices with publisher permission, not “from AppLovin.” It also points to AppLovin’s own ad-review tool, describing Ad Review as “far more intrusive” than the technology at issue. AppLovin disputes the comparison, saying its product is limited to MAX-mediated impressions and is not used to train its advertising models.
Unity has said it could remotely stop Ad Quality from collecting data related to MAX-mediated auctions within five business days. AppLovin says that offer was contingent on resolving the dispute and would not address information already collected.
Why the fight matters for everyone else
Mobile monetization now runs on a crowded stack: multiple rival SDKs, mediation platforms and demand sources operating inside the same app. The AppLovin–Unity case is effectively asking how much information one participant can legitimately extract from that shared environment, especially as the same companies use transaction data to train machine-learning systems that compete against each other.
AppLovin’s filing claims Unity’s Ad Quality technology supports data collection involving other ad networks, including Google, Liftoff, Digital Turbine and InMobi. That remains an allegation, not a judicial finding, but it shows why the case could sweep beyond the two litigants.
What marketers should watch
- Signal boundaries: whether courts treat impression-level revenue and engagement data as observable or proprietary.
- SDK consent: how publisher permission interacts with ad-network data rights in mediation setups.
- AI training claims: whether rivals can use transaction data to build competing optimization models.
For marketing teams running programmatic or app campaigns, the practical step is a data-flow audit: know which SDKs receive callbacks, what they are permitted to learn from won and lost impressions, and whether those terms hold up under the standard this case may set.
Source: Digiday
