Zasady ochrony prywatności dodatku Proxy V2Route
Proxy V2Route Autor: VelumArc
Privacy — Proxy V2Route
Proxy V2Route’s use of user data complies with the Chrome Web Store User Data Policy (https://developer.chrome.com/docs/webstore/program-policies/limited-use), including the Limited Use requirements.
Proxy V2Route
Profiles and preferences stay in the browser; imported nodes and their credentials stay in the local companion. These records are not sent to the developer. Browser traffic follows the applied browser proxy. No analytics or result history is collected by the extension.
Export profiles includes the selected nodes' runtime configurations, credentials and resolved predecessor paths in a local JSON download. This also includes nodes scanned from the local client. Import restores those nodes to the destination's private library with new local ports. Unused nodes, subscription URLs and tokens, local installation paths and measurement history are not included. Backups include each profile's last saved route and destination policies, including their addresses and referenced nodes. Saved configurations for its inactive basic, predecessor and chain modes stay in this browser and are not included in the portable backup. Backups are not encrypted; protect the downloaded file and share it only with trusted recipients.
Opening the popup or IP workspace, successfully switching routes, or requesting status triggers bounded exit-IP checks through ipify. Ping0 reports require optional site access. IP tools pre-fill the current browser exit IP; Globalping sends the displayed target to up to three probes in the selected region only after Start, including a China option. Probe availability varies; ICMP loss alone does not establish filtering. Domain checks use GreatFire. FAST.com is a separate embedded speed provider. Each provider receives normal connection data and handles it under its own privacy policy.
Website tests contact only selected, visible public homepages/icons after Start, with four concurrent credential-free requests at most. A response confirms browser reachability, not account access, HTTP success or regional unlocking. Timeouts and browser restrictions may produce an unconfirmed result.
Cloudflare speed tests use small HTTP latency samples and selected 10/50/100 MiB download/upload limits. Both mode transfers up to the selected size in each direction. Per-second rates and final results remain in dialog memory. Closing or hiding the page cancels local tests; already submitted remote measurements may finish at the provider.
Cloudflare
Optional scripting access may be used in a user-visible or background first-party Ping0 tab after a direct report read fails. The extension reads only bounded report text and original website links and never solves challenges, clicks verification controls, logs tokens or exports cookie values. If the background path is unavailable or verification is required, the original Ping0 page opens in a normal tab for the user. Verification remains user-controlled.
A failed popup connectivity check does not prove the selected node is offline: the check endpoint, current browser proxy setting or browser restrictions may fail independently.
In basic, predecessor and chain modes, per-layer diagnostics run a separate temporary local core only after Test is clicked. They contact api.ipify.org through each cumulative path, do not change the active route and delete temporary credentials/configuration after each bounded probe. Results identify a failed path boundary, not proof that a single server is offline.
Node-library tests contact Cloudflare through the selected node and inherited predecessor chain. Full tests transfer the selected 10/25/50/100 MiB in each direction; group totals are shown before starting. Results stay in the open workspace. Temporary authenticated test cores and configuration are removed when the owned native session closes. Node lists and proxy credentials are not sent as test payloads.
Subscription URLs and tokens are saved only in the private companion database. The extension stores only whether user-enabled updates exist and a shared browser alarm. Refresh contacts the subscription provider using the chosen policy; proxy-first attempts direct access only after the proxy attempt fails. The provider receives normal request information, including its subscription token and the network address used to reach it. Updates use the shared browser alarm.
Closing an IP tool unloads its frame and cancels local requests. Chrome uses the browsingData permission to clear HTTP cache and CacheStorage for that tool's exact allowed origin, then waits before reopening. This also affects cached resources from the same origin in other tabs, but does not clear other sites or cookies, passwords, localStorage, IndexedDB or Service Worker registrations. Third-party CDN caches are not included. Firefox cannot safely scope this cache API, so it unloads the tool and reports that cache deletion is unsupported.