DataCloud Tech LLC v. Poshmark Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: DataCloud Technologies, LLC (Georgia)
  • Defendant: Poshmark, Inc. (Delaware)
  • Plaintiff's Counsel: Stamoulis & Weinblatt LLC
• Case Identification: 1:26-cv-00952, D. Del., 07/31/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant is incorporated in the State of Delaware.
• Core Dispute: Plaintiff alleges that Defendant's website infrastructure infringes a patent related to a system and method for deploying software applications over a distributed network.
• Technical Context: The technology concerns methods for delivering dynamic, client-side applications where application logic is maintained on a central server and assembled for execution on a user's device, a foundational concept for modern web and mobile applications.
• Key Procedural History: The asserted patent was the subject of a Certificate of Correction issued on November 20, 2007, to correct minor errors in the patent text. The complaint also includes preemptive statements arguing the patent claims are not directed to an abstract idea, suggesting an anticipation of a patent eligibility challenge under 35 U.S.C. § 101.

Case Timeline

Date	Event
2001-02-20	'351 Patent Priority Date
2007-07-17	'351 Patent Issue Date
2007-11-20	'351 Patent Certificate of Correction Issued
2026-07-31	Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 7,246,351 - "System And Method For Deploying And Implementing Software Applications Over A Distributed Network"

• Patent Identification: U.S. Patent No. 7,246,351, "System And Method For Deploying And Implementing Software Applications Over A Distributed Network," issued July 17, 2007.

The Invention Explained

• Problem Addressed: The patent's background section describes the difficulty of deploying powerful software applications over networks, particularly to resource-constrained devices like wireless personal digital assistants (WPDAs) or over slow internet connections '351 Patent, col. 1:24-41 Traditional browser-based solutions were described as limited in functionality and requiring constant connectivity, while locally installed compiled applications were difficult to deploy, update, and maintain across different device platforms '351 Patent, col. 2:26-61
• The Patented Solution: The invention proposes a client-side "Application Virtual Machine" (AVM) that downloads and installs on a user's device '351 Patent, abstract This AVM fetches text files (e.g., XML files) containing application logic from a server and "assembles the retrieved program logic into a functioning, graphical application" locally on the client device '351 Patent, abstract '351 Patent, col. 4:29-38 This architecture allows for a rich, platform-native user interface while keeping the core application logic centralized on the server for easy updates, aiming to combine the benefits of native applications with the deployment advantages of web-based systems '351 Patent, col. 5:15-40 '351 Patent, Fig. 2
• Technical Importance: This approach provided a framework for creating "thin-client" applications that could offer a more robust user experience than was typical with the HTML-based web applications of the era, a key consideration for the emerging mobile and wireless device market '351 Patent, col. 2:62-68

Key Claims at a Glance

• The complaint asserts infringement of at least independent claim 14 Compl. ¶16
• The essential elements of independent claim 14 are:
  • A method for deploying a computer program over a network comprising:
  • storing and running a software module on a client device of a user;
  • providing to the client device text files containing embedded program logic for the software module to assemble into the computer program, wherein the computer program provides a graphical user interface for receiving and interpreting user inputs to the client device;
  • running the computer program assembled from the embedded program logic on the client device; and
  • enabling user interaction with the computer program running on the client device.
• The complaint requests an adjudication that "one or more claims" have been infringed, reserving the right to assert additional claims Compl. ¶21.A

III. The Accused Instrumentality

Product Identification

The complaint identifies the accused instrumentalities as Defendant's "products and services, including its website infrastructure" Compl. ¶16

Functionality and Market Context

• The complaint alleges that the Defendant "shipped, distributed, made, used, imported, offered for sale, sold, and/or advertised" the accused services Compl. ¶16
• The complaint does not provide sufficient detail for a technical analysis of the accused instrumentality's specific architecture. It refers to a claim chart in "Exhibit B" for a more detailed infringement theory, but this exhibit was not included with the complaint document provided Compl. ¶16

IV. Analysis of Infringement Allegations

