What this site records
There is no account here, so there is no profile of you to build. What follows is what this site records anyway — including the parts that are less flattering than a blanket privacy promise would be.
The website
There is no sign-up, no login and no email field anywhere on this site. Nothing is asked for, so nothing is stored.
One row is written: which server, which version of its config, whether the ad gate was on, and the time. Your IP address is not part of it, and neither is anything else that points back at you — the row has a user field and it is always empty for a web download. It exists so a server's download count is real.
Downloads and the public API are capped per address, so one script cannot walk the whole fleet. Your IP address is used as the key of a counter in our Redis cache, that key expires sixty seconds after it is created, and it is never written to the database or joined to the download record above.
Like any web server, the one in front of this site writes an access log: IP address, time, the page requested, the browser string and the referring page. It is used for debugging and for spotting abuse, is rotated and deleted by the server's normal log rotation, and is not sent anywhere.
Once you import a config, the connection is between your device and a volunteer's server. It does not pass through us and we cannot see it, log it, or interrupt it. That cuts both ways, and what the operator of that server can see is the more important page of the two.
What is never done
- Nothing is sold, rented, or shared with a data broker. No advertising network is loaded on these pages today. If that changes — an ad in front of a download is the one way this site might pay for itself, and we say so on the about page — this page will name the network and its cookies before the first ad is served, not after.
- No profile is built across sessions. Without an account there is no key to build one on.
- No email is ever sent to you, because no email address is ever collected.
- The configs you download are not fingerprinted or watermarked — the file you get is the file the volunteer published.
The mobile app
The companion app talks to the same public API as this website. It does carry a device token so downloads made in the app can be told apart from downloads made in a browser; that token identifies an installation, not a person, and it is never linked to anything else. If and when the app collects anything more, it will be written here first.
Questions, or a request
Ask at contact@huntvpn.dev. If you want to know whether anything about you is stored, the honest answer is almost certainly "only an entry in a web server log" — but ask and it will be checked properly rather than assumed.