Uber Can’t Be Fixed — It’s Time for Regulators to Shut It Down

Edelman, Benjamin G. “Uber Can’t Be Fixed — It’s Time for Regulators to Shut It Down.” Harvard Business Review (digital) (June 21, 2017). (Translations: Japanese, Russian.)

From many passengers’ perspective, Uber is a godsend — lower fares than taxis, clean vehicles, courteous drivers, easy electronic payments. Yet the company’s mounting scandals reveal something seriously amiss, culminating in last week’s stern report from former U.S. Attorney General Eric Holder.

Some people attribute the company’s missteps to the personal failings of founder-CEO Travis Kalanick. These have certainly contributed to the company’s problems, and his resignation is probably appropriate. Kalanick and other top executives signal by example what is and is not acceptable behavior, and they are clearly responsible for the company’s ethically and legally questionable decisions and practices.

But I suggest that the problem at Uber goes beyond a culture created by toxic leadership. The company’s cultural dysfunction, it seems to me, stems from the very nature of the company’s competitive advantage: Uber’s business model is predicated on lawbreaking. And having grown through intentional illegality, Uber can’t easily pivot toward following the rules.

Enumerating Uber’s Scandals

Collecting my thoughts for an article about Uber’s mounting scandals and the proper legal and regulatory response, I took some time to review the range of recent concerns. It’s overwhelming — new issues arising daily, and prior problems almost inevitably forgotten. But by dividing the misdeeds into a taxonomy of subject areas, I’m seeing trends — identifying the areas where Uber falls furthest short. I offer my notes to others in hopes that they can help.

My tabulation:

Uber Scandals

Racial Discrimination in the Sharing Economy: Evidence from a Field Experiment

Edelman, Benjamin, Michael Luca, and Daniel Svirsky. “Racial Discrimination in the Sharing Economy: Evidence from a Field Experiment.” American Economic Journal: Applied Economics 9, no. 2 (April 2017): 1-22.

In an experiment on Airbnb, we find that applications from guests with distinctively African-American names are 16% less likely to be accepted relative to identical guests with distinctively White names. Discrimination occurs among landlords of all sizes, including small landlords sharing the property and larger landlords with multiple properties. It is most pronounced among hosts who have never had an African-American guest, suggesting only a subset of hosts discriminate. While rental markets have achieved significant reductions in discrimination in recent decades, our results suggest that Airbnb’s current design choices facilitate discrimination and raise the possibility of erasing some of these civil rights gains.

English Translation of FAS Russia Decision in Yandex v. Google

In September 2015, the Russian Federal Antimonopoly Service announced its decision that Google had violated Russian law by tying its mobile apps to Google Play and setting additional restrictions on mobile device manufacturers, including limiting what other apps they install and how they configure those apps and devices. These topics are of great interest to me since I was the first to publicly distribute the Mobile Application Distribution Agreements, and because I explored related questions at length in my 2015 article Does Google Leverage Market Power Through Tying and Bundling? and more recently my working paper Android and Competition Law: Exploring and Assessing Google’s Practices in Mobile (with Damien Geradin).

For those who wish to understand the reasoning and conclusions of Russia’s FAS, one key limitation is that the September 2015 decision is available only in Russian. While the case document library summarizes key facts, allegations, and procedural developments, that’s no substitute for the full primary source documents.

In the course of expanding my Android and Competition Law paper, I recently obtained an English translation of the September 2015 decision. The decision is unofficial but, as best I can tell, accurate and reliable. It suffers redactions, but the original in Russian has the same limitation. I offer it here to anyone interested:

Yandex v. Google – Resolution on Case No. 1-14-21/00-11-15 – resolution of September 18, 2015 – unofficial English translation

Response to Airbnb’s Report on Discrimination

This month Airbnb released a report investigating discrimination by its hosts against guests (including racial minorities and others), assessing the evidence of the problem and evaluating proposed solutions. The accompanying announcement offers lofty principles—"creating a world where anyone can belong anywhere."

In contrast to the company’s prior denials, Airbnb now admits the problem is urgent: "discrimination must be addressed"; "minorities struggle more than others to book a listing"; "some members of the community did not receive the timely, compassionate response they expected and deserved when they reported instances of discrimination"; Airbnb’s nondiscrimination policy was not widely known, within or outside company. This much is beyond dispute.

While Airbnb’s report is a step in the right direction, it does little to address the crucial subject of how to actually fix the problem of discrimination. Indeed, the report proposes actions of uncertain or unproven effectiveness. At the same time, the report quickly dismisses a simpler alternative response—removing guest photos and names from booking requests—which would be far more likely to succeed. Meanwhile, the report completely fails to defend the legal gamesmanship by which Airbnb avoids litigation on the merits when consumers complain about Airbnb, and the report equally fails to defend Airbnb’s continued prohibition on users conducting research to uncover and measure discrimination for themselves.

This article offers my critique.

Airbnb’s bottom line

What exactly did Airbnb commit to change?

  1. Airbnb plans to increase the number of "Instant Book" properties, with a stated goal of one million by January 2017. Instant Book offers a potential mechanism to reduce discrimination: When hosts pre-promise to accept any interested guest who agrees to pay, they do not have the ability to screen each individual guest’s request, therefore leaving much less opportunity to discriminate.

    Nonetheless, Instant Book addresses only a portion of the problem. If disfavored guests are limited to Instant Book properties, they are left with a reduced set of properties, typically meaning an inferior match with their preferences as well as higher price and less flexibility. Furthermore, hosts can use cancellations—permitted, in certain quantities, under Airbnb’s rules—to undo the anti-discrimination benefits of Instant Book.

    Moreover, Airbnb’s million-property goal is at best ambiguous. Airbnb doesn’t say how many Instant Book properties are already available, so it’s hard to assess how big an increase that would be or how realistic it is. Nor does Airbnb indicate the methods to be used to achieve the increase. If January comes and the objective has not been reached, what then?

  2. Airbnb says it will "experiment with reducing the prominence of guest photos in the booking process." Certainly photos have been prominent, and to its credit Airbnb now agrees excessively so, in light of the limited information they actually convey and the superiority of other information (like objective verifications).

    Notably, Airbnb’s plan to experiment with reduced photo size has been misreported in the press. For example, the Wall Street Journal reported that Airbnb "is planning to reduce the prominence of guests’ photos," and Diversity Inc. reported that Airbnb’s changes "include displaying photos … less prominently." But Airbnb’s actual promise wasn’t to reduce photo prominence. Rather, the company promised only to run an experiment, of unspecified duration and scope, with no commitment whatsoever as to subsequent changes. With so many caveats, it’s hard to put much weight on this response.

  3. Effective November 1, Airbnb will require users to accept a stronger and more detailed nondiscrimination policy: "By joining this community, you commit to treat all fellow members of this community, regardless of race, religion, national origin, disability, sex, gender identity, sexual orientation or age, with respect, and without judgment or bias."

    Airbnb’s policy offers commendable principles. But the company’s existing policy already included the same substance as the new wording. Will a compulsory screen or checkbox actually prevent hosts from continuing to discriminate? Airbnb offers no evidence that a restated policy will make a difference. Indeed, experience from other types of discrimination suggests that those who seek to discriminate will change only slowly and under significant pressure.

  4. Sometime during the first half of 2017, Airbnb promises to modify its site to prevent a host from telling one guest that a property is unavailable, then later accepting another guest’s request for the same nights. This change seeks to penalize hosts who falsely claim a property is unavailable: If a host rejects a guest due to a false claim of unavailability, the host won’t be able to keep the property listed for others, making the pretextual rejection more costly.

    Unfortunately, there’s little reason to think this approach will operate as claimed. Instead, strategic hosts will switch to other reasons for rejecting guests—reasons guests can less readily prove to be pretextual. An "unavailable" response would prevent the host from booking the property to someone else, but the host can instead specify some other reason for declining the request. So there’s little reason to think this change will stop those who want to discriminate.

    This change will also hinder guests’ efforts to demonstrate discrimination. After rejection, a concerned guest may ask a friend to inquire (or creates a test account to do so), thereby proving that the rejection was due to guest identity and not genuine unavailability. This second inquiry provides a valuable verification, checking whether the host can keep his story straight. Substituting automatic software logic for fallible hosts, Airbnb makes it more difficult to catch a host in a lie.

    Finally, Airbnb offers no explanation why the company needs four to ten months to build this feature. Airbnb’s site already offers multiple categorizations for each night including available, unavailable, and booked. By all indications, this architecture could easily be extended to offer the promised feature—for example, a new status called "booked-locked" that a host cannot change back to available. If this feature is important and useful, why wait?

