Last updated: 20 October 2026 · Extension version: 0.2.2

Pronet Chrome Extension Privacy Policy

The service provider for this extension is Pronet (AbrPronet). This policy covers the Chrome extension and the AbrPronet services it uses to provide user-selected proxy connectivity for one regular Chrome profile. The bot, subscription purchases and other Pronet apps may have separate data practices and terms.

Information handled

• Account and identification: display name, username, account and Telegram identifiers; a random installation identifier, platform, extension version and device activity timestamps.
• Authentication: pairing code, access and refresh tokens, and temporary proxy credentials.
• Subscription and preferences: selected account and server, subscription usage, allowance and validity, favorites, connection preferences and measured response time.
• Network information: source IP for connection delivery and abuse prevention; destination host/address and request information needed to relay traffic; connection status, timing and errors for verification and recovery.
• Relayed content: ordinary HTTP requests and responses pass through the gateway. HTTPS uses a forwarding tunnel; the gateway does not install an interception certificate or decrypt the destination's HTTPS connection.

Purpose and recipients

Information is used to sign in, authorize subscription access, display accounts and usage, select servers, authenticate the proxy, relay traffic, maintain or recover connectivity, prevent abuse and handle support requests. The extension does not use Chrome's history API or inject content scripts to read pages. Providing a proxy nevertheless involves processing browsing destinations and relaying traffic.

Account and authentication requests go to AbrPronet over HTTPS. Selected traffic traverses the Pronet gateway and the provider server associated with the subscription; hosting and network providers process connection information as part of delivering the service, with their own infrastructure logging and retention practices. Telegram's own policy applies when obtaining a pairing code through Telegram.

Connectivity checks request www.gstatic.com/generate_204, a Google endpoint that receives the source IP of that connection. Account information and login tokens are not sent in that check. The current extension package contains no advertising or page-behavior analytics SDK.

Storage and retention

Chrome extension local storage holds the refresh token, account information, selected account/server, preferences, favorites, installation identifier and latency cache. Session storage holds access tokens, temporary proxy credentials and account/server caches. Logout removes local login/account information, account/server selections and session data. Preferences, favorites, the installation identifier and latency cache can remain until extension data or the extension is removed.

The service keeps account, device, session and subscription records to deliver service, control access and resolve issues. Access and proxy authorizations expire, but expiry does not itself delete service records. Service records and hosting technical data are retained according to operational, security and applicable requirements. Contact support to request access, deletion or information about your account data.

Your choices and security

You can disconnect, change automatic reconnect or direct .ir routing, log out, or remove the extension. Other applications and incognito windows are outside this extension's scope. Local/private destinations remain direct. Direct .ir routing is enabled by default, so those destinations see the IP of your direct connection.

Control requests and Chrome-to-gateway connections use HTTPS. This does not turn ordinary HTTP between an exit server and a destination website into HTTPS. Locally stored extension data relies on the protection of your Chrome profile and device. This policy does not promise separate encryption of all stored data or zero logging across all infrastructure.

While connected, the extension disables non-proxied WebRTC UDP and network prediction and clears its own privacy settings on disconnect. Network request events support proxy authentication and retry handling; they are not used to read page bodies.

Contact and deletion requests

For privacy questions, access or deletion requests, contact support through @abrpronetbot using the Telegram account associated with your subscription, or use the problem-report form. Account-ownership verification may be required. Disconnecting or uninstalling alone does not delete the service account and server-side records. Policy changes are published on this page with an updated date.

The report form receives your selected operating system, subject and the description you submit for handling the report. Visits to this policy and website pages may also produce technical web-server logs containing IP, requested path, time, status and browser information. These website logs are not a history of all proxied browsing. Do not include passwords or active pairing codes in a report.