YOUR CONNECTION. YOUR DATA.
Privacy policy
WG PROXYTOP provides browser proxy connections and an account portal. This page explains the extension and the service at wgproxy.top. Contact support@wgproxy.top about access to your information, correction or deletion.
Account and connection data
The service processes your email or username, display name, password hash, login and revocable device tokens, account status, subscription, balance, assigned connections and security or administrative actions. Sign-in sends your password over HTTPS; the extension does not save your service password. “Remember me” saves a revocable device token in this Chrome profile.
Service gateways necessarily process the source IP, requested destinations and traffic while routing it. Per-user usage statistics are off by default for existing and new VPN profiles and browser accounts. An administrator can explicitly enable collection globally and for selected profiles or accounts. The global switch takes precedence over individual settings. Optional VPN statistics include traffic volumes, connection measurements and sampled usage; optional browser statistics record the latest successful gateway authorization time and connection/disconnection events. Missing measurements are not proof that a user is offline.
Authentication sessions, access grants and expiry times, saved routing rules, subscription and billing records, and security or administrator actions are separate operational records. They remain necessary for access control and are not disabled by the statistics switch. Service health and infrastructure metrics can continue without per-user attribution. Where connection-origin history is explicitly enabled, IP location and ASN lookup uses local DB-IP Lite databases; client IP addresses are not sent to a geolocation API. Approximate location is not GPS location.
Destination history
Browser connections do not save destination IP addresses or DNS domain names in the activity history. The proxy processes destinations while routing requests, but the destination history collector excludes the browser ingress. Browser activity timestamps and connection events also remain off unless the administrator explicitly enables them. Saved multi-route rules are configuration, not a record of requests.
The separate WireGuard service can retain observed connection-origin IPs, destination IPs and DNS names for up to seven days only when statistics are enabled for that profile and the additional history controls are enabled. This is not a complete page history. Disabling collection stops new optional records and hides the corresponding historical views; it does not by itself erase previously stored records or protected backups. A separate administrator cleanup procedure handles existing working history. Account, audit and backup retention is described below.
Information in your browser
Routing mode, the basic Split list, favorites, language and cookie/incognito preferences are stored locally, not through Chrome Sync. When you save multi-route site rules, their domain or suffix patterns, assigned route IDs and filtering choices are also sent to WG PROXYTOP over HTTPS and stored for that browser login so the gateway can choose the correct exit. These are rules you enter, not a record of sites you visit. Removing a rule replaces the active policy; older copies may remain in protected backups under the retention policy below.
The current tab URL is used locally for the routing indicator and site-data menu. The extension does not read Chrome’s history database or cookie values and does not inject scripts into webpages. In version 0.10.0 and later, per-site cookie blocking requests the optional contentSettings permission only when you save a rule that needs it. It sets and checks Chrome’s cookie/site-data policy; it does not use the cookies API or receive cookie values. Blocking applies while the managed service connection is enabled and may prevent sign-in. “Keep browser settings” does not override a broader blocking rule or browser restrictions. If permission is removed or the policy cannot be enforced, affected sites are blocked until the rule is changed or permission is restored. Manual site-data clearing opens Chrome’s own settings for you to review and delete data. Temporary sessions use Chrome’s incognito mechanism, subject to Chrome’s own behavior and your permission. Incognito windows in one profile share a temporary cookie store; we do not provide independent cookie containers per site.
Your own proxy
You can use an independently configured HTTP, HTTPS or SOCKS5 proxy without a WG PROXYTOP account. Its address and optional username stay in this browser profile. Passwords use session storage unless you explicitly choose to remember them. Remembered proxy credentials use extension-local storage, which is not a separate password vault; protect access to your computer. These credentials are sent only in response to an authentication challenge from your configured proxy, never to the WG PROXYTOP account API.
A fixed HTTPS connection check at browser.wgproxy.top runs through the selected proxy and sees its exit IP. The selected proxy operator can process your traffic under its own policy. HTTP and SOCKS5 do not encrypt the browser-to-proxy transport; HTTPS websites still use their own TLS. The default own-proxy type is HTTPS. Do not use an untrusted proxy for sensitive activity.
Service providers and transfers
Optional premium ad blocking uses private Pi-hole instances on our VPN frontends. DNS is first resolved through your assigned VPN or proxy exit using Cloudflare DNS-over-HTTPS with certificate verification. Pi-hole then locally applies domain, CNAME and allowlist rules to that response. Cloudflare receives the requested domain, including domains subsequently blocked by Pi-hole, and sees the assigned exit address rather than the frontend address. If you explicitly use the frontend itself as your exit, that is the expected address. We remove EDNS Client Subnet and do not send your device IP in that field. DNS tests may display Cloudflare resolver addresses; these need not equal your exit IP. Pi-hole uses privacy level 3, no query log and no persistent DNS history; we retain aggregate service counters. If filtering is unavailable, the already obtained exit-routed DNS response is used without ad filtering. This never authorizes a blocked VPN route. This server-side DNS layer affects only WG PROXYTOP traffic, not direct Split traffic or an independently configured proxy. Device caches and applications using their own encrypted DNS can bypass domain filtering.
Hosting and network providers carry service traffic. Cloudflare provides authoritative DNS and the Turnstile security check on registration; Turnstile processes browser and network signals according to Cloudflare’s policy. Registration mail is sent through the operator’s MailHub. Support email is forwarded through Cloudflare Email Routing to a Google-hosted mailbox, so these providers handle messages you send to support. Do not email passwords, private keys or payment seed phrases.
In extension version 0.10.0 and later, eligible service connections can additionally apply a packaged domain list inside Chrome, including direct Split requests. Chrome evaluates these block rules locally; blocked requests, matching statistics and visited URLs are not uploaded for list matching. The packaged list is a pinned, MIT-licensed snapshot of Anudeep’s Blacklist, with its license and source checksums included in the extension. It changes through reviewed extension releases, not remote list downloads during browsing. This does not route otherwise direct traffic through WG PROXYTOP, does not apply in own-proxy mode and cannot remove every advertisement or cosmetic page element. This local layer is separate from Pi-hole. A local page exception need not exempt third-party resource domains from server-side filtering, which follows each request’s destination rule.
One-time links and verified handoffs
“Share a password” is optional and works without a WG PROXYTOP account. After you select Create, the extension encrypts the text in your browser and sends the ciphertext and your chosen lifetime over HTTPS to secret.wgproxy.top. The decryption key travels after the # in the link you share. The browser omits this fragment from its HTTP request. Anyone who receives the full ordinary link can redeem it once. A messaging preview can load the generic card without redeeming it.
The service stores ciphertext, expiry and hashes used to identify or revoke the link. It removes the ciphertext on successful release, revocation or expiry. Lifetimes for ordinary links are one hour, one day or seven days. The extension keeps your draft, link and revocation token in the open extension view. Copying them to your clipboard or a messaging service is your choice.
The service receives the connection IP when the link is created or opened. It may be your proxy exit or the address of a direct connection, depending on your routing choices. The service uses short-lived counters to limit abuse. It does not use device fingerprinting to identify participants.
On the separate WG PROXYTOP Secrets website you can also include encrypted files, require a separate opening code, or restrict a link to a recipient IP. For protected links, the server retains short-lived verification data and a delivery or revocation status until expiry. In the optional verified handoff, each tab generates a fresh key. The parties compare a code through another trusted channel before sending encrypted text. The service holds the channel state and any waiting ciphertext in memory for up to 15 minutes. The recipient can copy or save the plaintext after opening it.
We do not sell personal data or use it for advertising. Data is used to provide account access, route connections, deliver one-time links you create, support users and investigate service or security problems. Disclosures to providers are limited to these functions or applicable legal obligations. Real cryptocurrency deposits are accepted only where the operator has enabled VPN billing. Each account then receives a permanent public USDT (TRON) deposit address; blockchain transactions to it are independently public, and the portal checks them through TronGrid, which sees the queried deposit addresses but not your browsing, passwords or keys. Paid time is shared with the VPN service only to keep your own profile open until it ends.
WG PROXYTOP’s use and transfer of information received through Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not use browsing data for advertising or unrelated profiling. Human access is restricted to user-requested support, necessary security investigations and applicable legal requirements.
Retention and your choices
The seven-day limit applies to optional WireGuard activity history, not to every record. Optional browser last-activity records are attached to authorization sessions and removed with those session rows. Opted-in browser connection/disconnection audit events, account records, the financial ledger, security/administrative audit and protected backups are retained separately; they do not currently have one automatic deletion deadline. Deletion requests are handled manually after verifying account ownership. We will explain any records retained for security, financial integrity or legal reasons, and the status of backup removal. We do not promise immediate erasure from every backup.
You can disconnect, sign out, revoke service access, remove your own proxy profiles or uninstall the extension. Disconnecting stops new service traffic; it does not erase earlier server records. Removing the extension clears its local storage according to Chrome’s behavior. You can ask support whether optional collection has been enabled for your account and request that it be disabled. Support and deletion requests are available at the address above.
Security and scope
Account APIs and the managed browser gateway use TLS. Administrative access is restricted. HTTP traffic can be readable to a proxy; HTTPS destination content stays encrypted between Chrome and the destination unless you independently install interception software or certificates. This extension routes supported traffic in one Chrome profile, not all applications on the computer. It cannot promise anonymity, hide all browser fingerprints, or prevent every leak caused by browser, device or network failures.