Abebe v. Yum! Brands, Inc.

CourtDistrict Court, E.D. Texas
DecidedAugust 21, 2024
Docket4:23-cv-00682
StatusUnknown

This text of Abebe v. Yum! Brands, Inc. (Abebe v. Yum! Brands, Inc.) is published on Counsel Stack Legal Research, covering District Court, E.D. Texas primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Abebe v. Yum! Brands, Inc., (E.D. Tex. 2024).

Opinion

United States District Court EASTERN DISTRICT OF TEXAS SHERMAN DIVISION

AZANIA ABEBE, § § Plaintiff, § Civil Action No. 4:23-cv-682 § Judge Mazzant v. § § YUM! BRANDS, INC. and YUM § RESTAURANT SERVICES GROUP, LLC, § § Defendants. §

MEMORANDUM OPINION AND ORDER

Pending before the Court is Defendants Yum! Brands, Inc. and Yum Restaurant Service Group, LLC’s Amended and Opposed Motion to Compel Arbitration and to Stay Litigation (Dkt. #13). Having considered the relevant pleadings, the Court hereby ORDERS that Defendants’ Motion is DENIED without prejudice. Additionally, pending before the Court is Plaintiff Azania Abebe’s Motion to Stay Deadline to Respond to Defendants’ Motion to Compel Arbitration and, in the Alternative, Abebe’s Response to Defendants’ Motion to Compel Arbitration (Dkt. #18). Having considered the relevant pleadings, the Court hereby ORDERS that Plaintiff’s Motion is GRANTED in part. BACKGROUND I. Factual Background Azania Abebe (“Abebe”) was employed by Defendant Yum Restaurant Services Group, LLC from August 4, 2014, to July 15, 2023 (Dkt. #13 at p. 2). Defendants Yum Restaurant Services Group, LLC and Yum! Brands, Inc. (collectively, “Yum!”) allege that Abebe entered into an arbitration agreement (“Arbitration Agreement”) with Yum! on October 5, 2015 (Dkt. #13 at p. 2). Though the Arbitration Agreement includes what appears to be Abebe’s electronic signature, Abebe maintains that he did not sign the Arbitration Agreement (Dkt. #18 at p. 3). Abebe also “unequivocally den[ies] receiving a copy of the Yum! 2015 Arbitration Agreement during [his]

employment” and further states that “Yum! did not notify [him] of the existence of that agreement while [he] worked for Yum!” (Dkt. #20 at pp. 5–6). Abebe worked in the Yum! Information Technology (“IT”) department where he focused on the security of the Yum! IT infrastructure (Dkt. #20 at p. 1). Because of the positions he held within the IT department, Abebe alleges that he has “unique and detailed knowledge about Yum!’s IT infrastructure, how the IT systems were accessed and security issues and risks to Yum’s IT

infrastructure” (Dkt. #20 at pp. 2–3). Abebe explains that Yum! used multiple programs for learning management, including SABA Enterprise (“SABA”) (Dkt. #20 at p. 3). SABA had a Learning Management System (“LMS”) (Dkt. #20 at p. 3). According to Abebe, the SABA LMS had an “impersonation” function (Dkt. #20 at p. 6). This function gave approximately 100 specific users the ability to impersonate others and was “regularly used by support teams, contractors, and training administrators to log in as users to execute LMS commands and even to complete training” (Dkt.

#20 at pp. 6–7). Additionally, IT teams could allegedly “impersonate” users in order to trouble shoot problems that employees were experiencing with the various platforms (Dkt. #20 at p. 8). Further, Abebe alleges that a “backdoor URL was available for administrative access to LMS” (Dkt. #20 at p. 19). According to Abebe, “a backdoor URL is a hidden direct entry into the LMS that bypasses all of the security Yum! has in place” (Dkt. #20 at p. 19). It offers “unrestricted, unmanaged access” to those who know how to access the backdoor (Dkt. #20 at p. 19). Though this function is generally used for “remote tech purposes,” Abebe alleges that this is another means by which someone could have impersonated him (Dkt. #20 at p. 19). Abebe also alleges that there are security issues with the passwords given to newly hired

employees (Dkt. #20 at p. 10). All new employees are given a password that consists of the word “Yum,” the last five digits of that employee’s social security number, and an “@” sign (Dkt. #20 at p. 10). So if a new employee did not change the assigned password, anyone who knew that employee’s social security number could ascertain the password of that employee (Dkt. #20 at p. 11). Moreover, Abebe alleges that passwords are routinely shared on help desk tickets when an employee has an IT issue, and passwords could be shared among employees and contractors (Dkt.

#20 at p. 12). Lastly, Abebe alleges that there were potential issues with data migration that could have impacted the accuracy of Yum!’s data with respect to the Arbitration Agreement (Dkt. #20 at p. 16). Despite Abebe’s allegations, Yum! submits that Abebe was in fact notified of the Arbitration Agreement via “(1) multiple, general announcements sent to all Yum! employees, including Abebe, regarding the rollout and deadlines for the 2015 Compliance Period training,

which included the Arbitration Agreement among the required ʻcourses’ []; (2) an email sent directly and individually to Abebe from a Yum! Legal Assistant on July 15, 2015, directing him to ʻcomplete your 2015 compliance training courses’ by Friday, July 17, 2015, including the “Yum! 2015 Yum Arbitration Agreement (non-CA)” []; (3) an email sent directly to Abebe via a blind copy on August 3, 2015, asking him to complete ʻthe following courses . . . for the 2015 Compliance Training Window’ and specifically listing the Arbitration Agreement []; and (4) an email directly to Abebe on September 23, 2015, stating the 2015 Compliance Period training ʻcourses,’ and specifically referencing the Arbitration Agreement, ʻare part of our corporate compliance program and are required to be completed[]’” [] (Dkt. #25 at pp. 7–8).

Moreover, Yum! alleges that “on October 1, 2015, two different Yum! employees emailed Abebe directing him to log into [SABA] to complete ʻthe mandatory annual Yum! Brands Code of Conduct Questionnaire [“COCQ”] . . . by the end of day next Tuesday, October 6th,’ and to also complete ʻany other Compliance Training Courses immediately.’ [] On October 5, 2015, at 11:15 a.m., Abebe responded, stating that he would complete his COCQ ʻby tomorrow.’ [] An hour and a half later, at 12:48 p.m., the COCQ was completed in Abebe’s [SABA] account. [] Six minutes

later, at 12:54 p.m., Abebe confirmed he had completed the COCQ. [] Four minutes later, at 12:58 p.m., the Arbitration Agreement, which was in the same set of 2015 Compliance Period training materials, was executed in Abebe’s [SABA] account. [] Three days later, the same Yum! employees reminded Abebe that he still had four more 2015 Compliance Period trainings to complete—but notably, the Arbitration Agreement was not one of them. []” (Dkt. #25 at p. 9). Additionally, Yum! alleges that it implements “robust” security procedures to verify that the electronic signature on the Arbitration Agreement was made by Abebe (Dkt. #13 at p. 7). Those

security measures include: “(1) requiring personal identifying information to establish access to Yum! systems; (2) assigning a unique identifier to Yum! employees and then tying that identifier to the employee’s actions; (3) maintaining a system for tracking employees’ electronic signatures; (4) requiring employees to follow certain steps to create electronic signatures; and (5) creating timestamps showing when users completed certain actions” (Dkt. #13 at p. 7). More specifically, Yum! provides a detailed account of its alleged policy and procedure for employee passwords (Dkt. #13 at p. 8). Upon hire, employees are assigned a Network ID and a temporary default password consisting of the word “Yum”, the last 5 digits of the employee’s

social security number, and the “@” symbol (Dkt. #13 at p. 8). Yum!’s policy requires that employees change this default password as soon as possible, and employees are prompted to do so when they log in for the first time (Dkt. #13 at p. 8). Yum! requires employee passwords to be “at least 7 characters long, and include one upper case letter, one base number, and one special character (e.g., ! @ # $ % ^ & * ( ) - _ = + . /)” (Dkt. #13 at p. 8). Yum! alleges that this password remains confidential, and an employee would only be asked to share it for reasons related to

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Webb v. Investacorp, Inc.
89 F.3d 252 (Fifth Circuit, 1996)
Will-Drill Resources, Inc. v. Samson Resources Co.
352 F.3d 211 (Fifth Circuit, 2003)
Banc One Acceptance Corp. v. Hill
367 F.3d 426 (Fifth Circuit, 2004)
Joe Bell v. Koch Foods of Mississippi, LLC
358 F. App'x 498 (Fifth Circuit, 2009)
At&T Technologies, Inc. v. Communications Workers
475 U.S. 643 (Supreme Court, 1986)
Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
First Options of Chicago, Inc. v. Kaplan
514 U.S. 938 (Supreme Court, 1995)
Marian Fontenot, Etc. v. The Upjohn Company
780 F.2d 1190 (Fifth Circuit, 1986)
Compucredit Corp. v. Greenwood
132 S. Ct. 665 (Supreme Court, 2012)
Charles Grant v. Kevin Houser
469 F. App'x 310 (Fifth Circuit, 2012)
Christina Bazemore v. Jefferson Capital Systems, LLC
827 F.3d 1325 (Eleventh Circuit, 2016)
Ted Kubala, Jr. v. Supreme Production Svc, Inc.
830 F.3d 199 (Fifth Circuit, 2016)
IQ Products Company v. WD-40 Company
871 F.3d 344 (Fifth Circuit, 2017)
Henry Schein, Inc. v. Archer & White Sales, Inc.
586 U.S. 63 (Supreme Court, 2019)
Lloyd's Syndicate 457 v. FloaTEC, L.L.C.
921 F.3d 508 (Fifth Circuit, 2019)

Cite This Page — Counsel Stack

Bluebook (online)
Abebe v. Yum! Brands, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/abebe-v-yum-brands-inc-txed-2024.