Windows Tracks Users Through Persistent GDID Identifier: How to Minimize Your Digital Footprint
The case of a 19-year-old hacker who was tracked down using his Windows GDID identifier has once again demonstrated that Microsoft maintains a persistent device fingerprint that is difficult to erase. Even when users rely on VPNs or frequently change IP addresses, the underlying Windows installation remains recognizable to Microsoft services through this unique identifier.
What is GDID and Why It Matters
GDID is a permanent device identifier used across Microsoft’s ecosystem, including licensing verification, the Microsoft Store, telemetry collection, and various cloud services. Because it is tied directly to the Windows installation, it survives network changes and creates a stable link between a user’s device and their activity history.
Practical Steps to Reduce Tracking
Although Microsoft does not provide a single switch to disable GDID entirely, users can take several concrete measures to limit data exposure:
- Use a local account instead of a Microsoft Account. Signing in with a Microsoft Account strengthens the connection between the device, OneDrive, the Store, and activity history. A local profile remains significantly more private.
- Disable activity history. Navigate to Settings → Privacy & security → Activity history and turn off the option to store activity history. This may affect features such as cross-device synchronization and the cloud clipboard, but it reduces the data sent to Microsoft.
- Limit diagnostic and feedback data. In Settings → Privacy & security → Diagnostics & feedback, disable the sending of optional diagnostic data. While basic telemetry cannot be fully removed, this step prevents the transmission of non-essential information.
- Disable unused background services. Turn off Phone Link, Nearby Share, cloud synchronization, unnecessary AI features, and any startup programs that connect to Microsoft servers. The fewer connections to the Microsoft ecosystem, the smaller the digital footprint.
It is important to note that reinstalling Windows does not automatically solve the problem. While a fresh installation generates a new GDID, signing back into the same Microsoft Account allows Microsoft to link the new installation with previous ones through account activity, license activation, and service history.
Related articles
WhatsApp Introduces Parental Controls for Teen Privacy Settings
WhatsApp, owned by Meta (recognized as an extremist organization and banned in Russia), has rolled out new parental control tools for family accounts. Parents can manage privacy settings, group participation, channel access, status visibility, and Meta AI usage for teens, but cannot read personal messages due to end-to-end encryption. All controls are voluntary and require joint setup with the teenager, protected by a single PIN code that prevents easy reversal of restrictions. Notifications alert parents when teens join or leave groups or when group sizes change significantly. Separate options cover channel usage, viewable statuses, and audience controls for teen posts. Meta AI access can be set to a standard 13+ mode or a stricter Limited Content mode with undisclosed restrictions. The company plans to expand these features gradually based on family feedback while maintaining encryption protections.
Can Wi-Fi Owners See Your Google Search History? HTTPS, DNS, SNI and ECH Explained
A viral social media video sparked widespread concern that Wi-Fi owners could view users' search history and visited sites simply by knowing the router password. Security experts from Cybernews and Surfshark clarified that modern HTTPS encryption prevents reading of actual search queries or page content. However, metadata such as DNS requests, SNI fields in TLS handshakes, and device MAC addresses remain visible to the network administrator. The introduction of Encrypted Client Hello (ECH) under RFC 9849 aims to hide domain names, yet Russian authorities have blocked many ECH-enabled connections since November 2024. Corporate or school-managed devices with installed root certificates represent the main real-world exception where full traffic inspection is possible. VPNs hide destinations from the local router but transfer visibility to the VPN provider. The article emphasizes that password-protected Wi-Fi grants access only to connection metadata, not browser history.
Yandex Deploys OPRF Protocol to Protect Phone Numbers in Mandatory Audience Measurement Data Sharing
Yandex has detailed a cryptographic scheme using Oblivious Pseudorandom Function (OPRF) to help Russian audiovisual services comply with new legislation requiring transmission of user identifiers linked to phone numbers. The approach replaces a naive shared-secret hashing method that created a single point of compromise across dozens of competing companies. Instead, two independent third parties each hold separate secret keys and process blinded elliptic-curve points derived from normalized E.164 phone numbers. Services obtain deterministic identifiers without learning the third-party keys and without exposing raw numbers to the authorized research organization. The design distributes trust, limits offline brute-force attacks to scenarios requiring both keys plus final identifiers, and adds rate limits plus key-rotation capabilities to deter abuse. Yandex positions the solution as a practical compromise between regulatory demands, competitive secrecy, and user privacy.
CookieTin Extension Manages Partitioned Cookies Across Firefox, Chrome and Edge
Developer Perruer2 has released CookieTin, an open-source browser extension that fully supports partitioned cookies under Firefox Total Cookie Protection and Chrome CHIPS. The tool addresses limitations in older managers like Cookie Quick Manager by correctly retrieving and deleting cookies stored with partitionKey values. It works across Firefox, Chrome and Edge using a single Manifest V3 codebase written in TypeScript and Preact. Key features include accurate cookies.txt export compatible with curl and yt-dlp, protected cookies that survive explicit deletion, and pre-save validation of browser rules for __Host- prefixes and SameSite attributes. E2E tests using Puppeteer verify handling of HttpOnly, partitioned and container cookies in all three browsers.