DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Zywave seeks approval of $11 million data breach lawsuit settlement

Posted on March 8, 2022 by Dissent

It’s one thing to update a breach report with a notice of lawsuit settlement, but it’s another to realize you never covered the original breach at all.  Let’s remedy that now.

On February 27, 2021, Zywave and its subsidiary, Insurance Technologies Corp (ITC) suffered a data breach. From a press release by plaintiff’s counsel:

Cybercriminals allegedly made off with the names, Social Security numbers, driver’s license numbers, usernames, passwords, and other identifying information belonging to not only the companies’ clients, but their clients, mainly small insurance agencies, potential customers as well.  

The breach was first disclosed on May 10, 2021, two months after the firm allegedly completed its investigation. The delay in notification was one of the claims made by the plaintiffs. More than 4 million people were potentially impacted.

Now Zywave has agreed to pay $11 million to settle the claims that it and ITC  failed to protect the personal information of over four million customers. Counsel

also asked the court to establish three separate tiers of relief: a “tier one” fund paying $100-$300 to approximately 318,091 California subclass members; a “tier two” fund providing reimbursement of up to $5,000 in out-of-pocket expenses per class member, which includes $25 per hour for up to eight hours of attested lost time; and a “tier three” fund providing every settlement class member 12 months of Aura’s Financial Shield product, which offers a $1 million protection policy to every subscriber and focuses on protecting financial assets.

Only those California subclass members whose Social Security number and/or driver’s license information were accessed or potentially accessed during the breach, as confirmed by Insurance Technology’s business records, will be eligible to submit a tier one claim.

In order to qualify for a tier two reimbursement, class members will need to provide documentation supporting their claim, a brief description of the loss and information needed to verify the claim, including their name and mailing address, which will also be checked against Insurance Technology’s business records at the time of the breach.

Out-of-pocket losses will only be covered if the timing of the loss occurred on or after February 27, 2021, and the personal information used to commit the alleged identity theft or fraud was the same type of personal information provided to Insurance Technology before the breach.

The case is Heath et al. v. Insurance Technologies Corp. et al., Number 3:21-cv-01444-N, in the U.S. District Court for the Northern District of Texas.

Read more at Mason Lietz & Klinger.

 


Related:

  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Toys “R” Us Canada customers notified of breach of personal information
  • Kaufman County's data breach was their second one in three weeks
  • Hacking Formula 1: Accessing Max Verstappen's passport and PII through FIA bugs
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
Category: Breach IncidentsHack

Post navigation

← Herff Jones settles data breach law suit for $4.35 million
MN: District 518 is investigating whether data was compromised when an employee’s email account was hacked →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.