Google Assistant Privacy Settlement 2026 -- File a Claim by August 27
By eosguide editorial · Last updated
Owned a Google Home, Nest, or Pixel, or got recorded by Google Assistant by accident? You may claim a share of the $68M settlement. File by August 27, 2026. The assistant that woke up when nobody said "OK Google" was apparently still listening, and now it owes you.
What happened
Class period: May 18, 2016 through March 19, 2026
- The lawsuit alleges that Google Assistant can activate and record communications even when a user does not intentionally trigger it with a Hot Word like "OK Google" or manually turn it on. Plaintiffs call these instances "False Accepts."
- Plaintiffs claim that Google wrongfully collected, used, and disclosed audio recordings from these False Accepts, including sharing them with third-party review vendors to improve Google Assistant's speech recognition, in violation of users' privacy and Google's own Privacy Policy.
- Google denies all the allegations and any wrongdoing, and the Court has made no determination that Google did anything wrong. Both sides agreed to settle to avoid the cost and risk of a trial. The case is In re Google Assistant Privacy Litigation in the Northern District of California.
Your home address, phone number, relatives, or other personal details may already appear on data broker and people-search sites.
This settlement may pay eligible claimants for what happened here — worth filing. But data brokers are a separate, ongoing problem — hundreds of companies collect and sell your personal information continuously, from public records, loyalty programs, and more. They don’t need a hack to get it. Incogni sends removal requests to 420+ data brokers on your behalf and continues checking for reappearing data.
Start a data broker cleanupAffiliate disclosure: eosguide may earn a commission if you subscribe through this link, at no extra cost to you.
What you can get
Privacy class payment
Pro rata cash
1 point per claimant whose recordings were affected Purchaser class payment
Key dates
| Action | Date | What it means |
|---|---|---|
| Claim deadline | August 27, 2026 | Last day to file a claim |
| Opt out | August 27, 2026 | Keep your right to sue separately |
| Object | August 27, 2026 | Tell the court you disagree |
| Final hearing | October 1, 2026 at 9:00 a.m. PT, U.S. District Court for the Northern District of California, San Jose Courthouse, 280 South 1st Street, Courtroom 1 (5th Floor), San Jose, CA 95113 | Judge decides whether to approve |
Who may qualify
- Purchaser class: you are a U.S. user who bought a Google-made device (Google Home, Home Mini, Home Max, Nest Hub, Nest Hub Max, or a Pixel phone) between May 18, 2016 and March 19, 2026
- Privacy class: you used Google Assistant, or were part of a user's household, between May 18, 2016 and March 19, 2026, and your communications were recorded through a False Accept or shared with a third-party review vendor
- You can belong to one or both classes, and parents or guardians may file for a minor under 18 as of August 27, 2026
How to file
- Go to the official settlement website and click "File a Claim"
- If you received an email with a Unique ID and PIN, enter those codes; if not, you can still file as a class member
- Complete and sign the Claim Form under penalty of perjury, listing any qualifying Google-made devices
- Submit online or mail your Claim Form postmarked by August 27, 2026
Filed this claim?
Save the claim ID, deadline, payout notes, and official link in the free Settlement Claim Tracker. It stores entries in your browser, with no account needed.
Add to Tracker →Want the next deadline before it sneaks past you?
Get weekly settlement alerts: new settlements, upcoming deadlines, and claim tips once a week.
No spam. Unsubscribe anytime.
Proof required
- No documentation is strictly required to file, but the Claim Form must be personally signed under penalty of perjury
- Use the Unique ID and PIN from your notice email if you received one
- The form may require supporting information specified in its instructions, and bulk or aggregator submissions are not allowed
- A parent or legal guardian must file on behalf of any class member under 18 as of August 27, 2026
Payment timing
Payments go to authorized claimants after the Court grants final approval at the October 1, 2026 hearing and any appeals are resolved, which can take time. If money remains after distribution, a second payment may go to claimants who cashed their first check, or to a court-approved nonprofit. No funds return to Google.
Important links
Contact
Extra details
- The payout uses a points system: purchaser class members get 4 points per Google-made device (up to 3 devices), while privacy class members get 1 point, and the net fund is split proportionally by total points
- The final per-person amount is unknown until all valid claims are counted, so it depends on how many people file
- Almost everything in this settlement shares one deadline of August 27, 2026: filing a claim, opting out, objecting, and giving notice to speak at the hearing
- If you opted out of the certified Purchaser Class back in 2024, you can rejoin simply by filing a timely Claim Form
- Class Counsel are Erin Green Comite of Scott+Scott and Christian Levis of Lowey Dannenberg
- File only through the official site, since high-profile privacy settlements attract copycat scam pages
FAQ
Who qualifies for the Google Assistant settlement?
What is a "False Accept"?
How much money can I get?
What is the deadline?
Do I need proof or a receipt?
When will I get paid?
Info only. Verify details on the official site. Not legal, financial, or tax advice. Legal
Related guides
Duke University Health pixel tracking settlement
Duke Health's website allegedly used a tracking pixel that shared patient web activity, including health-related informa…
Grubhub driver misclassification California settlement
Grubhub agreed to pay $24.75 million to settle claims that it misclassified California delivery drivers as independent c…
Sophin v. WISP Inc. Meta Pixel privacy settlement
WISP Inc. -- the company behind hellowisp.com -- allegedly used Meta's tracking pixel to share customers' personal data …
Share this: