Security
The cryptography and key handling behind vpn.golf, stated plainly.
Encryption
WireGuard fixes one modern cipher suite: Curve25519, ChaCha20-Poly1305, BLAKE2s. There are no weak options to misconfigure into.
Key handling
Each device generates its own key pair locally; we store only the public key. Revoking a device removes its key from the exit nodes.
Isolation
Control plane and exit nodes are separate systems on separate providers, limiting the blast radius of any single compromise.
Reporting a vulnerability
Email security@vpn.golf (see our security.txt). We welcome good-faith research.
Frequently asked questions
WireGuard's fixed modern suite: Curve25519 for key exchange, ChaCha20-Poly1305 for encryption, BLAKE2s for hashing. There are no weak options to misconfigure.
Email security@vpn.golf (see our security.txt). We welcome good-faith research and will coordinate disclosure.
Your private key stays on your device. We store only your public key, which is removed from the exit nodes when you revoke a device.
No. The tunnel is encrypted end to end between your device and the exit node, and we never hold your private key, so we have no means to decrypt what you send.
The damage is contained. An exit node holds only public keys — no identity and no logs — and it's on infrastructure separate from the control plane, so one compromise doesn't expose accounts.
Yes. WireGuard rekeys sessions regularly, so even if a key were later exposed it would not unlock traffic from past sessions.
No. WireGuard fixes a single modern cipher suite with no negotiation, so there are no downgrade options or legacy ciphers to fall back to.
Our native apps include a kill switch, and a WireGuard configuration can be set to block traffic if the tunnel drops, so nothing exits outside the encrypted connection.
Curve25519 for the key exchange, paired with ChaCha20-Poly1305 for encryption and BLAKE2s for hashing — WireGuard's fixed, modern set.
It's a standard file at /.well-known/security.txt listing how to reach us about security issues. It points to security@vpn.golf for vulnerability reports.
We welcome good-faith research now and coordinate disclosure through security@vpn.golf. A formal bounty program is something we plan to add as the service grows; we won't overstate it before it exists.
Control plane and exit nodes run as separate systems on separate providers with minimal exposed services. Compromising one does not hand over the other, and exit nodes hold no logs to steal.