The proposed changes share common weaknesses. They all rely on unproven and indeed unstated assumptions about how hosts will respond. And each change leaves ample room to question whether it will help at all. One might hope the combination would be more than the sum of its parts. But when each change falls so far short, it’s hard to be optimistic. These are not the "powerful systemic changes" Airbnb promises.

The better policy: remove guest names and photos

In sharp contrast to the indirect changes Airbnb proposes, a much simpler adjustment would more directly prevent discrimination: remove guest photos and names from the information a host sees when evaluating a guest’s request. If a host could not see a guest’s photo and name before accepting a booking, the host would have no way to determine the guest’s race, age, gender or other characteristics. Even a host who wanted to discriminate would not have the information to make a decision based on the improper factor.

Removing photos and names is particularly compelling in light of best practice developed over decades in other contexts. In 1952, the Boston Symphony Orchestra began to audition musicians behind a screen. The result was a sharp rise in the number of female musicians—widely interpreted to be a decrease in arbitrary and improper discrimination. Similarly, Massachusetts landlords cannot ask about race, national origin, sexual orientation, age, religion, and myriad other factors—for there is little proper reason to make such inquiries, and if landlords have this information, many will struggle not to use it improperly.

Airbnb admits that "some have asked Airbnb to remove profile photos from the platform." But oddly Airbnb offers zero discussion of the benefits that approach might offer. If Airbnb thinks removing photos would not reduce discrimination, the company offers no statement of its reasoning. And Airbnb similarly says nothing of the other contexts where similar landlords, employers, and others have similarly elected to conceal information to reduce discrimination. Meanwhile, Airbnb says absolutely nothing of my proposal that hosts see guests’ pseudonyms, not actual names, when considering a request. Instead, Airbnb focuses on three supposed benefits of continuing to show photos before booking.

  • First, Airbnb argues that photos are "an important security feature: hosts and guests want to know who they will be meeting when a stay begins." Here, Airbnb’s report echoes April 2016 comments from Airbnb’s David King, Director of Diversity and Belonging, who told NPR: "The photos are on the platform for a reason. … You want to make sure that the guest that shows up at your door is the person that you’ve been communicating with."

    This reasoning is particularly unconvincing. No doubt, hosts and guests should eventually see each other’s photos—but after a booking is confirmed.

  • Second, Airbnb says "profile photos are an important feature that help build relationships and allow hosts and guests to get to know one another before a booking begins."

    Airbnb’s reasoning ignores the competing interests at hand. Perhaps profile photos help some guests and hosts get to know each other. But they also impede bookings by certain guests—notably including victims of longstanding and multifaceted discrimination. How should we weigh a small benefit to many, versus a large cost to a smaller (but important) group? At the same time, the "relationship" benefit is particularly shallow when the host offers an entire property, often with keys handed off via a doorman or lockbox, so the guest and host may never even meet in person. When there is little or no "relationship" to build, Airbnb’s reasoning provides particularly poor support for a policy that harms disadvantaged guests.

    Meanwhile, Airbnb’s "get to know one another" principle is undercut by the company’s actions in other contexts—calling into question whether this factor should be taken at face value. Notably, Airbnb prevents hosts and guests from sharing email addresses and phone numbers before confirming a booking, running software to scan every message for prohibited material. Airbnb does not impose these restrictions because they in some way help build relationships between users; quite the contrary, these restrictions prevent users from talking to each other directly, by email or phone, in the ways they find convenient. Rather, the Airbnb imposes these restrictions to protect its business interests—preventing guests from booking directly and circumventing the company’s fees. Airbnb’s "get to know one another" purpose thus seems conveniently self-serving—invoked when it supports Airbnb’s favored approach, but quickly discarded when costly.

  • Third, Airbnb proposes that "guests should not be asked or required to hide behind curtains of anonymity when trying to find a place to stay." The report continues: "technology shouldn’t ask us to hide who we are. Instead, we should be implementing new, creative solutions to fight discrimination and promote understanding."

    Here too, Airbnb’s approach favors the preferences of the many over the needs of those who face discrimination. While Airbnb frames its approach as not asking guests to be anonymous, in fact Airbnb does much more than that: Airbnb affirmatively prohibits guests from being anonymous, including requiring that guests register using their real names, validating names against government s and credit records, and presenting each guest’s real name, not a pseudonym, for host approval. Far from giving guests more choice to reveal or withhold information, Airbnb requires guests to reveal information—even when research makes clear that the information facilitates discrimination.

    If there was reason to think Airbnb’s other changes would actually, completely, and promptly end discrimination by hosts, guests might feel confident in sharing sensitive information such as race. But given the likelihood that discrimination will continue despite the changes Airbnb promises, disfavored guests have every reason to want to conceal information that could facilitate discrimination. Airbnb’s policy continues to disallow them from doing so.

Some might counter that Airbnb hosts are informal and ought to have more information than hotels or ordinary landlords. Indeed, one might imagine a policy that distinguished between classes of hosts. If a host occasionally offers a shared room or a portion of a property with the host on site, the relationship feels informal, and some might argue that anti-discrimination rules are overkill in such situations. Conversely, if the host is off-site and the guest uses the property exclusively, the arms-length relationship looks more like a hotel. By all indications, the latter is vastly more common than the former (whether measured in nights booked or, especially, revenue). Airbnb’s report could have considered policies that vary based on the property type—perhaps retaining photos and names for the most informal hosts, where personal interaction between guests and hosts is a realistic possibility, while removing them for hosts offering arms-length rental of entire properties. But Airbnb devoted not a single sentence to this possibility.

Airbnb report’s silence on compulsory arbitration—and the prior positions of Airbnb’s distinguished consultant-advisors

Airbnb’s report is completely silent on the company’s requirement that users arbitrate their disputes. Nowhere mentioned in the report, despite criticism in media discussions of discrimination at Airbnb, the company’s Terms of Service make arbitration compulsory for all complaints users may have about any aspect of Airbnb’s service. Airbnb drafted the arbitration requirement and does not allow users to negotiate its provisions (or anything else). The arbitration policy requires that any concerned user bring a claim on an individual basis, not in any kind of group with others who have similar concerns. The predictable—and by all indications, intended—effect of Airbnb’s arbitration requirement is that users cannot obtain meaningful relief for a broad set of complaints they may have against Airbnb.

Distinguished consumer organizations have widely criticized arbitration as improper for consumers’ disputes with companies. But for Airbnb, arbitration offers both procedural and substantive benefits. No individual consumer could bring a compelling arbitration case against Airbnb: There would be no economic rationale for an attorney to accept such a case, as even the most favorable resolution of the dispute would bring a small recovery and correspondingly limited funds to pay for the attorney’s time. Only representing hundreds or thousands of consumers, en masse, would justify the time and talent of top attorneys. But Airbnb’s arbitration clause specifically disallows class actions and other group suits.

