About 190,000 people who requested car insurance quotes through Lemonade’s online platform can collect a flat payment of roughly $55 each, with no requirement to prove they suffered harm. The catch: the filing window closes on September 8, and anyone who misses it walks away with nothing. The settlement, filed in the Southern District of New York under case number 1:25-cv-04106-JHR-KHP, resolves claims that a technical flaw in Lemonade’s quote system sent personal data to a third party without standard protections.
Why the $55 flat payment and September 8 deadline matter right now
Lemonade disclosed the incident in a regulatory filing with the SEC on April 9, 2025. The company stated that a technical issue in its car insurance quote flow likely exposed certain data received via an API call to a third-party data provider, and that this information was transmitted without what the company described as its standard means of protection.
The no-proof, flat-payment design lowers the barrier to filing but also creates a predictable pattern: most eligible people will never bother. Data-breach settlements with similar structures routinely draw claim rates well under 15 percent of the eligible class. If that pattern holds here, a large share of the settlement fund would go unclaimed, effectively reducing the cost to Lemonade while leaving tens of thousands of affected individuals uncompensated. The settlement administrator’s post-deadline public report will show whether this class follows the same trend or breaks from it.
For anyone who received a notification from Lemonade about the exposure, the practical question is simple: file through the official settlement website before September 8 or forfeit the payment entirely. No receipts, no documentation of losses, and no proof of identity theft are required. The claim form itself is the only step. Class members who do not submit a claim will not receive money but will still be bound by the settlement’s release of claims, meaning they generally cannot sue separately over the same incident.
SEC filing and court notice trace the exposure to Lemonade’s quote platform
Two primary documents anchor the factual record. Lemonade’s SEC disclosure describes the root cause as a technical issue, not a hack or external intrusion. According to the company, the flaw caused data to move to a third-party provider without encryption or other safeguards that would normally apply. The filing does not specify which data fields were exposed or identify the third-party recipient, leaving unanswered questions about the exact scope of the information that left Lemonade’s systems.
A court-authorized notice disseminated through PR Newswire fills in the litigation details. It identifies the class as approximately 190,000 individuals whose personal information may have been compromised through the insurance quotation platform and confirms that the case is pending in the Southern District of New York. The notice directs people who received a notification to an official settlement website where they can submit claims, opt out, or object.
Neither the SEC filing nor the public notice discloses the total dollar value of the settlement fund or explains how the roughly $55 per-person figure was calculated. That lack of detail makes it difficult for outsiders to assess whether the amount reflects a guaranteed minimum payout, a pro-rata distribution that could rise or fall depending on participation, or a hard cap that might trigger reductions if claim rates unexpectedly surge. Until the court grants final approval and the administrator reports on claims, the structure behind the headline number will remain largely opaque.
What affected consumers can do before the deadline
For individuals who received a notice, the options are straightforward but time-sensitive. Filing a claim preserves the right to the estimated $55 payment, subject to final court approval and any adjustments required by the settlement formula. Opting out, by contrast, removes a person from the class, which means they will not receive money from this settlement but could pursue their own lawsuit if they choose. Objecting allows a class member to tell the court why they think the settlement is unfair, while remaining eligible for payment if it is ultimately approved.
People who are unsure whether they are included should look closely at the instructions in their notice and on the official settlement site referenced there. The class is limited to those whose information was processed through Lemonade’s car insurance quotation platform during the period identified in the litigation, so not every Lemonade customer will qualify. As with other class actions distributed through newswire channels, the public notice is meant to supplement, not replace, direct outreach to those the parties believe were affected.
Regardless of whether they file a claim, individuals who were notified may want to take basic privacy precautions, such as monitoring financial accounts, updating passwords, and reviewing any security alerts from their banks or credit card issuers. While the settlement compensates people for the alleged exposure, it does not by itself prevent downstream misuse of data if any occurred. The legal resolution and the practical steps consumers take to protect themselves operate on parallel tracks.
Ultimately, the Lemonade settlement illustrates how modern data-exposure cases often end: with a modest, uniform payout, limited transparency into the underlying calculations, and a narrow window for people to act. For those in the class, the choice is less about endorsing that system and more about whether to leave money on the table. With the September 8 deadline approaching, the only way to keep that option open is to submit a claim before the clock runs out.



