Smart Speakers Always Listen: Privacy Controls for Yandex Alice, Marusya, Salyut, Siri and Google Assistant
Smart speakers and phones keep their microphones powered even when no one is speaking to them. The only purpose of this constant listening is to catch a short wake phrase such as Yandex Alice, Marusya, Salyut, Hey Siri or OK Google. Until that phrase is detected, audio normally stays on the device and is not transmitted to the cloud.
Yandex states that Alice processes sound locally for the activation phrase only. After the wake word is heard, the request is sent to Yandex servers. The same local-detection model is used by VK Marusya and Sber Salyut. Apple applies an on-device detector for “Hey Siri,” while Google Assistant and Gemini rely on account settings and device microphone permissions.
Hardware mute options
Most dedicated speakers provide a physical button that disables microphones at the hardware level. On Yandex Station models the crossed-microphone button turns the LEDs red. VK Capsule and VK Capsule Mini show a red ring when muted. SberBoom Mini requires a two-second press of the AI-assistant button to achieve the same red state. Phones lack an equivalent global hardware switch, so users must rely on software toggles.
Recommended privacy settings
- Disable “Listen for Hey Siri” and “Allow Siri When Locked” in iOS Settings.
- Turn off “Web & App Activity” and “Gemini Apps Activity” at myactivity.google.com.
- Revoke microphone access for unused apps in Android and iOS permission menus.
- Switch off the “Help Alice improve” toggle inside Yandex ID.
- Delete stored voice histories through each provider’s data-management portal.
Even with these steps, the microphone itself remains the only reliable way to guarantee silence. Security-conscious users are advised to mute devices during meetings, medical calls or any discussion involving financial or personal data.
Related articles
VPN Encryption Alone Cannot Hide Traffic from Network Detection Systems
A Habr user known as mr_tom detailed why encrypted VPN connections remain detectable despite their encryption. Observers can identify connections through visible metadata such as server IP addresses, ports, transport protocols, handshake patterns, packet sizes, timing intervals, and overall flow behavior. Simple DPI systems block traffic by restricting known IPs or ports, while advanced filters build traffic fingerprints and use active probing to verify suspicious endpoints. The popular combination of VLESS, XHTTP, and REALITY operates across different layers rather than functioning as three equivalent VPN protocols. Even traffic on port 443 can be distinguished from standard HTTPS by analyzing handshake details and subsequent packet behavior. The core conclusion is that no universally unblockable VPN exists, as detection can rely on IP blocking, new signatures, or active verification regardless of encryption strength.
Browser Extension Anonymizes Sensitive Data Before Sending to AI Chatbots
A new browser extension automatically detects and replaces sensitive information such as names, INN numbers, bank cards, and emails with pseudonyms before any text or files reach AI chat services. The tool operates entirely locally in the browser, ensuring original data never leaves the user's device while allowing AI models to process anonymized placeholders. Responses from the AI are decrypted back to readable form only on the user's screen using an in-memory mapping that disappears when the browser closes. The solution supports over 70 file formats including DOCX, XLSX, and PDF, plus offline OCR for scanned documents to handle the most common leakage vectors used by HR, legal, and accounting teams. Multiple validation layers including checksums, Luhn algorithm, entropy checks, and normalization for Russian name declensions reduce false positives that plagued earlier regex-based attempts. The extension is available in a free version on the Chrome Web Store covering 33 data categories, with advanced file and scan features offered on request.
Browser Privacy Ranking 2026: Tor Browser Leads at 9.5 While Chrome and Yandex Rank Lowest
SecurityLab.ru has published a detailed 2026 browser privacy ranking that evaluates major browsers across six criteria including initial network behavior, site isolation, fingerprint resistance, funding model, configurability, and code auditability. Tor Browser scores highest at 9.5 for its comprehensive protections including unified fingerprinting and layered JavaScript controls, followed by Mullvad Browser at 9.0 and LibreWolf at 8.5. Brave earns 7.5 for built-in tracker blocking but faces criticism over default telemetry and cryptocurrency features. Firefox scores 6.0 out of the box yet reaches 8.5 after extensive configuration, while Google Chrome, Microsoft Edge, Opera, and Yandex Browser occupy the bottom positions due to persistent tracking mechanisms and closed-source components. The report also highlights the Local Mess localhost tracking technique used by Meta and Yandex that bypassed browser isolation entirely.
Russian Ministry Certificates Enable Potential State MITM on Foreign Domains
Russian companies facing sanctions have started adopting root certificates issued by the Ministry of Digital Development and Communications to maintain HTTPS access after commercial CAs revoked or refused to renew their certificates. Installing these Ministry certificates allows browsers to trust sites using Russian national CAs but also creates a pathway for man-in-the-middle interception by state-controlled entities. The article details a concrete threat model where a government-linked operator could use the Ministry root to generate on-the-fly certificates for any domain, including foreign services outside Russian jurisdiction. To mitigate this, the author demonstrates how to re-sign the Ministry root with OpenSSL nameConstraints limited to .ru, .su, and .рф domains only. Tests on macOS with Homebrew show that the constrained certificate still validates Russian banking sites such as online.sberbank.ru while correctly rejecting attempts to validate foreign domains like sberbank.com. The technique requires users to maintain their own cross-signed root and never rely on pre-installed Ministry or Yandex Browser roots for full protection.