Moreover, arbitrators are chosen through processes that bias them against consumers’ claims. One lawyer recently explained why arbitration tends to favor companies over consumers: "I use the same arbitrators over and over, and they get paid when I pick them. They know where their bread and butter comes from."

In the context of discrimination at Airbnb, new and novel questions make arbitration particularly inappropriate. Arbitration lacks an appeal process where different judges evaluate an initial decision—the proper way to develop policy in new areas of law. And with arbitration results secret, even if one consumer prevailed in arbitration, others would not learn about it. Nor would other arbitrators be bound by a prior dispute’s conclusions even in identical circumstances.

Tellingly, Airbnb is at this moment invoking its arbitration requirement to attempt to dispose of class action litigation alleging discrimination. In May 2016, Virginia resident Gregory Selden filed a class action complaint, alleging that discrimination on Airbnb violated the Civil Rights Act of 1964, 42 USC 1981, and the Fair Housing Act. In response, Airbnb did not dispute that Selden had faced discrimination, nor did Airbnb explore the question of whether the host, Airbnb, or both should be responsible. Rather, Airbnb merely invoked the arbitration provision, arguing that the court could not hear the dispute because Airbnb required all users to agree to arbitrate, and thereby required all users to promise not to sue. As of September 2016, the court has yet to rule. (Case docket.)

Throughout its report, Airbnb cloaks itself in the names and resumes of distinguished advisors (including a seven-page personal introduction from the author and additional listing of experts consulted). But Airbnb’s advisors have taken tough positions against compulsory arbitration—positions which undercut Airbnb’s attempt to invoke arbitration to avoid judicial scrutiny of its practices.

Consider the position of the ACLU during the time when Airbnb consultant Laura Murphy, the report’s sole author, was ACLU’s Legislative Director. In a 2013 letter to senators considering the Arbitration Fairness Act of 2013, the ACLU explained the importance of "end[ing] the growing predatory practice of forcing … consumers to sign away their Constitutional rights to legal protections and access to federal and state courts by making pre-dispute binding mandatory arbitration … clauses unenforceable in civil rights, employment, antitrust, and consumer disputes." The letter continued: "Forced arbitration erodes traditional legal safeguards as well as substantive civil and employment rights and antitrust and consumer protection laws." Similarly, the ACLU’s 2010 letter also noted that "[f]orced arbitration particularly disadvantages the most vulnerable consumers." Murphy’s position at the ACLU entailed overseeing and communicating ACLU’s positions on proposed federal legislation including this very issue. Murphy’s failure to object to Airbnb’s ongoing use of arbitration clauses, which similarly eliminate both procedural safeguards and substantive rights for historically-disadvantaged groups, is particularly striking in the context of the ACLU positions she previously led.

Airbnb’s other consultant-advisors have similarly taken positions against compulsory arbitration. Consider Eric Holder, former US Attorney General, now a partner at the prestigious law firm Covington & Burling. Under Holder’s leadership, the US Department of Justice repeatedly opposed compulsory arbitration, including filing a Supreme Court amicus brief critiquing American Express’s attempt to impose arbitration on merchants. DOJ there argued that "the practical effect of [the arbitration agreement] would be to foreclose [merchants] from effectively vindicating their Sherman Act [antitrust] claims." DOJ went on to explain that the arbitration agreement makes an "impermissible prospective waiver" of unknown claims, and DOJ noted that private enforcement of federal statutes is important to the overall regulatory scheme—an objective that would be undermined if parties could be forced to effectively waive their claims through compulsory arbitration. Holder’s failure to object to Airbnb’s ongoing use of arbitration clauses, similarly designed to escape federal claims that cannot otherwise be pursued, is a sharp change from the DOJ positions he previously oversaw. I credit that Murphy is the sole author, and Holder and Airbnb’s other consult-advisors have taken no public position to endorse the report or Airbnb’s approach. But when Airbnb’s consultant-advisors allow Airbnb to use their names and credentials, both in the report body and in repeated statements to the press, they necesarily lend their reputations to the company’s approach.

Facing scrutiny of its arbitration provisions in June 2016, Airbnb told the New York Times that "these [arbitration] provisions are common." Certainly many companies require that customers arbitrate their disputes. But Airbnb’s service raises persistent and widespread concerns about discrimination (among other issues). Even if arbitration were appropriate for credit cards and cell phone plans (which, to be sure, many consumer advocates dispute), it may not be appropriate for questions of race, equality, and justice. Moreover, as Airbnb seeks public approval for its anti-discrimination efforts, it ought not reject the standard dispute resolution procedures provided by law. It is particularly galling to see Airbnb’s report totally silent on dispute resolution despite prior discussion in public discussions and the press. Airbnb should remove its arbitration clause, if not for all disputes, then at least for claims of discrimination.

Airbnb’s insistence that consumers arbitrate, without the benefit of courts or court procedures, is a stark contrast to Airbnb’s approach to protect its own interests. Airbnb does not hesitate to file lawsuits when lawsuits are in the company’s interest. Most notably, Airbnb recently sued San Francisco, Santa Monica, and Anaheim over laws it disliked. Whatever the merits of Airbnb’s claims (and on that point, see my July critique with Nancy Leong), Airbnb is happy to take its preferred disputes to court—while specifically prohibiting consumers from doing so.

Testing and data

Airbnb says fixing discrimination is a "top priority," and this month’s report repeatedly echoes that claim. In that context, one might expect the company to welcome academic research to help investigate. Instead, Airbnb specifically bans it.

Consider the limits of research to date. My 2015 paper (with Mike Luca and Dan Svirsky) analyzes experiences of rookie Airbnb guests in five cities. Much is left to be studied. How about outcomes in other cities? What happens when a guest gets a favorable review from a prior host? Do hosts tend to prefer a white rookie guest with no reviews, or a black guest with a single five-star review? How about guests who have verified their Airbnb credentials by linking Facebook and LinkedIn accounts or completing other profile verifications? Do outcomes change after Airbnb’s September email to users and (planned) November policy change? Via the same methodology demonstrated in our paper, other researchers could test these questions and more. But Airbnb specifically prohibits such research via Terms of Service provisions. For one, Airbnb disallows the use of software to study its site (TOS section 14.2) looking for patterns that indicate discrimination. Moreover, Airbnb specifically prohibits creating multiple accounts (14.14), an approach widely used (by us and others) to compare the way hosts respond to guests of varying race.

These problems have a particularly clear solution. Airbnb should revise its Terms of Service to allow bona fide testing.

Airbnb’s report also offers a series of claims grounded in data ("The company’s analysis has found…", "Airbnb’s research and data show…") as well as promises to collect additional data and run additional analyses. But Airbnb asks the public to accept its analyses and conclusions without access to the data supporting its conclusions. Airbnb should offer more to counter skepticism, particularly after widely-discussed allegations of misleading or incomplete data. Certainly Airbnb could provide the interested public with aggregate data measuring discrimination and showing the differential outcomes experienced by white versus black users. If Airbnb now has mechanisms to measure discrimination internally, as the report suggests, it’s all the more important that the company explain its approach and detail its methodology and numerical findings—so past outcomes can be compared with future measurements.

Airbnb’s response in context

In my June article proposing methods to prevent discrimination at Airbnb, I called for concealing guest photos when guests apply to hosts, similarly concealing guest names, normalizing dispute resolution, and allowing testing. I didn’t expect Airbnb to do all of this. But I was disappointed that Airbnb’s response discusses only the first of these four changes, and even that only superficially. Based on Airbnb’s promise of a "comprehensive review," I hoped for more.

