Browser extension privacy
What the ForestVPN browser extension and the ForestVPN Browser Helper collect, store and send, and where the helper keeps its files on your computer.
The ForestVPN browser extension connects one browser through ForestVPN. It works with the ForestVPN Browser Helper, a small program that runs as your own user (not as an administrator) and does the connecting. This page says what each of the two collects, stores and sends. For how ForestVPN handles accounts, payments and its servers in general, see the ForestVPN privacy policy, which covers the extension and the helper too; this page describes them in more detail.
The extension
| Question | Answer |
|---|---|
| What does the extension collect? | Nothing. It has no analytics, no crash reporter and no code that contacts a server of its own. It does hand data to the helper on your computer, and Firefox's data_collection_permissions says so: authenticationInfo (the account number you type) and browsingActivity (the address of each site you open, which travels through the helper). |
| What does it store in the browser? | One flag, saying you accepted the first-run notice. Nothing else is written to the browser's storage. |
| Does it store my account number? | No. The number crosses to the helper only to link this browser to your account (and once on screen when you create a new account, so you can save it). The extension does not keep it. |
| Where does the proxy password live? | In memory only. It is never written to the browser's storage. |
| Does my browsing history leave the browser? | Your pages go to the helper on your computer and from there through the tunnel to the ForestVPN server you chose. The extension does not record them, list them or send them anywhere else. Some traffic does not go through the tunnel: addresses on your local network, and ForestVPN's own sites (fvpn.net, api.fvpn.net, report.fvpn.net and console.fvpn.net, so that sign-in and checkout work) connect directly from your real address, and so does the browser's own update, telemetry, secure-DNS and QUIC traffic. In Firefox, one extra lookup per http:// site name also goes to your system's resolver, and Firefox's own requests go direct if the proxy dies. |
| When does protection end? | When you disconnect, or when a Free connection reaches its data limit. The browser then connects directly again and the extension tells you. |
The extension asks for broad permissions because routing and protecting a whole browser needs them. Each one has a single use:
| Permission | Why |
|---|---|
nativeMessaging | To talk to the helper on your computer. |
storage | The one first-run flag above. |
proxy | To send this browser's traffic to the helper's local connection, and to park it when the helper is gone. |
offscreen (Chrome family) | To learn whether the browser is in dark mode, so the toolbar icon stays visible. It shows nothing and reads no page. |
privacy | To switch off WebRTC address exposure and network prediction while connected. |
declarativeNetRequest | To block page loads when the helper stops, instead of letting them go direct. |
webRequest, and webRequestAuthProvider (Chrome) or webRequestBlocking (Firefox) | To answer the proxy's sign-in; to list the tabs the block cut off, so the popup can offer to reload them; and, in Firefox, to cancel a request that would not leave through ForestVPN's proxy. None of them reads or changes page content. |
| All sites | These rules apply to every page you open. The extension does not read page content. |
The helper
| Question | Answer |
|---|---|
| Who does it talk to? | The ForestVPN control plane, the same service and the same way the ForestVPN desktop app does: to register this install as a device, link it to your account, fetch the signed server list, get connection tickets, and check the result of a purchase. The tunnel itself goes to a ForestVPN exit server, over the Quantum protocol. When a connection has to find another road (a different network path, or a ForestVPN backup route through a content network), it uses that too. |
| Does it send reports? | Route reports, as the desktop app does: anonymous, aggregated network diagnostics about which kind of road worked, with no account number, device tag or site you visited. They are kept in memory until sent. |
| Does it write a log file? | No. It keeps no log file and prints nothing; diagnostics stay in memory and are gone when the helper exits. |
| Does it store my account number? | No. The link between this device and your account is kept on ForestVPN's side. |
| Does it send anything to anyone else? | If your network's DNS cannot find ForestVPN's own servers, it may ask a public resolver (Cloudflare, Google or Quad9) over encrypted DNS for the addresses of ForestVPN's own server names, never for a site you visit. Each learns your IP address, the time and that name. When ForestVPN's servers answer slowly or not at all, the signed server list may come from a copy on Amazon Web Services, which sees your IP address and the time. On a network that blocks ForestVPN, requests (and, on Pro and Premium, the tunnel) may go through a content network: Bunny.net, or Gcore for requests only. Gcore keeps your IP address, the hostname and the time for 3 days. See the privacy policy's section on carrying your connection through a CDN. No analytics or tracking service is built in. |
| Does it remember my choices? | Yes, on this computer only: one file in its state folder holds your route setting, the locations you starred or used recently and the last one you chose. They are location names from ForestVPN's list: no times and no addresses. The file is browser-prefs.json in the state folder (see below). Signing out in the extension deletes it; otherwise it stays until you delete the state folder, so to clear only your choices without signing in, delete that one file. Uninstalling the helper leaves it, with the rest of the state folder, so a reinstall picks up where it left off. |
| Does it show my data use? | While the extension's window is open, the helper sends it the received and sent totals of the current connection, how long it has been connected and how long ago its last key exchange was, so the window can show them. The helper does not store these readings or send them anywhere else. |
| When does it run? | While a browser has the extension connected. It exits by itself after ten idle minutes with no browser attached and no connection. |
What the helper keeps on disk
The helper keeps a per-user state directory: this install's device keys and registration record, a record of which user on this computer signed the helper in, connection tickets, the resume record it uses to restart a connection in the right state, a cached copy of the signed server list, which network paths worked on each network you have used, settings, and one small file of your browser choices (the route setting, starred and recent locations and the last location you chose; browser-prefs.json; deleted when you sign out in the extension, otherwise kept until you delete the folder). On Linux and macOS the files are readable by your user only (mode 0600 in a 0700 directory); on Windows the folder is limited to your Windows user. It never stores the account number. The machine key and the session keys of unused tickets are among those files: they are not in the system keychain. On Linux and macOS they are not encrypted on disk; on Windows they are encrypted with the Windows data protection API (DPAPI) for your Windows user. Uninstalling leaves the folder, so a reinstall is the same device; deleting it makes a new one.
| System | Where |
|---|---|
| Linux | State: $XDG_DATA_HOME/forestvpn-browser, by default ~/.local/share/forestvpn-browser. Program copy: $XDG_DATA_HOME/forestvpn/browser-helper, by default ~/.local/share/forestvpn/browser-helper. |
| macOS | State: ~/Library/Application Support/ForestVPN/BrowserHelper. Program: ~/Applications/ForestVPN Browser Helper.app. |
| Windows | State: %LOCALAPPDATA%\ForestVPN\BrowserHelper\state. Program: %LOCALAPPDATA%\Programs\ForestVPN\BrowserHelper. |
Installing also writes one small manifest per supported browser, so the browser can find the helper. They sit in the browsers' own native-messaging folders under ~/.config and ~/.mozilla on Linux and under ~/Library/Application Support on macOS. On Windows the manifests sit beside the program, and the browsers find them through two registry entries under HKEY_CURRENT_USER (one for the Chrome family, one for Firefox). It also adds a third key under HKEY_CURRENT_USER, the Settings > Apps entry, and a per-user scheduled task named ForestVPN-BrowserHelper with your user's ID on the end; uninstalling removes both the key and the task. How to remove all of it.
Who is responsible
The seller and the party responsible for the data the helper sends to ForestVPN is Digital Services LLC. Browser stores do not sell ForestVPN and do not receive your payment: purchases go through ForestVPN's own checkout in a normal browser tab, as in the desktop app.