AppLovin Sues Unity Over Ad Data: What Indian Ad-Funded Studios Should Check This Week

This week, two of the companies most Indian mobile studios rely on to earn money from ads ended up in court against each other. AppLovin has sued Unity in the Superior Court of California in San Francisco (case CPF-26-520212), alleging that Unity's Ad Quality SDK collected data from AppLovin's ad auctions without permission. A hearing was set for September 30, 2026, and a separate arbitration at JAMS is running in parallel. If you ship an ad-supported game from India, this is worth ten minutes of your time, even though you are not a party to it.

What AppLovin alleges. According to the filing as reported by trade press, AppLovin claims five things: breach of contract, intentional interference with contractual relations, intentional interference with prospective economic advantage, trade secret misappropriation, and unfair competition under California law. The core claim is that Ad Quality, a tool meant to screen ads for bad content, captured per-impression data from AppLovin's MAX mediation: creative assets, advertiser identifiers, per-impression revenue, mediation waterfall details, device and user identifiers, and even screen touch coordinates and timing. AppLovin says Unity used that to model its bidding behaviour. It wants collection switched off within five business days and the SDK changed within 30 days.

What Unity says. Unity calls the suit anticompetitive retaliation by a dominant incumbent. It says Ad Quality is a small, free tool that collects data only from publishers' own apps or devices with express permission, and that its ad performance gains come from other factors. Unity has reportedly offered to remotely disable collection for MAX auctions and to ship a Unity Ads SDK without Ad Quality within 30 days. AppLovin reportedly rejected that offer over data already collected. None of this has been decided by a court yet, and both sides' claims are allegations and positions, not findings.

Why this matters in India. Our market is ad-first. Most Indian casual and hyper-casual titles earn through rewarded video, interstitials and banners, not in-app purchases, and most of them mediate through MAX, LevelPlay or AdMob. The reporting says the dispute covers data from MAX-mediated auctions, LevelPlay and Google's AdMob. Public documents do not say how many apps or studios are affected, so nobody outside the companies can give you an honest number. What we can say is that mediation is the layer where a small studio's revenue is decided every single impression.

What a small studio can do this week. First, list every ad and analytics SDK in your build, including the ones pulled in by other SDKs. Second, read the data-sharing and permissions terms of each one; ad quality and brand-safety tools are optional in most mediation setups, so check whether you have switched one on. Third, make sure your privacy policy and consent flow describe what is actually collected, because India's Digital Personal Data Protection regime puts the duty on you as the app owner, not on the SDK vendor. Fourth, do not rip out a mediation partner in a panic. Test any change on a small share of traffic and watch eCPM and fill rate for a week before rolling it out.

The bigger lesson. When two infrastructure giants fight, the cost is usually paid in uncertainty by the studios in the middle. Keeping your ad stack modular, having at least two mediation options you have actually tested, and knowing exactly what each SDK sends out of your app is cheap insurance. We will keep watching how the hearing and the arbitration play out.