Last updated: 11 November 2026
MagicProxy operates no proxy service, account system, telemetry endpoint or analytics. It stores your configuration on your computer and routes traffic to the server you choose. The developers do not automatically receive your profiles, traffic or diagnostics. Data you voluntarily submit in a support message is received through that support channel.
Network adapter selection. The Windows component provides the names of active physical adapters to the extension. If you choose an adapter, its name is stored locally in that profile and included in profile exports.
Proxy server configuration that you enter. Server addresses, ports, UUIDs, passwords, pre-shared keys and similar values. This is authentication information. It is stored locally in your browser profile (chrome.storage.local), it is not synced to your Google account, and it is sent only to the MagicProxy background component running on the same computer, which needs it to configure the networking core.
Your on/off state, routing rules and runtime diagnostics. Stored locally in the same way, including the latest status/error and automatic recovery state.
Diagnostic log lines produced by the networking core. Kept in memory for display in the extension popup. Not written to disk by the extension, and not transmitted. The core uses the warn log level, which avoids routine per-connection history. Warnings and errors can still contain destination hostnames, IP addresses and connection details. The extension keeps at most 200 log entries in worker memory. Review logs and exported profiles before voluntarily sharing them with anyone.
A generated core configuration file. While the proxy runs, the background component writes a configuration file containing your server details to a temporary directory owned by that host process on your computer. Normal stopping/exiting removes the configuration; validation files are removed after the check. A forced crash can leave files behind. Later hosts remove old directories only when the owning process is no longer alive; uninstall does not wipe the shared temporary tree because another browser profile may still be using it.
MagicProxy does not inspect page contents, cookies or form data, and does not automatically transmit browsing history, analytics or crash reports to its developers. Proxying necessarily processes destinations, and diagnostic error lines can include destination information as described above.
The extension declares no host permissions and injects no scripts into web pages. Its permissions are limited to proxy, privacy, storage, nativeMessaging and alarms. The privacy permission is used for exactly one thing: while the proxy is on, the profile's WebRTC policy is set to disable_non_proxied_udp so WebRTC cannot leak your real IP address around the tunnel; the policy is removed when the proxy is switched off. No data is read through this API.
1. To the proxy server you configure. That server carries your traffic and sees your IP address and your destinations. We have no relationship with it — choose a server you trust. 2. To DNS resolvers. The operating system resolves the proxy server's hostname before the tunnel exists; a WireGuard peer hostname is also resolved during configuration. Destination DNS handled by the core is configured to use the resolver through the proxy (1.1.1.1 by default, or the configured address). Direct routing exceptions and traffic outside the selected browser profile retain their ordinary DNS behaviour. 3. To GitHub and its release delivery hosts, when you open a download link for the companion application. These services see your IP and ordinary request metadata. The Windows installer and portable archive include the core. This release disables in-app core downloads and update checks. 4. To pages you open explicitly, such as the extension store, documentation and support links. Their own privacy policies apply.
Connection checks. Manual checks and optional automatic checks of the running proxy make a fixed HTTPS request to api64.ipify.org through the proxy being checked. Automatic checks are off until you enable them in the profile settings. ipify sees the exit IP and ordinary request metadata. The extension keeps the exit IP, elapsed time and outcome in memory.
Technical update pauses keep the proxy setting and WebRTC restriction while ON; user OFF clears them. Browser policies or other extensions can prevent these settings from taking effect; the interface reports that limitation.
Our use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Removing the extension deletes its local storage, including your server profiles. Uninstalling the background component removes its installed files and only the browser registrations still owned by that installation. It does not delete extension profiles, another installation's registration or a live neighbouring host's temporary files. After a forced crash, residual temporary configurations may require manual removal once their owning process has stopped. MagicProxy has no developer-operated server-side profile or traffic data to delete.
Material changes will be noted in the project's CHANGELOG.md and in the release notes, and this date will be updated.
magicmaxlabs@gmail.com · https://github.com/MagicMaxLabs/MagicProxy/issues