Search Results For google

Scolding teacher

I have small children and, like any reasonably competent parent, I take an interest in monitoring their Internet usage. In particular, I am sensitive to what ad content they are being served and which sites they visit that might try to misuse their information. My son even uses Chromebooks at his elementary school, which underscores this concern for me, as I can’t always be present to watch what he does online. However, also like any other reasonably competent parent, I trust his school and his teacher to make good choices about what he is allowed to do online when I am not there to watch him. And so it is that I am both interested in and rather perplexed by what has EFF so worked up in its FTC complaint alleging privacy “violations” in the “Google for Education” program.

EFF alleges three “unfair or deceptive” acts that would subject Google to remedies under Section 5 of the FTCA: (1) Students logged into “Google for Education” accounts have their non-educational behavior individually tracked (e.g. performing general web searches, browsing YouTube, etc.); (2) the Chromebooks distributed as part of the “Google for Education” program have the “Chrome Sync” feature turned on by default (ostensibly in a terribly diabolical effort to give students a seamless experience between using the Chromebooks at home and at school); and (3) the school administrators running particular instances of “Google for Education” have the ability to share student geolocation information with third-party websites. Each of these violations, claims EFF, violates the K-12 School Service Provider Pledge to Safeguard Student Privacy (“Pledge”) that was authored by the Future of Privacy Forum and Software & Information Industry Association, and to which Google is a signatory. According to EFF, Google included references to its signature in its “Google for Education” marketing materials, thereby creating the expectation in parents that it would adhere to the principles, failed to do so, and thus should be punished.

The TL;DR version: EFF appears to be making some simple interpretational errors — it believes that the scope of the Pledge covers any student activity and data generated while a student is logged into a Google account. As the rest of this post will (hopefully) make clear, however, the Pledge, though ambiguous, is more reasonably read as limiting Google’s obligations to instances where a student is using  Google for Education apps, and does not apply to instances where the student is using non-Education apps — whether she is logged on using her Education account or not.

The key problem, as EFF sees it, is that Google “use[d] and share[d] … student personal information beyond what is needed for education.” So nice of them to settle complex business and educational decisions for the world! Who knew it was so easy to determine exactly what is needed for educational purposes!

Case in point: EFF feels that Google’s use of anonymous and aggregated student data in order to improve its education apps is not an educational purpose. Seriously? How can that not be useful for educational purposes — to improve its educational apps!?

And, according to EFF, the fact that Chrome Sync is ‘on’ by default in the Chromebooks only amplifies the harm caused by the non-Education data tracking because, when the students log in outside of school, their behavior can be correlated with their in-school behavior. Of course, this ignores the fact that the same limitations apply to the tracking — it happens only on non-Education apps. Thus, the Chrome Sync objection is somehow vaguely based on geography. The fact that Google can correlate an individual student’s viewing of a Neil DeGrasse Tyson video in a computer lab at school with her later finishing that video at home is somehow really bad (or so EFF claims).

EFF also takes issue with the fact that school administrators are allowed to turn on a setting enabling third parties to access the geolocation data of Google education apps users.

The complaint is fairly sparse on this issue — and the claim is essentially limited to the assertion that “[s]haring a student’s physical location with third parties is unquestionably sharing personal information beyond what is needed for educational purposes[.]”  While it’s possible that third-parties could misuse student data, a presumption that it is per se outside of any educational use for third-parties to have geolocation access at all strikes me as unreasonable.

Geolocation data, particularly on mobile devices, could allow for any number of positive and negative uses, and without more it’s hard to really take EFF’s premature concern all that seriously. Did they conduct a study demonstrating that geolocation data can serve no educational purpose or that the feature is frequently abused? Sadly, it seems doubtful. Instead, they appear to be relying upon the rather loose definition of likely harm that we have seen in FTC actions in other contexts ( more on this problem here).  

Who decides what ambiguous terms mean?

The bigger issue, however, is the ambiguity latent in the Pledge and how that ambiguity is being exploited to criticize Google. The complaint barely conceals EFF’s eagerness, and gives one the distinct feeling that the Pledge and this complaint are part of a long game. Everyone knows that Google’s entire existence revolves around the clever and innovative employment of large data sets. When Google announced that it was interested in working with schools to provide technology to students, I can only imagine how the anti-big-data-for-any-commercial-purpose crowd sat up and took notice, just waiting to pounce as soon as an opportunity, no matter how tenuous, presented itself.

EFF notes that “[u]nlike Microsoft and numerous other developers of digital curriculum and classroom management software, Google did not initially sign onto the Student Privacy Pledge with the first round of signatories when it was announced in the fall of 2014.” Apparently, it is an indictment of Google that it hesitated to adopt an external statement of privacy principles that was authored by a group that had no involvement with Google’s internal operations or business realities. EFF goes on to note that it was only after “sustained criticism” that Google “reluctantly” signed the pledge. So the company is badgered into signing a pledge that it was reluctant to sign in the first place (almost certainly for exactly these sorts of reasons), and is now being skewered by the proponents of the pledge that it was reluctant to sign. Somehow I can’t help but get the sense that this FTC complaint was drafted even before Google signed the Pledge.

According to the Pledge, Google promised to:

  1. “Not collect, maintain, use or share student personal information beyond that needed for authorized educational/school purposes, or as authorized by the parent/student.”
  2. “Not build a personal profile of a student other than for supporting authorized educational/school purposes or as authorized by the parent/student.”
  3. “Not knowingly retain student personal information beyond the time period required to support the authorized educational/school purposes, or as authorized by the parent/student.”

EFF interprets “educational purpose” as anything a student does while logged into her education account, and by extension, any of the even non-educational activity will count as “student personal information.” I think that a fair reading of the Pledge undermines this position, however, and that the correct interpretation of the Pledge is that “educational purpose” and “student personal information” are more tightly coupled such that Google’s ability to collect student data is only circumscribed when the student is actually using the Google for Education Apps.

So what counts as “student personal information” in the pledge? “Student personal information” is “personally identifiable information as well as other information when it is both collected and maintained on an individual level and is linked to personally identifiable information.”  Although this is fairly broad, it is limited by the definition of “Educational/School purposes” which are “services or functions that customarily take place at the direction of the educational institution/agency or their teacher/employee, for which the institutions or agency would otherwise use its own employees, and that aid in the administration or improvement of educational and school activities.” (emphasis added).

This limitation in the Pledge essentially sinks EFF’s complaint. A major part of EFF’s gripe is that when the students interact with non-Education services, Google tracks them. However, the Pledge limits the collection of information only in contexts where “the institutions or agency would otherwise use its own employees” — a definition that clearly does not extend to general Internet usage. This definition would reasonably cover activities like administering classes, tests, and lessons. This definition would not cover activity such as general searches, watching videos on YouTube and the like. Key to EFF’s error is that the pledge is not operative on accounts but around activity — in particular educational activity “for which the institutions or agency would otherwise use its own employees.”

To interpret Google’s activity in the way that EFF does is to treat the Pledge as a promise never to do anything, ever, with the data of a student logged into an education account, whether generated as part of Education apps or otherwise. That just can’t be right. Thinking through the implications of EFF’s complaint, the ultimate end has to be that Google needs to obtain a permission slip from parents before offering access to Google for Education accounts. Administrators and Google are just not allowed to provision any services otherwise.