Airbnb argues that "there is no single solution" to discrimination and that "no one product change, policy or modification … can eliminate bias and discrimination." Certainly one might imagine multiple policies that would help make a difference, and the combination of multiple policies might be more effective than a single policy alone. But temporarily concealing photos and names, as guests apply to hosts, is the simplest and most promising solution by far. The bar is high for Airbnb to reject this natural and well-established approach; Airbnb’s report offers little to convince a skeptical reader that appropriate concealment, so widely used in other contexts, would not work at Airbnb. Nor does Airbnb’s report make any serious effort to establish that Airbnb’s alternatives will be effective. In both these respects, the concerned public should demand more.

Assessing Airbnb’s Prospects in its San Francisco Litigation with Nancy Leong

Last week the Internet buzzed with news of Airbnb’s lawsuit against San Francisco. Dissatisfied with a new ordinance updating and enforcing 2014 regulations of short-term rentals, Airbnb filed suit against the city, arguing that the new ordinance violated both federal law and the federal constitution.

In today’s piece, Nancy Leong and I assess Airbnb’s arguments in its San Francisco complaint — finding some validity but, on the whole, considerable weakness.

Assessing Airbnb’s Prospects in its San Francisco Litigation – Yale Journal of Regulation – Notice & Comment

Refunds for Minors, Parents, and Guardians for Purchases of Facebook Credits

On May 26, 2016, the U.S. District Court for the Northern District of California approved the settlement of a class action against Facebook involving in-app purchases of Facebook Credits by minor children. The case was maintained on behalf of a class of children who were Facebook users (“child users”) below the age of 18 from whose Facebook accounts Facebook Credits were purchased. The case was filed by two minor children through their parents on February 23, 2012. The two children and the class were represented by attorneys Brooks Cutter and John R. Parker of the Cutter Law Firm in Sacramento, California; Daniel B. Edelman of the firm of Katz, Marshall & Banks in Washington, D.C.; and Benjamin Edelman, an associate professor at the Harvard Business School. On March 10, 2015, the Court certified the case as a class action for purposes of declaratory and injunctive relief on behalf of all minor children who were users of Facebook from whose Facebook accounts Facebook Credits were purchased at any time between February 23, 2008 and the date of the certification order, March 10, 2015. At the same time, the Court declined to certify a class action for purposes of class-wide monetary relief.

During the period covered by the suit, hundreds of thousands of child users purchased Facebook Credits for use in playing Facebook-based games and applications. To make such purchases, child users generally used credit cards, debit cards or other payment instruments that belonged to their parents or other responsible adults. Facebook made a practice of retaining the payment information provided at the time of the child user’s initial purchase for easy use in later purchases. Facebook advised that purchases by children were to be made only with the permission of the parent or guardian. Facebook did not, however, require evidence that any of the purchases was actually authorized by the parent, guardian or owner of the payment instrument. In many instances, the child user did not have authorization to use the card or other payment instrument to purchase Facebook Credits. Facebook specified in its terms of use that all transactions are “final”. It later stated that all transactions are “final except as otherwise required by law”.

Facebook’s Terms of Use state that purchase transactions are governed by the law of California. The Family Code of California provides that contracts with minors are voidable by the minor at any time before attaining the age of 18 or within a reasonable time thereafter. The court applied that principle to this case: “The law shields minors from their lack of judgment and experience and under certain conditions vests in them the right to disaffirm their contracts. Although in many instances such disaffirmance may be a hardship upon those who deal with an infant, the right to avoid his contracts is conferred by law upon a minor for his protection against his own improvidence and the designs of others. It is the policy of the law to protect a minor against himself and his indiscretions and immaturity as well as against the machinations of other people and to discourage adults from contracting with an infant.” (MTD decision, October 25, 2012, at pp. 11-12.) The court continued: “[O]ne who provides a minor with goods and services does so at her own risk.” (Id. at p.12.)

Facebook defended the claims in part by arguing that kids had received and used the electronic goods they paid for. The court specifically rejected this reasoning, finding that kids are entitled to refunds even for items they used. “Under California law, a minor may disaffirm all obligations under a contract, even for services previously rendered, without restoring consideration or the value of services rendered to the other party.” (MTD Decision at p.14, internal quotation marks omitted)

Prior to the settlement, Facebook provided an online procedure for refund requests in various specific circumstances such as fraudulent use of a user’s account by a third-party. Facebook’s refund procedure did not include an option to request a refund on the ground that the purchase was made when the user was a minor.

The settlement requires Facebook to apply refund practices and policies with respect to U.S. minors that comply with the California Family Code.

The settlement further requires Facebook to “add to its refund request form for In-App Purchases for U.S. users a checkbox or substantially similar functionality with accompanying text such that users are able to indicate that the In-App Purchases for which they are seeking a refund was made when the user was minor.”

The settlement additionally requires Facebook to “implement a dedicated queue within Facebook to address refund requests in In-App Purchases, made by U.S. Minors subject to verification of minority. The employees staffing the dedicated queue will receive further training regarding how to analyze and process such refund requests in accordance with applicable law.”

If you or your minor child were charged for Facebook credits purchased from an account belonging to someone age 17 or younger, you may be entitled to obtain refunds for such purchases through the use of the dedicated queue established by Facebook as a result of the settlement. Both minor account holders and the parents and guardians of such minors are entitled to claim such refunds. Claim refunds via the Facebook refund tool.

Free access to selected case documents via Archive.org.

Preventing Discrimination at Airbnb

In January 2014, Mike Luca and I posted a study finding that black hosts on Airbnb face discrimination: by all indications, guests are less willing to stay at their properties, forcing them to lower their prices to attract guests. More recently, Mike Luca, Dan Svirsky, and I contacted hosts using test guest accounts that were white and black, male and female, showing that black guests are less likely to be accepted by hosts. Both findings are troubling: The Internet has the power to make markets fairer and more inclusive, but Airbnb designed its platform to make race needlessly prominent, all but inviting discrimination.

Initially Airbnb responded to our research by framing discrimination as a problem that has "plagued societies for centuries" and emphasizing that the company "can’t control all the biases" of its users. After a barrage of media coverage, Airbnb CEO Brian Chesky this month admitted that discrimination is a "huge issue" and said the company "will be revisiting the design of our site from end to end to see how we can create a more inclusive platform." Indeed, today Airbnb convenes an invitation-only summit in Washington to discuss the situation and, perhaps, design improvements.

While I applaud Airbnb’s new interest in fighting discrimination on its platform, I can’t agree with Chesky’s subsequent claim that preventing discrimination on Airbnb is "really, really hard." Quite the contrary, the solution is apparent and has been known for years. In today’s piece, I renew my longstanding proposal that would substantially fix the problem, then offer two smaller adjustments that are appropriate under the circumstances.

The solution: Limit the distribution of irrelevant information that facilitates discrimination

Online environments make it easy to limit the information that guests and hosts reveal. If certain information causes discrimination, the natural remedy is to conceal that information so customers do not consider it when making booking and acceptance decisions.

Names and photos typically indicate the races of Airbnb guests and hosts. But names and photos are not necessary for guests and hosts to do business. Hosts and guests can amply assess one anothers’ trustworthiness using the significant other information Airbnb already collects and presents. For these reasons, I contend that the Airbnb site should not reveal sensitive race information until a transaction is confirmed. If guests and hosts don’t see names and photos in advance, they simply won’t be able to discriminate on that basis.

The proposal is a smaller change than it might at first appear. In fact, Airbnb has long limited information flows to advance its business interests. Airbnb’s revenue depends not just on introducing hosts to guests, and vice versa, but on transactions actually flowing through Airbnb’s platform so Airbnb can charge booking fees. Airbnb’s revenue would drop if guests and hosts could contact each other directly and agree to pay via Paypal, cash on arrival, or similar. To prevent hosts and guests from going around Airbnb, the company withholds email addresses and phone numbers while the users are still discussing a possible stay — letting each user examine the other’s profile, reviews, verifications, and more, but intentionally withholding the two pieces of information that would undermine Airbnb’s revenue. But Airbnb doesn’t just limit information presented in profiles and request templates; it also affirmatively filters messages between guests and hosts. Airbnb provides a text message system to let users ask questions and share more details, but it doesn’t want the messages to be used to cut Airbnb out of the transaction. So Airbnb’s servers examine each message and blocksanything that looks like an email address or a phone number. In short, there’s ample precedent for Airbnb withholding information — when it wants to.

I anticipate several objections to the proposed change:

  • Trust and safety. Certainly trust issues are central to Airbnb’s business — letting strangers stay in your home when you’re not there to supervise; staying in a stranger’s home when you’re at your most vulnerable (asleep). In that context, some might argue that every possible piece of additional information is important and should be provided. But I question what information the names and photos truly add. Airbnb already validates users’ identities, including checking driver’s license photographs and asking identity verification questions that impostors would struggle to answer. Airbnb reports linked Facebook and LinkedIn profiles, and Airbnb presents and tabulates reviews from prior transactions. Plus, all Airbnb transactions are prepaid. As a result, a host considering a guest’s request learns that the prospective guest has (say) a verified phone number and email, verified identity, verified Facebook and LinkedIn profiles with two hundred connections in total, and five favorable reviews from other Airbnb stays within the last year. A name and photo reveal race, gender, and age, but they provide little information about genuine trustworthiness. Whatever information the name and photo provide, that information comes more from (potentially inaccurate) stereotypes than from the name and photo themselves.
  • Perhaps users would be confused by communications without names. But "Airbnb Guest" and "Airbnb Host" make fine placeholders. Alternatively, Airbnb could move to a username system, letting users choose their own nicknames to use before a transaction is confirmed. eBay follows exactly that approach, and it works just fine. Airbnb would still organize a host’s messages with a given guest into a single page, and vice versa.
  • Some hosts want to see guest photos before accepting a request, and vice versa for guests choosing hosts. But if a homeowner is particularly concerned about strangers visiting his property, perhaps he shouldn’t be running a de facto hotel.
  • Photos help guests and hosts recognize each other. Airbnb’s David King, Director of Diversity and Belonging, in April 2016 told NPR: "The photos are on the platform for a reason. … You want to make sure that that guest that shows up at your door is the person that you’ve been communicating with." But nothing in the proposed change would prevent a host and guest from recognizing each other. After a booking is confirmed, they’d still see names and photos just as they do now. The change is to timing — revealing names and photos only after the booking is final.

In principle, Airbnb’s approach to names and photos could vary based on the type of listing. For example, names and photos might be viewed with special skepticism when a guest is renting the entire property. After all, when a guest occupies a property exclusively, the guest and host will have limited interaction. Indeed, they may never meet in person at all, exchanging keys via a doorman or lockbox. Then the specific identity of guest and host are all the less important. Conversely, it’s somewhat easier to see a proper role for photos and names when a host is truly "sharing" a property with a guest, jointly using common property facilities (perhaps a shared kitchen) or otherwise interacting with each other.

Allow testing

After our study, several users ran their own tests to assess possible discrimination. For example, after being rejected by a host, a black guest might create a new account with a "white-sounding" name and a photo of a white person — then use that new account to reapply to the same host. Multiple users have tested for discrimination via this methodology. (Examples: 1, 2)

Crucially, Airbnb prohibits such testing. Airbnb’s compulsory Terms of Service forbids all test accounts, instead requiring that users "agree to provide accurate, current and complete information during the registration process." Furthermore, Airbnb specifically insists that each user "may not have more than one (1) active Airbnb Account," and Airbnb claims the right to entirely eject any person who creates multiple accounts. But if each a user is limited to a single account, in the user’s true name, most testing procedures are unworkable.

Airbnb rigorously enforces its prohibitions on test accounts and follows through on its threats to exclude users with multiple accounts. Indeed, during the testing for my second article about Airbnb discrimination, the company closed my personal account — even removing my reputation and reviews accumulated from prior stays. I requested that Airbnb reopen my account but have received no reply, and my account remains disabled to this day.

Airbnb has no proper reason to penalize those who test its services. It would be intolerable for a car dealership to post a sign saying "No testers allowed" in hopes of concealing prices that vary prices based on a buyer’s race. Nor should Airbnb be able to conceal discrimination on its platform through contractual restrictions and penalties.

Normalize dispute resolution

The standard American approach to dispute resolution is the legal system — judge and jury. Dissatisfied hosts and guests — such as those who think they’ve faced discrimination — ordinarily could go to court to explain the problem and try to articulate a violation of applicable law. But Airbnb specifically prohibits users from filing a standard lawsuit. In particular, Airbnb’s Terms of Service instead demand that "any dispute, claim or controversy arising out of or relating to … the Services or use of the Site … will be settled by binding arbitration."

For guests and hosts, arbitration presents several key problems. For one, Airbnb chose the arbitration service, so anyone pursuing a grievance might naturally worry that the arbitrator will favor Airbnb. Furthermore, arbitration results are confidential — so even if some users prevail against Airbnb, the interested public would never find out. Arbitration also provides little to no ability for complainants to get the documents they need to prove their case, for example by searching Airbnb’s records to learn what the company knew, who else complained, and what alternatives it considered. Nor does arbitration provide an appeals process appropriate for exploring new or complex questions of law. Most of all, Airbnb requires that each dispute proceed solely on an individual basis, and "the arbitrator may not consolidate more than one person’s claims." But individual complaints are inevitably small, with value too low to justify the top-notch attorneys and experts who would be needed to prove discrimination and explore Airbnb’s responsibility.

Courts, not arbitrations, are the proper way to resolve these important disputes. The appearance of legitimacy would be much improved if decisions were rendered by a judge and jury chosen through formal government processes. With access to Airbnb documents and records as provided by law, aggrieved users would be able to search for information to support their claims — giving them a fair chance to assemble the evidence they need. With appeals, a series of judges would assess the situation and correct any errors in legal reasoning. And with a single case assessing the rights of a group of similar users, economies of scale would allow users to get the specialized assistance they need to have a real shot.

I don’t know that aggrieved guests or hosts would prevail against Airbnb on matters of discrimination. In some respects, such a case would break new ground, and Airbnb would forcefully argue that it is individual hosts, not Airbnb itself, whose actions are out of line. But Airbnb should face such complaints on the merits, not hide behind a contract that prevents users from bringing suit.

Airbnb told the New York Times that "these [arbitration] provisions are common." Certainly many companies require that customers arbitrate any disputes. But Airbnb’s service is special, raising persistent and serious concerns about discrimination (among other issues). These heightened sensitivities call for a different approach to dispute resolution — and a dispute system that works for credit cards and cell phone plans may not be right for questions of race, equality, and justice.

Airbnb also told the Times that "we believe ours [our arbitration agreement] is balanced and protects consumers." But it’s hard to see the balance in a contract that only takes rights away from users. Were the contract silent on dispute resolution, users could sue in any court authorized by law to hear the dispute, but instead Airbnb insists that not a single court, in any jurisdiction nationwide, can adjudicate any dispute pertaining to users’ relationships with Airbnb.

The incomplete benefits of Instant Book

Airbnb hosts are able to discriminate against disfavored guests because Airbnb’s standard process gives hosts discretion as to which guests to accept. Airbnb’s Instant Book feature thus offers a potential mechanism to reduce discrimination: When hosts pre-promise to accept any interested guest who agrees to pay, there’s much less opportunity to discriminate. Nonetheless, Instant Book addresses only a portion of the problem.

