DataCloud Tech LLC v. Vivian Health Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: DataCloud Technologies, LLC (Georgia)
  • Defendant: Vivian Health, Inc. (Delaware)
  • Plaintiff’s Counsel: Stamoulis & Weinblatt LLC; Kent & Risley LLC
• Case Identification: 1:26-cv-00153, D. Del., 02/10/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant is a Delaware corporation.
• Core Dispute: Plaintiff alleges that Defendant’s website infrastructure infringes two patents related to anonymous network communication and the deployment of software applications over a network.
• Technical Context: The technologies at issue concern methods for routing network traffic to preserve user anonymity and for efficiently delivering interactive software applications to client devices over the internet.
• Key Procedural History: The complaint notes that a Certificate of Correction was issued for U.S. Patent No. 7,246,351 on November 20, 2007, but alleges no other significant procedural events.

Case Timeline

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

U.S. Patent No. 7,209,959 - "Apparatus, System, and Method for Communicating to a Network Through a Virtual Domain Providing Anonymity to a Client Communicating on the Network," issued April 24, 2007

The Invention Explained

• Problem Addressed: The patent’s background section describes the privacy risks inherent in the internet's architecture, where a user's information, such as their IP address and web history, can be easily recorded and traced by web servers (’959 Patent, col. 1:57-65).
• The Patented Solution: The invention proposes a system using three distinct logical components—a "deceiver," a "controller," and a "forwarder"—to create an anonymous communication session '959 Patent, abstract When a user attempts to connect to a website, the "deceiver" intercepts the request and passes it to the "controller," which resolves the true destination IP address but provides the user's browser with the IP address of a "forwarder" instead '959 Patent, col. 3:45-54 '959 Patent, Fig. 1 All subsequent traffic is routed through the forwarder, which masks the client's identity from the destination server and the destination server's identity from the client '959 Patent, col. 4:46-52
• Technical Importance: This architecture was designed to provide session-specific anonymity for internet browsing and to enable the creation of "virtual namespaces" for secure, private group communications '959 Patent, col. 2:49-54

Key Claims at a Glance

• The complaint asserts independent method claim 1 Compl. ¶17
• Essential elements of claim 1 include:
  • In response to a client request to communicate with a destination website, setting up a forwarding session.
  • The session employs a "forwarder" between the client and destination server to forward packets in both directions.
  • The session is implemented such that neither the client nor the destination server is aware of the forwarder's employment.
  • A "controller" communicates with the forwarder and a domain name server to resolve the destination's name.
  • A "deceiver" communicates with the controller and the client, receives the client's initial request, and initiates the controller to query the domain name server.
  • The controller initiates the forwarding session after receiving the answer from the domain name server.
• The complaint alleges infringement of "one or more claims," reserving the right to assert others Compl. ¶16

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 identifies challenges in deploying functional software applications to remote users, particularly on resource-constrained devices like early wireless personal digital assistants (WPDAs) (’351 Patent, col. 2:4-14). Conventional methods, such as browser-based HTML applications or fully compiled, locally installed programs, were seen as suffering from slow performance, limited functionality, or cumbersome installation and update processes '351 Patent, col. 2:25-40
• The Patented Solution: The patent describes a client-side "application assembler," also termed an "Application Virtual Machine" (AVM), that is installed on the user's device '351 Patent, col. 3:10-14 '351 Patent, col. 4:29-31 This assembler downloads one or more text files (e.g., XML files) from a server that contain embedded program logic '351 Patent, col. 3:14-19 The assembler then interprets these files and assembles the logic into a functioning, graphical application "on the fly" in the device's temporary memory, providing a rich user experience without requiring a large, pre-compiled application to be downloaded '351 Patent, abstract
• Technical Importance: This approach sought to merge the benefits of web-based deployment (ease of updates, no complex installation) with the performance and rich graphical user interface (GUI) of traditional client-server applications '351 Patent, col. 3:1-6

Key Claims at a Glance

• The complaint asserts independent method claim 14 Compl. ¶28
• Essential elements of claim 14 include:
  • Storing and running a software module on a client device.
  • Providing to the client device text files containing embedded program logic for the software module to assemble into a computer program.
  • The program provides a graphical user interface for receiving and interpreting user inputs.
  • Running the assembled program on the client device.
  • Enabling user interaction with the running program.
• The complaint alleges infringement of "one or more claims," reserving the right to assert others Compl. ¶27

III. The Accused Instrumentality

Product Identification

Defendant’s "website infrastructure" Compl. ¶¶17, 28

Functionality and Market Context

