# Guber Global LLC, et al. v. Notion Labs, Inc., et al. - Filed Class Action Complaint Canonical: https://hallattorneys.com/dockets/fireworks Source PDF: https://hallattorneys.com/dockets/fireworks/01-complaint.pdf Filed: November 17, 2026 Docket entry: ECF No. 1 Case number: 3:26-cv-14010 Court: U.S. District Court for the Northern District of California, San Francisco Division Defendants: Notion Labs, Inc., Replit, Inc., Fireworks.ai, Inc., and Uber Technologies, Inc. The following is extracted text of the original 39-page complaint only, without exhibits. Allegations are not findings. No class has been certified. The PDF controls if extraction differs. Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 1 of 39 PageID #: 1 1 CHRISTOPHER FROST (SBN 200336) chris@frostllp.com 2 KEVIN S. DICKER (SBN 179315) kevin@frostllp.com 3 FROST LLP 10960 Wilshire Boulevard, Suite 2100 4 Los Angeles, California 90024 Telephone: (424) 254-0441 5 Facsimile: (424) 600-8504 6 Attorneys for Plaintiff and the Proposed Class 7 8 UNITED STATES DISTRICT COURT 9 NORTHERN DISTRICT OF CALIFORNIA, SAN FRANCISCO DIVISION 10 11 GUBER GLOBAL LLC, SOPHIA ALIAGA, SAMER TALLAUZE, and BRENNON 12 LEWIS JR., individually and on behalf of all others similarly situated, 13 Plaintiffs, 14 vs. 15 NOTION LABS, INC., REPLIT, INC., 16 FIREWORKS.AI, INC., and UBER TECHNOLOGIES, INC., 17 Defendants. 18 Case No. 3:26-cv-14010 CLASS ACTION COMPLAINT FOR: 1. 2. 3. 4. NEGLIGENCE AGAINST FIREWORKS; NEGLIGENCE AGAINST NOTION; NEGLIGENCE AGAINST REPLIT; NEGLIGENCE AGAINST UBER. JURY TRIAL DEMANDED 19 20 21 22 23 24 25 26 27 28 Case No. 3:26-cv-14010 CLASS ACTION COMPLAINT Case 3:26-cv-14010 1 Document 1 Filed 11/17/26 Page 2 of 39 PageID #: 2 Plaintiffs GUBER Global LLC ("GUBER"), Sophia Aliaga ("Aliaga"), Samer Tallauze 2 ("Tallauze"), and Brennon Lewis Jr. (“Lewis”), individually and on behalf of the classes defined 3 below, allege the following against Defendants Notion Labs, Inc. ("Notion"), Replit, Inc. 4 ("Replit"), Fireworks.ai, Inc. ("Fireworks"), and Uber Technologies, Inc. ("Uber"). Plaintiffs allege 5 matters concerning their own conduct and experiences on personal knowledge and other matters 6 on information and belief, based on counsel's investigation, the notices provided to GUBER and 7 Aliaga, Uber's formal notices and regulatory disclosures, Defendants' public statements, and the 8 other sources identified below. Further evidentiary support for matters within Defendants' 9 possession is expected after a reasonable opportunity for discovery. 10 I. 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 1. NATURE OF THE ACTION This action concerns the loss of confidentiality of information entrusted to three widely used platforms and exposed through their common infrastructure provider or credentials entrusted to that provider. GUBER used Replit to develop commercial technology. Aliaga used Notion for university-related activities and startup development. Both platforms sent customer information to Fireworks and later notified GUBER and Aliaga that their account information was affected. On information and belief, the Uber records accessed through compromised Fireworks credentials included Tallauze's and Lewis’ driver’s license and extracted text data, including at least their names, addresses, dates of birth, and driver’s license numbers. 2. The information at issue includes private educational information, unreleased software-development material, proprietary technical designs, confidential business workflows, and sensitive government-issued identification records. An AI conversation can contain confidential information in the prompt, the response, or related session material. Removing an account label does not remove confidential facts appearing in the text, restore the secrecy of a technical design, or prevent the text from identifying its subject through context. A driver's-license image and extracted identifying fields present a separate, directly identifying category of nonpublic information. 28 2 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 3. Document 1 Filed 11/17/26 Page 3 of 39 PageID #: 3 Fireworks occupied the common position in this arrangement. Notion, Replit, and 2 Uber offered the services with which the affected people and businesses interacted; Fireworks 3 supplied infrastructure or received access authority for work supporting those services. These 4 relationships form the hub-and-spoke structure relevant to this action: separate customer-facing 5 businesses entrusted information or processing access to the same infrastructure provider. Each 6 Defendant retained responsibility for the systems, access, and data-handling decisions within its 7 own control. 8 4. The Notion spoke presents a particularly concrete discrepancy between an agreed 9 safeguard and actual handling. Notion now reports that Fireworks made a contractual zero-retention 10 commitment for Notion's use of its platform, yet Notion's investigation found that the Fireworks 11 endpoints it used had retained data. That admission directly concerns why a downstream copy of 12 customer content existed to be compromised. 1 13 5. GUBER's and Aliaga's connections to the incident are account specific. Replit told 14 GUBER that its account was affected and identified prompts from July 14 through July 29, 2026, 15 together with related session data. Notion identified Aliaga's workspace and made affected-content 16 records available to her. Aliaga reviewed records identifying 151 messages in seven conversation 17 threads, with content dated October 5 through October 23, 2026. Tallauze's and Lewis’ separate 18 allegations concern the sensitive identification records described in Uber's formal disclosures. 19 6. The dates when Plaintiffs created their content are different from the dates of 20 unauthorized access. Fireworks disclosed an initial credential incident in early October and later 21 activity involving research-and-development machines on October 24. The precise path by which 22 each Plaintiff's data was obtained, and the relationship between retained copies and the 23 compromised systems, are matters primarily documented in Defendants' records. 24 7. Fireworks controlled its credentials, internal access paths, processing 25 environments, and storage. Notion and Replit controlled their respective customer relationships, 26 27 1 Notion, Notice About the Fireworks AI Incident That May Impact Some Notion Workspaces, 28 https://www.notion.com/help/security-incident-involving-a-third-party-ai-vendor (last visited Nov. 17, 2026) (FAQs concerning retention and instructions for affected-content review). 3 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 4 of 39 PageID #: 4 1 the information they supplied to Fireworks, the purposes for which they supplied it, and their own 2 vendor-selection and oversight practices. Uber controlled the storage environment and access 3 arrangements it established for the provider's work. Plaintiffs lacked equivalent access to those 4 systems and could not themselves inspect or correct the provider-side conditions that exposed their 5 information. 6 8. Plaintiffs seek relief for their own injuries and those of the four classes defined 7 below: the Fireworks Class, the Notion Class, the Replit Class, and the Uber Class. GUBER asserts 8 its claims against Replit and Fireworks; Aliaga asserts hers against Notion and Fireworks; and 9 Tallauze and Lewis asserts theirs against Uber and Fireworks. The Fireworks Class encompasses 10 affected information received through any customer or intermediary, as well as information 11 supplied directly to Fireworks or reached through compromised Fireworks credentials. The 12 platform classes encompass affected users and other persons or entities whose information was 13 contained in the compromised platform data. 14 9. The claims address each Defendant's own custody, transmission, retention, access 15 controls, and security of nonpublic information. They rest on duties imposed by law in handling that 16 information, not on a claim to enforce a subscription agreement or to obtain third-party-beneficiary 17 rights under a vendor contract. Processing instructions and public security statements are relevant 18 to the purposes, risks, and operational choices known to Defendants. 19 20 II. 10. PARTIES Plaintiff GUBER Global LLC is a limited liability company organized under 21 Delaware law on December 30, 2025. It develops commercial AI technology and related 22 applications. It maintains a mailing address in North Carolina. GUBER brings this action through 23 its authorized representative, founder Dimetris Bowden, solely for the company's own rights and 24 injuries. 25 11. GUBER used Replit in its commercial development work during July 2026. Its 26 relevant information included nonpublic technical designs, development material, and business 27 workflows. Replit's November 10, 2026 security notice identified the account used for that work 28 as affected by the Fireworks incident. 4 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 12. Document 1 Filed 11/17/26 Page 5 of 39 PageID #: 5 Plaintiff Sophia Aliaga is a citizen of Nebraska and was a university student 2 during the relevant period. She maintained a Notion account, upgraded to a paid Business 3 subscription in August 2026, and used the service for academic activities and software4 development work, including a startup project. 5 13. Plaintiff Samer Tallauze is an individual who maintains a United States mailing 6 address in Austin, Texas. On information and belief, Uber held his nonpublic driver's-license image 7 and related identifying information among the records accessed in the incident described below. 8 Tallauze brings claims against Uber and Fireworks for the exposure of his own information. 9 14. Plaintiff Brennon Lewis Jr. is an individual domiciled in Angleton, Texas. 10 Plaintiff Lewis received a notice letter from Defendant Uber dated November 10, 2026, informing 11 him that his Private Information, including at least an image of his driver’s license and text data 12 that included his name, address, date of birth, and driver’s license number, was impacted in the 13 Breach. See Exhibit 1. 14 15. Defendant Notion Labs, Inc. is a Delaware corporation with its principal place of 15 business and headquarters located at 685 Market Street, San Francisco, California 94105. Notion 16 supplies a workspace platform, calendar products, and AI features, including the Notion AI service 17 Aliaga used. Notion selects and contracts with providers that process information in connection 18 with those features.2 Notion’s registered agent is CT Corporation System, which can be served at 19 330 N Brand Boulevard, Suite 700, Glendale, California 91203. 20 16. Defendant Replit, Inc. is a Delaware corporation with its principal place of 21 business and headquarters located at 1001 E Hillsdale Boulevard, 400W, Foster City, California 22 94404. Replit supplies a platform for building and operating software, including an AI agent that 23 receives development instructions and produces or interacts with code and other project material. 3 24 2 Notion Labs, Inc., Notice of Exempt Offering of Securities (Form D) (Oct. 12, 2021), https://www.sec.gov/Archives/edgar/data/1781814/000178181421000002/xslFormDX01/primary 26 _doc.xml; Notion, Privacy Policy, https://www.notion.com/trust/privacy-policy (last visited Nov. 13, 2026). 27 3 Replit, Inc., Simple Agreement for Future Equity 1 (2022), https://www.sec.gov/Archives/edgar/data/1920974/000167025422000289/document_4.pdf; 28 Replit, Replit Closes $250 Million in Funding to Build on Customer Momentum (Sept. 10, 2025), https://replit.com/news/funding-announcement-series-c. 25 5 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 6 of 39 PageID #: 6 1 Replit’s registered agent is Robert Kohse, who can be served at 1001 E Hillsdale Boulevard, 400W, 2 Foster City, California 94404. 3 17. Defendant Fireworks.ai, Inc., doing business as Fireworks AI, is a Delaware 4 corporation with its principal place of business and headquarters located at 900 Concar Drive, San 5 Mateo, California 94402. Its own privacy notice identifies the operating entity as Fireworks.ai, Inc. 6 Fireworks provides AI inference, training, and related infrastructure to business customers, 7 including Notion and Replit. Uber has also identified Fireworks as the provider involved in its 8 incident, as alleged below.4 Firework’s registered agent is National Registered Agents, Inc., which 9 can be served at 330 N Brand Boulevard, Suite 700, Glendale, California 91203. 10 18. Defendant Uber Technologies, Inc. is a Delaware corporation with its principal 11 place of business and headquarters located at 1725 3rd Street, San Francisco, California 94158. 12 Uber operates a technology platform connecting users with transportation and other services. Its 13 principal executive offices are located at 1725 3rd Street, San Francisco, California 94158. Uber 14 selected the service-provider relationship and created the cloud environment described below for 15 work involving Uber information.5 Uber’s registered agent is CT Corporation System, which can 16 be served at 330 N Brand Boulevard, Suite 700, Glendale, California 91203. 17 19. Each Defendant is sued for its own acts, omissions, and obligations. Fireworks 18 controlled the common processing infrastructure or provider credentials; Notion, Replit, and Uber 19 selected and directed their respective processing arrangements and controlled their own data20 handling functions. The following allegations identify the conduct and undertaking attributable to 21 each. 22 / / / 23 / / / 24 4 Fireworks.ai, Inc., Statement of Information, Cal. Sec'y of State filing no. BA20230319395 (Feb. 24, 2023), https://static.bizprofile.net/7/4/3/9/9/5/7439958.pdf; Fireworks AI, Company Profile, 26 LinkedIn, https://www.linkedin.com/company/fireworks-ai (last visited Nov. 13, 2026); Fireworks, Privacy Policy, https://fireworks.ai/privacy-policy (last visited Nov. 13, 2026); 27 Fireworks, Fireworks Raises a $1.5 Billion Series D to Lead the Specialized Intelligence Revolution (July 16, 2026), https://fireworks.ai/news/fireworks-raises-1-5-billion-series-d. 28 5 Uber Techs., Inc., Quarterly Report (Form 10-Q), cover & pt. I, item 1, note 1 (Nov. 4, 2026), https://www.sec.gov/Archives/edgar/data/1543151/000154315126000041/uber-20260930.htm. 25 6 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 2 Document 1 III. 20. Filed 11/17/26 Page 7 of 39 PageID #: 7 JURISDICTION AND VENUE Jurisdiction. Plaintiffs invoke the Class Action Fairness Act, 28 U.S.C. § 3 1332(d)(2), (5)(B), and (6). The proposed classes collectively contain at least 100 members. In 4 addition to the affected Notion and Replit datasets, Uber's regulatory reporting identifies 4,296 5 affected Texans, as described in paragraph 81. Minimal diversity exists because Plaintiff Aliaga is 6 a citizen of Nebraska and each Defendant is a citizen of Delaware headquartered in California. The 7 aggregate amount in controversy exceeds $5,000,000, exclusive of interest and costs, based on the 8 scope of the incident and the compensatory relief sought for the Classes. 9 21. The proposed classes concern affected persons and entities throughout the United 10 States. Their alleged injuries include disclosure of nonpublic personal and business information, 11 impairment of proprietary interests, and recoverable investigation, containment, remediation, and 12 other consequential losses where established. The jurisdictional amount concerns the claims 13 actually asserted and accounts for overlapping class membership without counting the same injury 14 more than once. Uber's reported incident total is not alleged to establish that every reported person 15 belongs to the United States classes. Platform user totals and upper-bound incident percentages are 16 not alleged to establish the number of affected persons. 17 22. This Court has personal jurisdiction over each Defendant because each maintains 18 its principal place of business in California and is therefore at home in this State. In addition, the 19 claims arise out of or relate to Defendants' operation of their California-based businesses and their 20 decisions concerning the products, provider relationships, and data-handling practices described in 21 this complaint. 22 23. Venue is proper under 28 U.S.C. § 1391(b)(1) and (2). Defendants reside in this 23 District for venue purposes, and a substantial part of the acts and omissions giving rise to the claims 24 occurred here, including, on information and belief, decisions concerning provider selection, 25 contractual safeguards, data retention, internal security, and incident response. 26 24. Divisional Assignment. Assignment to the San Francisco or Oakland Division is 27 proper under Civil Local Rule 3-2(c) and (d), because the action arises in substantial part from 28 conduct of businesses headquartered in San Francisco and San Mateo Counties. Fireworks and 7 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 8 of 39 PageID #: 8 1 Replit maintain their principal places of business in San Mateo County, and Notion and Uber 2 maintain their principal places of business in San Francisco County. 3 25. Joinder is proper under Federal Rule of Civil Procedure 20(a). Plaintiffs' claims 4 concern a series of related data-handling events and unauthorized-access incidents involving the 5 same infrastructure provider and overlapping issues of retention, credential control, segmentation, 6 investigation, and affected-data identification. The duties and conduct attributable to each platform 7 are pleaded separately, permitting the Court to address common Fireworks issues and distinct 8 platform issues without attributing one platform's conduct to another. The Uber allegations concern 9 the earlier credential-access episode and do not depend on treating every spoke's records as one 10 dataset or assigning every exposure to the October 24 event. 11 12 IV. FACTUAL ALLEGATIONS 13 14 A. Defendant Collected Plaintiff’s and Class Members’ Private Information 26. In an AI application, the visible interface and the systems processing a request 15 may belong to different companies. A person may submit a message to Notion or an instruction to 16 Replit while an outside infrastructure provider performs part of the computation. The outside 17 provider can therefore receive the substance of the user's work even though the user has no direct 18 account with that provider. 19 27. Provider access can also reach identification records maintained outside a 20 conversational interface. A platform may make stored records available for a provider's work 21 through credentials and permissions. If those credentials are compromised, the confidentiality risk 22 extends to the records they can reach, even when the storage environment belongs to the customer 23 rather than the provider. 24 28. A prompt is not merely a record that someone used a feature. It can be the 25 document to summarize, the problem to solve, the software design to implement, or the factual 26 context needed to produce a useful answer. A response can restate, organize, or derive further 27 information from that same confidential material. A sequence of prompts and responses can 28 disclose a project more fully than any single message. 8 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 29. Document 1 Filed 11/17/26 Page 9 of 39 PageID #: 9 In a development environment, related tool output can add information that was 2 not manually typed into a prompt. Tool output may reflect the result of a program, a file operation, 3 or another step in an agent's work. The exact tool output affected here must be determined from 4 GUBER's records and Replit's disclosure. Replit's notice expressly included related tool outputs. 5 Notion's notice to Aliaga described her affected transcripts as excluding tool-call results; its current 6 broader guidance qualifies that exclusion as applying to most affected transcripts. 7 30. Operational metadata and content also serve different purposes. A token count or 8 elapsed time may describe how a system operated. A technical design or business workflow 9 describes what its owner is building. Combining both in a retained session record does not convert 10 the proprietary content into an innocuous usage counter. 11 31. Plaintiffs' nonpublic information was held for processing in the services at issue. 12 Authorization to process a private conversation, assist with a development task, or handle 13 identification records does not itself authorize disclosure to an intruder or uncontrolled access 14 through compromised credentials. The scope of authorized processing and the conditions under 15 which Defendants held the information are relevant to the reasonable safeguards required for that 16 information. 17 32. Nor does omitting a user's name from an outer record establish that the record is 18 anonymous. A conversation may contain names, project details, organizational information, or 19 combinations of facts that reveal its source. Confidentiality also protects information whose 20 commercial or personal value would be impaired even if a recipient initially did not know its 21 author's name. 22 33. The relevant security inquiry accordingly extends across the information's 23 lifecycle: what was sent, why it was sent, which environment received it, what copies were made, 24 how long they persisted, which credentials could reach them, and how the parties verified deletion 25 and investigated access. Those are operational facts that can be established through routing 26 configurations, storage inventories, access logs, job records, contracts, and incident records. 27 28 9 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 1 B. Fireworks was the common provider. 2 34. Page 10 of 39 PageID #: 10 Fireworks markets infrastructure for adapting and serving models using 3 customers' proprietary information and workflows. Its July 16, 2026 financing announcement 4 5 6 7 described commercial use at substantial scale and reported more than $1 billion in annualized revenue run rate. Its business model thus contemplated receiving valuable enterprise information and supplying services that other companies would incorporate into their operations. 6 35. 8 The sensitivity of downstream information was foreseeable from those uses. An 9 infrastructure provider supporting workspace analysis and software development would expect 10 some customer payloads to contain personal records, nonpublic business plans, and proprietary 11 12 technical material. Those are ordinary reasons customers use such tools, rather than an unforeseeable deviation from their commercial purpose. 13 36. 14 15 Fireworks knew which enterprise customers supplied data or access authority to its platform and, on information and belief, maintained account, resource, and job records reflecting 16 the services used for those customers. It could identify processing environments and credential 17 permissions that an individual Notion, Replit, or Uber user could neither see nor administer. 18 19 20 21 22 37. Fireworks's published security documentation describes encryption during transfer and storage, restricted access, monitoring, workload isolation, network safeguards, and vulnerability management. Its current descriptions identify controls that Fireworks recognizes as important when receiving and handling customer information. 7 38. 23 Fireworks's retention rules also depend on the product and configuration. Its 24 current documentation describes zero retention for ordinary open-model requests absent an 25 applicable opt-in, while identifying storage-dependent exceptions, including batch processing and 26 6 Fireworks, Fireworks Raises a $1.5 Billion Series D to Lead the Specialized Intelligence Revolution, supra note 4. 28 7 Fireworks, Data Security, https://docs.fireworks.ai/guides/security_compliance/data_security (last visited Nov. 13, 2026). 27 10 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 11 of 39 PageID #: 11 1 certain Responses API requests. The actionable Notion-specific retention facts are pleaded 2 separately; Plaintiffs do not infer that all Fireworks products were technically incapable of storing 3 information.8 4 39. 5 6 7 The enterprise relationships supplied Fireworks with information or access authority for defined service purposes. Customer authorization to perform work did not eliminate the need to protect the information and credentials accepted for that work. The service-specific 8 processing instructions, access permissions, and actual configurations are evidence of the custody 9 and control Fireworks exercised. 10 C. Notion supplied conversation content to Fireworks. 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 40. Norton’s notice to Aliaga identified Fireworks as one of Notion's vendors. It explained that Notion used Fireworks to serve open-weight models inside Notion's product and to perform classification jobs supporting a feature called Insights. The same notice identified chat transcripts used for Insights as part of the affected material. 9 41. Insights helped customers understand their use of Notion AI. Performing that function involved supplying conversation content for analysis, not merely reporting that a workspace had made a specified number of requests. Notion selected the vendor and the processing arrangement that carried this content outside the direct Notion interface. 42. A customer-facing function and a downstream processing copy involve distinct security decisions. The relevant facts include the purpose of the downstream copy, its persistence, the access permitted to it, and the safeguards implemented for it. Paragraph 4 identifies Notion's reported discrepancy between the intended retention configuration and the endpoints actually used. 43. Notion was positioned to determine what data was included in the classification payload, whether less revealing material could serve the same purpose, which endpoints received 8 Fireworks, Zero Data Retention, 27 https://docs.fireworks.ai/guides/security_compliance/data_handling (last visited Nov. 13, 2026). 9 Notion, Important Security Notice About the Fireworks AI Incident That May Impact Your 28 Notion Workspace (Nov. 10, 2026) (notice to Aliaga, received Nov. 11, 2026; retained by counsel). 11 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 12 of 39 PageID #: 12 1 it, and what contractual and technical controls governed those endpoints. Aliaga could use her own 2 permissions and account controls, but she could not audit Notion's vendor configurations or inspect 3 Fireworks's stored copies. 4 44. Notion's published AI privacy practices describe customer-data protections, 5 contractual requirements for model and inference providers, and review of subprocessors. They 6 state that AI use respects the permissions governing workspace content and that customer data is 7 not used for model training by default. These representations distinguish permission to provide a 8 requested AI function from unrestricted exploitation of the underlying data. 10 9 45. Notion's current security page also describes vendor assessments and contracts 10 requiring subprocessors to process information under Notion's instructions. That is relevant to 11 Notion's own role in selecting and directing the provider. The alleged failure includes the 12 implementation and verification of safeguards governing that relationship, rather than an allegation 13 that the mere use of a disclosed outside vendor was necessarily unlawful. 11 14 46. Notion controlled the transfer of the affected conversation content and the 15 configuration and oversight of the processing arrangement it selected. Its responsibility to exercise 16 reasonable care in handling nonpublic information arose from that conduct and the foreseeable 17 exposure risk. The negligence claim concerns those operational responsibilities. 18 D. Replit’s relationship with Fireworks reached development content. 47. Replit’s subprocessor list, updated in August 2026, identifies Fireworks AI, Inc. 19 20 as a United States provider of AI infrastructure. The list explains that subprocessors help Replit 21 deliver its services and process customer data. This independently corroborates the relationship 22 later identified in GUBER's security notice.12 23 48. Replit further described Fireworks as its partner for open-weight model inference 24 and training in an engineering article published October 28, 2026. The publication concerns Replit's 25 26 10 Notion, Notion AI Security & Privacy Practices, https://www.notion.com/help/notion-aisecurity-practices (last visited Nov. 13, 2026). 28 11 Notion, Security @ Notion, https://www.notion.com/security (last visited Nov. 13, 2026). 12 Replit, Subprocessors (updated Aug. 2026), https://replit.com/subprocessors. 27 12 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 13 of 39 PageID #: 13 1 software-development benchmark and corroborates an operational relationship extending beyond 2 a passive listing of a vendor's name.13 3 49. The affected data described in GUBER's notice consisted of development-session 4 material. The inference and training partnership identifies the operational relationship; the relevant 5 job and dataset records will establish the particular functions for which GUBER's content was 6 transmitted or retained. 7 50. GUBER supplied proprietary development instructions and related material for 8 private development work. The nature and context of that material made its sensitivity foreseeable 9 to a platform that accepted and processed it. The content could remain commercially sensitive even 10 when an outer session record lacked a company or account label. 11 51. Before GUBER created the affected July content, Replit published a detailed 12 security explanation on April 20, 2026, updated April 21. Replit described layered safeguards, 13 minimum necessary privileges, authentication between internal services using short-lived tokens, 14 and segmentation to limit the effect of a compromise. The publication described security for both 15 development environments and Replit's own control plane. 14 16 52. The use of an infrastructure subprocessor introduced an additional processing 17 environment into the service Replit furnished. On information and belief, Replit controlled its 18 selection of Fireworks, the permissions and data supplied under that relationship, and its own 19 assessment and verification of the safeguards for that processing. Those decisions were outside 20 GUBER's ability to administer its own project or account. 21 53. Replit's notice identifies July content affected in an incident disclosed in 22 November. That establishes that the relevant historical content, or a copy of it, remained reachable 23 somewhere in the processing chain when unauthorized access occurred. It does not by itself 24 establish when Fireworks first received the content or whether every copy persisted continuously 25 26 13 Preeya Kirani et al., ViBench 2.0: A Benchmark for Long-Horizon Software Building, Replit 27 Frontier (Oct. 28, 2026), https://frontier.replit.com/vibench-2-long-horizon-software-benchmark/. 14 Luis Héctor Chávez, Defense in Depth: How Replit Secures Every Layer of the Vibe Coding 28 Stack, Replit (Apr. 20, 2026, updated Apr. 21, 2026), https://replit.com/blog/defense-in-depthhow-replit-secures-every-layer-of-the-vibe-coding-stack. 13 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 14 of 39 PageID #: 14 1 from July. Those questions are answerable from dataset creation records, transfers, storage history, 2 and deletion records. 3 4 E. Fireworks disclosed two periods of unauthorized activity. 5 54. Fireworks’s first bulletin reported discovery of unauthorized use of internal 6 credentials on October 6, 2026. It described access to environment variables used in evaluation 7 jobs, including API keys and tokens. Its timeline placed initial customer notifications on October 15 8 7, employee-key rotation on October 9, and additional credential revocation on October 10. 55. 9 The first bulletin expressly qualified its findings as preliminary. It reported no 10 detected access to additional categories of information within Fireworks's security perimeter or 11 control at that time. The later disclosures expanded both the categories affected and the 12 environments implicated, making the scope and timing of Fireworks's investigation material to the 13 claims. 56. 14 In its November 9 update, Fireworks described an October 23 security incident at 15 an unnamed cloud provider hosting Fireworks research-and-development machines. Fireworks 16 reported that an unauthorized party used that access on October 24 to reach development machines 17 and run a workload that caused additional customer-data impact. Fireworks stated that it detected 16 18 that activity the same day. 57. 19 The update expanded the disclosed categories to account and billing information 20 and, for certain accounts, secrets, datasets, and incomplete model material. It excluded stored 21 payment-card numbers, which Fireworks said it did not hold. Fireworks described assistance from 22 Palo Alto Networks Unit 42 and measures addressing credentials, permissions, network isolation, 23 storage access, and logging. 58. 24 The response addressed the same operational areas implicated by the disclosed 25 events: credential scope, pathways between environments, access to stored data, and the ability to 26 15 Fireworks, Fireworks October 2026 Security Incident (updated Oct. 10, 2026), https://fireworks.ai/security/bulletins/october-2026-security-incident. 28 16 Fireworks, Update on October 2026 Security Incident (Nov. 9, 2026), https://fireworks.ai/security/bulletins/october-2026-security-incident-update. 27 14 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 15 of 39 PageID #: 15 1 reconstruct activity. The underlying access and configuration records will establish the controls in 2 place and the failures that permitted the unauthorized activity affecting Plaintiffs. 3 59. The disclosed sequence is significant because the second period involved 4 development infrastructure after Fireworks had already identified an internal-credential 5 compromise. Reasonable incident response required assessing the reach of exposed credentials and 6 protecting the environments through which customer information could be reached. Plaintiffs 7 allege failures in those functions to the extent supported by the specific access and retention facts 8 below. 9 60. Fireworks's use of an upstream cloud provider added another layer between 10 Plaintiffs and the infrastructure holding or able to reach their information. Fireworks has not 11 publicly identified that provider. Its contracts, network design, and development-environment 12 records will establish the allocation of access and responsibilities at that layer. 13 14 F. Notion’s investigation connected the retained data to affected users. 15 61. Notion’s revised public timeline states that Fireworks notified it on November 2 16 about a dataset initially understood to contain synthetic testing information. Notion disconnected 17 from Fireworks on November 3 and deleted its data there on November 4. Fireworks raised 18 potential customer-data exposure on November 6, confirmed the affected dataset on November 8, 17 19 and Notion began notifying affected customers on November 9. 62. 20 The notice sent to Aliaga was dated November 10, 2026; she received and 21 reviewed it on November 11. It identified her workspace as among the fewer than one percent of 22 Notion workspaces potentially affected. The notice instructed affected customers to review their 23 records and treat the identified information as exposed. 63. 24 Notion's notice to Aliaga described her affected sessions as lacking separate labels 25 identifying their authors or workspaces and as containing no tool-call results. It expressly qualified 26 27 17 Notion, Fireworks AI Incident (updated Nov. 12, 2026, with incident updates through Nov. 13, 28 2026), https://www.notion.com/en-gb/security/advisories/security-incident-involving-a-thirdparty-ai-vendor (last visited Nov. 17, 2026). 15 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 16 of 39 PageID #: 16 1 that description by referring to what appeared in the words of the transcripts. That qualification 2 preserved the possibility that the text itself revealed confidential or identifying information. 3 64. Notion's current guidance further identifies complete user messages and AI 4 responses as affected content. Selected page text and source fragments reproduced in responses 5 could also appear. It limits its metadata and tool-use exclusions to most affected transcripts. 6 Meeting Notes could be implicated when entered in messages or referenced in responses; original 7 attachments and the rest of a selected page were outside the described content. These are incident8 wide descriptions, while Aliaga's own affected material is identified through the records she 9 reviewed.18 10 65. Notion's subsequent public updates disclosed concrete sensitive content in 11 affected messages. It revoked exposed Notion API keys on November 11 and reported exposed 12 third-party API keys to their issuers on November 12. This concerns the broader affected dataset; 13 Plaintiffs do not allege from those disclosures alone that Aliaga's own messages contained an 14 exposed credential. 15 66. Notion's incident instructions distinguish an affected-content export from an 16 annotated export. The former supplies affected text. The latter adds context, including identifiers 17 and dates, to help customers investigate. Notion says that added metadata was not itself exposed. 18 Its affected-member records also link members, including deactivated members, to counts of 19 affected material. These records provide a means to identify the population and distinguish 20 compromised content from later investigative annotation. 21 67. The export structure permits two separate inquiries: what the unauthorized actor 22 received and who owns or is identified in that material. The distinction supports both individualized 23 injury analysis and administration of notice to affected members. 24 68. The account-specific evidence connects the retained material to downstream 25 injury. The copy history, endpoint settings, access permissions, and investigation records will 26 27 18 Notion, Notice About the Fireworks AI Incident That May Impact Some Notion Workspaces, 28 supra note 1 (sections concerning affected content and affected-member records; last visited Nov. 17, 2026). 16 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 17 of 39 PageID #: 17 1 establish how the affected information remained available to the unauthorized actor and which 2 operational failures permitted access. 3 69. The Notion claim concerns the affected conversation material and the information 4 contained in it. Those conversations are the identified source of Aliaga's privacy and development5 information injuries. Notion's notice supplies a defined affected dataset that can be examined 6 without equating a connected external service with wholesale access to all of that service's records. 7 G. Replit confirmed GUBER’s account was affected. 8 9 10 11 70. entitled "Security Notice: Third-Party Provider Security Incident Affecting Replit User Data." Replit identified Fireworks as the provider involved and stated that some data associated with GUBER's account was impacted.19 12 13 14 15 16 71. 19 20 21 identified GUBER's account among the fewer than 0.05 percent of accounts affected. It identified a subset of prompts dated July 14 through July 29, 2026, together with token counts, timings, tool outputs, and settings. 72. 24 25 Replit described the records as lacking labels tying them to a person, account, or organization, but warned that the prompt text could contain information identifying the source. It excluded account passwords and payment information outside the agent sessions from the described exposure. Those exclusions do not eliminate the proprietary development content within the affected sessions. 22 23 The notice stated that Fireworks informed its customers on November 9 that an unauthorized party had obtained access to certain data. Replit said its further investigation 17 18 Replit sent the account used by GUBER a security notice on November 10, 2026, 73. Replit recommended rotating potentially exposed credentials, reviewing activity in Replit and connected services, and watching for phishing. It distinguished credentials a user might have included in a prompt from ordinary account credentials outside the session. The notice accordingly required an account-specific assessment of the actual text and related material. 26 27 28 19 Replit, Security Notice: Third-Party Provider Security Incident Affecting Replit User Data (Nov. 10, 2026) (notice to the account used by GUBER; retained by counsel). 17 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 74. Document 1 Filed 11/17/26 Page 18 of 39 PageID #: 18 GUBER requested an account-specific disclosure and preservation of evidence 2 from Replit. As of its initial inquiry to counsel, it had not received enough information to determine 3 the complete scope of exposure or additional resulting harm. The original notice supplies a direct 4 affected-account link even though the complete payload and access history remain in Defendants' 5 possession. 6 75. For GUBER, material unanswered questions include which prompts and tool 7 outputs were retained; what project or file content those outputs contained; which copies reached 8 Fireworks; the permissions governing those copies; the unauthorized access actually recorded; and 9 what steps were taken to isolate, recover, or render unusable the exposed material. A percentage of 10 all Replit accounts does not answer any of those questions. 11 12 H. Uber disclosed access to ID records via compromised provider credentials. 13 76. Uber’s formal notice states that its provider warned it of compromised internal 14 credentials on October 9, 2026. Uber disconnected the provider and investigated. By October 13, 15 Uber had determined that the credentials had been used to access personal information. The notice 20 16 is dated November 10. 77. 17 Uber's Iowa filing dates the unauthorized access to October 7. It describes Uber- 18 created cloud storage supporting the provider's work, overseen by Uber's Cloud Security team. 19 Alerts were enabled but did not trigger because the intruder used valid credentials and existing data 20 flows. The filing identifies driver's-license images and extracted names, addresses, birth dates, and 21 21 license numbers. 22 23 24 25 20 Uber Techs., Inc., Notice of Security Incident 1–2 (Nov. 10, 2026), 26 https://oag.ca.gov/system/files/Multistate%20Template%20-%20Final.pdf (filed with the California Attorney General). 27 21 Letter from Amelia M. Gerlicher, Counsel for Uber Techs., Inc., to Consumer Prot. Div., Off. of the Att'y Gen. of Iowa, Re: Notification of Security Incident 1–2 (Nov. 10, 2026), 28 https://www.iowaattorneygeneral.gov/media/cms/11102026_Uber_Technologies_Inc_089721E61 CBAB.pdf. 18 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 78. Document 1 Filed 11/17/26 Page 19 of 39 PageID #: 19 An Uber spokesperson identified Fireworks.ai as the third-party vendor involved 2 in the notices sent to drivers, according to the Wall Street Journal. That identification connects the 3 formally disclosed access mechanism to the common provider in this action. 22 4 79. The access path involved two distinct security responsibilities: safeguarding 5 provider credentials and restricting access to the records those credentials could reach. A system's 6 recognition of a credential as valid does not establish that the person presenting it is authorized. On 7 information and belief, reasonable safeguards required limiting the information reachable through 8 those credentials and assessing misuse of authorized access paths. 9 80. The Iowa filing states that the credentials did not provide access to other Uber 10 systems and that the investigation remained ongoing. The alleged exposure concerns the identified 11 environment; it does not require access to every Uber system. The October 7 date also precedes the 12 separate October 24 Fireworks development-machine event. Plaintiffs allege the chronology 13 specific to this spoke rather than treating the later event as the date of the Uber access. 14 81. Texas's published Uber report identifies 149,346 affected individuals in total, 15 including 4,296 Texans. Oregon's listing independently reports 149,346 affected individuals. These 16 are reported incident figures, not an allegation that every person counted resided in the United 17 States or that the totals from the two states should be added together. 23 18 82. Uber's consumer notice offers credit monitoring and fraud assistance and states 19 that Uber had not identified misuse of the information as of that notice. The absence of identified 20 misuse does not undo the access Uber reported. The offering also does not establish that Plaintiffs 21 Tallauze or Lewis enrolled in monitoring or incurred a particular expense. 22 23 24 22 Natalie Weger, Uber Says Personal Data Was Exposed in Third-Party Data Breach, Wall St. J. 25 (Nov. 13, 2026), https://www.wsj.com/tech/uber-says-personal-data-was-exposed-in-third-partydata-breach-02e3a875 (reporting a statement by Uber's spokesperson identifying Fireworks.ai). 26 23 Off. of the Att'y Gen. of Tex., Data Security Breach Reports, Uber Technologies, Inc., report no. BR-0005510 (published Nov. 13, 2026), 27 https://oag.my.site.com/datasecuritybreachreport/apex/DataSecurityReportsPage (last visited Nov. 17, 2026); Or. Dep't of Just., Data Security Breaches, Uber Technologies, Inc. (reported Nov. 10, 28 2026), https://justice.oregon.gov/consumer/databreach/ (last visited Nov. 17, 2026) (corroborating the reported affected-person total). 19 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 83. Document 1 Filed 11/17/26 Page 20 of 39 PageID #: 20 The relevant common evidence includes the records placed in the provider-access 2 environment, the affected-person mapping, credential privileges, access logs, alerting rules, and 3 the chronology of revocation and investigation. Those records can establish the data reached, the 4 scope of each Defendant's control, and whether the safeguards reasonably addressed the access 5 mechanism disclosed by Uber. 6 I. Independent disclosures corroborate the provider access risks. 7 8 9 10 11 12 84. was exposed there and used to copy a shared read-only storage bucket. Cursor described the bucket as containing historical coding-agent traces from sessions outside Privacy Mode, some containing unredacted credentials. It reported further access through credentials found in those traces, affecting selected internal services and information. Cursor distinguished those historical records from active inference and said Privacy Mode prompts and code were unaffected. 24 13 14 15 16 17 18 85. 21 22 system as the compromised credential. The account corroborates the importance of credential scope, customer-side access permissions, retained copies, and investigation across connected systems. Plaintiffs do not infer that Notion and Replit used Cursor's bucket or the same processing configuration. 86. Nikken's November 13 notice states that affected Notion AI material included business information and the names of contact people at business partners. It distinguishes attached files themselves from AI-generated content based on those files and describes continuing review and business-partner notifications.25 23 24 This account identifies an additional way compromised provider credentials can expose downstream information. The relevant information need not reside on the same physical 19 20 In a November 13 disclosure, Cursor reported that a key it had issued to Fireworks 87. Information in an affected conversation may therefore concern someone other than the person who held the submitting account or received the workspace notice. A company 25 24 Cursor Team, An Update on Our Recent Security Incident, Cursor (Nov. 13, 2026), https://cursor.com/blog/security-incident-update (sections entitled "What happened" and "What 27 was not affected"). 25 Nikken Sekkei Ltd., Notice Regarding a Data Breach in the Cloud Service (Notion AI) Used by 28 Nikken Group Companies §§ 2–4 (Nov. 13, 2026), https://www.nikken.co.jp/en/news/news/20261113j.html. 26 20 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 21 of 39 PageID #: 21 1 may own the development material in an employee's session, and a private conversation may 2 contain another person's nonpublic information. The four classes below address those interests 3 through the affected information itself. 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 J. Aliaga’s affected educational and startup information. 88. Aliaga had a Notion account for several years before upgrading to the Business plan in August 2026. She subscribed for one paid seat at $24 per month. Her paid invoices are dated August 26, September 26, and October 26, 2026. The affected October conversations were created after that upgrade. 89. Aliaga used Notion to organize academic activities and to work on software development, including an early-stage startup project with other students. She supplied information for those tasks within her account. She did not intend the affected conversations to be disclosed to an unauthorized outsider. 90. Aliaga connected her Canvas calendar to Notion Calendar through her school email calendar. Her use of the connected services brought academic scheduling information into her Notion-related workflow. Separately, her review of the affected conversation records confirmed that the identified text included information about her academic activities and development projects. 91. After receiving the notice, Aliaga retrieved and reviewed the records Notion made available for her affected conversations. Those records identified 151 messages across seven threads, with content dates spanning October 5 through October 23, 2026. She recognized private material concerning her academic activities, scheduling, and software-development work. 92. On information and belief, the affected development material included Aliaga's proprietary startup information and nonpublic technical work, including information she maintained as confidential trade-secret information, and the unauthorized disclosure compromised the confidentiality of those materials. Their substantive contents can be identified in protected discovery without republishing the technical details in this complaint. 93. Aliaga asserts injury to her own privacy and, on information and belief, her interests in the affected startup and trade-secret information. Her claims concerning collaborative 21 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 22 of 39 PageID #: 22 1 work are limited to rights she holds. The allocation of rights in particular materials can be 2 established through project records and agreements while protecting the underlying information. 3 94. The affected educational conversations concerned her own activities in a context 4 she treated as private. Her decision to use an AI tool to organize or work with information did not 5 eliminate that expectation as against an unauthorized third party. The ability of a provider to read 6 data for a limited service purpose differs from unrestricted disclosure beyond that purpose. 7 95. The content itself carried details associated with Aliaga's activities and projects. 8 Even without an added account label, contextual information could connect the material to her or 9 reveal confidential project details. She became concerned about that possibility after examining the 10 actual records, rather than solely from learning that some unrelated account had experienced an 11 incident. 12 96. On information and belief, Aliaga's identified nonpublic conversation content was 13 among the material accessed or acquired without authorization in the incident. That allegation is 14 supported by Notion's workspace-specific notification, the affected-content records supplied to her, 15 her recognition of their contents, and Notion's public explanation of its incident-review exports. 16 97. The resulting injury includes the disclosure and loss of confidentiality of private 17 information. A conversation disclosed to an unauthorized person is no longer confined to the 18 audience for which it was provided, regardless of whether the recipient has yet attempted financial 19 fraud. Aliaga also spent time reviewing the identified material and determining its relevance to her 20 private activities and development work. 21 98. The unauthorized disclosure and resulting loss of confidentiality are present 22 injuries. The extent of additional legally recoverable loss will be established through evidence of 23 actual consequences and expenses. Aliaga does not allege that every affected person suffered 24 identity theft, fraud, or the same amount of monetary loss. 25 26 K. GUBER’s affected commercial development information. 27 99. During July 14 through July 29, 2026, GUBER was actively using Replit to 28 develop commercial AI technology and associated applications. Its founder acted for the company 22 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 23 of 39 PageID #: 23 1 in that work. The development sessions included instructions and technical context needed to make 2 the software perform GUBER's intended business functions. 3 100. The affected subject matter included GUBER's proprietary technical designs, 4 development material, and business workflows. These materials reflected how its commercial 5 technology would operate and included information GUBER maintained as trade secrets. Their 6 contents could reveal implementation choices and nonpublic functionality developed for the 7 company. 8 101. GUBER treated the affected proprietary material as confidential company 9 information and supplied it for its development work. It seeks recovery for the impairment of its 10 rights in that material. The specific technical information and evidence of the measures used to 11 protect it can be disclosed under appropriate discovery protections, preserving the confidentiality 12 remaining in the information. 13 102. Replit's account-specific notice supports an allegation that GUBER's 14 development-session information was within the affected data. Plaintiffs do not infer that every 15 GUBER repository, application, line of code, or company record was obtained. The exposed subset 16 and its significance can be determined by comparing the affected records with GUBER's 17 development history. 18 103. The inclusion of tool outputs in Replit's notice increases the importance of 19 comparing the affected records with GUBER's development history. An agent session can contain 20 material beyond the instruction originally entered by the user. The identified tool output may show 21 whether additional nonpublic development material was exposed during that work. 22 104. GUBER's affected development material was exposed to an unauthorized actor, 23 impairing the confidentiality in which the company maintained that material. Its representative 24 requested disclosure and preservation to identify what had been compromised and evaluate an 25 appropriate response. The extent of any competitive injury will be determined by comparing the 26 compromised information with the company's development records and evidence of subsequent 27 use. 28 23 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 105. Document 1 Filed 11/17/26 Page 24 of 39 PageID #: 24 GUBER seeks recovery for legally cognizable injury caused by the exposure and 2 established through evidence, including reasonable investigation and containment expenses, 3 necessary remediation of specifically exposed material, and impairment of proprietary interests to 4 the extent recoverable under the governing law. Its claim concerns the consequences of the affected 5 disclosure rather than an undifferentiated valuation of the entire company. 6 7 L. Tallauze’s affected identification information. 8 106. Uber obtained and maintained an image of Tallauze's driver's license and related 9 identification information in connection with its platform operations. The information was supplied 10 or maintained for a limited service purpose and was not intended for public dissemination or use 11 by an unauthorized third party. 12 107. On information and belief, the affected Uber records included Tallauze's driver's- 13 license image and extracted text containing his name, street address, date of birth, and driver's14 license number, together with identifying information appearing on that image. These are the 15 categories described in Uber's formal disclosures. Tallauze's actual license number, full birth date, 16 street address, and document image are not reproduced in this public pleading. 17 108. On information and belief, Tallauze's identification records were among the Uber 18 information accessed or acquired through the compromised provider credentials. The allegation 19 concerns the Uber environment described above and the access permitted through Fireworks; it 20 does not depend on a direct subscription relationship between Tallauze and Fireworks or on an 21 allegation that he personally supplied credentials to Fireworks. 22 109. On information and belief, that unauthorized acquisition disclosed Tallauze's 23 sensitive identification records beyond their intended custodians and caused a present loss of 24 confidentiality. A government-issued identification image combined with the identifying fields 25 extracted from it can enable impersonation and targeted misuse. The alleged privacy injury arises 26 from the completed unauthorized access and disclosure, without an allegation that a particular 27 fraudulent transaction has already occurred. 28 24 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 110. Document 1 Filed 11/17/26 Page 25 of 39 PageID #: 25 Uber's account records and affected-person mapping, together with the storage 2 and access records, will further establish Tallauze's connection to the compromised records. 3 Tallauze seeks compensatory relief for legally cognizable injury caused by the disclosure and any 4 additional recoverable consequences established by evidence. He does not allege a presumed 5 monetary value for each exposed field or an unverified expenditure. 6 7 M. Lewis’ affected identification information. 8 111. Plaintiff Lewis received a notice letter from Defendant dated November 10, 2026, 9 informing him that his Private Information, including at least an image of his driver’s license and 10 text data that included his name, address, date of birth, and driver’s license number, was impacted 26 11 in the Breach. 112. 12 Lewis’ identification records were among the Uber information accessed or 13 acquired through the compromised provider credentials. The allegation concerns the Uber 14 environment described above and the access permitted through Fireworks; it does not depend on a 15 direct subscription relationship between Lewis and Fireworks or on an allegation that he personally 16 supplied credentials to Fireworks. 113. 17 The unauthorized acquisition disclosed Lewis’ sensitive identification records 18 beyond their intended custodians and caused a present loss of confidentiality. A government-issued 19 identification image combined with the identifying fields extracted from it can enable 20 impersonation and targeted misuse. The alleged privacy injury arises from the completed 21 unauthorized access and disclosure, without an allegation that a particular fraudulent transaction 22 has already occurred. 23 N. Specific security oversight failures caused the exposure. 24 114. 25 Having accepted nonpublic information or authority to access it for service 26 processing, Fireworks was required to exercise reasonable care within the scope of that custody 27 28 26 Exhibit 1 25 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 26 of 39 PageID #: 26 1 and control. The affected population was bounded by identifiable customer relationships and the 2 information reached through them. Fireworks's conduct directly determined whether downstream 3 data subjects and owners faced unauthorized access, while Fireworks derived a commercial benefit 4 from the processing. 5 115. On information and belief, Fireworks failed to restrict credential access and the 6 reach of internal accounts sufficiently to prevent the unauthorized access affecting Plaintiffs. The 7 factual basis includes Fireworks's disclosed misuse of internal credentials, the Uber access 8 mechanism described in paragraph 76, and the later access to development machines that caused 9 additional customer-data impact. The particular credentials, privileges, and affected storage paths 10 remain within its records. 11 116. On information and belief, Fireworks failed to maintain sufficient separation 12 between systems vulnerable to the unauthorized activity and customer content reachable from those 13 systems. This allegation is grounded in Fireworks's account of an unauthorized workload on 14 development machines causing customer-data impact. It concerns the actual connection between 15 those environments, rather than an assumption that all development infrastructure must operate 16 without any customer data. 17 117. For the Notion material, the discrepancy described in paragraph 4 identifies 18 retained conversation content at endpoints expected to discard it. On information and belief, 19 Fireworks failed to apply and verify retention and access controls appropriate to that content and 20 processing purpose. Those operational failures were substantial factors in leaving the affected 21 conversations available for unauthorized access. 22 118. Reasonable operation of the relevant systems required verifying the settings, 23 copies, and access permissions governing the nonpublic information accepted for processing. On 24 information and belief, inadequate verification allowed the conditions described above to persist. 25 The claim concerns those security practices independently of a demand that Plaintiffs receive 26 performance under a vendor agreement. 27 119. On information and belief, Notion, Replit, and Uber each failed to exercise 28 reasonable care in configuring, supervising, and verifying the processing or access arrangements 26 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 27 of 39 PageID #: 27 1 for their respective affected data. These allegations concern each platform's own data flows, 2 permissions, and oversight. They do not rest solely on the proposition that a vendor suffered an 3 attack. 4 120. For Notion, the factual basis includes the identified data flow and retention 5 discrepancy described in paragraphs 39 and 4. Reasonable oversight required verification of the 6 material safeguards governing that processing arrangement. On information and belief, Notion's 7 verification was inadequate. 8 121. For Replit, the factual basis includes its use of Fireworks and its identification of 9 GUBER's historical prompts and tool outputs in the affected data. On information and belief, Replit 10 failed to apply or verify safeguards sufficient for the duration, sensitivity, and access paths of those 11 development records. GUBER's unanswered request for fuller disclosure separately demonstrates 12 why the complete scope and resulting response needs remain unresolved. 13 122. For Uber, the factual basis includes the disclosed provider-access environment 14 and failure of its enabled alerting to identify the use of compromised credentials. On information 15 and belief, Uber failed to implement or verify access restrictions and monitoring reasonably suited 16 to that environment and the sensitivity of the identification records. The claim concerns the 17 permissions and safeguards Uber controlled, including protection against misuse of an otherwise 18 valid provider credential; it does not assume that Uber had no monitoring or that every authorized 19 provider connection was improper. 20 123. Each Defendant also had responsibilities within its own role to investigate the 21 reach of compromised credentials and identify affected data accurately. Plaintiffs do not treat a 22 later notification date, without the accompanying investigation facts, as proof of a particular 23 statutory notification violation. The relevant questions include when a Defendant learned of access 24 affecting the relevant data, what it could reasonably determine, and what information it supplied to 25 enable a meaningful response. 26 124. Plaintiffs could manage their own access and content choices, but they could not 27 revoke a Fireworks employee credential, segregate its development network, inspect a retained 28 processing dataset, administer Uber's provider-access environment, or determine which 27 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 28 of 39 PageID #: 28 1 downstream copies had been accessed. The alleged failures concern those functions rather than an 2 unsupported assertion that a Plaintiff disclosed an account password or disabled a protection. 3 125. The exposure alleged here is the foreseeable result of failures to protect 4 information accepted for processing. Restricting credentials reduces the records an intruder can 5 reach; separating environments limits movement into customer-data systems; and eliminating an 6 unnecessary retained copy removes it from the available target set. On information and belief, 7 failures in those controls were substantial factors in the unauthorized access to Plaintiffs' identified 8 information. 9 126. Protecting nonpublic data against unauthorized actors is a principal purpose of the 10 credential, access, retention, and vendor controls at issue. The malicious actor's intervention 11 presented the very category of risk those safeguards were intended to address. Plaintiffs allege 12 failures to exercise reasonable care in the functions each Defendant actually controlled. 13 127. The causal allegations combine the specific platform-to-provider relationships, 14 the allegations concerning each Plaintiff's affected information, GUBER's and Aliaga's affected15 account notices, Lewis’ notice letter from Uber informing him he was affected by the data breach, 16 Uber's regulatory disclosures, the categories and dates supplied by Defendants, and the disclosed 17 access and retention conditions. Tallauze's inclusion in the affected Uber records is alleged on 18 information and belief. Defendants' account mappings, storage inventories, and forensic records 19 will further establish the connection between the identified access paths and each Plaintiff's 20 information. 21 22 O. Common evidence can establish the extent of the incident. 23 128. The principal sources of common proof include the affected datasets; mappings 24 between those datasets and customer accounts; notices; routing and job records; storage and 25 deletion records; credential and permission histories; forensic access records; and the instructions 26 and agreements governing processing. These materials concern how Defendants handled the same 27 categories of information through centralized systems. 28 28 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 129. Document 1 Filed 11/17/26 Page 29 of 39 PageID #: 29 Common records can distinguish the scope of system access from the records 2 actually obtained, permitted storage from retention exceeding an applicable instruction, and 3 compromised content from later investigative annotations. Those distinctions will establish the 4 reach and consequences of the common processing failures. 5 130. Individual evidence will establish the content of a claimant's affected records, the 6 claimant's interest in that information, and any recoverable personal or business loss. That evidence 7 can be considered through phased proceedings and appropriate damages procedures without 8 requiring every class member to reproduce the same proof about Fireworks's internal systems or a 9 platform's common security practices. 10 131. The precise contents of the affected private conversations and proprietary 11 technical material can be exchanged under an appropriate protective order and, where the legal 12 standard is met, presented to the Court through narrowly tailored sealing procedures. The public 13 complaint describes the categories and circumstances necessary to plead the claims without 14 republishing the sensitive material whose confidentiality Plaintiffs seek to protect. 15 V. 16 17 18 19 20 21 22 23 24 25 26 27 28 132. CLASS ACTION ALLEGATIONS Plaintiffs bring this action under Federal Rule of Civil Procedure 23(a) and (b)(3), and alternatively seek certification of appropriate common issues under Rule 23(c)(4). They propose only the following four classes. For these definitions, the "Fireworks Security Incidents" are the unauthorized-access events described above and disclosed by Fireworks and affected customers in October and November 2026. "Persons and entities in the United States" includes individuals who resided in the United States when their information was accessed or acquired, and entities then organized under the laws of a United States jurisdiction or maintaining their principal place of business in the United States. 133. Fireworks Class: All persons and entities in the United States whose nonpublic information or content was accessed or acquired by an unauthorized person in the Fireworks Security Incidents, including information held by Fireworks or reached through credentials compromised in those incidents. 29 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 134. Document 1 Filed 11/17/26 Page 30 of 39 PageID #: 30 Notion Class: All persons and entities in the United States whose nonpublic 2 information or content was contained in data supplied or made accessible through Notion and 3 accessed or acquired by an unauthorized person in the Fireworks Security Incidents. 4 135. Replit Class: All persons and entities in the United States whose nonpublic 5 information or content was contained in data supplied or made accessible through Replit and 6 accessed or acquired by an unauthorized person in the Fireworks Security Incidents. 7 136. Uber Class: All persons and entities in the United States whose nonpublic 8 information or content was contained in data supplied or made accessible through Uber and 9 accessed or acquired by an unauthorized person in the Fireworks Security Incidents. 10 137. The four classes include affected current and former users, account holders, 11 workspace or organization members, guests, and persons or entities whose information others 12 supplied. Membership does not depend on whether access was free or paid, personal or commercial, 13 or obtained through an individual or organizational account. Receipt of an incident notice, use of a 14 particular subscription plan, and a direct account with Fireworks are not required. The Fireworks 15 Class is not limited to information supplied through Notion, Replit, or Uber. 16 138. The Fireworks Class is asserted against Fireworks; the Notion Class against 17 Notion; the Replit Class against Replit; and the Uber Class against Uber. Aliaga, GUBER, Tallauze 18 and Lewis seek to represent the Fireworks Class, Aliaga the Notion Class, GUBER the Replit Class, 19 and Tallauze and Lewis the Uber Class. A person or entity may belong to more than one class. 20 Each Defendant's liability and each claimant's legally protected interest and recoverable injury must 21 be established under the applicable claim, without duplicating recovery for the same injury. 22 139. Excluded are Defendants; their officers and directors; entities they control; 23 persons who participated in the unauthorized access; the judicial officers assigned to this action 24 and their immediate families; and persons who timely and validly request exclusion from a certified 25 damages class. Membership requires nonpublic information or content about or belonging to the 26 member within the affected data. Platform use alone does not establish membership. 27 140. Numerosity. On information and belief, the proposed classes are sufficiently 28 numerous that joinder is impracticable. Uber's reported total and Texas population are set out in 30 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 31 of 39 PageID #: 31 1 paragraph 80. Notion and Replit describe affected data across multiple accounts and workspaces 2 and maintain member-mapping or account records. The precise membership of each class, 3 including overlap and the applicable United States population, can be determined from those 4 records. The reported Notion and Replit percentages are not treated as counts of persons or as proof 5 that every platform account was affected. 6 141. Commonality. Common questions include the nature and reach of the Fireworks 7 access paths; which data copies were retained; what retention and access controls applied; whether 8 reasonable safeguards were implemented; whether the alleged failures caused unauthorized access 9 to the identified data; and what common remediation or disclosure obligations remain. 10 142. For the Notion Class, additional common questions concern the actual processing 11 arrangement, the endpoint and retention conditions described in paragraph 4, vendor oversight, the 12 identification of affected content, and whether Notion exercised reasonable care in transmitting and 13 supervising the processing of that content. 14 143. For the Replit Class, additional common questions include the content and 15 duration of retained development-session records; the instructions governing Fireworks's 16 processing; the nature of the affected tool outputs; the access paths reaching the records; and 17 whether Replit reasonably assessed, implemented, and verified the safeguards for that processing. 18 144. For the Uber Class, additional common questions concern the provider-access 19 environment, the scope and protection of credentials, the permissions and monitoring governing 20 that environment, identification of the affected records, and whether Uber exercised reasonable 21 care in safeguarding information reachable through the provider's access. 22 145. Typicality. Each named Plaintiff alleges loss of confidentiality of nonpublic 23 information reached through a platform's relationship with Fireworks. Aliaga's claims arise from 24 affected Notion conversations and GUBER's from affected Replit development sessions; their 25 respective notices identify their own workspace or account. On information and belief, Tallauze's 26 and Lewis’ claims arise from the affected Uber identification records and the credential-access path 27 Uber disclosed. Their claims challenge the security and processing failures applicable to the 28 information and classes each seeks to represent. 31 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 146. Document 1 Filed 11/17/26 Page 32 of 39 PageID #: 32 The proposed common questions concern the handling and protection of affected 2 information. Differences in a member's status as a user, data subject, or information owner do not 3 change the identity of the affected systems or the challenged security practices. Plaintiffs will 4 establish the protected interests and remedies applicable to their own injuries and to the claims 5 presented for certification. 6 147. Adequacy. Plaintiffs will fairly and adequately protect the interests of the classes 7 they seek to represent. Their interests in establishing the relevant failures, obtaining appropriate 8 relief, and preserving the confidentiality of affected material align with those classes. They have 9 retained counsel to prosecute the action and will discharge their duties as representatives, subject 10 to the Court's supervision. 11 148. If discovery identifies material differences in the applicable law, processing paths, 12 or recoverable injuries, Plaintiffs will propose appropriate issue certification, trial procedures, 13 additional representatives where warranted, or refinement of the four class definitions under Rule 14 23(c)(1)(C). Plaintiffs do not assume that all members suffered the same loss or that one business's 15 proprietary material has the same value as another's. 16 149. Predominance. The central liability evidence concerns centralized systems, 17 retained datasets, provider instructions, access controls, and common security practices. It will 18 substantially overlap across members of the applicable class. Individual questions concerning the 19 amount of loss can be addressed separately where the common liability issues otherwise satisfy 20 Rule 23(b)(3). 21 150. Plaintiffs seek application of California law where supported by the applicable 22 choice-of-law rules and facts, including the locations of Defendants and the relevant conduct. The 23 location of a headquarters alone does not supply California law for every claim nationwide. 24 Plaintiffs will address material differences in governing law through the certification analysis, 25 proposed common issues, and any necessary refinement of the four classes. 26 151. Superiority. Common proceedings would avoid duplicating discovery and 27 adjudication of Defendants' processing arrangements and security systems. Many individual claims 28 concerning unauthorized disclosure would be uneconomic to litigate separately. The class 32 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 33 of 39 PageID #: 33 1 procedure also permits owners with materially different business losses to evaluate their own 2 interests and exercise applicable exclusion rights. 3 152. Manageability. Defendants' affected-account notices, member records, and 4 dataset mappings provide objective starting points for identifying members. Claimant evidence can 5 verify ownership or personal connection to particular material and resulting losses, including 6 claims by persons who did not hold the submitting account or receive the original notice. Any 7 distribution or damages process can account for reimbursements, overlapping accounts, and 8 duplicate claims so that the same injury is not compensated more than once. 9 153. Alternatively, Plaintiffs seek certification of particular issues under Rule 23(c)(4), 10 including applicable common duties, retention or access practices, breach, and common causation 11 questions, to the extent those issues can be resolved fairly on a class basis. Plaintiffs request a 12 certification structure responsive to the evidence and the Court's choice-of-law analysis. 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 VI. CLAIMS FOR RELIEF FIRST CAUSE OF ACTION NEGLIGENCE AGAINST FIREWORKS (GUBER, Aliaga, Tallauze, and Lewis on behalf of themselves and the Fireworks Class) 154. Plaintiffs incorporate the preceding factual and class allegations applicable to Fireworks and the Fireworks Class. GUBER, Aliaga, Tallauze, and Lewis assert this claim for their respective affected information and injuries. 155. Fireworks owed a duty to use reasonable care in receiving, processing, retaining, securing, and controlling access to Plaintiffs' nonpublic information, including protecting credentials capable of reaching that information. The duty arises from Fireworks's own acceptance of custody or access authority and its control of the systems and permissions through which an unauthorized actor could reach the information. 156. The relationship was concrete and bounded: Fireworks received information or access authority through identifiable enterprise customers for particular processing functions; the 33 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 34 of 39 PageID #: 34 1 downstream subjects and owners could not administer Fireworks's security; the disclosure risk was 2 foreseeable from the substance and purpose of the processing; and Fireworks benefited 3 commercially from that work. The responsibility asserted concerns the foreseeable effect of 4 Fireworks's own conduct on the people and businesses whose information it handled. 5 157. Reasonable care included restricting credential scope, applying effective 6 authorization, segregating relevant environments, limiting unnecessary retention, verifying the 7 operation of material controls, and investigating known compromises sufficiently to identify and 8 contain access affecting customer information. The appropriate safeguards depended on the 9 sensitivity, purpose, and duration of the processing. 10 158. Fireworks breached that duty through the failures alleged in paragraphs 114 11 through 123, including the access paths by which unauthorized activity reached affected data and 12 the retention and verification failures affecting Notion information. Plaintiffs will establish the 13 technical details through the records of the affected systems and investigation. 14 159. Those failures were substantial factors in permitting access to Plaintiffs' identified 15 information. The unauthorized actor's intervention was within the category of risk the safeguards 16 were intended to address. The allegations concerning each Plaintiff and the access paths described 17 above, including Tallauze's allegations on information and belief, connect the alleged provider-side 18 conduct to the affected information. 19 160. Aliaga suffered unauthorized disclosure of her nonpublic personal information 20 and related response burdens and, on information and belief, impairment of her interests in the 21 affected startup and trade-secret information. GUBER suffered loss of confidentiality and 22 impairment of its interests in its development information. Lewis suffered unauthorized acquisition 23 and disclosure of his sensitive identification records and the resulting loss of confidentiality. On 24 information and belief, Tallauze suffered unauthorized acquisition and disclosure of his sensitive 25 identification records and the resulting loss of confidentiality. Each seeks damages proximately 26 caused by Fireworks's breach and recoverable under the governing law for the injury established, 27 without duplicating another recovery. 28 34 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 161. Document 1 Filed 11/17/26 Page 35 of 39 PageID #: 35 SECOND CAUSE OF ACTION NEGLIGENCE AGAINST NOTION (Aliaga on behalf of herself and the Notion Class) Aliaga incorporates the preceding factual and class allegations applicable to her, Notion, and the Notion Class. 162. Notion owed a duty of reasonable care in its own handling and transmission of nonpublic information and in the configuration and oversight of the processing arrangements it selected for that information. Aliaga entrusted personal and development content through Notion's service, while Notion controlled the vendor relationship and the information routed for Insights. 163. Notion's custodial responsibility concerned protection against unauthorized disclosure of private information already entrusted to it. Notion chose the outside recipient and controlled the purpose and parameters of the transfer. Its independent conduct exposed Aliaga to a privacy injury beyond the failure to furnish an ordinary product feature. 164. Notion breached the duty through the failures alleged in paragraphs 114 through 123, including inadequate implementation and verification of the controls governing the relevant processing. The particular operational discrepancy described above supplies a factual basis for the claim beyond the occurrence of a vendor attack. 165. Notion's conduct was a substantial factor in the exposure of Aliaga's identified conversations. Notion supplied the material for the relevant processing and was responsible for its own choices and oversight within that arrangement. The data included private educational information and, on information and belief, confidential startup and trade-secret information, as described without republishing the material in this complaint. 166. Aliaga and members of the Notion Class suffered the unauthorized disclosure of their affected information and resulting legally cognizable injuries. Aliaga seeks compensatory damages according to proof under the governing law, without duplicating any recovery under another claim. /// /// /// 35 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 Filed 11/17/26 Page 36 of 39 PageID #: 36 THIRD CAUSE OF ACTION NEGLIGENCE AGAINST REPLIT (GUBER on behalf of itself and the Replit Class) 2 3 Document 1 167. GUBER incorporates the preceding factual and class allegations applicable to it, 4 Replit, and the Replit Class. 5 168. Replit owed a duty to exercise reasonable care in receiving, transmitting, and 6 securing nonpublic development information and in configuring and supervising the processing 7 arrangements it selected for that information. GUBER supplied proprietary material for 8 development work, while Replit controlled the provider relationship, the data it transmitted, and its 9 assessment and oversight of the relevant safeguards. 10 169. The duty asserted concerns Replit's own handling of information entrusted to it 11 and protection against unauthorized access to that information. The challenged conduct includes 12 operational decisions about the data supplied to an outside processor, the duration and location of 13 retained copies, the permissions capable of reaching them, and verification of the security controls 14 governing that processing. 15 170. The risk to the owners and subjects of the information was foreseeable from the 16 nature of Replit's development service and the prompts and related session material it accepted. 17 The affected population was bounded by the information Replit caused to be processed. GUBER 18 could not inspect the provider's retained datasets, configure its internal permissions, or revoke its 19 compromised credentials. Replit was positioned to assess and supervise the processing arrangement 20 it selected. 21 171. Reasonable care required safeguards appropriate to the sensitivity and persistence 22 of the development records, including appropriately restricted provider access, evaluation of the 23 processing purpose and retention settings, verification of material security controls, and 24 investigation of unauthorized access affecting the information. These precautions concern the 25 actual processing functions Replit directed or controlled. 26 172. On information and belief, Replit breached that duty through the failures described 27 in paragraphs 114 through 123. The account-specific notice, the identified historical prompts and 28 tool outputs, and the documented processing relationship supply the factual basis for the allegation. 36 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 Document 1 Filed 11/17/26 Page 37 of 39 PageID #: 37 1 Routing records, dataset histories, permissions, vendor reviews, and incident records will establish 2 the particular conditions that permitted access. 3 173. On information and belief, Replit's failures were substantial factors in permitting 4 unauthorized access to GUBER's affected development information. Protecting that information 5 from an outside actor was within the purpose of the safeguards at issue. Replit's own notice 6 identifies GUBER's account and the affected content period, connecting the alleged failures to 7 GUBER's information. 8 174. The unauthorized access impaired the confidentiality of GUBER's affected 9 development material and the proprietary interests described above. GUBER seeks damages 10 according to proof for legally cognizable injury proximately caused by Replit's conduct, including 11 reasonable response and remediation expenses to the extent established and recoverable. It does 12 not seek a presumed value for every affected record or duplicate recovery for the same injury. 13 14 FOURTH CAUSE OF ACTION NELIGENCE AGAINST UBER (Tallauze and Lewis on behalf of himself and the Uber Class) 15 16 175. Tallauze and Lewis incorporate the preceding factual and class allegations 17 applicable to them, Uber, and the Uber Class. Tallauze’s allegations concerning the inclusion and 18 exposure of his identification records are made on information and belief. 19 176. Uber owed a duty to exercise reasonable care in obtaining, maintaining, securing, 20 and controlling access to Tallauze's and Lewis’ nonpublic identification information. The duty 21 arises from Uber's own handling of sensitive records and its control over the environment and 22 permissions through which the provider could reach them. 23 177. The relationship was concrete and bounded by the people whose identification 24 records Uber maintained in the affected environment. Those people could not configure that 25 environment, restrict the provider's credential privileges, or administer Uber's security monitoring. 26 Unauthorized disclosure of sensitive identifying records was a foreseeable consequence of 27 inadequate safeguards for that access. 28 37 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 178. Document 1 Filed 11/17/26 Page 38 of 39 PageID #: 38 Reasonable care required access restrictions, credential controls, monitoring, and 2 verification appropriate to the information's sensitivity and the purpose of the provider's work. 3 Uber's responsibilities included evaluating the reach of provider access and whether its controls 4 reasonably addressed misuse of valid credentials. The claim concerns those operational duties 5 independently of enforcement of a subscription or driver agreement. 6 179. On information and belief, Uber breached that duty through the failures described 7 in paragraphs 114 through 123. Its disclosures identify a specific storage environment, provider 8 access mechanism, and monitoring result that support investigation of the controls at issue. The 9 permissions, configurations, and access records will establish the particular failures within Uber's 10 control. 11 180. Uber's failures were substantial factors in permitting unauthorized access to 12 Tallauze's and Lewis’ identification records. Safeguarding those records against misuse of provider 13 credentials was within the purpose of the duties alleged. The intruder's intervention presented the 14 category of foreseeable risk that reasonable data-security controls were intended to address. 15 181. Tallauze and Lewis suffered unauthorized disclosure and loss of confidentiality 16 of the sensitive information described in paragraphs 106 through 113. They and the Uber Class 17 seek compensatory damages according to proof for legally cognizable injury proximately caused 18 by Uber's conduct, without duplicating recovery against Fireworks or presuming that every 19 member suffered identity theft or incurred the same loss. 20 21 22 VII. PRAYER FOR RELIEF WHEREFORE, Plaintiffs request judgment against the Defendant or Defendants 23 responsible for each claim, as follows: 24 A. Certifying the Fireworks Class, the Notion Class, the Replit Class, and the Uber 25 Class, or appropriate common issues under Federal Rule of Civil Procedure 23; 26 appointing the appropriate named Plaintiffs as representatives; and appointing class 27 counsel under Rule 23(g); 28 38 CLASS ACTION COMPLAINT Case No.3:26-cv-14010 Case 3:26-cv-14010 1 B. Document 1 Filed 11/17/26 Page 39 of 39 PageID #: 39 Awarding compensatory and consequential damages to the extent authorized by the 2 governing law and established by proof, with appropriate allocation among the 3 responsible Defendants and no double recovery; 4 C. Granting appropriate equitable relief, if supported by a named Plaintiff's standing 5 and the substantive claim established, concerning any continuing handling or 6 threatened disclosure of that Plaintiff's affected confidential information; 7 D. Awarding pre-judgment and post-judgment interest as allowed by law; 8 E. Awarding reasonable attorneys' fees and costs where authorized by applicable law, 9 10 or from a common fund or other basis properly approved by the Court; and F. Granting such other and further relief as the Court deems just and proper. 11 VIII. DEMAND FOR JURY TRIAL 12 13 14 Pursuant to Federal Rule of Civil Procedure 38, Plaintiffs demand a trial by jury on all issues so triable. 15 16 17 DATED: November 17, 2026 FROST LLP 18 19 20 21 22 23 24 25 By: CHRISTOPHER FROST KEVIN S. DICKER Nicholas Hall (Pro Hac Vice Forthcoming) HALL ATTORNEYS PC Ryan Myers (Pro Hac Vice Forthcoming) FEDERMAN & SHERWOOD Attorneys for Plaintiff and the Proposed Class 26 27 28 39 CLASS ACTION COMPLAINT Case No.3:26-cv-14010