Overview
This Chrome browser extension routes your browsing traffic through an encrypted relay server, providing one-click proxy switching with optional split-tunneling to control which sites use the proxy.
This Privacy Policy explains what information is collected when you use the extension, how it is used, and what choices you have. We are committed to collecting only the minimum data required to operate the service.
Information We Collect
Device Identifier
When you first install the extension, a random device ID (a UUID) is generated locally by your browser and stored in the extension's local storage. This ID is not linked to your name, email, or any other personal information. It is used solely to maintain your proxy session on our server.
Session Tokens
Each time you connect, a short-lived session token is issued by our server and stored temporarily in the extension. The token is cleared when you disconnect and is used only to authenticate your relay connection during that session.
Connection Metadata
Our relay server records minimal operational data per connection:
- Device ID (anonymous, not linked to personal identity)
- Connection start and end time
- Proxy server exit location (not your source IP address)
We do not record your originating IP address, the websites you visit, DNS queries, or traffic content.
Your Real IP Address (Local Display Only)
When the proxy is inactive, the extension fetches your current public IP from api.ipify.org and displays it inside the popup. This is for your reference only — it is never sent to our servers and is discarded when the popup closes.
Exit IP Address
After connecting, the extension calls our server's /exit-ip endpoint, which fetches your exit IP through the relay and returns it. This IP is the address seen by websites you visit — not your real IP. The result is displayed in the popup and stored locally only.
Extension Settings
Your preferences (auto-connect, split-tunneling rules) are stored in Chrome's built-in storage APIs (chrome.storage.sync and chrome.storage.local). If you are signed into Chrome, sync settings may be replicated across your devices by Google — governed by Google's Privacy Policy.
What We Do Not Collect
- Browsing history or visited URLs
- DNS query logs
- Your originating IP address on our servers
- The content of your network traffic
- Name, email address, or account information
- Payment information (no payments are processed)
How We Use Information
| Data | Purpose |
|---|---|
| Device ID | Identifying your relay session; allocating a dedicated relay port |
| Session token | Authenticating your active proxy connection |
| Connection timestamps | Detecting stale sessions and freeing server resources |
| Exit IP & location | Displaying your exit IP and location in the popup UI |
| Extension settings | Restoring your preferences across browser sessions |
We do not use any collected data for advertising, user profiling, or sale to third parties.
Data Retention
- Session tokens: Cleared from the extension on disconnect. Invalidated on the server when the session ends or expires after 5 minutes of inactivity.
- Connection logs: Retained on our server for up to 30 days for operational monitoring, then permanently deleted.
- Device ID: Stored locally in the extension until you uninstall it.
- Extension settings: Stored in Chrome's storage until you clear extension data or uninstall. Chrome sync data is managed according to your Google account settings.
Third-Party Services
| Service | Purpose | Data Sent | Policy |
|---|---|---|---|
| api.ipify.org | Display your real IP when proxy is off | Standard HTTP request (your IP is the request source) | ipify.org |
| ipinfo.io | Resolve exit IP and location (server-side, via relay) | Relay exit IP — not your real IP | ipinfo.io |
| flagcdn.com | Display country flag watermark when connected | Country code only, fetched server-side via relay | flagcdn.com |
| Google Chrome Storage | Sync extension settings across your Chrome devices | Extension preferences only, if signed into Chrome |
We do not use advertising networks, analytics platforms, or any user-tracking services.
Security
- All communication between the extension and our relay server is encrypted with HTTPS / TLS.
- Each user session is assigned a dedicated relay process and a unique 256-bit session token, isolating your traffic from other users.
- WebRTC leak protection (
disable_non_proxied_udp) is applied while the proxy is active to prevent real IP exposure via WebRTC. - Session tokens are cryptographically random and invalidated immediately on disconnect.
- The
/exit-ipendpoint is Cloudflare-protected — your server IP is never exposed to the browser.
No method of transmission over the internet is 100% secure. While we strive to protect your information, we cannot guarantee absolute security.
Your Rights
Depending on your location, you may have the following rights regarding your data:
- Access: Request information about data we hold related to your device ID.
- Deletion: Request deletion of your connection records. Your device ID is visible in browser storage as
deviceIdin the extension's local storage. - Portability: Request a copy of your connection metadata in a structured format.
- Objection: Object to processing of your data for any purpose beyond service operation.
EEA / UK users (GDPR): You have the right to lodge a complaint with your local data protection authority if you believe your data has been processed unlawfully.
Children's Privacy
This extension is not directed at children under the age of 13. We do not knowingly collect personal information from children. If you believe a child has used the extension and data has been collected, please contact us and we will delete it promptly.
Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page and, where appropriate, notify users via the Chrome Web Store listing or extension update notes.
Continued use of the extension after changes are posted constitutes acceptance of the revised policy.