Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
Data Resonance v. IPVanish — Data Record Management Patent Suit | PatSnap
Explore in Eureka
Case ID1:25-cv-01769
FiledMar 2025
ClosedMay 2025
Patent Litigation

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.

Resolution time
70days
70 days — resolved before defendant answered; well under median SDNY patent case duration
Patents asserted
1
US6934714B2 — method and system for identification and maintenance of families of data records
Outcome
Voluntary dismissal
Voluntary Rule 41(a)(1)(A)(i) dismissal with prejudice; plaintiff cannot refile same claims
Cost ruling
Own Costs
Each party bears its own costs, expenses, and attorneys’ fees — no fee-shifting order
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

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.

Case at a glance
Case no.1:25-cv-01769
CourtNew York Southern
JudgeMary Kay Vyskocil
FiledMarch 3, 2025
ClosedMay 12, 2025
Duration70 days
OutcomeVoluntary dismissal
Verdict causeInfringement Action
BasisVoluntary dismissal
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / New York Southern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Voluntary dismissal in 70 days

70 days — resolved before defendant answered; well under median SDNY patent case duration

Case timeline: Complaint filed MAR 3 2025, APR–MAY — 70 days total Horizontal timeline showing the three key events in Data Resonance, LLC v IPVanish, Inc. from filing to resolution. Source: PACER, New York Southern District Court. MAR 3 2025 Complaint filed Pre-trial proceedings MAY 12 2025 Voluntary dismissal 70 DAYS TOTAL
Dismissal terms

Voluntary dismissal with prejudice: what it means for both parties

Legal mechanism

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 needed
Plaintiff outcome

With 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 refile
Defendant outcome

IPVanish 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 only
Commercial implications

US6934714B2 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 persists
Legal analysis based on PACER docket records for case 1:25-cv-01769 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffData Resonance, LLCCompanyData management patent assertion entity — holder of US6934714B2Search in Eureka ↗
DefendantIPVanish, Inc.CompanyIPVanish, Inc. — US-based VPN and online privacy services providerSearch in Eureka ↗
Plaintiff counselIsaac RabicoffAttorneyCounsel for Data Resonance, LLCSearch in Eureka ↗
Plaintiff law firmRabicoff Law LLCLaw FirmRepresenting Data Resonance, LLCSearch in Eureka ↗
Defendant counselEtai Yaacov LahavAttorneyCounsel for IPVanish, Inc.Search in Eureka ↗
Defendant law firmRadulescu LLPLaw FirmRepresenting IPVanish, Inc.Search in Eureka ↗
Presiding judgeJudge Mary Kay VyskocilJudgeNew York Southern District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(i), Plaintiff hereby voluntarily dismisses this action with prejudice. Because Defendant has not served “either an answer or a motion for summary judgment,” no stipulation or Court Order is required. Fed. R. Civ. Proc. 41(a)(1)(A)(i). Each party shall bear its own costs, expenses, and attorneys’ fees.”
Source: PACER Docket, Case 1:25-cv-01769, New York Southern District Court

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.

PACER case 1:25-cv-01769 · Public docket record Explore in Eureka ↗
Patent at issue

US6934714B2 — Method and System for Identification and Maintenance of Families of Data Records

Publication No.US6934714B2
Application No.US10/091378
Patent details
ProductMethod and system for identification and maintenance of families of data records
Cited in actionMarch 3, 2025

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.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

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.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US6934714B2 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

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.

🔍
Access 40+ similar cases in PatSnap Eureka
Data Resonance, LLC patent enforcement history, New York Southern case history, Data Resonance, LLC’s full IP portfolio, and comparable case analysis
Comparable SDNY patent exitsData management NPE casesVPN sector infringement suitsRule 41 with-prejudice patterns
Unlock similar cases in Eureka →
Strategic implications

What 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.

🔒
Full strategic analysis in PatSnap Eureka
Unlock full enforcement pattern analysis for data record management patent assertions in district court proceedings, including SDNY filing trends.
Assertion campaign analysisVPN sector patent risk mapUS6934714B2 claim scope review
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Data v IPVanish — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

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.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.