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
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers
The article from Aurorium details how WebRTC technology can leak real IP addresses even when users route traffic through proxies. It explains the peer-to-peer mechanics of WebRTC, the role of STUN servers in generating ICE candidates, and why standard TCP proxies fail to handle UDP traffic. Disabling WebRTC via flags or JavaScript extensions creates detectable anomalies that anti-fraud systems flag as non-standard environments. The recommended approach involves native emulation inside the browser kernel so that STUN requests return proxy IPs while preserving full API integrity across workers. Additional leaks through local network addresses, mDNS candidates, and IPv6 are also covered with practical verification methods using tools like BrowserLeaks and CreepJS.
Docx Anonymizer: Open-Source Chrome Extension Uses Fine-Tuned rubert-tiny2 to Anonymize Personal Data Before AI Uploads
A Russian developer has released Docx Anonymizer, a browser extension that automatically detects and replaces personal data in documents using a lightweight NER model before they reach public AI services such as ChatGPT. The tool was created to help organizations comply with Russia’s 152-FZ personal data protection law while avoiding the risks of uploading contracts and other sensitive files to cloud-based LLMs. It runs entirely locally via ONNX Runtime and WebAssembly, requires no network calls, and supports any AI chat interface. The underlying model, rubert-tiny2, was further trained through knowledge distillation on WikiANN, factRuEval, and synthetic business documents, reaching strong F1 scores for person and organization entities after int8 quantization. The extension intercepts text on the fly, performs named-entity recognition in under two seconds for typical contracts, and replaces detected entities with placeholders. The project is fully open source and designed for minimal user friction, addressing the growing problem of employees inadvertently leaking corporate and personal data to public AI platforms.
Hybrid Post-Quantum Message Sealing: X25519 + ML-KEM-1024 in Umbera Messenger with Public Rust Tests
Umbera messenger has open-sourced its cryptographic core and published seven Rust tests that anyone can run to verify its hybrid post-quantum message sealing scheme. The design combines X25519 with ML-KEM-1024 so that an attacker must break both algorithms to decrypt a message. Messages are protected by Double Ratchet for forward secrecy, sealed sender packaging, and per-message ephemeral keys derived via HKDF-SHA256 into AES-256-GCM. The relay server stores only an opaque box identifier and encrypted blob with no sender or recipient fields visible. Media calls use DTLS-SRTP end-to-end while TURN servers see only encrypted datagrams. Addresses for message boxes rotate weekly and are derived solely from the shared secret between the two parties.
Free Ad Blocker for iPhone, Android, and Desktop Uses DNS Parsing Without Libraries and Skips YouTube Influencer Ads From the First Second
A new free ad-blocking solution has been released for iPhone, Android, and desktop platforms. The tool relies on a lightweight DNS parser that operates without external libraries. It includes a dedicated mode for users who already run VPN connections. An accompanying browser extension automatically skips sponsored segments in YouTube videos, even when the advertisement begins at the zero-second mark. The developer describes the technical challenges encountered after launch and the fixes applied to maintain compatibility across operating systems. The project emphasizes user privacy by avoiding unnecessary data collection and third-party dependencies.