The biggest weakness of Instant Book is that only a fraction of properties offer this feature. A guest who wants to use Instant Book to avoid discrimination is thus accepting a much narrower range of properties. Airbnb periodically encourages hosts to try Instant Book, and it seems the proportion of properties with Instant Book is increasing, but slowly. That’s unsatisfactory: Guests shouldn’t have to choose between fair treatment and a full range of properties.

A second problem with Instant Book is that it serves only to protect guests from discrimination by hosts, but not to protect hosts from discrimination by guests. My research indicates that both problems are real, and Instant Book does nothing about the second.

A final concern is the prospect of cancellations that undo the anti-discrimination benefits of Instant Book. In principle a host could invoke Airbnb’s cancellation feature to reject a disfavored guest whose request was automatically confirmed by Instant Book. That’s exceptionally disruptive to the guest, taking away a booking which had already been paid in full and presented, to the guest and in Airbnb records, as confirmed. These problems are more than speculative; among others, the racist North Carolina host who canceled a black guest’s confirmed reservation had initially accepted that reservation via Instant Book.

To its credit, Airbnb requires a host to provide a reason when cancelling an Instant Book reservation, and Airbnb limits such cancellation to three per year. But the cancellations are penalty-free without any charge to hosts or any indication on a host’s profile page. (In contrast, when non-Instant Book hosts cancel reservations, they are charged fees and are penalized in profiles and on search results.) Moreover, three cancellations may suffice for many hosts to implement discriminatory preferences. If a host receives only occasional requests from the guests it seeks to discriminate against, the host could cancel those guests’ Instant Book stays with relative impunity.

Looking forward

Airbnb co-founder Joe Gebbia recently explained the site’s widespread use of photos of guests and hosts: "[A]nytime we could show a face in our service, we would … – in search results, on profiles, on the actual homepage.” Certainly photos are visually appealing and add some information. But the risk of discrimination appears to be unavoidable when photos are presented before a transaction is confirmed. No one would tolerate a hotel that required prospective guests to submit photos — nor a traditional bed-and-breakfast that did so. Nor should this approach be used online. The risk of discrimination is just too great relative to any benefit the photos may provide.

In January 2014, Mike Luca and I suggested the changes Airbnb should make to prevent discrimination:

[T]here is no fundamental reason why a guest need s see a host’s picture in advance of making a booking — nor does a guest necessarily even need to know a host’s name (from which race may be infered…). Indeed, Airbnb itself prohibits (and run s software to prevent) hosts and guests from sharing email addresses or phone numbers before a booking is made, lest this information exchange let parties contract directly and avoid Airbnb fees. Given Airbnb’s careful consideration of what information is available to guests and hosts, Airbnb might consider eliminating or reducing the prominence of host photos: It is not immediately obvious what beneficial information these photos provide, while they risk facilitating discrimination by guests. Particularly when a guest will be renting an entire property, the guest’s interaction with the host will be quite limited, and we see no real need for Airbnb to highlight the host’s picture.

Two and a half years later, the proposal remains appropriate, easy, and effective. Airbnb CEO Brian Chesky says the company "needs help solving" discrimination on Airbnb . Perhaps our longstanding proposal can be of assistance.

How Uber Uses API Restrictions to Block Price Comparison and Impede Competition updated June 3, 2016

Popular as Uber may be, it isn’t the only way to summon a car for a ride across town. In most US cities, Lyft is a strong number two. Here in Boston, Fasten touts lower fees to drivers, promising cheaper rides for passengers and greater revenue to drivers. Drivers often run multiple apps, and passengers switch between them too. If these apps competed fiercely, Uber might be forced to lower its fee, reducing or eliminating profit. So what justifies Uber’s lofty $68+ billion valuation?

For years, Uber has tried to use its API as a potential barrier against competition. Uber invites third-party developers to connect to its servers to get real-time information about vehicle location (how many minutes until a vehicle can pick up a passenger at a given location) and the current level of surge pricing. But there’s a catch: To access data through Uber’s API, developers must agree not to include Uber API data in any tool that Uber deems competitive.

Uber encourages app developers and the general public to think this API restriction is Uber’s right—that Uber’s data is for Uber to use or restrict as it chooses. But the restriction is calculated and intended to block competition—a purpose considered improper under competition laws, and a special stretch for Uber in light of the company’s positions on related issues of competition and regulation.

Uber’s API restrictions

Uber’s API Terms of Use explains Uber’s purpose in remarkable simplicity:

Be a strong, trustworthy partner to Uber. Please do not:

Compete with Uber or try to drive traffic away from Uber.

Aggregate Uber with competitors.

Uber’s API Terms of Use then instruct:

In general, we reserve the sole right to determine whether or not your use of the Uber API, Uber API Materials, or Uber Data is acceptable, and to revoke Uber API access for any Service that we determine is not providing added benefit to Uber users and/or is not in the best interests of Uber or our users.

The following are some, but not all, restrictions applicable to the use of the Uber API, Uber API Materials, and Uber Data:

You may not use the Uber API, Uber API Materials, or Uber Data in any manner that is competitive to Uber or the Uber Services, including, without limitation, in connection with any application, website or other product or service that also includes, features, endorses, or otherwise supports in any way a third party that provides services competitive to Uber’s products and services, as determined in our sole discretion.

Uber’s developer documentation specifically warns:

Using the Uber API to offer price comparisons with competitive third party services is in violation of § II B of the API Terms of Use. Please make sure that you familiarize yourself with the API Terms of Use to avoid losing access to this service.

Assessing Uber’s API restrictions

The most favorable reading of Uber’s API restrictions is that Uber alone controls information about the price and availability of its vehicles. From Uber’s perspective, accessing Uber’s API is a privilege, not a right. Indeed, some might ask why Uber might be expected, let alone required, to assist a company that might send users elsewhere. A simple contract analysis shows no reason why the restriction is improper; if Uber prominently announces these requirements, and developers willingly accept, some would argue that there’s no problem.

A strong counterargument begins not with the contract but with Uber’s purpose. One might ask why Uber seeks to ban comparisons with other vehicle dispatch services. Uber doesn’t ban aggregators and price comparison tools because it believes these tools harm passengers or drivers. On the contrary, Uber bans aggregators and price comparison tools exactly because they help passengers and drivers but, potentially, harm Uber by directing transactions onto other platforms. Uber’s purpose is transparently to impede competition —to make it more difficult for competing services to provide relevant and timely offers to appropriate customers. Were such competitors to gain traction, they would push Uber to increase quality and reduce its fees. But blocking competing services positions Uber to retain and indeed increase its fees.

Consider a competitor’s strategy in attempting to compete with Uber: Attract a reasonable pool of drivers, impose a lower platform fee than Uber, and split the savings between drivers and passengers. If Uber’s current fee is, say, 20%, the new entrant might charge 10%—yielding savings which could be apportioned as a 5% lower fare to passengers and a 5% higher payment to drivers.

Crucially, aggregators help the entrant reach passengers at the time when they are receptive to the offer. Every user at an aggregator is in the market for transportation, not just generally but at that very moment, making them naturally receptive to an entrant’s offer. Furthermore, a user who visits an aggregator has all but confirmed his willingness to try an alternative to Uber. So aggregators are the most promising way for an entrant to reach appropriate users.

At least as important, aggregators help an entrant gain momentum despite a small scale of operations. At the outset, a new entrant wouldn’t have many drivers. So if a consumer installs the entrant’s app and opens it to check vehicle availability, the entrant’s proposed vehicle would often be further away, requiring that passengers accept longer wait times and that drivers accept longer unpaid trips to reach paid work. Notably, an aggregator helps the entrant reach users already close to the available vehicles—providing an efficient way for the entrant to begin service.

