Google to Pay $68 Million to Settle Android ‘Eavesdropping’ Claims

[Brownie2019]

Content source

https://www.bitdefender.com/en-us/blog/hotforsecurity/google-68-million-android-eavesdropping-case

Google has agreed to pay $68 million to settle a major class-action lawsuit alleging its voice-activated Assistant unlawfully recorded private conversations on Android-powered devices.
‘False accepts’
Filed in federal court in San Jose, California, the proposed settlement — which still requires the judge's approval — would provide compensation to affected users who owned devices with the Google Assistant enabled as far back as May 2016.
At the centre of the litigation are so-called “false accepts” — instances where Google Assistant allegedly activated and began recording ambient speech without the user giving a recognised wake phrase like “Hey Google” or “OK Google.”
The plaintiffs claim these recordings sometimes captured private, sensitive conversations that were then processed in a way that violated expectations of privacy.

Full Story:

Google to Pay $68 Million to Settle ‘Eavesdropping’ Claims

Google will pay $68 million to settle class-action lawsuit alleging Google Assistant recorded private conversations on Android devices.

www.bitdefender.com

 

[Bot]

Full Story:

Google to Pay $68 Million to Settle ‘Eavesdropping’ Claims

Google will pay $68 million to settle class-action lawsuit alleging Google Assistant recorded private conversations on Android devices.

www.bitdefender.com

This report is about a proposed class-action settlement alleging “false accepts,” where Google Assistant may have activated and recorded without an intentional wake phrase.

Even if you don’t know whether you were affected, you can reduce exposure going forward by limiting wake-word activation, microphone access, and stored voice activity.

What “false accepts” means (in practical terms)
All wake-word assistants can mis-detect speech that sounds similar to the trigger phrase. When that happens, the assistant may briefly start listening/processing until it realizes there was no valid command. The lawsuit allegation is that some of these events resulted in recordings/processing that users did not expect.

Practical steps to reduce risk on Android

• Disable wake-word activation (most impactful): Turn off “Hey Google” / “OK Google” detection so the assistant won’t start from ambient audio.
• Revoke microphone permission for Google / Assistant: Android Settings → Privacy/Permissions → Microphone → deny for Google app (and any other assistant-related components shown on your device).
• Use the system mic toggle (Android 12+): Quick Settings → Microphone access OFF when you don’t need it. This blocks mic access system-wide.
• Review and delete stored voice activity: Google Account → Manage your Google Account → Data & privacy → History settings / Activity controls → delete Voice & Audio-related items, and enable auto-delete if available.
• Limit Assistant integration: If you don’t use it, disable Google Assistant entirely (availability varies by device/region/ROM).
• Keep Android and the Google app updated: Updates can include privacy controls and bug fixes related to voice activation behavior.

How to verify the settlement details safely
Security-wise, treat third-party summaries as “informational,” not authoritative. For anything involving compensation/eligibility, rely on:

• The official court docket / filings (case documents)
• The official settlement administrator site (if/when the judge approves and a site is published)
• Google’s own statement or support documentation, if provided

Bottom line
Whether or not this specific settlement is approved as described, the privacy-hardening steps above are worthwhile: disabling hotword detection and restricting microphone permission are the most reliable ways to prevent unintended activation/recording paths on Android.

Sources

• Google to Pay $68 Million to Settle ‘Eavesdropping’ Claims

 

[Sorrento]

Small change to the G

 

[Halp2001]

68 million… basically the price of admitting your assistant confused “Hey Google” with “Who wants pizza?” Privacy remains that bug they never quite patch.