People who received Rent-A-Center marketing texts after replying “stop” may be covered by a proposed class action alleging Rent-A-Center ignored opt-out requests and sent solicitations without a Texas registration certificate. No class has been certified and there is nothing to file yet.
This article describes a class action complaint. The statements below are unproven allegations. Rent-A-Center has not been found liable, there is no certified class, and nothing to claim at this time. This page is informational. It is not legal advice.
Free settlement alerts
Join thousands of readers who get the latest class action settlements you may qualify for — delivered straight to your inbox.
The complaint in Alejandro v. Rent-A-Center, Inc. alleges that Rent-A-Center kept sending promotional text messages from short code 94210 after the plaintiff replied “stop” three times in August 2026, in violation of the Telephone Consumer Protection Act’s internal do-not-call rules. It also alleges Rent-A-Center sent telephone solicitations without a registration certificate from the Texas Secretary of State. These are unproven allegations.
The complaint proposes a National Internal Do Not Call Class of people in the U.S. who, within four years before the October 20, 2026 filing, received at least two promotional Rent-A-Center texts in a 12-month period on a personal number while Rent-A-Center allegedly lacked required do-not-call procedures, and a Texas Telephone Solicitation Registration Class. No court has certified either class.
The complaint seeks TCPA statutory damages of $500 per violation, or up to $1,500 per violation if the court finds the violations knowing or willful, plus an injunction. For the Texas claim it seeks costs and fees under the Texas Business and Commerce Code. No money has been awarded, and there is nothing to claim.
No. The text message case is a separate lawsuit against Rent-A-Center, Inc. over marketing texts. The data breach lawsuits name Upbound Group, Rent-A-Center’s parent company, and concern a July 2026 incident that Upbound disclosed in September 2026.