ParkMobile might owe you money. Here’s how data-breach victims can submit a claim for cash

Finally, some good news for consumers who have been the target of a data breach.

ParkMobile, a parking payment app, has agreed to a $32.8 million settlement after a massive data breach in 2021 leaked personal information on 21 million users.

Launched in 2009 in the United States, ParkMobile allows customers to quickly pay for parking via its app instead of having to use a meter. So if you’ve used the mobile parking app and your information was compromised, you may qualify for a piece of the settlement.

A 2021 class-action lawsuit filed in Georgia accused ParkMobile of failing to protect customers after “an unknown actor’s unauthorized access to the Personal Information of ParkMobile App users,” according to The Hill.

The lawsuit also alleges that ParkMobile exposed users to fraud, identity theft, and cost time, all of which caused long-term damage. That data includes license plate addresses, phone numbers, email addresses, and “hashed passwords.”

In agreeing to the settlement, ParkMobile did not admit wrongdoing.

Who is eligible for the settlement?

According to ParkMobile’s settlement website, everyone who received a notification of the 2021 data security incident from ParkMobile is eligible for payment, also known as the “settlement class.”

Of the $32.8 million settlement, $9 million is allocated for settlement class members who claim payments, and another $21 million will go to class members with in-app credits, if they do not claim a cash payment.

How can I receive a cash payment?

To apply for a cash payment, settlement class members must download, complete, and submit a claim using this form by March 5, or request one by mail by calling 1-866-944-4062 or emailing [email protected].

You will need the notice ID and confirmation code that ParkMobile sent to you via mail or email , which you can look up here.

If you are eligible for payment and do nothing, you will still receive a $1 credit in the ParkMobile app.

No comments

Read more