And here is where the long game comes in. EFF and its peers induced Google to sign the Pledge all the while understanding that their interpretation would necessarily require a re-write of Google’s business model.  But not only is this sneaky, it’s also ridiculous. By way of analogy, this would be similar to allowing parents an individual say over what textbooks or other curricular materials their children are allowed to access. This would either allow for a total veto by a single parent, or else would require certain students to be frozen out of participating in homework and other activities being performed with a Google for Education app. That may work for Yale students hiding from microaggressions, but it makes no sense to read such a contentious and questionable educational model into Google’s widely-offered apps.

I think a more reasonable interpretation should prevail. The privacy pledge is meant to govern the use of student data while that student is acting as a student — which in the case of Google for Education apps would mean while using said apps. Plenty of other Google apps could be used for educational purposes, but Google is intentionally delineating a sensible dividing line in order to avoid exactly this sort of problem (as well as problems that could arise under other laws directed at student activity, like COPPA, most notably). It is entirely unreasonable to presume that Google, by virtue of its socially desirable behavior of enabling students to have ready access to technology, is thereby prevented from tracking individuals’ behavior on non-Education apps as it chooses to define them.

What is the Harm?

According to EFF, there are two primary problems with Google’s gathering and use of student data: gathering and using individual data in non-Education apps, and gathering and using anonymized and aggregated data in the Education apps. So what is the evil end to which Google uses this non-Education gathered data?

“Google not only collects and stores the vast array of student data described above, but uses it for its own purposes such as improving Google products and serving targeted advertising (within non-Education Google services)”

The horrors! Google wants to use student behavior to improve its services! And yes, I get it, everyone hates ads — I hate ads too — but at some point you need to learn to accept that the wealth of nominally free apps available to every user is underwritten by the ad-sphere. So if Google is using the non-Education behavior of students to gain valuable insights that it can monetize and thereby subsidize its services, so what? This is life in the twenty-first century, and until everyone collectively decides that we prefer to pay for services up front, we had better get used to being tracked and monetized by advertisers.

But as noted above, whether you think Google should or shouldn’t be gathering this data, it seems clear that the data generated from use of non-Education apps doesn’t fall under the Pledge’s purview. Thus, perhaps sensing the problems in its non-Education use argument, EFF also half-heartedly attempts to demonize certain data practices that Google employs in the Education context. In short, Google aggregates and anonymizes the usage data of the Google for Education apps, and, according to EFF, this is a violation of the Pledge:

“Aggregating and anonymizing students’ browsing history does not change the intensely private nature of the data … such that Google should be free to use it[.]”

Again the “harm” is that Google actually wants to improve the Educational apps:  “Google has acknowledged that it collects, maintains, and uses student information via Chrome Sync (in aggregated and anonymized form) for the purpose of improving Google products”

This of course doesn’t violate the Pledge. After all, signatories to the Pledge promise only that they will “[n]ot collect, maintain, use or share student personal information beyond that needed for authorized educational/school purposes.” It’s eminently reasonable to include the improvement of the provisioned services as part of an “authorized educational … purpose[.]” And by ensuring that the data is anonymized and aggregated, Google is clearly acknowledging that some limits are appropriate in the education context — that it doesn’t need to collect individual and identifiable personal information for education purposes — but that improving its education products the same way it improves all its products is an educational purpose.

How are the harms enhanced by Chrome Sync? Honestly, it’s not really clear from EFF’s complaint. I believe that the core of EFF’s gripe (at least here) has to do with how the two data gathering activities may be correlated together. Google has ChromeSync enabled by default, so when the students sign on at different locations, the Education apps usage is recorded and grouped (still anonymously) for service improvement alongside non-Education use. And the presence of these two data sets being generated side-by-side creates the potential to track students in the educational capacity by correlating with information generated in their non-educational capacity.

Maybe there are potential flaws in the manner in which the data is anonymized. Obviously EFF thinks anonymized data won’t stay anonymized. That is a contentious view, to say the least, but regardless, it is in no way compelled by the Pledge. But more to the point, merely having both data sets does not do anything that clearly violates the Pledge.

The End Game

So what do groups like EFF actually want? It’s important to consider the effects on social welfare that this approach to privacy takes, and its context. First, the Pledge was overwhelmingly designed for and signed by pure education companies, and not large organizations like Google, Apple, or Microsoft — thus the nature of the Pledge itself is more or less ill-fitted to a multi-faceted business model. If we follow the logical conclusions of this complaint, a company like Google would face an undesirable choice: On the one hand, it can provide hardware to schools at zero cost or heavily subsidized prices, and also provide a suite of useful educational applications. However, as part of this socially desirable donation, it must also place a virtual invisibility shield around students once they’ve signed into their accounts. From that point on, regardless of what service they use — even non-educational ones — Google is prevented from using any data students generate. At this point, one has to question Google’s incentive to remove huge swaths of the population from its ability to gather data. If Google did nothing but provide the hardware, it could simply leave its free services online as-is, and let schools adopt or not adopt them as they wish (subject of course to extant legislation such as COPPA) — thereby allowing itself to possibly collect even more data on the same students.

On the other hand, if not Google, then surely many other companies would think twice before wading into this quagmire, or, when they do, they might offer severely limited services. For instance, one way of complying with EFF’s view of how the Pledge works would be to shut off access to all non-Education services. So, students logged into an education account could only access the word processing and email services, but would be prevented from accessing YouTube, web search and other services — and consequently suffer from a limitation of potentially novel educational options.

EFF goes on to cite numerous FTC enforcement actions and settlements from recent years. But all of the cited examples have one thing in common that the current complaint does not: they all are violations of § 5 for explicit statements or representations made by a company to consumers. EFF’s complaint, on the other hand, is based on a particular interpretation of an ambiguous document generally drafted, and outside of the the complicated business practice at issue. What counts as “student information” when a user employs a general purpose machine for both educational purposes and non-educational purposes?  The Pledge — at least the sections that EFF relies upon in its complaint — is far from clear and doesn’t cover Google’s behavior in an obvious manner.

Of course, the whole complaint presumes that the nature of Google’s services was somehow unfair or deceptive to parents — thus implying that there was at least some material reliance on the Pledge in parental decision making. However, this misses a crucial detail: it is the school administrators who contract with Google for the Chromebooks and Google for Education services, and not the parents or the students.  Then again, maybe EFF doesn’t care and it is, as I suggest above, just interested in a long game whereby it can shoehorn Google’s services into some new sort of privacy regime. This isn’t all that unusual, as we have seen even the White House in other contexts willing to rewrite business practices wholly apart from the realities of privacy “harms.”

But in the end, this approach to privacy is just a very efficient way to discover the lowest common denominator in charity. If it even decides to brave the possible privacy suits, Google and other similarly situated companies will provide the barest access to the most limited services in order to avoid extensive liability from ambiguous pledges. And, perhaps even worse for overall social welfare, using the law to force compliance with voluntarily enacted, ambiguous codes of conduct is a sure-fire way to make sure that there are fewer and more limited codes of conduct in the future.

