New open-source IVPN website: subscribe without providing your email

IVPN News By Viktor Vecsei | Posted on November 10, 2020

In a nutshell

Generating an account for our VPN service no longer requires an email address, and we dropped renewing subscriptions by default in favor of a pre-paid system. We have introduced a new onboarding process with QR code setup, and two-factor authentication for account IDs that act as a sole identifier.
We have also changed our website structure and copy, emphasizing our policies and the limitations of VPNs. The website is now open-source on GitHub and supports light/dark mode switching.

Why the changes?

We’ve been vocal about the shortcomings of the VPN industry and our competitors for multiple reasons. Two of them stand out:

  1. VPN services promise privacy protection, yet most of them collect and share personally identifiable information about you. Methods for this include using Google Analytics, website trackers and third-party tools - all shunned by IVPN. A handful of services stopped these violations, but yet they still require an email address to sign up. Disclosing your email address makes you personally identifiable and should not be necessary to subscribe to a privacy protection service.
  2. Most VPN services over-promise on the actual value they offer - they claim to make you anonymous and invisible on the internet and pledge to solve every privacy problem online. As we have demonstrated in a previous blog post, false promises are rampant on VPN websites, marketing materials and landing pages. We aim to do better, and do it in the most transparent way possible.

ivpn new website dark mode do you need a vpn

What has changed exactly?

  1. We have dropped the email address requirement and removed our initial signup form. From now on, customers create a unique identifier instantly by pressing a ‘Generate account’ button. The generated Account ID is the only information you need to manage your account and use our service (please keep it secret, keep it safe - 2FA is supported). If you pay for your subscription with cash or anonymously sourced cryptocurrency, no personally identifiable information can be tied to your IVPN account.
  2. Our subscriptions are now pre-paid by default. Getting a recurring subscription is optional during account generation, and we don’t store any payment details unless you ask us to. You can now add 2 and 3 years of service time with one payment (and a discount).
  3. We have revamped our website and written new copy that’s clear on VPN capabilities and their value for privacy protection. Review our home page to see how we think a responsible VPN service should communicate without overselling or creating fear, uncertainty, and doubt.
  4. The IVPN website - following precedent set by our apps - is now open-source. Source code is available on GitHub. You can follow changes to any page on, e.g. our Privacy Policy or Terms of Service.

ivpn signup form without email prepaid

Note to current IVPN subscribers:

IVPN Staff

Open Source Privacy Transparency Subscriptions
We invite you to discuss this post in our Reddit community or on Twitter. You can also send your feedback to

Independent security audit concluded

By Nick Pestell


IVPN applications are now open source

By Viktor Vecsei


Beta IVPN Linux app released

By Viktor Vecsei

DNS traffic leak outside VPN tunnel on Android IVPN News

DNS traffic leak outside VPN tunnel on Android

Posted on June 13, 2024 by IVPN Staff

Recently we were made aware of a potential DNS traffic leak outside the VPN tunnel on Android. Even with Android OS “Always-on VPN” and “Block connections without VPN” options enabled, as per the report the plaintext DNS traffic can be observed outside the VPN tunnel.
IVPN web infrastructure security audit concluded IVPN News

IVPN web infrastructure security audit concluded

Posted on April 11, 2024 by Nick Pestell

We’re pleased to announce that a sixth annual independent security audit has concluded. The assessment focused on Web UI, backend components, API endpoints, underlying web servers, and web infrastructure. We’d like to share two key excerpts from the report:
Spotted a mistake or have an idea on how to improve this page?
Suggest an edit on GitHub.