Bosley Data Breach 2022: More Details! ($500k Class Action Settlement)

There was a Bosley data breach as the database was hacked on August 17, 2020 and more than 100,000 people were affected.

What is The Bosley Data Breachal

The Bosley database was hacked on August 17, 2020 and more than 100,000 people were affected. Bosley says it sent notices to 100,839 individuals between January and February of 2021 indicating their critical personal information may have been taken as a result of malware infecting its computers.

The information that was potentially accessed includes names, addresses, DOB, Social Security numbers, driver’s license numbers, financial account and credit card numbers, medical and health insurance information.

Information that was exposed in the Data Breach

The breach of data led to the release of multiple documents that have been linked to personal information such as names and address, residence address social security number, and various other documents that were submitted.

What is the Lawsuit All about

The Bosley Data Breach was a direct result of Bosley’s failure to implement adequate cybersecurity measures. If you received a data breach notification, it is essential you understand what is at risk. T

How to know if you are in the settlement class

Recently, Bosley has agreed to pay $500,000 in order to resolve claims that it mismanaged cyber security, resulting in a data breach in 2020.

The settlement benefits a nationwide Class of individuals who were notified in 2021 of the Bosley data breach and whose information was compromised in the breach. The settlement also covers a California Subclass of Class Members who lived in the Golden State at the time of the data breach

Conclusion

Under the terms of the settlement, Class Members can collect a cash payment for ordinary and extraordinary expenses related to the data breach. The settlement also provides an additional statutory damages award of $50 to members of the California subclass.

click Here to read about other settlement cases.

Leave a Comment

error: Content is protected !!