Privacy Policy

SafeBrowse is a Chrome browser extension that routes your browser traffic through your own proxy servers with one-click activation. You supply the proxy credentials — SafeBrowse manages the connection, automatic failover, and split-tunneling entirely within your browser.

This Privacy Policy explains what information is handled when you use SafeBrowse, how it is used, and what choices you have. Because SafeBrowse operates without any server infrastructure operated by us, the scope of data handling is minimal.

Proxy Credentials & Configuration

Your proxy server addresses, ports, usernames, and passwords are entered by you and stored exclusively in chrome.storage.local on your device. They are never transmitted to any server operated by us. Credentials are only sent directly to the proxy server you have configured, as part of the normal proxy authentication handshake.

Extension Settings

Your preferences (auto-connect toggle, split-tunneling mode, domain list) 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 — this is governed by Google's Privacy Policy.

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 in the popup for your reference. This request is made directly from your browser without going through any proxy, and the result is never stored or transmitted to us.

Exit IP Address (Verification After Connect)

After you connect, the extension calls ipinfo.io/json through your configured proxy to verify the connection and display your exit IP address and location. This request goes through your proxy, so the IP seen by ipinfo.io is your proxy's exit IP — not your real IP. The result is stored locally to display in the popup and is not sent to us.

What We Do Not Collect

• Browsing history or visited URLs
• DNS query logs
• Your real IP address on any server we operate
• The content of your network traffic
• Name, email address, or any account information
• Payment information (no payments are processed by the extension)

All data handling occurs locally within your browser or directly between your browser and the proxy servers you have configured. We do not receive, store, or process any of this data.

We do not collect, store, or have access to your proxy credentials, browsing activity, or any personal information. Because we operate no servers that handle your data, there is no information held by us that could be shared, sold, or disclosed.

The only scenario where disclosure could arise is if we were compelled by law to produce information — however, as we hold no user data, there is nothing to disclose.

• Proxy credentials & proxy list: Stored in chrome.storage.local on your device. Cleared when you remove the extension or manually delete them from the settings panel.
• Exit IP & location: Stored in chrome.storage.local while the proxy is active and cleared on disconnect.
• 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.
• Server-side data: None. We do not operate any servers that receive or retain your data.

We do not use advertising networks, analytics platforms, or any user-tracking services.

• Your proxy credentials are stored only in chrome.storage.local on your device and are never transmitted to any server we operate.
• Credentials are sent only to your own proxy server during authentication, using the proxy protocol you have configured (HTTP, HTTPS, SOCKS4, or SOCKS5).
• WebRTC leak protection (disable_non_proxied_udp) is applied while the proxy is active to prevent your real IP address from being exposed through WebRTC.
• The extension generates the PAC script locally — no executable code is fetched from remote servers.

The security of your proxy connection depends on the proxy server you configure. We recommend using proxy servers that support TLS or HTTPS to encrypt traffic between your browser and the proxy endpoint.

Depending on your location, you may have the following rights regarding your data:

Because SafeBrowse stores all data locally in your browser and operates no external servers, you have full and direct control over your data at all times:

• Access & deletion: Your proxy list and credentials can be viewed and deleted at any time from the Settings panel within the extension.
• Full removal: Uninstalling the extension removes all locally stored data including proxy credentials, connection state, and preferences.
• Portability: Your proxy list can be exported at any time using the Download Template feature as a reference.

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.

SafeBrowse is not directed at children under the age of 13. As the extension does not collect or transmit personal data to any server we operate, there is no data for us to delete. All data is stored locally in the browser and can be removed by uninstalling the extension.

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 SafeBrowse after changes are posted constitutes acceptance of the revised policy.