Skip to content

feat(data): add DotVPN - #397

Merged
NotAFlightRisk merged 1 commit into
mainfrom
data/dotvpn
Nov 11, 2026
Merged

NotAFlightRisk merged 1 commit into
mainfrom
data/dotvpn

Conversation

@NotAFlightRisk

Copy link
Copy Markdown
Owner

Category

New provider

Overview

DotVPN is a Chrome extension with about 500,000 users, run by Smart Security Limited in Hong Kong (on the register since May 2014). It's a browser proxy now: the Chrome one was updated in September, but the Android, iOS and Firefox apps the site still links are gone, and the Opera one stopped in 2018.

The Chrome listing sells a "verified" zero-logs policy, Double VPN, a kill switch and not collecting IPs or connection times. None of it's audited, the extension has no kill switch or second hop, and the user agreement keeps your IP and connection history for 24 hours, so misleading_claims is true. The extension also reports when you open it, connect and disconnect under an install ID with no way to turn it off, so telemetry is forced. Prices only show once you've signed in, so monthly is the $4.99 in the extension and the rest is null.

Sources

  • User agreement1, privacy policy2 and refund policy3
  • Chrome Web Store listing4 and the extension itself5
  • Hong Kong Companies Registry6

Issue number

None

Additional info

No conflicts of interest.

Footnotes

  1. DotVPN user agreement ↩

  2. DotVPN privacy policy ↩

  3. DotVPN refund policy ↩

  4. DotVPN on the Chrome Web Store ↩

  5. DotVPN Chrome extension 2.8.12 ↩

  6. Hong Kong Companies Registry, Smart Security Limited ↩

@github-actions github-actions Bot added the new-provider Adds a VPN provider label Nov 11, 2026
@NotAFlightRisk
NotAFlightRisk merged commit 4bd6325 into main Nov 11, 2026
11 checks passed
@NotAFlightRisk
NotAFlightRisk deleted the data/dotvpn branch November 11, 2026 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-provider Adds a VPN provider

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant