1:23-cv-00042
Web 20 Tech LLC v. TaskWorld Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Web 2.0 Technologies, LLC (Texas)
- Defendant: TaskWorld Inc. (Delaware)
- Plaintiff’s Counsel: Devlin Law Firm LLC
- Case Identification: 1:23-cv-00042, D. Del., 01/13/2023
- Venue Allegations: Venue is alleged to be proper in the District of Delaware on the basis that Defendant is a Delaware corporation.
- Core Dispute: Plaintiff alleges that Defendant’s TaskWorld online collaboration platform infringes patents related to the secure, permission-based management and collaborative editing of online information and documents.
- Technical Context: The technology resides in the field of cloud-based project management and software-as-a-service (SaaS) collaboration tools, a market focused on enabling remote teams to share and manage work.
- Key Procedural History: The complaint alleges that Defendant has had actual knowledge of the patents-in-suit and its alleged infringement since at least June 15, 2021, the date it allegedly received a notice letter from Plaintiff.
Case Timeline
| Date | Event |
|---|---|
| 2000-01-07 | Priority Date for '448 and '644 Patents |
| 2005-01-18 | U.S. Patent No. 6,845,448 Issues |
| 2012-02-14 | U.S. Patent No. 8,117,644 Issues |
| 2021-06-15 | Alleged Date Defendant Received Notice of Infringement |
| 2023-01-13 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 6,845,448, "Online Repository for Personal Information," issued January 18, 2005
The Invention Explained
- Problem Addressed: The patent describes the inefficiency and annoyance faced by internet users who must repeatedly fill out lengthy online forms with personal and demographic information for various websites and services ('448 Patent, col. 1:16-33). It notes the lack of a central method for a user to store this information once and selectively authorize its distribution ('448 Patent, col. 1:44-51).
- The Patented Solution: The invention proposes a server-based system where a user establishes an account to store various "information objects" (e.g., contact information, preferences, demographics) in a database. The user can then assign different "security levels" to each piece of information, granting granular control over which authorized requesters can access specific data ('448 Patent, Abstract; col. 2:21-41). When an authorized party requests information, the system verifies the request against the stored permissions and transmits only the approved data ('448 Patent, col. 2:37-41).
- Technical Importance: The technology conceptualized a centralized, user-permissioned data repository, a foundational concept for modern digital identity management and single sign-on systems that allow users to control the flow of their personal data online.
Key Claims at a Glance
- The complaint asserts independent claim 1.
- The essential elements of claim 1, as corrected by a 2013 Certificate of Correction, include a method performed by a server computer comprising the steps of:
- Establishing an account for a first party and assigning an identifier.
- Entering the first party's personal information, comprising one or more "information objects."
- Receiving from the first party an assignment of security levels to each information object at any granularity.
- Storing the identifier, information object, and its assigned security level in a database.
- Receiving a request from a second party that includes the first party's identifier.
- Selecting and retrieving a portion of the personal information objects for transmission to the second party based on the stored permissions.
- Securely transmitting the retrieved information to the second party.
- Obtaining a second party identifier and, if the second party is not authorized, recording the identifier and rejecting the request.
- The complaint reserves the right to assert other claims (Compl. ¶30).
U.S. Patent No. 8,117,644, "Method and System for Online Document Collaboration," issued February 14, 2012
The Invention Explained
- Problem Addressed: The patent identifies a need for an improved system for online document collaboration, particularly for sharing information in a controlled manner with a widespread audience while respecting restrictions, such as copyrights ('644 Patent, col. 2:1-9).
- The Patented Solution: The invention describes a server-based method where a first user can store a document and associate specific access restrictions with it for a group of other users ('644 Patent, Abstract). A second, identified user can then request to modify the document. The system verifies the second user's identity and, based on their access rights, permits the modification. Crucially, the system then receives "approval or disapproval" for the changes from other users and stores identifying information about who approved or disapproved ('644 Patent, Abstract; col. 26:12-18).
- Technical Importance: The patent addresses core functionalities of modern collaborative workflow tools, such as permission-based editing, version control, and auditable approval cycles, which are essential for enterprise project management.
Key Claims at a Glance
- The complaint asserts independent claim 1.
- The essential elements of claim 1 include a method performed by a server computer comprising the steps of:
- Establishing accounts for a plurality of users.
- Storing a document created by a first user.
- Associating a set of access restrictions with the document, defining a group of users who can access it for modification.
- Receiving a request to modify the document from a second user, which includes the second user's identification.
- Verifying the identity of the second user.
- Permitting the second user to modify the document based on granted access rights.
- Receiving approval or disapproval for the modifications from one or more users.
- Storing identifying information of the users who approved or disapproved the modifications.
- The complaint reserves the right to assert other claims (Compl. ¶42).
III. The Accused Instrumentality
Product Identification
The accused instrumentalities are the TaskWorld online collaboration platform and its associated products, including those for Project Management, Business Operations, and Product Management (Compl. ¶20, ¶33).
Functionality and Market Context
The complaint describes TaskWorld as a service that allows users to create projects, invite other users as "Members" or "Guests," and assign tasks (Compl. ¶21, ¶34). A key alleged function is the ability for project owners to control access by setting a project to "public or private" and assigning permissions such as "Full Access/Limited Access/Restricted Access" to different users (Compl. ¶22, ¶35). The complaint also highlights features for requesting, approving, and tracking changes to project work, citing a help article on how to "Approve, Request changes, or Leave Comments" (Compl. ¶36-37). A screenshot from a TaskWorld help article shows a user interface for assigning specific individuals, such as "Eleanor Pena" and "Ronald Richards," to a task (Compl. p. 6). The platform is presented as a commercial product offered for sale throughout the United States (Compl. ¶10, ¶20).
IV. Analysis of Infringement Allegations
'448 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| entering the first party's personal information, said first party's personal information comprising at least one of a plurality of information objects | Users enter personal information, such as their first and last names, which is then shared with other authorized users within a project or task. | ¶21 | col. 2:30-33 |
| receiving, from the first party, assignment of at least one of a plurality of security levels to each information object at any granularity | Project owners can set different permission levels for users, such as "Full Access/Limited Access/Restricted Access," and can set projects to be "public or private." | ¶22, ¶24 | col. 2:33-37 |
| securely transmitting the retrieved first portion of personal information objects to the second party | The system transmits a user's personal information from a server operated by TaskWorld to a second authorized party upon request. | ¶21 | col. 2:39-41 |
| if the second party is not authorized to receive the information... rejecting the second party's request for such information | If a requesting user does not have the appropriate permission level to view certain information, their request for that information is rejected. | ¶24 | col. 14:62-64 |
'644 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| storing, on the server computer, a document created by a first user | The platform allows a user to create documents that are stored on a server. | ¶35 | col. 25:57-58 |
| associating a set of access restrictions with the document... including an ability to access the document for modification by one of a first group of users | A user can restrict access for other users to only view, comment, edit, or have no access to a project. A screenshot shows "Permission Settings" options for "Full Access/Limited Access/Restricted Access" (Compl. p. 15). | ¶35 | col. 25:59-62 |
| receiving, from a second user, a request to modify the document | A second user with suitable permissions can request access to modify a TaskWorld document. | ¶35 | col. 26:3-6 |
| receiving approval or disapproval for the modifications from one or more users | The platform provides options to "Approve" or "Request changes" for a task. A help article screenshot explains this functionality (Compl. p. 16). | ¶36-37 | col. 26:12-14 |
| storing identifying information of the one or more users who approved or disapproved the modifications to the document | The system stores information on who approved changes, which is made accessible via an "Approval Request" filter. A screenshot shows this filter in the user interface (Compl. p. 18). | ¶37 | col. 26:15-18 |
Identified Points of Contention
- Scope Questions: A potential dispute for the '448 Patent concerns the definition of "personal information." The complaint primarily identifies user names (Compl. ¶21), while the patent specification provides much broader examples, including financial and medical data ('448 Patent, col. 7:4-16). This raises the question of whether the accused functionality meets the qualitative scope of the claimed term. For the '644 Patent, a similar question arises over the term "document." The infringement allegations center on collaboration within "projects" and "tasks," and it may be disputed whether these dynamic platform entities constitute a "document" as contemplated by the patent.
- Technical Questions: For the '448 Patent, a key technical question is whether TaskWorld's project-level "public/private" or user-level "Full/Limited Access" settings (Compl. ¶22, ¶24) constitute the "assigning... security levels to each information object at any granularity" as required by the claim. The analysis may depend on whether these permissions can be applied to individual data elements within a project, not just the project as a whole.
V. Key Claim Terms for Construction
For the '448 Patent
- The Term: "personal information"
- Context and Importance: The infringement case for the '448 Patent hinges on whether the user data managed by TaskWorld qualifies as "personal information." The complaint focuses on user names (Compl. ¶21). Practitioners may focus on this term because its construction will determine whether the accused system handles the type of data the patent claims to protect.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim language itself is not explicitly limited. The Background section refers to forms with "demographic and other information" and mentions a "user name" ('448 Patent, col. 1:17-21), suggesting the term can encompass basic identifying data.
- Evidence for a Narrower Interpretation: The specification provides extensive examples of more sensitive information, such as property ownership, health records, biometric data, and credit information ('448 Patent, col. 7:4-21). A party could argue these detailed examples define the intended scope as something more substantial than just a user's name in a collaborative workspace.
For the '644 Patent
- The Term: "document"
- Context and Importance: The '644 Patent's claims are directed to "online document collaboration." The accused features, however, relate to "projects" and "tasks" in a management platform (Compl. ¶35-37). The case will likely turn on whether a "task" in TaskWorld, which can contain descriptions, comments, and file attachments, is legally equivalent to a "document."
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification provides a very broad definition, stating that a "digital item" (used interchangeably with "document") can be "a web page, data, a document such as a news article, word processor document, spread sheet... a graphical image... or a similar thing" ('644 Patent, col. 12:22-29). This expansive language may support construing a "task" or "project" as a "document."
- Evidence for a Narrower Interpretation: The patent is titled "Method and System for Online Document Collaboration" and the abstract refers to "a document created by a first user." A party could argue that, in context, the term implies a more traditional, self-contained file (e.g., a text file, spreadsheet) rather than a composite, dynamic entity like a project management task.
VI. Other Allegations
Indirect Infringement
While the complaint primarily alleges direct and "jointly" infringing activity with users (Compl. ¶20, ¶33), it provides a basis for a potential inducement theory. The complaint repeatedly cites Defendant's help articles and instructions that allegedly guide users on how to perform the claimed methods, such as inviting users, setting permissions, and approving changes (Compl. ¶21-24, ¶34-37). These allegations may be used to argue that Defendant provides instructions with the intent to cause its users to infringe.
Willful Infringement
The complaint explicitly alleges that Defendant’s infringement has been willful, knowing, and deliberate. This allegation is based on alleged pre-suit knowledge of the patents, stemming from a notice letter Plaintiff claims to have sent on June 15, 2021, and Defendant's alleged continuation of the infringing activities after receiving that notice (Compl. ¶29, ¶41).
VII. Analyst’s Conclusion: Key Questions for the Case
- A core issue will be one of definitional scope: Can the term "personal information" in the '448 Patent, which the specification illustrates with extensive financial and medical data, be construed to cover the user names and roles within the accused project management system? Similarly, for the '644 Patent, can the term "document" be construed to cover a dynamic "task" or "project" entity in a modern SaaS platform, or is it limited to more traditional, static files?
- A key evidentiary question will be one of functional implementation: Does the evidence show that TaskWorld's permission system operates with the granularity required by the '448 Patent, allowing security levels to be assigned to individual "information objects," or are permissions only applied at a higher project or user level? The outcome may depend on technical evidence of how the accused system applies and enforces access controls.
- Finally, a central question for damages will be willfulness: Did the Defendant receive notice of its alleged infringement on June 15, 2021, as the complaint alleges? If proven, this could expose the Defendant to a finding of willful infringement and the potential for enhanced damages for any post-notice conduct.