In contrast, without aggregators, entrants face inferior options for getting started. They could advertise in banners or on billboards to attract some users. But those general-purpose ad channels tend to reach a broad swath of users, only a portion of whom need Uber-style service, and even fewer of whom are ready to try a new service. Meanwhile, any users found through these channels will tend to have diverse requirements for ride timing and location; there is no way for an entrant to reach only the passengers interested in rides at the times and places where the entrant has available drivers. With a low density of drivers and passengers, the entrant’s passengers will face longer wait times and drivers will face longer unpaid positioning trips. Some users may nonetheless be willing to try the entrant’s service. But they’ll have to open the entrant’s app to check, for each trip, whether its availability and pricing meet expectations—extra steps that impose delay and will quickly come to seem pointless to all but the most dedicated passengers. As a whole, these factors reduce the likelihood of the new service taking off. Indeed, small transport services have famously struggled. Consider, for example, the 2015 cessation of Sidecar.

Uber might have tried to explain away its API restrictions with pretextual purposes such as server load or consumer protection. These arguments would have been difficult: Price comparison requests are not burdensome to Uber’s servers; Uber nowhere limits the quantity of requests for other purposes (e.g. through an API fee or through throttling). Nor is there any genuine contention that price comparison services are, say, confusing to users; the difference between an Uber and a Lyft ride can be easily communicated via an appropriate logo, on-screen messaging, and the like. But in any event Uber hasn’t attempted these arguments; as Uber itself admits in the rules quoted above, the API restrictions are designed solely to advance the company’s business interests by blocking competition.

The relevant legal principles

One doesn’t readily find antitrust cases about APIs or facilitating price comparison. But Uber’s API partners act as de facto distributors—telling the interested public about Uber’s offerings, prices, and availability. A long line of cases takes a dim view of dominant firms imposing exclusivity requirements on their distributors. Areeda and Hovenkamp explain the tactic, and its harm, in their treatise (3d ed. 2011, ¶1802c at 76):

[S]uppose an established manufacturer has long held a dominant position but is starting to lose market share to an aggressive young rival. A set of strategically planned exclusive-dealing contracts may slow the rival’s expansion by requiring it to develop alternative outlets for its product, or rely at least temporarily on inferior or more expensive outlets. Consumer injury results from the delay that the dominant firm imposes on the smaller rival’s growth.

Most recently, the FTC brought suit against McWane, the dominant US pipe fitting supplier, which had controversially required distributors to sell only its products, and not products from competitors, by threatening forfeiture of rebates and perhaps loss of access to any McWane products at all. The FTC found that McWane’s exclusionary distribution policy maintained its monopoly power; the Eleventh Circuit upheld the FTC’s finding; and the Supreme Court declined to hear the case. McWane thus confirms the competition concerns resulting from exclusive contracts from distributors. In relevant respects, the parallels between Uber and McWane are striking: Both companies use contracts to raise rivals’ costs to prevent them from growing into effective competitors. Compared to McWane, Uber’s API restrictions are in notable respects more aggressive. For example, McWane’s first response to a noncompliant distributor was to withhold rebates, and in litigation McWane protested that its practice was not literally exclusive dealing but rather a procompetitive inducement (through rebates yielding lower prices). Putting aside McWane’s failure in these arguments, Uber could make no such claims, as its API restrictions (and threats to UrbanHail, discussed below) exactly implement exclusive dealing, expelling the noncompliant app or site from access to Uber’s API as a penalty for including competitors.

More generally, Uber’s conduct falls within the general sphere of exclusionary conduct which has been amply explored through decades of caselaw and commentary. The Department of Justice’s 2009 guidance on Single-Firm Conduct Under Section 2 of the Sherman Act is broadly on point and usefully surveys relevant doctrines. As the DOJ points out, the essential question for exclusionary conduct cases is whether a given tactic is appropriate, aggressive competition (which competition policy sensibly allows) versus a practice intended to exclude competition (more likely to be prohibited under competition law). After considering several alternatives, the DOJ favorably evaluates a "no-economic-sense test" that asks whether the challenged conduct contributes profits to the firm apart from its exclusionary effects. In Uber’s case, no such profits are apparent. Indeed, the API restrictions require Uber to turn down referrals from apps that violate the API restrictions—foregoing short-term profits in service of the long-term exclusionary purpose.

The DOJ ultimately offers its greatest praise for an "equally efficient competitor test," asking whether the challenged conduct is likely in the circumstances to exclude a competitor that is equally efficient or more efficient. Uber’s restrictions fare poorly under this test. Consider a more efficient competitor—one with, perhaps, lower general and administrative costs that allow it to charge a lower fee on top of payments to drivers. Uber’s restrictions prevent such a competitor from effectively reaching the consumers who would be most receptive to its offer.

Separately, the DOJ notes the promise of conduct-specific tests that disallow specific practices. While the caselaw on APIs, data access, and price comparison is not yet well-developed, one might readily imagine a conduct-specific test in this area. In particular, if a company offers a standardized and low-burden mechanism for consumers, intermediaries, and others to check its prices and availability, the company arguably ought not be able to withhold access to that information for the improper purpose of blocking competition.

Relatedly, the DOJ points out the value of considering the scope of harm from the challenged conduct, impact of false positives and false negatives, and ease of enforcement. Uber’s restrictions fare poorly on these fronts too. Uber would face little burden in being required to provide data about its prices and availability to comparison services; Uber has already built the software interface to provide this data, and the servers are by all indications capacious and reliable. Enforcement would be easy: Require Uber to strike the offending provisions from its API Terms and Conditions. Uber need not create any new software interfaces or APIs in order to comply; only Uber’s lawyers, but not Uber’s developers, would need take action.

Uber might argue that it is one of many transportation services and that the Sherman Act should not apply given Uber’s small position in a large transport market. Indeed, Sherman Act obligations are predicated on market power, but Uber’s size and positioning leave little doubt about the company’s power. As the leading app-based vehicle dispatch service, Uber would certainly be found a dominant firm in such a market. In a broader market for hired transport services, including taxis and sedans, Uber surely still has market power. For example, analysis of expense reports indicates that business travelers use Uber more than taxis.

Experience of transport comparison services and the case of UrbanHail

As early as August 2014, analysts had flagged Uber’s restriction on developers promoting competing apps. Indeed, the subsequent two years have brought few apps or sites that help consumers choose between transportation platforms—some with static data or general guidance, but no widely-used service with up-to-the-minute location-specific data about surges and vehicle availability. Uber’s API restrictions seem to be working in exactly the way the company hoped.

An intriguing counterexample comes from UrbanHail, an app which promises to present "all of your ridesharing and taxi options in one click to help you save time and money [and] frustration." (UrbanHail was created by five Harvard Business School MBA students as their semester project for the required FIELD 3 course. As part of my academic duties as a HBS faculty member, I happen to teach FIELD 3, though I was not assigned these students. I advised them informally and have no official academic, supervisory, or other affiliation with the students or UrbanHail.)

UrbanHail prompted a response from Uber the same day it launched. In a first email, Uber’s Chris Messina (Developer Experience Lead) wrote:

Hey guys, my name is Chris Messina and I run Developer Experience for Uber. Chris Saad [CC’ed] is the PM of the API.

We wanted to congratulate on your recent press as we love seeing folks innovating in the transit space, but wanted to let you know that your use of our API is in violation of section II B of our terms of use.

We’re more than happy for you to continue developing your app, but ask that you remove any features that list Uber’s prices next to our competitors.