The complaint references a claim chart in an external exhibit (Exhibit B) that was not provided Compl. ¶16 Therefore, a detailed element-by-element analysis cannot be performed. The narrative theory of infringement, based on the allegations in the complaint, is that Poshmark's website infrastructure practices the method of asserted claim 14 Compl. ¶16 This theory suggests that Poshmark's system involves a client-side component (the alleged "software module") that runs on a user's device. This module allegedly receives "text files containing embedded program logic" from Poshmark's servers and uses them to "assemble" a "computer program" with a graphical user interface, which then runs on the user's device to enable user interaction Compl. ¶16 Compl. ¶17

No probative visual evidence provided in complaint.

• Identified Points of Contention:
  • Scope Questions: A central dispute may arise over the scope of the claim terms in the context of modern web technologies. The court will need to determine if a standard web browser and its JavaScript engine can be considered a "software module" and if dynamically rendering a webpage from JavaScript files and data constitutes "assembling" a "computer program" as those terms are used in the patent, which was filed in 2002.
  • Technical Questions: A key evidentiary question will be whether Poshmark's architecture operates in the manner described by the patent. The patent describes a specific "Application Virtual Machine" (AVM) that parses XML files to build and render an application '351 Patent, col. 7:31-45 The infringement case may depend on whether the plaintiff can demonstrate that Poshmark's system performs a technically equivalent "assembly" process, or if its operation is more akin to standard dynamic website rendering, which may fall outside the claimed method.

V. Key Claim Terms for Construction

• The Term: "software module"

  • Context and Importance: The definition of this term is critical for determining what client-side component is required. The plaintiff may argue it covers general-purpose software like a web browser, while the defendant may argue it is limited to a dedicated, installed application as described in the patent. Practitioners may focus on this term because its breadth will dictate whether the claim can read on modern web architectures that rely on standard browser technology.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The term "software module" itself is generic and is not explicitly defined in the patent, which could support an argument that it is not limited to a specific embodiment.
    • Evidence for a Narrower Interpretation: The specification consistently describes the client-side component as an "Application Virtual Machine" (AVM) that is downloaded and installed as a distinct entity '351 Patent, col. 4:29-34 '351 Patent, col. 5:15-20 This consistent description could be used to argue that "software module" should be construed more narrowly to mean a dedicated AVM-like component.

• The Term: "assemble into the computer program"

  • Context and Importance: This term defines the core inventive action. The case could turn on whether the dynamic rendering of a webpage by a browser from script and data files qualifies as "assembling" a program.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The claim language itself does not specify the mechanism of assembly. One might argue that any process that combines logic files and data to create an interactive, functional user interface constitutes "assembly."
    • Evidence for a Narrower Interpretation: The detailed description outlines a specific assembly process where the AVM parses XML files, builds a "Document Tree," and uses "Component Factories" to render a GUI '351 Patent, col. 11:5-13 '351 Patent, col. 13:27-44 '351 Patent, Fig. 5 This detailed disclosure may support a narrower construction limited to this or a very similar technical process.

VI. Other Allegations

• Indirect Infringement: The complaint alleges that if a third party performs any step of the claimed method, the Defendant "conditioned the third party's use of the functionality" and "controlled the manner and/or timing of the functionality" Compl. ¶17 This language appears to lay the groundwork for an argument of liability for divided infringement under 35 U.S.C. § 271(a) or induced infringement under § 271(b).
• Willful Infringement: The complaint does not contain specific factual allegations supporting willful infringement, such as pre-suit knowledge of the patent. However, the prayer for relief requests that the court "declare this to be an exceptional case and award Plaintiff its reasonable attorneys' fees and costs" under 35 U.S.C. § 285 Compl. ¶21.D

VII. Analyst's Conclusion: Key Questions for the Case

• A core issue will be one of definitional scope: can the claim term "software module", rooted in the 2001-era context of a specialized "Application Virtual Machine" (AVM), be construed to cover a modern, standard web browser? Similarly, can the term "assemble", described in the patent as a specific process of parsing XML files, be interpreted to encompass a browser's routine rendering of a dynamic webpage using JavaScript?
• A central dispute will be one of technological equivalence: the case will likely turn on whether the plaintiff can prove that the architecture of Poshmark's modern web platform is technically equivalent to the specific method of deploying and assembling applications disclosed in the '351 patent. The court will need to examine if there is a fundamental match in technical operation or if Poshmark's system represents a distinct, later-developed technology.