VPN security: what the tunnel covers and what it cannot

Who sees what on Wi-Fi, at your provider and at the website, and the parts no key can reach.

Every Royal Key location runs a single protocol, VLESS over Reality. TLS 1.3 encrypts the traffic from your device to the location, which protects the journey. It does not protect your accounts, or a device that is already compromised.

On Wi-Fi that is not yours

Whoever runs the hotel, café or train network sees one HTTPS session going to one address, and that is all. Your DNS lookups go through the tunnel as well, so the local resolver never learns which names you looked up.

At your provider

BT, Sky, Virgin Media or your mobile network sees the same single session. Because Reality looks like ordinary HTTPS, a filtering network finds nothing VPN-shaped to stop.

At the website

Sites see the address of the location you chose rather than yours. Sign in, though, and the account knows it is you, key or no key.

What no key can do

If a phone or laptop already has malware on it, the key changes nothing. Nor can any service promise total anonymity, and Royal Key does not.

Whose code runs on your device

We never wrote an app. The key runs in clients made by other people, and widely used ones such as v2rayNG and Hiddify publish their source code for anyone to read. There is no Royal Key app for a store to pull.

Found a weakness? Tell the bot. A genuine report is fixed within the same week, and this page will say so.