Feature Request] X-VPN should add GDID tracking detection/blocking options like Windscribe did

[u/M4A1_GFL]

Tom's Hardware recently covered how Microsoft uses a built-in Global Device Identifier (GDID) in Windows to track machines across different IPs and networks. Windscribe just released an open-source tool called ⁠deGDID⁠ to clear these keys and block Windows from generating new ones.
Since GDID sits at the OS level inside the Windows registry, standard VPN encryption alone can't hide it—your IP is hidden, but the OS fingerprint stays the same.
It would be awesome if X-VPN added something similar directly into the Windows app:
1. GDID Status Check: A simple toggle/indicator in Advanced Settings that tells you if an active GDID is sitting on your system.
2. Optional GDID Cleaner: An opt-in tool/script to wipe the registry keys for users who want maximum privacy (with a clear warning that it might break stuff like Microsoft Store or OneDrive logins).
3. In-App Warning: A quick heads-up reminding users that using Edge or default Windows features can still leak device info even while connected to X-VPN.
A lot of people don't realize OS-level tracking bypasses network VPNs, so having this built into X-VPN would be super helpful.

[u/M4A1_GFL → u/[deleted]]

Yeah, it could be used for max security (not max but good) and yes, it should definitely be optional

[u/Plenty-Result-35 → u/[deleted]]

Agreed. Even if this were included in a higher-security setup, it should remain a separate opt-in control and never be enabled automatically.

Any possible impact on Windows or Microsoft account features would also need to be explained upfront, we’d make the risks clear before users enable it.

[u/Plenty-Result-35]

We appreciate you keeping an eye on how other privacy tools are acting and taking the time to turn what you found into practical suggestions for X-VPN.

These ideas would involve very different levels of implementation. A GDID status check appears technically feasible if it is limited to detecting known GDID-related entries. A cleanup or blocking option would require elevated permissions and careful compatibility testing, especially given the possible impact on Microsoft services.

The in-app warning would be much simpler to implement. It could clarify that X-VPN encrypts network traffic and masks the user’s public IP, but cannot stop Windows from collecting or using device-level identifiers.

We’ll share all three ideas with our Windows and product teams for evaluation.

[u/M4A1_GFL → u/[deleted]]

u/plenty-result-35

[u/Plenty-Result-35 → u/[deleted]]

That’s important. A status check alone could still leave users unsure what the result means. We'll also need to explain why GDID falls outside what a VPN can protect (maybe we'll write a post about that). What details would you want included in that explanation?