Yandex Details Alice Voice Assistant Audio Buffering and Data Handling in Android Apps
Yandex has published a comprehensive technical reply to recent scrutiny of its Android applications, addressing allegations of excessive data collection including audio, contacts, and banking information.
The company confirmed that the Alice voice assistant maintains a cyclic audio buffer of roughly 1.5 seconds prior to the activation phrase and 0.5 seconds afterward. This buffer operates in memory when the app is open, and a portion of the audio preceding a command may be sent to servers to evaluate speech recognition quality. Yandex noted that remote adjustment of buffer size could raise user concerns and pledged to impose strict limits in an upcoming release.
Regarding contacts, Yandex stated that access supports voice commands such as “Call mom.” On initial synchronization the entire address book may be transmitted to servers, after which only modifications are sent. Names and numbers are not hashed because raw values are required for accurate speech recognition.
The company emphasized that its applications do not read message content from WhatsApp, Telegram, or Viber. They only observe contact details that these messengers publish to the system address book on Android.
Accusations concerning insecure handling of bank cards were dismissed: card details are routed directly to an isolated PCI DSS environment rather than ordinary application servers. The VPN interface was attributed to network diagnostics, the backup DNS to bypassing provider outages, and the list of other applications in the manifest to a standard Android mechanism.
Related articles
Hydrat Project Builds Automated WireGuard Gateway for Resilient VLESS and Tor Routing
A developer has released Hydrat, a self-hosted gateway that connects devices via WireGuard while automatically managing VLESS and Tor backends to survive server blocks and quality degradation. The system maintains a pool of tested proxies, performs continuous health checks, and switches routes without requiring client-side profile changes. Two Go processes handle control logic and network enforcement separately, using SQLite for state and nftables plus Xray for traffic routing. TCP and UDP can be assigned independent exits, with geoip.dat support and custom rules to keep marketplace apps functional. The project emphasizes stability over direct connections and is designed for deployment on servers in Russian jurisdiction.
OpenAI Contractors Manually Review Real User Chats in Project Lily
OpenAI has engaged hundreds of external contractors to analyze actual user conversations with ChatGPT as part of its model improvement efforts. The reviewers, working under project Lily, examine real queries that may contain personal, medical, or other sensitive information despite the use of a Privacy Filter. Contractors summarize prompts, compare four model responses, and assign ratings from one to seven while flagging behaviors such as excessive sycophancy or inappropriate emojis. User identities are hidden and some data is filtered, yet OpenAI acknowledged that not all personal information is reliably removed. The same human review process is also employed by Anthropic for its Claude model. Users can opt out of future training use through account settings, although prior data remains unaffected.
UDP Proxies and QUIC Protocol: How Real IP Addresses Leak Through Anti-Detect Browsers
Anti-detect browser users relying on UDP-capable proxies face a hidden risk of real IP leakage when the browser fails to properly route UDP traffic. The QUIC protocol, which powers HTTP/3, runs over UDP and enables features like 0-RTT handshakes, independent streams, and connection migration that can bypass proxy routes. WebRTC connections using ICE, STUN, and TURN further increase exposure because they often attempt direct UDP paths outside the configured SOCKS5 proxy. Without deep network stack control such as TUN interfaces or socket interception, browsers may send WebRTC and QUIC packets through the host's real network interface. Aurorium Browser claims to solve this by natively supporting UDP proxying so that both QUIC and WebRTC traffic stays inside the tunnel. The article stresses that simply disabling WebRTC or forcing HTTP/2 fallback is insufficient and can itself create detectable anomalies for anti-fraud systems.
Google to Offer Granular Controls for Advanced Protection Mode in Android 16
Google is preparing more flexible settings for its Advanced Protection security mode that first appeared in Android 16. The changes were discovered by Android Authority researchers while examining Google Play Services version 26.36.30. A new Expert features section will let users enable individual protections such as USB Protection, intrusion detection logging, and restrictions on unsafe Wi-Fi networks without activating the entire strict mode. USB Protection blocks new USB connections while the screen is locked to prevent physical attacks, though it can interfere with fast charging on Pixel 6 and newer devices. Users will also be able to opt out of automatic connections to open or risky Wi-Fi networks if they regularly use public hotspots. Intrusion Logging remains optional and stores encrypted security logs in the cloud. The update aims to preserve core security benefits while removing the all-or-nothing requirement of the current Advanced Protection implementation.