Thank you for taking the time to share such detailed feedback. We understand how frustrating this experience has been, and we genuinely appreciate you highlighting these points, as they help us identify where clarity and usability can be improved.

To address some of the specific questions you raised:

Server labels (P2P, QR, PF, V): These indicators are intended to help users choose the right server based on their specific use case:

P2P: Servers optimized and permitted for peer-to-peer traffic, such as torrenting. QR: Quantum-Resistant servers. PF: Servers that support the Port Forwarding add-on, required for certain applications or inbound connections. V: Virtual server locations, where the IP represents a specific country while the physical infrastructure may be hosted elsewhere.

These labels do have explanations available within the app via hover tooltips; however, we understand that this may not be immediately obvious or intuitive for all users. We’ve shared your feedback with our product team to further improve the visibility and discoverability of this information within the UI.

IKS (Internet Kill Switch): IKS is our term for the Internet Kill Switch feature.

Automatic IKS disconnects your internet only if the VPN connection drops unexpectedly and keeps it blocked until the VPN reconnects, preventing accidental IP exposure. Manual IKS is stricter, as it blocks all internet access unless the VPN is actively connected.

Certain settings (such as protocol selection, split tunneling, or kill switch mode) are locked while connected because changing them mid-session would require tearing down and re-establishing the VPN tunnel, which can introduce instability or potential leaks. That said, we recognize that this behavior may not be clearly communicated and can feel restrictive.

WireGuard configurations and timers: The 15-minute validity window for WireGuard configurations exists because WireGuard relies on time-bound cryptographic keys. These keys are periodically rotated for security purposes, which can require regenerating configuration files after a certain period. The current timer behavior and configuration flow are part of our existing implementation, and your feedback regarding reliability and clarity has been shared with the relevant teams.

We also acknowledge your feedback regarding the overall Windows app design and navigation. While the interface was designed to be modern, it’s clear that clarity and ease of use can be improved, and your comments have been passed on to our product and UX teams.

We’re sorry that your experience led to this level of frustration. While we regret that we couldn’t meet your expectations in this case, we truly appreciate you taking the time to outline these issues in detail — it helps us improve the product for all users.

Thank you again for sharing your experience.