The precise details underlying the European Commission’s (EC) April 15 Statement of Objections (SO), the EC’s equivalent of an antitrust complaint, against Google, centered on the company’s promotion of its comparison shopping service (CSS), “Google Shopping,” have not yet been made public.  Nevertheless, the EC’s fact sheet describing the theory of the case is most discouraging to anyone who believes in economically sound, consumer welfare-oriented antitrust enforcement.   Put simply, the SO alleges that Google is “abusing its dominant position” in online search services throughout Europe by systematically positioning and prominently displaying its CSS in its general search result pages, “irrespective of its merits,” causing the Google CSS to achieve higher rates of growth than CSSs promoted by rivals.  According to the EC, this behavior “has a negative impact on consumers and innovation”.  Why so?  Because this “means that users do not necessarily see the most relevant shopping results in response to their queries, and that incentives to innovate from rivals are lowered as they know that however good their product, they will not benefit from the same prominence as Google’s product.”  (Emphasis added.)  The EC’s proposed solution?  “Google should treat its own comparison shopping services and those of rivals in the same way.”

The EC’s latest action may represent only “the tip of a Google EC antitrust iceberg,” since the EC has stated that it is continuing to investigate other aspects of Google’s behavior, including Google agreements with respect to the Android operating system, plus “the favourable treatment by Google in its general search results of other specialised search services, and concerns with regard to copying of rivals’ web content (known as ‘scraping’), advertising exclusivity and undue restrictions on advertisers.”  For today, I focus on the tip, leaving consideration of the bulk of the iceberg to future commentaries, as warranted.  (Truth on the Market has addressed Google-related antitrust issues previously — see, for example, here, here, and here.)

The EC’s April 15 Google SO is troublesome in multiple ways.

First, the claim that Google does not “necessarily” array the most relevant search results in a manner desired by consumers appears to be in tension with the findings of an exhaustive U.S. antitrust investigation of the company.  As U.S. Federal Trade Commissioner Josh Wright pointed out in a recent speech, the FTC’s 2013 “closing statement [in its Google investigation] indicates that Google’s so-called search bias did not, in fact, harm consumers; to the contrary, the evidence suggested that ‘Google likely benefited consumers by prominently displaying its vertical content on its search results page.’  The Commission reached this conclusion based upon, among other things, analyses of actual consumer behavior – so-called ‘click through’ data – which showed how consumers reacted to Google’s promotion of its vertical properties.”

Second, even assuming that Google’s search engine practices have weakened competing CSSs, that would not justify EC enforcement action against Google.  As Commissioner Wright also explained, the FTC “accepted arguments made by competing websites that Google’s practices injured them and strengthened Google’s market position, but correctly found that these were not relevant considerations in a proper antitrust analysis focused upon consumer welfare rather than harm to competitors.”  The EC should keep this in mind, given that, as former EC Competition Commissioner Joaquin Almunia emphasized, “[c]onsumer welfare is not just a catchy phrase.  It is the cornerstone, the guiding principle of EU competition policy.”

Third, and perhaps most fundamentally, although EC disclaims an interest in “interfere[ing] with” Google’s search engine algorithm, dictating an “equal treatment of competitors” result implicitly would require intrusive micromanagement of Google’s search engine – a search engine which is at the heart of the company’s success and has bestowed enormous welfare benefits on consumers and producers alike.  There is no reason to believe that EC policing of EC CSS listings to promote an “equal protection of competitors” mandate would result in a search experience that better serves consumers than the current Google policy.  Consistent with this point, in its 2013 Google closing statement, the FTC observed that it lacked the ability to “second-guess” product improvements that plausibly benefit consumers, and it stressed that “condemning legitimate product improvements risks harming consumers.”

Fourth, competing CSSs have every incentive to inform consumers if they believe that Google search results are somehow “inferior” to their offerings.  They are free to advertise and publicize the merits of their services, and third party intermediaries that rate browsers may be expected to report if Google Shopping consistently offers suboptimal consumer services.  In short, “the word will get out.”  Even in the absence of perfect information, consumers can readily at low cost browse alternative CSSs to determine whether they prefer their services to Google’s – “help is only a click away.”

Fifth, the most likely outcome of an EC “victory” in this case would be a reduced incentive for Google to invest in improving its search engine, knowing that its ability to monetize search engine improvements could be compromised by future EC decisions to prevent an improved search engine from harming rivals.  What’s worse, other developers of service platforms and other innovative business improvements would similarly “get the message” that it would not be worth their while to innovate to the point of dominance, because their returns to such innovation would be constrained.  In sum, companies in a wide variety of sectors would have less of an incentive to innovate, and this in turn would lead to reduced welfare gains and benefits to consumers.  This would yield (as the EC’s fact sheet put it) “a negative impact on consumers and innovation”, because companies across industries operating in Europe would know that if their product were too good, they would attract the EC’s attention and be put in their place.  In other words, a successful EC intervention here could spawn the very welfare losses (magnified across sectors) that the Commission cited as justification for reining in Google in the first place!

Finally, it should come as no surprise that a coalition of purveyors of competing search engines and online shopping sites lobbied hard for EC antitrust action against Google.  When government intervenes heavily and often in markets to “correct” perceived “abuses,” private actors have a strong incentive to expend resources on achieving government actions that disadvantage their rivals – resources that could otherwise have been used to compete more vigorously and effectively.  In short, the very existence of expansive regulatory schemes disincentivizes competition on the merits, and in that regard tends to undermine welfare.  Government officials should keep that firmly in mind when private actors urge them to act decisively to “cure” marketplace imperfections by limiting a rival’s freedom of action.

Let us hope that the EC takes these concerns to heart before taking further action against Google.

The Wall Street Journal reported yesterday that the FTC Bureau of Competition staff report to the commissioners in the Google antitrust investigation recommended that the Commission approve an antitrust suit against the company.

While this is excellent fodder for a few hours of Twitter hysteria, it takes more than 140 characters to delve into the nuances of a 20-month federal investigation. And the bottom line is, frankly, pretty ho-hum.

As I said recently,

One of life’s unfortunate certainties, as predictable as death and taxes, is this: regulators regulate.

The Bureau of Competition staff is made up of professional lawyers — many of them litigators, whose existence is predicated on there being actual, you know, litigation. If you believe in human fallibility at all, you have to expect that, when they err, FTC staff errs on the side of too much, rather than too little, enforcement.

So is it shocking that the FTC staff might recommend that the Commission undertake what would undoubtedly have been one of the agency’s most significant antitrust cases? Hardly.

Nor is it surprising that the commissioners might not always agree with staff. In fact, staff recommendations are ignored all the time, for better or worse. Here are just a few examples: R.J Reynolds/Brown & Williamson merger, POM Wonderful , Home Shopping Network/QVC merger, cigarette advertising. No doubt there are many, many more.

Regardless, it also bears pointing out that the staff did not recommend the FTC bring suit on the central issue of search bias “because of the strong procompetitive justifications Google has set forth”:

Complainants allege that Google’s conduct is anticompetitive because if forecloses alternative search platforms that might operate to constrain Google’s dominance in search and search advertising. Although it is a close call, we do not recommend that the Commission issue a complaint against Google for this conduct.

But this caveat is enormous. To report this as the FTC staff recommending a case is seriously misleading. Here they are forbearing from bringing 99% of the case against Google, and recommending suit on the marginal 1% issues. It would be more accurate to say, “FTC staff recommends no case against Google, except on a couple of minor issues which will be immediately settled.”

And in fact it was on just these minor issues that Google agreed to voluntary commitments to curtail some conduct when the FTC announced it was not bringing suit against the company.

The Wall Street Journal quotes some other language from the staff report bolstering the conclusion that this is a complex market, the conduct at issue was ambiguous (at worst), and supporting the central recommendation not to sue:

