Privacy Policy — Invisible VPN Chrome Extension
Effective date: 26/01/2026
Operator: Invisible Vpn (“we”, “us”, “our”)
Contact: developer@invisiblevpn.net
Effective date: 26/01/2026
Operator: Invisible Vpn (“we”, “us”, “our”)
Contact: developer@invisiblevpn.net
This Privacy Policy explains what information is processed when you use our Chrome browser extension (Extension) named [Product name as shown in the Chrome Web Store] to connect or disconnect VPN/proxy routing for your browser, and when you interact with optional sponsored content shown only inside the Extension’s own pages.
The Extension lets you turn browser VPN/proxy protection on or off by applying Chrome proxy settings based on configuration retrieved from our backend API. When you disconnect, the Extension restores normal direct browsing where applicable.
Optional sponsored messages may appear only inside the Extension’s popup and options pages. The Extension does not inject advertisements into websites you visit.
The Extension uses Chrome’s extension storage (for example chrome.storage.local) to keep information needed for the service to work, including:
Your preferences and Extension settings (which may include a configurable API base URL for connecting to our servers)
A pseudonymous install identifier used with our API
Connection-related state such as session identifiers and selected VPN/proxy server identifiers
Proxy authentication details when your configured proxy requires credentials (for example username/password or token material), so you do not have to re-enter them on every browser restart
This local information remains on your device unless it is sent to our servers as described below. Chrome may sync certain extension data according to your Chrome settings; we do not control Chrome sync behavior.
When you use features that contact our backend API (for example: listing servers, connecting, disconnecting, loading sponsored banner metadata, or recording a sponsored banner click), the Extension sends HTTPS requests to the API endpoint configured for the Extension (by default our production API).
Depending on the action, requests may include:
Pseudonymous identifiers such as an install identifier
Extension version and technical identifiers needed to operate the service
Session identifiers required to establish or end VPN/proxy access
Server selection or preferences needed to fulfill connection requests
For sponsored content shown inside the Extension: banner identifiers, placement (for example popup vs options), timestamps, and similar minimal interaction data when you choose to click
Like most internet services, when your device contacts our servers our systems may automatically receive technical information such as IP address, approximate region derived from network routing, browser/User-Agent related signals associated with the request, and timestamps.
Sponsored banners are displayed using metadata (such as title, image URL, and destination link URL) retrieved from our API. Loading an image URL or opening a destination link may cause your browser to contact third-party websites or content delivery networks. Those third parties have their own privacy practices; this Policy does not govern third-party sites.
Based on how this Extension is designed:
We do not use the Extension to read or scrape the contents of webpages you visit for advertising purposes.
We do not use the Extension to log keystrokes, capture screenshots of webpages, or collect email/message contents.
We do not sell your browsing history.
Important note about VPN/proxy routing: While you are connected, your browser traffic may be routed through VPN/proxy infrastructure as part of providing the service. Whether additional logging applies on VPN/proxy servers may be described separately in our broader service documentation and applicable agreements; this Extension-focused Policy describes Extension-local behavior and Extension-to-API communications as implemented.
The Extension requests Chrome permissions needed for its single VPN/proxy purpose, including:
storage: Save preferences and operational state on your device (including session/install identifiers and proxy authentication details when applicable).
proxy: Apply or remove Chrome proxy settings when you connect or disconnect.
webRequest / webRequestAuthProvider: Respond only to proxy authentication challenges for the configured proxy endpoint.
Host permissions / broad patterns: Needed so proxy authentication can occur across navigations while you are connected; API traffic uses the configured backend hosts.
We retain server-side records only as long as needed to operate the service, maintain security, prevent abuse or fraud, comply with legal obligations, and resolve disputes. Local Extension data remains until you remove Extension data in Chrome or uninstall the Extension.
We use reasonable technical and organizational safeguards appropriate to the nature of the service. No method of transmission or storage is completely secure.
If you use the Extension from regions with privacy laws that apply to you (for example the EEA or UK), you may have rights to access, correct, delete, restrict, or object to certain processing, and to lodge a complaint with a supervisory authority, subject to applicable law. Contact us using the email above.
Where GDPR applies, we generally process information as necessary to perform the contract with you (provide the Extension and related service) and for our legitimate interests in operating, securing, and improving the service (unless overridden by your rights).
The Extension is not directed to children under 13 (or the minimum age required in your jurisdiction). Do not use the Extension if you are not permitted to do so.
We may update this Policy from time to time. When we do, we will update the Effective date above. If changes are material, we will provide additional notice where required.
This Policy is provided for transparency and convenience. It is not legal advice. You should have qualified counsel review your disclosures for your jurisdictions and your actual data practices.