Privacy

Limited data for controlled browser access

BusinessProxy does not sell browsing data or use it for advertising. We process limited technical data to operate managed-browser proxy sessions, enforce limits and policy, prevent abuse, diagnose incidents, support paid checkout when used, and comply with valid legal obligations.

This policy applies to the BusinessProxy service, including the BusinessProxy browser extension, gateway and web application.

Chrome Web Store · Limited Use

Limited Use disclosure

The BusinessProxy Chrome extension's use and transfer of information received from Google APIs, and of any user data it handles, adhere to the Chrome Web Store User Data Policy, including its Limited Use requirements. Data accessed by the extension is used only to provide and improve the extension's single purpose — managed, browser-scoped access to organization-approved web applications. We do not sell this data, do not use or transfer it for advertising (including personalized, re-targeted or interest-based ads), and do not allow humans to read it except: with your consent, for security or abuse investigation, to comply with applicable law, or as aggregated/anonymized data for internal operations.

Chrome Web Store User Data Policy →

Boundary

Service boundary

BusinessProxy is a controlled browser access service. The browser-extension path is not a device-wide VPN and does not inspect HTTPS page content. It uses domain, port, policy and category metadata to route, limit and filter traffic. Depending on the routing policy configured by your organization’s administrator, the managed session may carry only traffic to approved private apps and work domains, or — when the administrator selects all-browser mode — all traffic from the managed browser profile. In every mode the proxy is scoped to the supported browser profile where the extension is installed; it is not a device-wide VPN. In all-browser mode, destination metadata (domain, port, policy/category result) is processed for all browsed domains, as described in the table below.

Private App Access

Layer-7 alias path

Private App Access uses a Layer-7 alias/reverse-proxy path. That path relays full HTTP requests and responses, including method, path, headers and bodies, between the browser and your connector. Request and response bodies pass through in transit; BusinessProxy does not write them to logs or store them.

Data classes

What is processed

Data typeWhy it is processedLegal basis (GDPR)RetentionShared with
Account email and verification stateLogin, email verification, workspace membership and account support.Contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)): account security and abuse prevention.While the account is active, then according to account deletion and backup policy.Email delivery and infrastructure services.
Authentication data (account password, access and refresh tokens, short-lived proxy session credentials)Authenticate the account, issue and maintain a device-bound proxy session, and authorize requests to the BusinessProxy API.Contract (Art. 6(1)(b)): authenticating you and operating the service.The account password is verified at sign-in and is not stored by the extension in persistent storage; the short-lived proxy password is held only for the active browser session and cleared when the browser closes. Tokens are retained while the session is valid.Infrastructure services only. Never publicly disclosed.
Client IP address of the proxy sessionInherent to operating a proxy: the gateway receives the connecting IP to establish and relay the managed session, enforce regional routing, apply limits and prevent abuse.Legitimate interests (Art. 6(1)(f)): operating and securing the proxy session, regional routing, limits and abuse prevention.Derived session/usage events follow the retention policy (usage events 30 days by default); raw connection logs are rotated within up to 14 days.Infrastructure services only.
Waitlist request details and consent recordsReview access requests, manage the waitlist, reply about availability and, when separately accepted, send product or access updates.Consent (Art. 6(1)(a)) for optional updates; legitimate interests (Art. 6(1)(f)): handling access requests.Until the request is resolved, consent is withdrawn or deletion is requested where legally available.Infrastructure and configured waitlist intake services.
Device ID and proxy session IDSession issuance, heartbeat, revoke, quota enforcement and abuse prevention.Contract (Art. 6(1)(b)): issuing and managing your sessions and devices.Session-linked usage events follow the retention policy; session records are kept while needed for account operation unless deletion is requested and legally available.Infrastructure services only.
Traffic volumeTraffic limits, billing state, capacity planning and quota cutoff.Contract (Art. 6(1)(b)): enforcing plan limits; legal obligation (Art. 6(1)(c)): billing and tax records.Usage events: 30 days by default.Infrastructure services; YooKassa or another configured payment provider when paid checkout is used.
Destination domain, port and policy/category resultPolicy filtering, blocked-event analytics and abuse prevention.Legitimate interests (Art. 6(1)(f)): policy enforcement, security and abuse prevention.Blocked events: 30 days by default.Infrastructure services; local versioned category feed.
Workspace audit eventsAccountability for workspace, connector, private app and admin actions.Legitimate interests (Art. 6(1)(f)): accountability and security review.180 days by default.Infrastructure services only.
Admin/audit IP address, where capturedSecurity, abuse triage and audit accountability.Legitimate interests (Art. 6(1)(f)): security, abuse triage and fraud prevention.Same as the related audit event.Infrastructure services only.
Raw gateway/API service logsOperations, security triage and incident response.Legitimate interests (Art. 6(1)(f)): operations, security triage and incident response.Rotated within up to 14 days.Infrastructure services only.
Browser-proxy HTTPS page contentNot inspected on the browser-proxy path.Not applicable — not processed.Not applicable.Not applicable.
Private App request/response bodiesRelayed in transit on the Layer-7 alias path.Contract (Art. 6(1)(b)): providing access you requested; processed on the organization’s instructions.Not written to logs or stored by BusinessProxy.Infrastructure services involved in service transit.