We are faced with a set of facts that can most plausibly be accounted for by a narrative of mixed motives: one in which Google’s course of conduct was premised on its desire to innovate and to produce a high quality search product in the face of competition, blended with the desire to direct users to its own vertical offerings (instead of those of rivals) so as to increase its own revenues. Indeed, the evidence paints a complex portrait of a company working toward an overall goal of maintaining its market share by providing the best user experience, while simultaneously engaging in tactics that resulted in harm to many vertical competitors, and likely helped to entrench Google’s monopoly power over search and search advertising.

On a global level, the record will permit Google to show substantial innovation, intense competition from Microsoft and others, and speculative long-run harm.

This is exactly when you want antitrust enforcers to forbear. Predicting anticompetitive effects is difficult, and conduct that could be problematic is simultaneously potentially vigorous competition.

That the staff concluded that some of what Google was doing “harmed competitors” isn’t surprising — there were lots of competitors parading through the FTC on a daily basis claiming Google harmed them. But antitrust is about protecting consumers, not competitors. Far more important is the staff finding of “substantial innovation, intense competition from Microsoft and others, and speculative long-run harm.”

Indeed, the combination of “substantial innovation,” “intense competition from Microsoft and others,” and “Google’s strong procompetitive justifications” suggests a well-functioning market. It similarly suggests an antitrust case that the FTC would likely have lost. The FTC’s litigators should probably be grateful that the commissioners had the good sense to vote to close the investigation.

Meanwhile, the Wall Street Journal also reports that the FTC’s Bureau of Economics simultaneously recommended that the Commission not bring suit at all against Google. It is not uncommon for the lawyers and the economists at the Commission to disagree. And as a general (though not inviolable) rule, we should be happy when the Commissioners side with the economists.

While the press, professional Google critics, and the company’s competitors may want to make this sound like a big deal, the actual facts of the case and a pretty simple error-cost analysis suggests that not bringing a case was the correct course.

Critics of Google have argued that users overvalue Google’s services in relation to the data they give away.  One breath-taking headline asked Who Would Pay $5,000 to Use Google?, suggesting that Google and its advertisers can make as much as $5,000 off of individuals whose data they track. Scholars, such as Nathan Newman, have used this to argue that Google exploits its users through data extraction. But, the question remains: how good of a deal is Google? My contention is that Google’s value to most consumers far surpasses the value supposedly extracted from them in data.

First off, it is unlikely that Google and its advertisers make anywhere close to $5,000 off the average user. Only very high volume online purchasers who consistently click through online ads are likely anywhere close to that valuable. Nonetheless, it is true that Google and its advertisers must be making money, or else Google would be charging users for its services.

PrivacyFix, a popular extension for Google Chrome, calculates your worth to Google based upon the amount of searches you have done. Far from $5,000, my total only comes in at $58.66 (and only $10.74 for Facebook). Now, I might not be the highest volume searcher out there. My colleague, Geoffrey Manne states that he is worth $125.18 on Google (and $10.74 for Facebook). But, I use Google search everyday for work in tech policy, along with Google Docs, Google Calendar, and Gmail (both my private email and work emails)… for FREE!*

The value of all of these services to me, or even just Google search alone, easily surpasses the value of my data attributed to Google. This is likely true for the vast majority of other users, as well. While not a perfect analogue, there are paid specialized search options out there (familiar to lawyers) that do little tracking and are not ad-supported: Westlaw, Lexis, and Bloomberg. But, the price for using these services are considerably higher than zero:


Can you imagine having to pay anywhere near $14 per search on Google? Or a subscription that costs $450 per user per month like some firms pay for Bloomberg? It may be the case that the costs are significantly lower per search for Google than for specialized legal searches (though Google is increasingly used by young lawyers as more cases become available). But, the “price” of viewing a targeted ad is a much lower psychic burden for most people than paying even just a few cents per month for an ad-free experience. For instance, consumers almost always choose free apps over the 99 cent alternative without ads.

Maybe the real question about Google is: Great Deal or Greatest Deal?

* Otherwise known as unpriced for those that know there’s no such thing as a free lunch.

On July 24, the Federal Trade Commission issued a modified complaint and consent order in the Google/Motorola case. The FTC responded to the 25 comments on the proposed Order by making several amendments, but the Final Order retains the original order’s essential restrictions on injunctions, as the FTC explains in a letter accompanying the changes. With one important exception, the modifications were primarily minor changes to the required process by which Google/Motorola must negotiate and arbitrate with potential licensees. Although an improvement on the original order, the Complaint and Final Order’s continued focus on the use of injunctions to enforce SEPs presents a serious risk of consumer harm, as I discuss below.

The most significant modification in the new Complaint is the removal of the original UDAP claim. As suggested in my comments on the Order, there is no basis in law for such a claim against Google, and it’s a positive step that the FTC seems to have agreed. Instead, the FTC ended up resting its authority solely upon an Unfair Methods of Competition claim, even though the Commission failed to develop any evidence of harm to competition—as both Commissioner Wright and Commissioner Ohlhausen would (sensibly) require.

Unfortunately, the FTC’s letter offers no additional defense of its assertion of authority, stating only that

[t]he Commission disagrees with commenters who argue that the Commission’s actions in this case are outside of its authority to challenge unfair methods of competition under Section 5 and lack a limiting principle. As reflected in the Commission’s recent statements in Bosch and the Commission’s initial Statement in this matter, this action is well within our Section 5 authority, which both Congress and the Supreme Court have expressly deemed to extend beyond the Sherman Act.

Another problem, as noted by Commissioner Ohlhausen in her dissent from the original order, is that

the consent agreement creates doctrinal confusion. The Order contradicts the decisions of federal courts, standard-setting organizations (“SSOs”), and other stakeholders about the availability of injunctive relief on SEPs and the meaning of concepts like willing licensee and FRAND.

The FTC’s statements in Bosch and this case should not be thought of as law on par with actual court decisions unless we want to allow the FTC to determine the scope of its own authority unilaterally.

This is no small issue. On July 30, the FTC used the Google settlement, along with the settlement in Bosch, as examples of the FTC’s authority in the area of policing SEPs during a hearing on the issue. And as FTC Chairwoman Ramirez noted in response to questions for the record in a different hearing earlier in 2013,

Section 5 of the FTC Act has been developed over time, case-by-case, in the manner of common law. These precedents provide the Commission and the business community with important guidance regarding the appropriate scope and use of the FTC’s Section 5 authority.

But because nearly all of these cases have resulted in consent orders with an administrative agency and have not been adjudicated in court, they aren’t, in fact, developed “in the manner of common law.” Moreover, settlements aren’t binding on anyone except the parties to the settlement. Nevertheless, the FTC has pointed to these sorts of settlements (and congressional testimony summarizing them) as sufficient guidance to industry on the scope of its Section 5 authority. But as we noted in our amicus brief in the Wyndham litigation (in which the FTC makes this claim in the context of its “unfair or deceptive acts or practices” authority):

Settlements (and testimony summarizing them) do not in any way constrain the FTC’s subsequent enforcement decisions; they cannot alone be the basis by which the FTC provides guidance on its unfairness authority because, unlike published guidelines, they do not purport to lay out general enforcement principles and are not recognized as doing so by courts and the business community.