The complaint alleges that the accused infrastructure provides the technical functionality of the Vivian Health website to end-users Compl. ¶¶17, 28 For the ’959 Patent, this allegedly involves a method of anonymizing communications between a user (client) and a destination server through a forwarding architecture Compl. ¶17 For the ’351 Patent, the infrastructure is accused of providing text files with embedded program logic to a user's device, where they are assembled into a functioning application with a graphical user interface Compl. ¶28 The complaint does not provide further detail on the specific components of the accused infrastructure or its market positioning.

IV. Analysis of Infringement Allegations

No probative visual evidence provided in complaint.

’959 Patent Infringement Allegations

’351 Patent Infringement Allegations

Identified Points of Contention

• ’959 Patent: The complaint’s allegations map the patent’s specific "deceiver-controller-forwarder" architecture onto the Defendant’s "website infrastructure" Compl. ¶17 A central point of contention may be whether conventional web technologies—such as load balancers, reverse proxies, or content delivery networks (CDNs)—perform the specific functions of the claimed "deceiver" and "controller." The analysis may question what evidence supports the allegation that the client is actively "deceived" into communicating with a forwarder under the belief it is the destination server, as described in the patent '959 Patent, col. 4:43-46
• ’351 Patent: The infringement theory rests on the characterization of Defendant’s website as providing "text files containing embedded program logic" that a "software module" on the client device "assembles" into an application Compl. ¶28 This raises the question of whether a standard web browser processing modern JavaScript, HTML, and CSS constitutes the "software module" or "Application Virtual Machine" described in the patent '351 Patent, col. 4:29-31 The dispute may focus on whether the patent’s claims can be construed to cover the routine operation of a modern browser, or if they are limited to the specific type of downloadable, installable "assembler" program detailed in the specification '351 Patent, col. 3:10-14

V. Key Claim Terms for Construction

• Term: "deceiver" (from ’959 Patent, Claim 1)

  • Context and Importance: This term is not a standard industry term and appears to be a neologism specific to the patent. Its construction is critical because infringement depends on identifying a component in the accused infrastructure that performs the unique, initiating role of the claimed "deceiver."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification states the deceiver "provides name resolution for clients" and "works the same as a standard name server, except when a query is received from a client, the deceiver allows the controller to supply the information" '959 Patent, col. 2:39-43 This language could support an interpretation covering any component that intercepts a name resolution request and redirects it for processing by another system.
    • Evidence for a Narrower Interpretation: The patent’s figures and detailed description depict the deceiver as a distinct architectural component (104) that transparently receives a packet from the client and forwards the query to the controller '959 Patent, Fig. 1 '959 Patent, col. 3:45-54 This may support a narrower construction requiring a discrete element that performs this specific handoff.

• Term: "software module to assemble into" (from ’351 Patent, Claim 14)

  • Context and Importance: The definition of what constitutes a "software module" and what it means to "assemble" an application from text files will be central to the infringement analysis. Practitioners may focus on this term because the accused functionality appears to describe a standard web browser, and the outcome may depend on whether a browser falls within this definition.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The abstract states an "application assembler" downloads text files and "assembles the retrieved program logic into a functioning application" '351 Patent, abstract This functional language could be argued to broadly cover a web browser's JavaScript engine and rendering process, which takes text-based code and creates an interactive application.
    • Evidence for a Narrower Interpretation: The specification repeatedly refers to the "software module" as an "Application Virtual Machine (AVM)" that is downloaded and installed on the client device as a distinct program or plugin '351 Patent, col. 3:10-14 '351 Patent, col. 4:29-31 This suggests the term may be limited to a specific, non-native software component, rather than a pre-existing, general-purpose web browser.

VI. Other Allegations

• Indirect Infringement: The complaint alleges that to the extent any claim steps are performed by a third party (such as an end-user), Defendant is liable for infringement because it "conditioned the third party's use of the functionality" on performing the steps and "controlled the manner and/or timing of the functionality" Compl. ¶¶18, 29
• Willful Infringement: The complaint does not plead facts sufficient to support a claim for willful infringement, such as alleging that Defendant had pre-suit knowledge of the asserted patents.

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

The resolution of this dispute may turn on the court's interpretation of patent claims in the context of evolving web technologies. Two key questions emerge:

• A core issue for the ’959 Patent will be one of architectural correspondence: does the defendant's website infrastructure, which likely relies on conventional components such as proxies and CDNs, embody the specific, unconventional "deceiver-controller-forwarder" architecture required by the patent's claims, or do the allegations represent an attempt to map claim terms onto fundamentally different technology?
• For the ’351 Patent, a central question will be one of technological scope: can the term "software module...to assemble" an application, rooted in the context of a specialized, downloadable "virtual machine" from the early 2000s, be construed to read on the routine, client-side rendering of a modern dynamic webpage by a standard, pre-installed web browser?