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
Yandex Apps Leak Pre-Trigger Audio Buffers, Payment Data, and Contacts via Reverse Engineering
Reverse engineering of Yandex Search and Yandex Browser APKs reveals extensive data collection practices on Android devices. The apps maintain a server-controlled pre-trigger audio buffer that captures up to three seconds or more of microphone input before the wake word Alice is detected. WiFi fingerprinting, full contact book synchronization via ContentObserver, and transmission of PAN and CVV details to mobpayment.yandex.net occur before tokenization. Additional findings include 94 JavaScript Bridge methods, logcat exfiltration with AES encryption, hardcoded Yandex DNS servers, and a native surveillance library named libquarkenstein_daemons.so. The analysis also covers passive geolocation, cell tower data collection, and inventory of installed applications including competitors such as Chrome, Firefox, WhatsApp, and Telegram. These mechanisms operate under remote configuration flags and bypass several Android privacy restrictions through manifest queries.
TSPU Filtering Disrupts Timeweb Cloud Servers: Diagnosis, CDN Failures, and Reverse Proxy Bypass
Russian hosting provider Timeweb Cloud experienced widespread TSPU-based DPI filtering starting in early June that selectively blocked TLS handshakes on port 443 while leaving SSH, ICMP, and TCP connectivity intact. The issue affected multiple providers including Beget and Selectel, was publicly acknowledged by Timeweb on June 5, and proved highly variable by region, operator, and time of day. Attempts to mitigate via new IP addresses or Timeweb's own CDN failed due to poisoned caches and platform outages, while Yandex Cloud CDN blocked all POST requests required for WordPress functionality. A working solution involved deploying a minimal nginx reverse proxy on another Russian cloud VPS that preserves full HTTP methods, handles certificate synchronization, and routes ACME challenges correctly. Timeweb support later closed tickets without resolution after requesting ineffective mtr traces that cannot detect DPI behavior. The case highlights systemic challenges in diagnosing state-mandated filtering and the limitations of standard network diagnostics against selective TLS interference.
UnifiedPush and Public ntfy.sh: Why Push Notifications Fail on Android Without Google Services
Developers building a messenger without Google services adopted UnifiedPush with the public ntfy.sh instance as the default distributor and push server. Production logs revealed that four out of five delivery attempts failed from day one, with error codes 507, 429, and 400 dominating. The 507 errors occurred because ntfy from Google Play relies on Firebase for instant delivery, leaving no active subscriber visible to the server when FCM is unavailable. Rate-limit 429 responses were triggered against the recipient's IP rather than the sender, collapsing under carrier-grade NAT used by mobile users. WebPush endpoints additionally rejected requests missing the mandatory TTL header. The team ultimately deployed a self-hosted ntfy instance and an embedded distributor inside the app to bypass these constraints.
Innovative Tunneling Techniques Leverage File Storage, IMAP, Meek, and NTP for Covert Connectivity
A new wave of experimental tunneling tools has emerged for establishing network connectivity through unconventional channels such as shared file storage, email accounts, legacy CDN protocols, and NTP. File-Tunnel enables TCP proxying by writing data to common storage backends including S3 and WebDAV, allowing traffic to blend with ordinary object storage access. True IMAP Tunnel (Secure) turns an IMAP mailbox into a bidirectional transport by storing encrypted frames as draft messages, supporting providers like Gmail, Outlook, and Yandex while offering optional AES-256-GCM encryption. Meek, originally from the Tor project, is being repurposed as a standalone pluggable transport that uses HTTP POST requests with session headers to traverse CDNs and shared hosting environments. ntptun implements IP-over-NTP and UDP-over-NTP by embedding payloads in NTP extension fields, with poll and push modes for downstream traffic and integration options with GOST for KCP-based proxies. These methods target dissidents and network experimenters seeking resilient bypass techniques against filtering and surveillance.