Data Resonance v. IPVanish: Patent Suit Dismissed With Prejudice in 70 Days
Data Resonance, LLC asserted US6934714B2 — covering methods for identifying and maintaining families of data records — against VPN provider IPVanish, Inc. in the Southern District of New York. The plaintiff voluntarily dismissed the action with prejudice just 70 days after filing, before the defendant had served an answer or summary judgment motion.
A VPN Provider Walks Away Clean Before Answering
On 3 March 2025, Data Resonance, LLC filed a patent infringement complaint against IPVanish, Inc. in the United States District Court for the Southern District of New York (Case No. 1:25-cv-01769), before Judge Mary Kay Vyskocil. The asserted patent, US6934714B2, covers a method and system for the identification and maintenance of families of data records — a data management technology whose relevance to a VPN service provider suggests the complaint may have targeted IPVanish’s backend data handling or subscriber record architecture.
On 12 May 2025, just 70 days after filing, Data Resonance filed a unilateral notice of voluntary dismissal with prejudice pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(i). Because IPVanish had not yet served an answer or a motion for summary judgment, no court order or stipulation was required. The dismissal with prejudice is a permanent relinquishment — Data Resonance is barred from reasserting the same claims against IPVanish based on the same patent conduct.
The speed of resolution — before any substantive briefing — and the with-prejudice designation together suggest that the parties likely reached a private resolution, though the public record is silent on any settlement terms or licensing arrangement. Alternatively, plaintiff counsel may have assessed the infringement position as untenable following pre-suit communications with IPVanish. The each-party-bears-own-costs arrangement is consistent with a negotiated exit rather than a capitulation, as defendants who force a dismissal through early motion practice typically seek fee awards.
Filing to Voluntary dismissal in 70 days
70 days — resolved before defendant answered; well under median SDNY patent case duration
Voluntary dismissal with prejudice: what it means for both parties
Rule 41(a)(1)(A)(i): plaintiff’s unilateral exit before answer
Federal Rule of Civil Procedure 41(a)(1)(A)(i) permits a plaintiff to dismiss an action without a court order by filing a notice of dismissal before the opposing party serves an answer or a motion for summary judgment. IPVanish had not done either, so Data Resonance could act unilaterally. The addition of ‘with prejudice’ goes beyond the rule’s default — a standard Rule 41(a)(1) dismissal is without prejudice — meaning Data Resonance affirmatively chose to close the door permanently.
Rule 41(a)(1)(A)(i) — no court order neededWith prejudice: Data Resonance forfeits its right to refile
A dismissal with prejudice operates as a final adjudication on the merits for claim-preclusion purposes. Data Resonance cannot refile this infringement action against IPVanish on US6934714B2 for the same alleged conduct. This is a meaningful concession by the plaintiff. The public record does not disclose any licensing fee, settlement payment, or other consideration received, though a private arrangement consistent with this outcome cannot be excluded.
Claim-preclusive — cannot refileIPVanish exits with no liability and no fee award
IPVanish achieved dismissal before incurring the cost of drafting an answer, conducting claim construction, or engaging in discovery. The each-party-bears-own-costs term means IPVanish did not recover its legal fees, which typically signals the defendant was willing to accept the exit without pressing for sanctions or an exceptional-case motion under 35 U.S.C. § 285. IPVanish faces no injunction, no damages award, and no admission of infringement.
No liability — own costs onlyUS6934714B2 remains enforceable — but against others only
The patent itself is not invalidated or challenged by this outcome. Data Resonance retains the right to assert US6934714B2 against other defendants in future proceedings. For VPN providers, data infrastructure operators, and SaaS platforms with comparable data-record management architectures, the patent remains a live enforcement risk. The rapid dismissal without any IPR or invalidity challenge filed suggests the patent was not stress-tested on validity grounds in this proceeding.
Patent survives — enforcement risk persistsFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Data Resonance, LLC | Company | Data management patent assertion entity — holder of US6934714B2Search in Eureka ↗ |
| Defendant | IPVanish, Inc. | Company | IPVanish, Inc. — US-based VPN and online privacy services providerSearch in Eureka ↗ |
| Plaintiff counsel | Isaac Rabicoff | Attorney | Counsel for Data Resonance, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Rabicoff Law LLC | Law Firm | Representing Data Resonance, LLCSearch in Eureka ↗ |
| Defendant counsel | Etai Yaacov Lahav | Attorney | Counsel for IPVanish, Inc.Search in Eureka ↗ |
| Defendant law firm | Radulescu LLP | Law Firm | Representing IPVanish, Inc.Search in Eureka ↗ |
| Presiding judge | Judge Mary Kay Vyskocil | Judge | New York Southern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The dismissal notice invokes Rule 41(a)(1)(A)(i) precisely, confirming the procedural posture: no answer had been served, making court involvement unnecessary. The explicit election of ‘with prejudice’ — beyond the rule’s without-prejudice default — is the operative commercial fact. It permanently bars Data Resonance from reasserting these infringement claims against IPVanish, while leaving the patent valid and enforceable against the broader market. The each-party-bears-own-costs term forecloses any subsequent fee motion.
US6934714B2 — Method and System for Identification and Maintenance of Families of Data Records
US6934714B2, filed under application number US10/091378, protects a method and system for identifying and maintaining families of data records — a foundational data management technology covering how related records are grouped, tracked, and maintained within a system. The patent’s technical domain sits at the intersection of database architecture and data lifecycle management, areas that underpin subscription management, user session tracking, and backend record organisation for digital service providers including VPN platforms.
The strategic value of this patent lies in its potential breadth across any system that organises user or operational data into related record families — a description that could encompass VPN subscriber management systems, cloud data stores, and enterprise identity platforms. Because the patent was not subjected to validity scrutiny in this proceeding, its claim scope remains untested in litigation. For competitors in data infrastructure, VPN services, or SaaS, this patent represents an unresolved enforcement vector that warrants proactive FTO analysis before product roadmap decisions.
Should your data infrastructure team run an FTO against US6934714B2?
Any organisation operating systems that identify, group, or maintain relational families of data records should assess exposure to US6934714B2. This includes VPN providers managing subscriber records, SaaS platforms with multi-tenant data architectures, cloud database vendors, and enterprise identity management systems. The patent survived this litigation without any validity challenge — meaning its claims are uncontested and its enforcement risk is real. An FTO review is especially urgent for teams building or scaling backend data management pipelines.
PatSnap Eureka’s FTO Search Agent allows R&D and legal teams to map product features against US6934714B2’s claim language, identify prior art that could support an IPR petition, and benchmark the patent against the broader data record management landscape. Eureka can surface related continuations, family members, and co-owned patents that may extend the assertion risk beyond this single asset — giving your team the intelligence needed to design around, challenge, or license proactively.
Run a freedom-to-operate analysis on US6934714B2 to assess your product’s exposure
Run FTO in Eureka →Similar Patent Cases: Data Record Management Assertions in Federal District Courts
Explore related patent infringement actions asserting data management and record systems patents in US district courts, including SDNY, with comparable rapid-dismissal outcomes.
Related patent case — similar technology
Comparable case in the same technology domain. Patent holder and defendant reached resolution after proceedings.
SettledRelated infringement action — same court
Comparable Method and system for identification and maintenance of families of data records-adjacent infringement action. Patent enforcement dynamics analysed in depth.
Active · District CourtRelated invalidity challenge — appellate outcome
Combined invalidity and infringement action in the same technology space. Decided after substantive proceedings.
DecidedData Resonance, LLC’s broader IP enforcement history
Data Resonance, LLC’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat this case signals for the data management IP landscape
A 70-day lifecycle and with-prejudice exit before any answer raises questions about enforcement strategy, patent scope, and VPN sector exposure.
Pre-answer dismissals with prejudice typically reflect private resolution
When a plaintiff voluntarily exits with prejudice before the defendant even answers, it strongly suggests either a confidential settlement or a reassessment of claim strength. Neither outcome is visible in the public record. IP teams monitoring similar assertion campaigns should treat this pattern as a signal of potential licensing activity, not necessarily a failed case.
US6934714B2 was not validity-tested — it remains a live enforcement asset
No IPR petition, invalidity counterclaim, or § 101 challenge was filed before dismissal. The patent emerged from this litigation entirely unscathed. Companies operating data record management systems — including VPN providers, cloud infrastructure operators, and enterprise SaaS platforms — should treat this patent as an active infringement risk requiring FTO review.
Data Resonance’s assertion pattern warrants portfolio-level monitoring
A single rapid-exit assertion in SDNY may indicate a broader licensing campaign. Tracking Data Resonance’s filing history, co-asserted patents, and target defendant profiles can reveal whether this is an isolated action or part of a systematic monetisation strategy targeting the data infrastructure and VPN sector.
IPVanish’s own-costs exit may reflect a negotiated licence, not a defence win
Defendants who successfully defeat meritless claims typically pursue § 285 exceptional-case fee awards. IPVanish did not. The mutual own-costs agreement is more consistent with a negotiated resolution — possibly including a royalty-bearing or paid-up licence — than a clean vindication. Competitors in the VPN space should assess whether a licensing programme is now underway.
Data v IPVanish — key questions answered
It means Data Resonance permanently gave up its right to sue IPVanish again on US6934714B2 for the same alleged conduct. Filed under Rule 41(a)(1)(A)(i), the dismissal required no court order because IPVanish had not yet answered. The with-prejudice designation — beyond the rule’s default — operates as a final adjudication on the merits for claim-preclusion purposes.
No. The case was dismissed before any substantive proceedings — no answer, no claim construction, no invalidity challenge, and no IPR petition was filed. The patent remains in force and is fully enforceable against other defendants. This litigation did not test or adjudicate the validity or infringement scope of US6934714B2.
US6934714B2 covers a method and system for the identification and maintenance of families of data records. It relates to how related data records are grouped and managed within a system — a technology with potential application across database platforms, VPN subscriber management systems, SaaS data architectures, and enterprise identity management environments.
The public record does not explain the plaintiff’s motivation. However, a with-prejudice dismissal is consistent with either a confidential settlement — where the plaintiff receives consideration in exchange for a permanent release — or a deliberate strategic withdrawal. Dismissing without prejudice would have preserved the option to refile, making the with-prejudice choice commercially significant and suggesting a likely negotiated resolution.
Not definitively. While IPVanish faces no liability, the own-costs arrangement is equally consistent with a negotiated exit as with a defence victory. Defendants who successfully defeat meritless patent claims typically pursue fee awards under 35 U.S.C. § 285. The absence of any fee motion by IPVanish suggests the parties reached a mutually acceptable resolution rather than IPVanish prevailing on the merits.
Monitor data management patent enforcement before it hits your inbox
US6934714B2 survived this litigation unchallenged. PatSnap Eureka helps you track enforcement activity, run FTO searches against data record management patents, and identify exposure before litigation is filed against your organisation.
PatSnap Eureka searches patents and litigation data to answer instantly.