Beyond this more general problem, the Google Final Order retains its own, substantive problem: considerable constraints upon injunctions. The problem with these restraints are twofold: (1) Injunctions are very important to an efficient negotiation process, as recognized by the FTC itself; and (2) if patent holders may no longer pursue injunctions consistently with antitrust law, one would expect a reduction in consumer welfare.

In its 2011 Report on the “IP Marketplace,” the FTC acknowledged the important role of injunctions in preserving the value of patents and in encouraging efficient private negotiation.

Second, the credible threat of an injunction deters infringement in the first place. This results from the serious consequences of an injunction for an infringer, including the loss of sunk investment. Third, a predictable injunction threat will promote licensing by the parties. Private contracting is generally preferable to a compulsory licensing regime because the parties will have better information about the appropriate terms of a license than would a court, and more flexibility in fashioning efficient agreements. But denying an injunction every time an infringer’s switching costs exceed the economic value of the invention would dramatically undermine the ability of a patent to deter infringement and encourage innovation. For this reason, courts should grant injunctions in the majority of cases.

Building on insights from Commissioner Wright and Professor Kobayashi, I argued in my comments that injunctions create conditions that

increase innovation, the willingness to license generally and the willingness to enter into FRAND commitments in particular–all to the likely benefit of consumer welfare.

Monopoly power granted by IP law encourages innovation because it incentivizes creativity through expected profits. If the FTC interprets its UMC authority in a way that constrains the ability of patent holders to effectively police their patent rights, then less innovation would be expected–to the detriment of consumers as well as businesses.

And this is precisely what has happened. Innovative technology companies are responding to the current SEP enforcement environment exactly as we would expect them to—by avoiding the otherwise-consumer-welfare enhancing standardization process entirely.

Thus, for example, at a recent event sponsored by Global Competition Review (gated), representatives from Nokia, Ericsson, Siemens and Qualcomm made no bones about the problems they see and where they’re headed if they persist:

[Jenni Lukander, global head of competition law at Nokia] said the problem of “free-riding”, whereby technology companies adopt standard essential patents (SEPs) without complying with fair, reasonable and non-discriminatory (FRAND) licensing terms was a “far bigger problem” than patent holders pursuing injunctive relief. She said this behaviour was “unsustainable”, as it discouraged innovation and jeopardised standardisation.

Because of the current atmosphere, Lukander said, Nokia has stepped back from the standardisation process, electing either not to join certain standard-setting organisations (SSOs) or not to contribute certain technologies to these organisations.

The fact that every licence negotiation takes places “under the threat of injunction litigation” is not a sign of failure, said Lukander, but an indicator of the system working “as it was designed to work”.

This, said [Dan Hermele, director of IP rights and licensing for Qualcomm Europe], amounted to “reverse hold-up”. “The licensor is pressured to accept less than reasonable licensing terms due to the threat of unbalanced regulatory intervention,” he said, adding that the trend was moving to an “infringe and litigate model”, which threatened to harm innovators, particularly small and medium-sized businesses, “for whom IPR is their life blood”.

Beat Weibel, chief IP counsel at Siemens, said…innovation can only be beneficial if it occurs within a “safe and strong IP system,” he said, where a “willing licensee is favoured over a non-willing licensee” and the enforcer is not a “toothless tiger”.

It remains to be seen if the costs to consumers from firms curtailing their investments in R&D or withholding their patents from the standard-setting process will outweigh the costs (yes, some costs do exist; the patent system is not frictionless and it is far from perfect, of course) from the “over”-enforcement of SEPs lamented by critics. But what is clear is that these costs can’t be ignored. Reverse hold-up can’t be wished away, and there is a serious risk that the harm likely to be caused by further eroding the enforceability of SEPs by means of injunctions will significantly outweigh whatever benefits it may also confer.

Meanwhile, stay tuned for tomorrow’s TOTM blog symposium on “Regulating the Regulators–Guidance for the FTC’s Section 5 Unfair Methods of Competition Authority” for much more discussion on this issue.

I filed comments today on the FTC’s proposed Settlement Order in the Google standards-essential patents (SEPs) antitrust case. The Order imposes limits on the allowable process for enforcing FRAND licensing of SEPs, an area of great complexity and vigorous debate among industry, patent experts and global standards bodies. The most notable aspect of the order is its treatment of the process by which Google and, if extended, patent holders generally may attempt to enforce their FRAND-obligated SEPs through injunctions.

Unfortunately, the FTC’s enforcement action in this matter had no proper grounding in antitrust law. Under Supreme Court doctrine there is no basis for liability under Section 2 of the Sherman Act because the exercise of lawfully acquired monopoly power is not actionable under the antitrust laws. Apparently recognizing this, the Commission instead brought this action under Section 5 of the FTC Act. But Section 5 provides no basis for liability either, where, as here, there is no evidence of consumer harm. The Commission’s Order continues its recent trend of expanding its Section 5 authority without judicial oversight, charting a dangerously unprincipled course.

The standard-setting organizations (SSOs) that govern the SEPs in this case have no policies prohibiting the use of injunctions. Even if an SSO agreement (or a specific license) did disallow them, seeking an injunction would be a simple breach of contract. Reading a limitation on injunctions into the SSO agreement is in severe tension with the normal rules of contract interpretation. To turn Motorola’s effort to receive a reasonable royalty for its patents by means of an injunction into an antitrust problem seems directly to undermine the standard-setting process. It also seems to have no basis in law.

My comments rely heavily on Bruce Kobayashi and Josh Wright’s article, Federalism, Substantive Preemption, and Limits on Antitrust: An Application to Patent Holdup, published in Competition Policy and Patent Law Under Uncertainty: Regulating Innovation (Manne & Wright, eds.).

For previous posts on the topic see, e.g.:

The suit against Google was to be this century’s first major antitrust case and a model for high technology industries in the future. Now that we have passed the investigative hangover, the mood has turned reflective, and antitrust experts are now looking to place this case into its proper context. If it were brought, would the case have been on sure legal footing? Was this a prudent move for consumers? Was the FTC’s disposition of the case appropriate?

Join me this Friday, January 11, 2013 at 12:00 pm – 1:45 pm ET for an ABA Antitrust Section webinar to explore these questions, among others. I will be sharing the panel with an impressive group:

Hill B. Welford will moderate. Registration is open to everyone here and the outlay is zero. Remember — these events are not technically free because you have to give up some of your time, but I would be delighted if you did.

The Federal Trade Commission yesterday closed its investigation of Google’s search business (see my comment here) without taking action. The FTC did, however, enter into a settlement with Google over the licensing of Motorola Mobility’s standards-essential patents (SEPs). The FTC intends that agreement to impose some limits on an area of great complexity and vigorous debate among industry, patent experts and global standards bodies: The allowable process for enforcing FRAND (fair, reasonable and non-discriminatory) licensing of SEPs, particularly the use of injunctions by patent holders to do so. According to Chairman Leibowitz, “[t]oday’s landmark enforcement action will set a template for resolution of SEP licensing disputes across many industries.” That effort may or may not be successful. It also may be misguided.

In general, a FRAND commitment incentivizes innovation by allowing a SEP owner to recoup its investments and the value of its technology through licensing, while, at the same, promoting competition and avoiding patent holdup by ensuring that licensing agreements are reasonable. When the process works, and patent holders negotiate licensing rights in good faith, patents are licensed, industries advance and consumers benefit.

