FAQ
BusinessProxy is managed browser access for work browsing. The FAQ states the product boundary, what admins control, what stays outside, and how early-access billing works.
No. BusinessProxy manages browser proxy settings through an extension. The current beta package uses Chrome/Chromium APIs. It does not route your whole operating system. Calls, local apps, personal browsing, banking, and non-browser traffic stay outside the proxy path. It is not an anonymity, unblock, scraping, or evasion tool.
Users install the Chrome extension. There is no device VPN and no OS-level agent. If the Chrome Web Store listing is live, install from that listing; otherwise beta users receive the extension package through the pilot process.
No. Users sign in with account email and password. The backend issues separate, random, short-lived proxy credentials for each session. The account password is never reused as the proxy credential.
On the browser-proxy path, no. There is no TLS interception and HTTPS page content is not decrypted. Filtering uses domains, network metadata, configured allow/deny rules, and a versioned category list. The alias/private-app path is different; see the next answer.
The alias path is a Layer-7 reverse proxy. It terminates the external request at the BusinessProxy gateway and relays the full request and response to your connector: method, path, headers, and request/response bodies pass through in transit. We process metadata for routing, policy, and audit; request and response bodies are not logged or retained.
Private App Access is beta and sales-assisted. If beta access is enabled, email us about a pilot at support@business-proxy.com. It is not a self-serve product.
Admins can revoke active sessions from the account. Proxy credentials are short-lived by default, so access also expires naturally when credentials are not refreshed.
BusinessProxy records operational and audit events needed to run the service: account, workspace, session, device, policy, usage, and admin-event metadata. On the browser path, HTTPS page content is not decrypted. See the log-retention page for retention periods.
Paid plans are activated with a one-time payment through Robokassa. Plans do not auto-renew during early access. When your paid period ends, renew manually from your account. The price, period, and currency are shown before payment.
The managed path is browser-extension based. The current beta package supports Chrome/Chromium desktop through the BusinessProxy extension. Firefox, Safari, mobile browsers, Edge Add-ons, and OS-wide routing are not supported.
BusinessProxy controls the browser path it manages. On unmanaged devices, users can still use other browsers or unmanaged profiles outside the product boundary. For enforced deployments of the current Chrome/Chromium package, use Chrome Enterprise or MDM to require the extension and lock managed settings.