Data minimization

How we minimize data

Rights, bases and operator

How the law applies

Legal bases (EEA/UK)
Where the GDPR or UK GDPR applies, we rely on: (a) performance of a contract — to provide the managed-access service to you or your organization; (b) legitimate interests — to secure the service, prevent abuse, diagnose incidents and plan capacity, balanced against your rights; (c) consent — where we ask for it, e.g. optional product updates (you may withdraw it at any time); and (d) legal obligation — to comply with applicable law and valid legal requests.
Providing your data is optional
You are not obliged to provide personal data. However, some data is required to create an account and operate a managed session (for example, email, authentication data, device and session identifiers); without it we cannot provide the corresponding part of the service. Optional items, such as consent to product updates, can be declined or withdrawn without affecting access to the core service.
Our role (controller / processor)
When you use BusinessProxy through an organization or workspace, that organization is generally the data controller and BusinessProxy (UPRAVTREB LLC) acts as a data processor handling data on the organization’s documented instructions; a Data Processing Addendum is available on request. When you interact with us directly (e.g. account registration, support, billing), we act as a controller for that data.
International transfers
We operate a hybrid model. Personal data of users in the Russian Federation is processed and stored on infrastructure located in the Russian Federation, consistent with applicable Russian data-localization law (incl. Federal Law No. 152-FZ). For other users, personal data is processed on global infrastructure (including edge, database and cache providers) that may be located in the EEA, the United Kingdom or the United States. Where the GDPR applies to a cross-border transfer, we rely on an adequacy decision (Art. 45), appropriate safeguards such as the Standard Contractual Clauses (Art. 46(2)(c)), or, where neither applies, a derogation for a specific situation (Art. 49). A copy of the relevant safeguards is available on request.
U.S. (California and similar)
The categories of personal information we collect are listed in the “What is processed” table above. We do not sell or share personal information as defined by the CCPA/CPRA, so no “Do Not Sell or Share My Personal Information” mechanism is required, and we do not use it for cross-context behavioral advertising. California residents may request to know, delete or correct personal information and may use an authorized agent; we will not discriminate against you for exercising these rights. To exercise CCPA rights, contact privacy@business-proxy.com.
Security
Data in transit between the extension and the BusinessProxy API and gateway is protected with TLS/HTTPS. Stored service data is protected by the security controls described in the security model and the hosting environment. Short-lived session credentials are kept only in volatile session storage in the browser and are not persisted. See our security model for details.
On-device diagnostics
The extension stores limited diagnostic information (such as connection events and timestamps for approved Private App hosts) locally in your browser to help you and your administrator troubleshoot access. This diagnostic data remains on your device and is not transmitted to BusinessProxy.
Children
BusinessProxy is a business service not directed to children and is not intended for use by anyone under 18. We do not knowingly collect personal data from children.
Data controller / operator
BusinessProxy is operated by UPRAVTREB LLC (OOO «UpravTreb»), OGRN 1247700140973, INN 9709106589, Nizhny Susalny lane 5, bld. 19, Basmanny District, 105064 Moscow, Russia — the operator responsible for processing personal data under Federal Law No. 152-FZ. Privacy contact: privacy@business-proxy.com; general contact: support@business-proxy.com.
Changes to this policy
We may update this policy from time to time. Material changes will be communicated by updating this notice and the date above and, where appropriate, notifying account administrators. Continued use after changes take effect constitutes acceptance.

Processors and hosting

We use sub-processors (infrastructure, database, cache, email and payment providers) that process data on our documented instructions under data-processing terms, within the EEA or under Standard Contractual Clauses where applicable. Sub-processor list →

Disclosure to authorities

We disclose personal data to public authorities only where required by a legal obligation or to establish, exercise or defend legal claims, and we review requests for validity and scope before responding. Lawful requests →

Your rights

Your rights, by article

Subject to applicable law, you have the following rights. To exercise them, email privacy@business-proxy.com from the email associated with your account; we verify the request before acting. You may also lodge a complaint with a supervisory authority — Roskomnadzor in the Russian Federation, or your local data protection authority in the EEA/UK. Where you use BusinessProxy through an organization, please direct requests to that organization; we support them as processor.

Do you sell browsing data?

No. BusinessProxy does not sell browsing data or use it for advertising.

Do you inspect HTTPS content?

Not on the browser-proxy path. Filtering there is based on domain, port, policy and category metadata. Private App Access is different: the alias path is Layer 7 and relays full HTTP requests and responses in transit.

How do I request deletion?

Contact privacy@business-proxy.com from the email associated with your account. We verify the request before changing account or workspace data.

Questions about privacy or data requests? privacy@business-proxy.com Log retention →

Key terms

Terms used in this policy

Workspace
a logical area where an admin manages users, plan, policy and sessions.
Browser-proxy path
the Layer-1 path through the extension; policy by domain/metadata, no HTTPS decryption.
Private App / alias path
the Layer-7 reverse-proxy path that relays full HTTP to an internal app via a connector.
Gateway
the BusinessProxy access gateway that verifies, scopes, logs and revokes sessions.

Full glossary →

This privacy policy describes how we handle personal data and applies on its own terms. It is complemented by our Terms of Service; in case of conflict regarding privacy, this policy governs the processing of personal data. Terms of Service → Security model →