FRAND terms are inherently indeterminate and flexible—indeed, they often apply precisely in situations where licensors and licensees need flexibility because each licensing circumstance is nuanced and a one-size-fits-all approach isn’t workable. Superimposing process restraints from above isn’t necessarily the best thing in dealing with what amounts to a contract dispute. But few can doubt the benefits of greater clarity in this process; the question is whether the FTC’s particular approach to the problem sacrifices too much in exchange for such clarity.

The crux of the issue in the Google consent decree—and the most controversial aspect of SEP licensing negotiations—is the role of injunctions. The consent decree requires that, before Google sues to enjoin a manufacturer from using its SEPs without a license, the company must follow a prescribed path in licensing negotiations. In particular:

Under this Order, before seeking an injunction on FRAND-encumbered SEPs, Google must: (1) provide a potential licensee with a written offer containing all of the material license terms necessary to license its SEPs, and (2) provide a potential licensee with an offer of binding arbitration to determine the terms of a license that are not agreed upon. Furthermore, if a potential licensee seeks judicial relief for a FRAND determination, Google must not seek an injunction during the pendency of the proceeding, including appeals.

There are a few exceptions, summarized by Commissioner Ohlhausen:

These limitations include when the potential licensee (a) is outside the jurisdiction of the United States; (b) has stated in writing or sworn testimony that it will not license the SEP on any terms [in other words, is not a “willing licensee”]; (c) refuses to enter a license agreement on terms set in a final ruling of a court – which includes any appeals – or binding arbitration; or (d) fails to provide written confirmation to a SEP owner after receipt of a terms letter in the form specified by the Commission. They also include certain instances when a potential licensee has brought its own action seeking injunctive relief on its FRAND-encumbered SEPs.

To the extent that the settlement reinforces what Google (and other licensors) would do anyway, and even to the extent that it imposes nothing more than an obligation to inject a neutral third party into FRAND negotiations to assist the parties in resolving rate disputes, there is little to complain about. Indeed, this is the core of the agreement, and, importantly, it seems to preserve Google’s right to seek injunctions to enforce its patents, subject to the agreement’s process requirements.

Industry participants and standard-setting organizations have supported injunctions, and the seeking and obtaining of injunctions against infringers is not in conflict with SEP patentees’ obligations. Even the FTC, in its public comments, has stated that patent owners should be able to obtain injunctions on SEPs when an infringer has rejected a reasonable license offer. Thus, the long-anticipated announcement by the FTC in the Google case may help to provide some clarity to the future negotiation of SEP licenses, the possible use of binding arbitration, and the conditions under which seeking injunctive relief will be permissible (as an antitrust matter).

Nevertheless, U.S. regulators, including the FTC, have sometimes opined that seeking injunctions on products that infringe SEPs is not in the spirit of FRAND. Everyone seems to agree that more certainty is preferable; the real issue is whether and when injunctions further that aim or not (and whether and when they are anticompetitive).

In October, Renata Hesse, then Acting Assistant Attorney General for the Department of Justice’s Antitrust Division, remarked during a patent roundtable that

[I]t would seem appropriate to limit a patent holder’s right to seek an injunction to situations where the standards implementer is unwilling to have a neutral third-party determine the appropriate F/RAND terms or is unwilling to accept the F/RAND terms approved by such a third-party.

In its own 2011 Report on the “IP Marketplace,” the FTC acknowledged the fluidity and ambiguity surrounding the meaning of “reasonable” licensing terms and the problems of patent enforcement. While noting that injunctions may confer a costly “hold-up” power on licensors that wield them, the FTC nevertheless acknowledged the important role of injunctions in preserving the value of patents and in encouraging efficient private negotiation:

Three characteristics of injunctions that affect innovation support generally granting an injunction. The first and most fundamental is an injunction’s ability to preserve the exclusivity that provides the foundation of the patent system’s incentives to innovate. Second, the credible threat of an injunction deters infringement in the first place. This results from the serious consequences of an injunction for an infringer, including the loss of sunk investment. Third, a predictable injunction threat will promote licensing by the parties. Private contracting is generally preferable to a compulsory licensing regime because the parties will have better information about the appropriate terms of a license than would a court, and more flexibility in fashioning efficient agreements.

* * *

But denying an injunction every time an infringer’s switching costs exceed the economic value of the invention would dramatically undermine the ability of a patent to deter infringement and encourage innovation. For this reason, courts should grant injunctions in the majority of cases.…

Consistent with this view, the European Commission’s Deputy Director-General for Antitrust, Cecilio Madero Villarejo, recently expressed concern that some technology companies that complain of being denied a license on FRAND terms never truly intend to acquire licenses, but rather “want[] to create conditions for a competition case to be brought.”

But with the Google case, the Commission appears to back away from its seeming support for injunctions, claiming that:

Seeking and threatening injunctions against willing licensees of FRAND-encumbered SEPs undermines the integrity and efficiency of the standard-setting process and decreases the incentives to participate in the process and implement published standards. Such conduct reduces the value of standard setting, as firms will be less likely to rely on the standard-setting process.

Reconciling the FTC’s seemingly disparate views turns on the question of what a “willing licensee” is. And while the Google settlement itself may not magnify the problems surrounding the definition of that term, it doesn’t provide any additional clarity, either.

The problem is that, even in its 2011 Report, in which FTC noted the importance of injunctions, it defines a willing licensee as one who would license at a hypothetical, ex ante rate absent the threat of an injunction and with a different risk profile than an after-the-fact infringer. In other words, the FTC’s definition of willing licensee assumes a willingness to license only at a rate determined when an injunction is not available, and under the unrealistic assumption that the true value of a SEP can be known ex ante. Not surprisingly, then, the Commission finds it easy to declare an injunction invalid when a patentee demands a (higher) royalty rate in an actual negotiation, with actual knowledge of a patent’s value and under threat of an injunction.

As Richard Epstein, Scott Kieff and Dan Spulber discuss in critiquing the FTC’s 2011 Report:

In short, there is no economic basis to equate a manufacturer that is willing to commit to license terms before the adoption and launch of a standard, with one that instead expropriates patent rights at a later time through infringement. The two bear different risks and the late infringer should not pay the same low royalty as a party that sat down at the bargaining table and may actually have contributed to the value of the patent through its early activities. There is no economically meaningful sense in which any royalty set higher than that which a “willing licensee would have paid” at the pre-standardization moment somehow “overcompensates patentees by awarding more than the economic value of the patent.”

* * *

Even with a RAND commitment, the patent owner retains the valuable right to exclude (not merely receive later compensation from) manufacturers who are unwilling to accept reasonable license terms. Indeed, the right to exclude influences how those terms should be calculated, because it is quite likely that prior licensees in at least some areas will pay less if larger numbers of parties are allowed to use the same technology. Those interactive effects are ignored in the FTC calculations.

With this circular logic, all efforts by patentees to negotiate royalty rates after infringement has occurred can be effectively rendered anticompetitive if the patentee uses an injunction or the threat of an injunction against the infringer to secure its reasonable royalty.

The idea behind FRAND is rather simple (reward inventors; protect competition), but the practice of SEP licensing is much more complicated. Circumstances differ from case to case, and, more importantly, so do the parties’ views on what may constitute an appropriate licensing rate under FRAND. As I have written elsewhere, a single company may have very different views on the meaning of FRAND depending on whether it is the licensor or licensee in a given negotiation—and depending on whether it has already implemented a standard or not. As one court looking at the very SEPs at issue in the Google case has pointed out:

