Privacy Policy for Secure Proxy
Effective Date: July 1, 2026
This Privacy Policy explains how the Secure Proxy Chrome Extension handles user information.
Secure Proxy is a minimal browser proxy switcher for Google Chrome. The extension allows users to manually enable or disable a SOCKS5 proxy connection from the extension popup.
We respect user privacy and designed this extension to operate with minimal permissions and without collecting personal data.
1. Overview
Secure Proxy is a Chrome Extension that provides a simple way to enable or disable a browser proxy connection.
The extension has only one main purpose:
- to enable a SOCKS5 proxy connection when the user clicks the Connect button;
- to disable the proxy connection when the user clicks the Disconnect button.
The extension does not provide analytics, advertising, tracking, user profiling, or behavioral monitoring.
2. Information We Collect
Secure Proxy does not collect, store, sell, share, or transmit personal user information.
The extension does not collect:
- browsing history;
- visited URLs;
- search queries;
- website content;
- page text;
- cookies;
- authentication data;
- usernames;
- passwords;
- email addresses;
- payment information;
- personal files;
- location data;
- device identifiers;
- advertising identifiers;
- IP-based analytics;
- behavioral analytics.
The extension does not track how users browse the web.
3. Local Data Stored by the Extension
Secure Proxy may store a small amount of local technical data using Chrome local storage.
This data may include:
- whether the proxy connection is currently enabled or disabled;
- the active proxy server identifier.
This information is stored locally in the user’s browser and is used only to display the correct connection status in the extension popup.
For example, when the user opens the popup, the extension may show whether the proxy is currently Connected or Disconnected.
This local data is not transmitted to our servers or to third parties.
4. Chrome Permissions Used
Secure Proxy uses only the minimum permissions required for its core functionality.
The extension uses the following permissions:
- proxy;
- storage.
No additional host permissions are used.
5. Proxy Permission
The proxy permission is required because the core function of the extension is to enable and disable Chrome proxy settings.
When the user clicks the Connect button, the extension uses the Chrome Proxy API to configure a SOCKS5 proxy connection.
When the user clicks the Disconnect button, the extension clears the proxy configuration and returns Chrome to its default connection settings.
The extension does not use the proxy permission for any other purpose.
The extension does not automatically enable the proxy without user action.
6. Storage Permission
The storage permission is used only to store local extension state.
This may include:
- connection status;
- active server identifier.
This permission is not used to store personal data, browsing history, cookies, website content, or sensitive user information.
The stored data remains local to the user’s browser.
7. No Website Content Access
Secure Proxy does not read, modify, inject into, or analyze website content.
The extension does not use content scripts.
The extension does not access the DOM of web pages.
The extension does not inspect forms, messages, pages, text, images, or user activity inside websites.
8. No Browsing History Collection
Secure Proxy does not collect or access the user’s browsing history.
The extension does not know which websites the user visits.
The extension does not store visited URLs.
The extension does not create browsing profiles.
9. No Cookies Access
Secure Proxy does not access, read, modify, or store cookies.
The extension does not use Chrome cookie permissions.
The extension does not interact with session cookies, authentication cookies, tracking cookies, or third-party cookies.
10. No Analytics or Tracking
Secure Proxy does not include analytics tools.
The extension does not use:
- Google Analytics;
- Firebase Analytics;
- Meta Pixel;
- third-party tracking SDKs;
- advertising pixels;
- fingerprinting scripts;
- behavioral tracking;
- event tracking.
No usage statistics are collected by the extension.
11. No External API Requests
Secure Proxy does not make external API requests.
The extension does not contact external services to download configuration, scripts, user profiles, advertising, analytics, or remote logic.
The extension does not use DNS over HTTPS, remote configuration, or remote JavaScript.
All extension functionality is included in the extension package.
12. No Remote Code
Secure Proxy does not use remote executable code.
The extension does not load JavaScript from external servers, CDNs, or third-party websites.
The extension does not use:
- remote JavaScript;
- dynamic external scripts;
- eval;
- new Function;
- obfuscated code;
- hidden iframes;
- external code execution.
All code required for the extension to work is included in the installed extension package.
13. Proxy Server Connection
When the user manually enables the proxy connection, Chrome routes browser traffic through the configured SOCKS5 proxy server.
This is the expected and core function of the extension.
Secure Proxy itself does not inspect or store the content of the user’s browsing activity.
However, users should understand that when any proxy server is enabled, browser network traffic is routed through that proxy server. The privacy and security of such traffic may depend on the proxy server configuration, the websites visited, and whether the websites use HTTPS.
Secure Proxy does not decrypt HTTPS traffic.
Secure Proxy does not inspect website content.
Secure Proxy does not store browsing data.
14. User Control
The user has full control over the proxy connection.
The proxy is enabled only when the user clicks the Connect button.
The proxy is disabled when the user clicks the Disconnect button.
The extension does not automatically connect without user action.
The user may also disable or remove the extension at any time through Chrome extension settings.
15. Data Sharing
Secure Proxy does not share user data with third parties.
Because the extension does not collect personal data, there is no personal data to sell, rent, transfer, or disclose.
We do not sell user data.
We do not use user data for advertising.
We do not provide user data to data brokers.
16. Data Retention
Secure Proxy does not collect personal data.
Local extension state may remain stored in the browser until:
- the user disconnects the proxy;
- the user clears extension data;
- the user removes the extension from Chrome.
Because this data is local and technical, it is not retained on our servers.
17. Data Security
Secure Proxy is designed to minimize data handling.
The extension does not collect personal data, does not use analytics, and does not transmit user data to third parties.
The extension uses official Chrome Extension APIs for proxy and local storage functionality.
18. Children’s Privacy
Secure Proxy is not designed to collect information from children.
The extension does not knowingly collect personal information from children or any other users.
Because the extension does not collect personal data, it does not knowingly collect data from users under any specific age.
19. International Users
Secure Proxy is a browser extension that may be used by users in different countries.
The extension does not collect personal data from users, regardless of location.
Users are responsible for ensuring that their use of proxy services complies with applicable laws and regulations in their jurisdiction.
20. Changes to This Privacy Policy
We may update this Privacy Policy from time to time.
If changes are made, the effective date at the top of this document may be updated.
Continued use of the extension after changes to this Privacy Policy means that the user accepts the updated policy.
21. Contact
If you have questions about this Privacy Policy or the Secure Proxy extension, you can contact us at:
Email: dnsvvvvv@gmail.com
22. Summary
Secure Proxy is designed to be minimal and privacy-friendly.
The extension:
- allows users to manually enable or disable a SOCKS5 proxy connection;
- uses the proxy permission only to manage Chrome proxy settings;
- uses the storage permission only to store local connection status;
- does not collect browsing history;
- does not read website content;
- does not access cookies;
- does not use analytics;
- does not make external API requests;
- does not use remote JavaScript;
- does not sell or share user data.