AVG Secure VPN: Understanding No Logs Policy With SSTP
AVG Secure VPN: Understanding No Logs Policy With SSTP
AVG Secure VPN states a "no logs" policy, meaning they claim not to track your browsing history, data content, or IP addresses. However, understanding the nuances of this policy, especially when using the Secure Socket Tunneling Protocol (SSTP), is crucial. While AVG does not log the content of your traffic, connection logs are necessary for maintaining the service and preventing abuse. These logs typically include timestamps, bandwidth usage, and sometimes, source IP addresses – albeit often anonymized or truncated. The key is understanding how this data is handled and for how long it's retained. AVG's policy states that this data is used for diagnostics and preventing abuse, and is supposedly deleted after a certain period. It's vital to consult their privacy policy directly for the most up-to-date information on retention periods and specific data points logged.
SSTP encapsulates PPP (Point-to-Point Protocol) or L2TP (Layer Two Tunneling Protocol) traffic within an HTTPS connection. This makes it harder to block than other VPN protocols. However, the SSTP implementation itself can introduce logging opportunities. The SSTP server (in AVG's case, their VPN server) needs to maintain session information to route traffic correctly. This session information could be logged, even if AVG claims to have a no-logs policy.
Furthermore, the Windows operating system, which often serves as the SSTP client, may also maintain logs related to VPN connections. Check the Windows Event Viewer (eventvwr.msc) under "Applications and Services Logs" -> "Microsoft" -> "Windows" -> "RasClient" for connection logs. While these logs may not contain the content of your traffic, they will contain connection timestamps and potentially other identifying information.
Even with a no-logs VPN, firewall configurations can inadvertently leak information. Ensure your firewall is configured to only allow traffic through the VPN interface when the VPN is active. Otherwise, traffic might leak through your default gateway, exposing your real IP address. Use tools like iptables (Linux) or the Windows Firewall with Advanced Security (wf.msc) to create rules that block all traffic except that going through the VPN interface (e.g., tun0 or tap0).
For example, using iptables on Linux:
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT DROP
# Allow established and related connections
iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
# Allow loopback interface
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
# Allow traffic through the VPN interface (replace tun0 with your VPN interface)
iptables -A INPUT -i tun0 -j ACCEPT
iptables -A OUTPUT -o tun0 -j ACCEPT
# Allow DNS resolution (replace 192.168.1.1 with your DNS server)
iptables -A OUTPUT -p udp --dport 53 -d 192.168.1.1 -j ACCEPT
iptables -A INPUT -p udp --sport 53 -s 192.168.1.1 -j ACCEPT
Directly verifying a no-logs policy is difficult, as it relies on trust. However, you can monitor your network traffic using tools like Wireshark to ensure that DNS requests are being routed through the VPN and that no unexpected traffic is being sent outside the VPN tunnel. While this doesn't prove AVG isn't logging, it can help identify potential leaks.
Consider using third-party DNS leak test websites (e.g., dnsleaktest.com) to confirm that your real IP address and DNS servers are not being exposed. Regularly check AVG's privacy policy for updates to their logging practices. Be aware that a warrant canary (if AVG employs one) disappearing could indicate legal pressure to log data.