[T]he court is mindful that at the time of an initial offer, it is difficult for the offeror to know what would in fact constitute RAND terms for the offeree. Thus, what may appear to be RAND terms from the offeror’s perspective may be rejected out-of-pocket as non-RAND terms by the offeree. Indeed, it would appear that at any point in the negotiation process, the parties may have a genuine disagreement as to what terms and conditions of a license constitute RAND under the parties’ unique circumstances.

The fact that many firms engaged in SEP negotiations are simultaneously and repeatedly both licensors and licensees of patents governed by multiple SSOs further complicates the process—but also helps to ensure that it will reach a conclusion that promotes innovation and ensures that consumers reap the rewards.

In fact, an important issue in assessing the propriety of injunctions is the recognition that, in most cases, firms would rather license their patents and receive royalties than exclude access to their IP and receive no compensation (and incur the costs of protracted litigation, to boot). Importantly, for firms that both license out their own patents and license in those held by other firms (the majority of IT firms and certainly the norm for firms participating in SSOs), continued interactions on both sides of such deals help to ensure that licensing—not withholding—is the norm.

Companies are waging the smartphone patent wars with very different track records on SSO participation. Apple, for example, is relatively new to the mobile communications space and has relatively few SEPs, while other firms, like Samsung, are long-time players in the space with histories of extensive licensing (in both directions). But, current posturing aside, both firms have an incentive to license their patents, as Mark Summerfield notes:

Apple’s best course of action will most likely be to enter into licensing agreements with its competitors, which will not only result in significant revenues, but also push up the prices (or reduce the margins) on competitive products.

While some commentators make it sound as if injunctions threaten to cripple smartphone makers by preventing them from licensing essential technology on viable terms, companies in this space have been perfectly capable of orchestrating large-scale patent licensing campaigns. That these may increase costs to competitors is a feature—not a bug—of the system, representing the return on innovation that patents are intended to secure. Microsoft has wielded its sizeable patent portfolio to drive up the licensing fees paid by Android device manufacturers, and some commentators have even speculated that Microsoft makes more revenue from Android than Google does. But while Microsoft might prefer to kill Android with its patents, given the unlikeliness of this, as MG Siegler notes,

[T]he next best option is to catch a free ride on the Android train. Patent licensing deals already in place with HTC, General Dynamics, and others could mean revenues of over $1 billion by next year, as Forbes reports. And if they’re able to convince Samsung to sign one as well (which could effectively force every Android partner to sign one), we could be talking multiple billions of dollars of revenue each year.

Hand-wringing about patents is the norm, but so is licensing, and your smartphone exists, despite the thousands of patents that read on it, because the firms that hold those patents—some SEPs and some not—have, in fact, agreed to license them.

The inability to seek an injunction against an infringer, however, would ensure instead that patentees operate with reduced incentives to invest in technology and to enter into standards because they are precluded from benefiting from any subsequent increase in the value of their patents once they do so. As Epstein, Kieff and Spulber write:

The simple reality is that before a standard is set, it just is not clear whether a patent might become more or less valuable. Some upward pressure on value may be created later to the extent that the patent is important to a standard that is important to the market. In addition, some downward pressure may be caused by a later RAND commitment or some other factor, such as repeat play. The FTC seems to want to give manufacturers all of the benefits of both of these dynamic effects by in effect giving the manufacturer the free option of picking different focal points for elements of the damages calculations. The patentee is forced to surrender all of the benefit of the upward pressure while the manufacturer is allowed to get all of the benefit of the downward pressure.

Thus the problem with even the limited constraints imposed by the Google settlement: To the extent that the FTC’s settlement amounts to a prohibition on Google seeking injunctions against infringers unless the company accepts the infringer’s definition of “reasonable,” the settlement will harm the industry. It will reinforce a precedent that will likely reduce the incentives for companies and individuals to innovate, to participate in SSOs, and to negotiate in good faith.

Contrary to most assumptions about the patent system, it needs stronger, not weaker, property rules. With a no-injunction rule (whether explicit or de facto (as the Google settlement’s definition of “willing licensee” unfolds)), a potential licensee has little incentive to negotiate with a patent holder and can instead refuse to license, infringe, try its hand in court, avoid royalties entirely until litigation is finished (and sometimes even longer), and, in the end, never be forced to pay a higher royalty than it would have if it had negotiated before the true value of the patents was known.

Flooding the courts and discouraging innovation and peaceful negotiations hardly seem like benefits to the patent system or the market. Unfortunately, the FTC’s approach to SEP licensing exemplified by the Google settlement may do just that. Continue Reading…

I have been a critic of the Federal Trade Commission’s investigation into Google since it was a gleam in its competitors’ eyes—skeptical that there was any basis for a case, and concerned about the effect on consumers, innovation and investment if a case were brought.

While it took the Commission more than a year and a half to finally come to the same conclusion, ultimately the FTC had no choice but to close the case that was a “square peg, round hole” problem from the start.

Now that the FTC’s investigation has concluded, an examination of the nature of the markets in which Google operates illustrates why this crusade was ill-conceived from the start. In short, the “realities on the ground” strongly challenged the logic and relevance of many of the claims put forth by Google’s critics. Nevertheless, the politics are such that their nonsensical claims continue, in different forums, with competitors continuing to hope that they can wrangle a regulatory solution to their competitive problem.

The case against Google rested on certain assumptions about the functioning of the markets in which Google operates. Because these are tech markets, constantly evolving and complex, most assumptions about the scope of these markets and competitive effects within them are imperfect at best. But there are some attributes of Google’s markets—conveniently left out of the critics’ complaints— that, properly understood, painted a picture for the FTC that undermined the basic, essential elements of an antitrust case against the company.

That case was seriously undermined by the nature and extent of competition in the markets the FTC was investigating. Most importantly, casual references to a “search market” and “search advertising market” aside, Google actually competes in the market for targeted eyeballs: a market aimed to offer up targeted ads to interested users. Search offers a valuable opportunity for targeting an advertiser’s message, but it is by no means alone: there are myriad (and growing) other mechanisms to access consumers online.

Consumers use Google because they are looking for information — but there are lots of ways to do that. There are plenty of apps that circumvent Google, and consumers are increasingly going to specialized sites to find what they are looking for. The search market, if a distinct one ever existed, has evolved into an online information market that includes far more players than those who just operate traditional search engines.

We live in a world where what prevails today won’t prevail tomorrow. The tech industry is constantly changing, and it is the height of folly (and a serious threat to innovation and consumer welfare) to constrain the activities of firms competing in such an environment by pigeonholing the market. In other words, in a proper market, Google looks significantly less dominant. More important, perhaps, as search itself evolves, and as Facebook, Amazon and others get into the search advertising game, Google’s strong position even in the overly narrow “search market” is far from unassailable.

This is progress — creative destruction — not regress, and such changes should not be penalized.

Another common refrain from Google’s critics was that Google’s access to immense amounts of data used to increase the quality of its targeting presented a barrier to competition that no one else could match, thus protecting Google’s unassailable monopoly. But scale comes in lots of ways.

