Storebound, LLC v. Sensio

1:22-cv-05967 S.D.N.Y. Closed

Infringement action filed 13 Jul 2022 in the United States District Court for the Southern District of New York, asserting 2 design patents titled “Egg cooker” (USD884411S and USD906035S). The case closed 17 Nov 2022.

View the 2 asserted patents in Patsnap Eureka Claims, drawings and current legal status

Case summary

Plaintiff
Storebound, LLC
Defendant
Sensio
Patents asserted
USD884411S“Egg cooker” · design patentUSD906035S“Egg cooker” · design patent
Products listed
Egg cooker
Court
S.D.N.Y.
Verdict cause
Infringement action
Filed
13 Jul 2022
Closed
17 Nov 2022 (127 days)
Recorded category
Voluntary dismissal
Judge
Vernon S. Broderick
Case no.
1:22-cv-05967
Counsel of record · 4 attorneys, 2 firms
  • Gavin Purcell Lentz, plaintiff counsel
  • Matthew Louis Minsky, plaintiff counsel
  • Alicia Carroll, defendant counsel
  • Scott David Wofsy, defendant counsel
  • Plaintiff firm: Bochetto & Lentz PC
  • Defendant firm: Locke Lord LLP
Source: Patsnap Litigation Data. Party, attorney and judge names are shown with standard capitalization; products and categories appear as recorded in the docket. Patent titles from Patsnap patent data.
Closing order

How the case ended

The undersigned parties hereby voluntarily dismiss all claims and counterclaims asserted in this action pursuant TO F.R.C.P. 41(a)(1)(A)(ii) with prejudice. SO STIPULATED AND AGREED.

Case 1:22-cv-05967 · S.D.N.Y. · closed 17 November 2022 · Reproduced verbatim from the case record
The patents behind this order. Read the full claims of USD884411S and USD906035S. Open in Patsnap Eureka
Design patent in this case

Check your product’s appearance against design patents

Design FTO Search in Patsnap Eureka finds design patents relevant to how your product looks, so you can review them before launch.

Run a Design FTO Search
Monthly newsletter

Need a monthly report on closed US patent cases?

Every case that closed last month, with the court, the outcome and the patents involved.

Docket fields sourced from PACER via Patsnap Litigation Data. Patent bibliographic data from Patsnap.

General information only. This page reproduces publicly available court docket data for case 1:22-cv-05967 and is provided for general information and reference only. It is not legal advice and must not be relied upon as such. It does not create an attorney-client relationship.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.