Two of mobile advertising’s biggest platforms have moved a long-running rivalry into a California courtroom. AppLovin is asking the Superior Court of California in San Francisco for a temporary restraining order against Unity over what an advertising SDK can see and do with auction data. The request is part of a wider dispute that is also heading to arbitration.
What the filing claims
AppLovin alleges that Unity’s Ad Quality SDK improperly collected data relating to ads AppLovin served, including information about creatives, users, devices, impression revenue and engagement. The company further claims, on information and belief, that Unity used this material to train models that compete in mobile advertising auctions, including modeling AppLovin’s own ad decisions. In its court papers, AppLovin says Unity used AppLovin’s “own output to train those models and to model AppLovin’s ad decisions.” The allegations have not been adjudicated.
What AppLovin is asking for
- Prohibit Unity from collecting, intercepting, extracting, using or disclosing what AppLovin defines as “Protected Data.”
- Require Unity to disable the collection within five business days.
- Require Unity to modify its Ad Quality SDK within 30 days.
The requested relief covers data from ads AppLovin wins and serves, plus information derived from its auctions, such as clearing prices, auction identifiers, impression identifiers and its mediation waterfall. It would not stop Unity from collecting data on ads Unity itself wins and serves.
Unity’s side of the story
Unity intends to appear and oppose the application. According to the filing, Unity has argued that AppLovin runs a comparable product, Ad Review, formerly SafeDK, which Unity called “far more intrusive” than its own Ad Quality product. AppLovin rejects that comparison, saying Ad Review only handles impressions mediated through MAX and is used to spot problematic ads rather than train models.
Why marketers should pay attention
This is not just a legal fight between two vendors. It raises a practical question for mobile app publishers and brands: how much of your auction and mediation data is visible to partners, and what can they do with it? The dispute touches bidstream data, SDK permissions and the boundary between measurement and competitive intelligence.
The papers show the dispute escalated from an August cease-and-desist demand. Unity later proposed winding down Ad Quality’s collection for MAX-mediated auctions, but AppLovin rejected the offer because it did not address previously collected data, models allegedly trained on it, or data from other mediation platforms such as Unity’s LevelPlay and Google’s AdMob.
Action for marketing teams
Marketers do not need to take sides to use this moment. Review the SDKs and mediation partners in your app stack, ask how bidstream and auction data is reused, and update vendor agreements to cover model training and retention. A simple data-flow lens helps: what is collected, who can use it, for how long, and whether it feeds another ad platform’s optimization.
A hearing was scheduled for Sept. 29 at 11 a.m. PT. The outcome could influence how mobile ad platforms write data terms across the industry.
Source: Digiday