Even if scale doesn’t come cheaply, the fact that challenging firms might have to spend the same (or, in this case, almost certainly less) Google did in order to replicate its success is not a “barrier to entry” that requires an antitrust remedy. Data about consumer interests is widely available (despite efforts to reduce the availability of such data in the name of protecting “privacy”—which might actually create barriers to entry). It’s never been the case that a firm has to generate its own inputs for every product it produces — and there’s no reason to suggest search or advertising is any different.

Additionally, to defend a claim of monopolization, it is generally required to show that the alleged monopolist enjoys protection from competition through barriers to entry. In Google’s case, the barriers alleged were illusory. Bing and other recent entrants in the general search business have enjoyed success precisely because they were able to obtain the inputs (in this case, data) necessary to develop competitive offerings.

Meanwhile unanticipated competitors like Facebook, Amazon, Twitter and others continue to knock at Google’s metaphorical door, all of them entering into competition with Google using data sourced from creative sources, and all of them potentially besting Google in the process. Consider, for example, Amazon’s recent move into the targeted advertising market, competing with Google to place ads on websites across the Internet, but with the considerable advantage of being able to target ads based on searches, or purchases, a user has made on Amazon—the world’s largest product search engine.

Now that the investigation has concluded, we come away with two major findings. First, the online information market is dynamic, and it is a fool’s errand to identify the power or significance of any player in these markets based on data available today — data that is already out of date between the time it is collected and the time it is analyzed.

Second, each development in the market – whether offered by Google or its competitors and whether facilitated by technological change or shifting consumer preferences – has presented different, novel and shifting opportunities and challenges for companies interested in attracting eyeballs, selling ad space and data, earning revenue and obtaining market share. To say that Google dominates “search” or “online advertising” missed the mark precisely because there was simply nothing especially antitrust-relevant about either search or online advertising. Because of their own unique products, innovations, data sources, business models, entrepreneurship and organizations, all of these companies have challenged and will continue to challenge the dominant company — and the dominant paradigm — in a shifting and evolving range of markets.

It would be churlish not to give credit where credit is due—and credit is due the FTC. I continue to think the investigation should have ended before it began, of course, but the FTC is to be commended for reaching this result amidst an overwhelming barrage of pressure to “do something.”

But there are others in this sadly politicized mess for whom neither the facts nor the FTC’s extensive investigation process (nor the finer points of antitrust law) are enough. Like my four-year-old daughter, they just “want what they want,” and they will stamp their feet until they get it.

While competitors will be competitors—using the regulatory system to accomplish what they can’t in the market—they do a great disservice to the very customers they purport to be protecting in doing so. As Milton Friedman famously said, in decrying “The Business Community’s Suicidal Impulse“:

As a believer in the pursuit of self-interest in a competitive capitalist system, I can’t blame a businessman who goes to Washington and tries to get special privileges for his company.… Blame the rest of us for being so foolish as to let him get away with it.

I do blame businessmen when, in their political activities, individual businessmen and their organizations take positions that are not in their own self-interest and that have the effect of undermining support for free private enterprise. In that respect, businessmen tend to be schizophrenic. When it comes to their own businesses, they look a long time ahead, thinking of what the business is going to be like 5 to 10 years from now. But when they get into the public sphere and start going into the problems of politics, they tend to be very shortsighted.

Ironically, Friedman was writing about the antitrust persecution of Microsoft by its rivals back in 1999:

Is it really in the self-interest of Silicon Valley to set the government on Microsoft? Your industry, the computer industry, moves so much more rapidly than the legal process, that by the time this suit is over, who knows what the shape of the industry will be.… [Y]ou will rue the day when you called in the government.

Among Microsoft’s chief tormentors was Gary Reback. He’s spent the last few years beating the drum against Google—but singing from the same song book. Reback recently told the Washington Post, “if a settlement were to be proposed that didn’t include search, the institutional integrity of the FTC would be at issue.” Actually, no it wouldn’t. As a matter of fact, the opposite is true. It’s hard to imagine an agency under more pressure, from more quarters (including the Hill), to bring a case around search. Doing so would at least raise the possibility that it were doing so because of pressure and not the merits of the case. But not doing so in the face of such pressure? That can almost only be a function of institutional integrity.

As another of Google’s most-outspoken critics, Tom Barnett, noted:

[The FTC has] really put [itself] in the position where they are better positioned now than any other agency in the U.S. is likely to be in the immediate future to address these issues. I would encourage them to take the issues as seriously as they can. To the extent that they concur that Google has violated the law, there are very good reasons to try to address the concerns as quickly as possible.

As Barnett acknowledges, there is no question that the FTC investigated these issues more fully than anyone. The agency’s institutional culture and its committed personnel, together with political pressure, media publicity and endless competitor entreaties, virtually ensured that the FTC took the issues “as seriously as they [could]” – in fact, as seriously as anyone else in the world. There is simply no reasonable way to criticize the FTC for being insufficiently thorough in its investigation and conclusions.

Nor is there a basis for claiming that the FTC is “standing in the way” of the courts’ ability to review the issue, as Scott Cleland contends in an op-ed in the Hill. Frankly, this is absurd. Google’s competitors have spent millions pressuring the FTC to bring a case. But the FTC isn’t remotely the only path to the courts. As Commissioner Rosch admonished,

They can darn well bring [a case] as a private antitrust action if they think their ox is being gored instead of free-riding on the government to achieve the same result.

Competitors have already beaten a path to the DOJ’s door, and investigations are still pending in the EU, Argentina, several US states, and elsewhere. That the agency that has leveled the fullest and best-informed investigation has concluded that there is no “there” there should give these authorities pause, but, sadly for consumers who would benefit from an end to competitors’ rent seeking, nothing the FTC has done actually prevents courts or other regulators from having a crack at Google.

The case against Google has received more attention from the FTC than the merits of the case ever warranted. It is time for Google’s critics and competitors to move on.

[Crossposted at]

I will be participating in a wide-ranging discussion of Google and antitrust issues at the upcoming AALS meeting in New Orleans in January. The Antitrust and Economic Regulation Section of the AALS is hosting the roundtable, organized by Mike Carrier. Mike and I will be joined by Marina Lao, Frank Pasquale, Pam Samuelson, and Mark Patterson, and the discussion will cover Google Book Search as well as the FTC investigations/possible cases against Google based on search and SEPs.

The session will be on Saturday, January 5, from 10:30 to 12:15 in the Hilton New Orleans Riverside (Newberry, Third Floor).

 Google and Antitrust

(Papers to be published in Harvard Journal of Law & Technology Digest)


Michael A. Carrier, Rutgers School of Law – Camden


Marina L. Lao, Seton Hall University School of Law

Geoffrey A. Manne, Lewis & Clark Law School

Frank A. Pasquale, Seton Hall University School of Law

Mark R. Patterson, Fordham University School of Law

Pamela Samuelson, University of California, Berkeley, School of Law

How should the antitrust laws apply to Google? Though the question is simple, the answer implicates an array of far-reaching issues related to how we access information and how we interact with others. This program will feature a distinguished panel engaging in a fastpaced discussion (no PowerPoints!) about these topics.

The panel will explore the Federal Trade Commission’s potential case against Google. It will discuss Google’s position in the search market and potential effects of its conduct on rivals. The panel also will explore the nuances of the Google Book Search settlement. What would – and should – antitrust law do about the project? How should the procompetitive justifications of the increased availability of books be weighed against the effects of the project on rivals?

Antitrust’s role in a 21st-century economy is frequently debated. Google provides a fruitful setting in which to discuss these important issues.