Data residency and processing

Updated 4 November 2026. The main BusinessProxy cloud deployment, including authentication servers and account and session databases, is hosted in Russia. An employee connecting from another country does not move their account there. A shared website address does not mean that account data is replicated worldwide.

• A separate international region, recovery across data centres and deployment in customer infrastructure require a separate agreement. Their scope and availability are confirmed for the specific deployment; registration does not enable them automatically.
• The main deployment location does not describe every external service. Email, payments, support and your corporate identity provider have their own data flows. Details of the processors involved and their hosting locations are available on request.

Location matters for more than names and email addresses. Device, session and corporate account identifiers, IP addresses and activity history may also be personal data. Encryption or replacing a name with an identifier does not by itself remove data-processing obligations.

• Accounts and access: email, workspace membership, assigned permissions, passkey credential details and SSO links.
• A connected corporate directory: employee identifiers, status and groups required by the configured synchronization.
• Sessions and events: connection time, IP address, device, allowed or blocked requests and access revocation.
• Operational copies: backups, logs, diagnostic exports and search results. Their storage location, access and deletion schedule also matter.

• A CMS on its own HTTPS address, Direct mode. The browser retrieves pages directly from your site. The module contacts BusinessProxy for managed-access checks and SSO; the service processes the data associated with those operations.
• A CMS or private application through Gateway. The browser HTTPS connection terminates at the BusinessProxy gateway, which forwards HTTP requests to the application. Page content passes through the gateway, so its location is part of the data-processing arrangement.
• An application inside the company network. The connector establishes an outbound connection to BusinessProxy and delivers requests to the internal server. The application needs no public inbound port. Your organization determines where the application and corporate identity provider run.
• Corporate sign-in. AD FS or another configured provider authenticates the user and sends the configured user attributes to BusinessProxy. The provider location and the attributes it transmits are part of the assessment.

A hosting agreement covers more than the database country. It also matters where servers receive credentials, validate sessions, terminate encrypted connections and process logs, and who can access data for support. Access from another country requires separate assessment even when no backup is moved there.

• Primary storage and backup locations are specified separately.
• The operator and providers, their legal entities, roles and access to data are considered.
• Selecting a browser-proxy exit country does not select an account storage region.

The target BusinessProxy architecture keeps a shared product and familiar sign-in while assigning data and access decisions to an agreed regional deployment. Servers and recovery sites can be added within that deployment. This is the architecture direction; each regional installation requires its own preparation and acceptance.

• The Russian profile calls for customer data storage and server-side processing at agreed locations in Russia.
• An international profile specifies countries, processors and transfer terms. The label “international” does not identify a storage location.
• Deployment in customer infrastructure requires agreement on infrastructure, external dependencies, updates, backups and support responsibilities.

A recovery site must meet the same location requirements as the primary deployment. A shared domain does not authorize automatic movement of accounts or sessions to another country. Recovery time, acceptable data loss and active-session behaviour during an outage are agreed for the selected configuration.

• Private application availability also depends on the connector, application origin and corporate identity provider.
• Separate regions are designed to operate independently. An organization still depends on the availability of the locations permitted to process its data.
• SLA terms depend on the agreement and accepted deployment. This page does not establish additional availability guarantees.

Storage in a selected country and lawful data transfer are separate questions. Russian data requires consideration of collection-localization and cross-border transfer rules. Where GDPR applies, processing grounds and third-country transfer rules must be assessed. US customers require assessment of applicable federal, state and sector requirements, including restrictions on certain sensitive-data transactions. Choosing a data centre alone does not establish compliance with every requirement.

Tell us which country your organization requires and which applications you plan to connect. We will clarify the data flows and propose a deployment. Do not include passwords, keys or personal-data exports in your request.

• Required countries for storage, processing and backups, and whether support access from other countries is permitted.
• Application and data types, corporate identity provider and your organization requirements for service providers.
• User count, expected load and access recovery requirements.