Please let us know if you have any questions. Thanks!

Three weeks later, he followed up:

Hey guys,

I haven’t heard back from you, so I wanted to follow up.

Unfortunately, UrbanHail is still violating the agreements you entered with Uber, including not only the API Terms of Use which I mentioned in my previous email, but also Uber’s rider terms (which prohibit scraping or making Uber’s services available for commercial use).

I’d like to highlight that not only are these conditions found in the legal text, but the spirit of our terms are summarized in plain english at the top of that document. Further, a specific warning to not create a price comparison app is provided in-line in the technical reference for the price estimates API.

Thousands of developers around the world use the Uber API to build new, interesting apps. To preserve the integrity of the Uber experience, we require these apps to stay within the guardrails we’ve created, and are set forth in our terms. Despite our efforts to make these terms and policies clear and transparent, you chose to act against them.

All that being said, we very much value the time and energy that developers like you invest in building with the Uber API, and we actively support and encourage them to be creative and innovate with us.

If you build something that complies with our Terms of Use, we would love to reward your effort in a number of ways. Here are just some of the things we can offer:

* A post on our blog featuring your app

* A listing in our showcase

* Affiliate revenue for referring new Uber riders to us

* Access to our "Insiders Program" which offers office hours with the Uber Developer Platform team and exclusive developer events

Please let me know when you’ve taken UrbanHail out of the App Store and removed any related marketing materials so we can start working on a new opportunity together.

Please note, however, if I don’t hear from you by May 31, I’ll be forced to revoke your client ID’s access the Uber API.

Chris

Today, May 31, is Chris’s deadline. I’ll update this post if Chris follows through on the threat to disable UrbanHail’s API access and prevent the app from including Uber in its price comparison.

Update (June 3): UrbanHail reports that Uber terminated its API access, preventing Uber from appearing within Urbanhail’s results page.

Special challenges for Uber in imposing these restrictions

Uber styles itself as a champion of competition. Consider, for example, CEO Travis Kalanick’s remarks to attendees at TechCrunch Disrupt in 2012. His bottom line: "Competition is good." Uber takes similar positions in its widespread disputes with regulators and incumbents transportation providers—styling its offering as important competition that benefits consumers. Against that backdrop, Uber struggles to restrict third-party services that promise to enhance competition.

Indeed, media coverage of Uber’s dispute with UrbanHail has flagged the irony of Uber criticizing competition from other services. The Boston Globe captioned its piece "New app gives Uber a little disruption of its own," opening with "Uber Technologies Inc. built a big business by pushing past regulations that limit competition with taxis. But the tech-industry darling isn’t always happy with smaller companies trying similar tactics." Boston.com was in accord: "Uber rankled by app that compares ride-hailing prices," as was BostInno: "Uber is trying to shut down this Boston price-comparison app."

Twitter users agreed: Henry George: "@Uber Do you find it the least bit ironic that you’re complaining about ride competition with @urbanhail? Don’t try legal BS, innovate!" Michael Nicholas: "The irony of @Uber complaining @urbanhail is ‘breaking the rules’ of api usage is breathtaking." Gustavo Fontana: "@Uber should leave them alone. It’s fair game."

Uber may dispute whether it has the market power necessary to trigger antitrust law and Sherman Act duties. But Uber’s general position on competition is clear. Uber struggles to chart a path that lets it compete with taxis without the permits and inspections required in many jurisdictions—but doesn’t let comparison shopping services compare Uber’s prices with taxis, Lyft, and other alternatives.

Moreover, Uber’s professed allies are equally difficult to reconcile with the company’s API restrictions. For example, Uber this month announced an advisory board including distinguished ex-competition regulators. Consider Neelie Kroes, formerly the European Commission’s Commissioner for Competition who, in that capacity, oversaw the EC’s €497 million sanctions against Microsoft. Having overseen European competition policy and subsequently digital policy for fully a decade, Kroes is unlikely to look favorably on Uber’s efforts to foreclose entry and reduce competition.

Special challenges for Uber’s developer team in imposing these restrictions

A further challenge for Uber is that its key managers—distinguished experts on software architecture—have previously taken positions that are difficult to reconcile with Uber’s efforts to restrict competition.

Best known for creating the hashtag, Chris Messina (Uber’s Developer Experience Lead) boasts a career espousing "openness." In his LinkedIn profile, he notes a prior position as an "Open Web Advocate" and a board member at the "Open Web Foundation." Describing his work at Citizen Agency, he says he "appl[ied] design and open source principles to consulting." Wikipedia disambiguates Messina from others with the same name by calling him an "open source advocate," a phrase repeated in the first sentence of Wikipedia’s article. Wikipedia also notes a 2008 article entitled "So Open It Hurts" about Messina and his then-girlfriend, describing their "public and open relationship." Google reports 1,440 different pages on Messina’s personal site, factoryjoe.com, mentioning the word "open." While the meaning of "open" varies depending on the context, the general premise is a skepticism towards restrictions and limitations—be they requirements to pay for software, limits on how software is used, or, here, restrictions on how data and APIs are used. It’s a world view not easily reconciled with Uber’s restriction on price comparisons.

Chris Saad (Uber’s API Product Manager) has been similarly skeptical of restrictions on data. His LinkedIn page notes that he co-founded the DataPortability Project which he says "coined and popularized the phrase "data portability"; and led "an explosion of conversation[s] about open standards and interoperability." That’s a distinguished background—but here, too, not easily reconciled with Uber’s API restrictions.

It’s no coincidence that Uber’s developer team favors openness. Openness is the natural approach as a company seeks to connect to external developers. But in limiting how other companies use data, Uber violates key tenets of openness, restricting the flow and use of data that partners and consumers reasonably expect to access.

Looking ahead

Uber faces a looming battle to retain its early lead in smartphone-based vehicle dispatch. But as the dominant firm in this sector—with the largest market share and, to be sure, a category-defining name and concept—Uber is rightly subject to restrictions on its methods of competition. Cloaking itself in the aura of competition as it seeks to avoid regulations that apply to other commercial vehicles, Uber is poorly positioned to simultaneously oppose competition from other app-based services.

Uber is not alone in limiting the ways users can access data. In 2008, I flagged Google’s AdWords API restrictions, which impeded advertisers’ efforts to use other ad platforms as well as Google. Google defended the restrictions, but competition regulators agreed with me: Even as the FTC declined to pursue other aspects of early competition claims against Google, FTC pressure compelled Google to withdraw the API restrictions in January 2013. In Europe, these same restrictions were among the EC’s initial objections to Google’s conduct. Google has yet to resolve this dispute in Europe, and may yet face a fine for this conduct (in addition to substantial fines for other challenged practices). Uber’s API restrictions risk similar sanctions—perhaps even more quickly given Uber’s many regulatory proceedings.

What comes next? If Uber follows through on its threat to UrbanHail, as Messina said it soon would, there will again be no app or site to compare prices and availability across Uber and competitors. Uber won’t need to go to court to block UrbanHail; it can simply withdraw the security credentials that let UrbanHail access the Uber API. From what I know of UrbanHail’s size and stature, it’s hard to imagine UrbanHail filing suit; that would probably require resources beyond UrbanHail’s current means.

Nonetheless, Uber is importantly vulnerable. For example, transport is highly regulated, and Uber needs regulatory approval in most jurisdictions where it operates. This approval presents a natural and easy way for policy makers to unlock Uber’s API restrictions: As a condition of participation in a city’s transit markets—using the public roads among other resources—Uber should be required to remove the offending API restrictions, letting aggregators use this information as they see fit. Once one city establishes this requirement, dozens more would likely follow, and Uber’s API restrictions could disappear as suddenly as they arrived.