Technology companies with Russian users must store personal data on Russian servers. A step-by-step compliance guide for in-house counsel. Make an enquiry.
Unlike the GDPR, which regulates data transfers through a layered system of adequacy decisions and standard contractual clauses, Russian data protection law imposes a direct and absolute localisation requirement: personal data collected from Russian users must be stored on servers physically located within the Russian Federation before any cross-border transfer takes place. For technology and software companies serving a Russian audience — whether through a cloud platform, a mobile application, or a SaaS product — this obligation is operational and immediate. Roskomnadzor, the federal supervisory authority, has demonstrated a willingness to enforce this requirement through website blocking, and the enforcement posture has strengthened materially in recent years. This guide sets out what in-house counsel at foreign technology companies need to understand and do to achieve a defensible compliance position.
Before working through the compliance steps, confirm the following:
If all five items are confirmed, proceed through the steps below in sequence. If your data collection is limited to anonymised or aggregated data with no linkage to identifiable individuals, the localisation obligation does not apply — but this threshold should be verified with counsel, because the definition of personal data under Russian law is broad.
If you are uncertain whether your data processing triggers localisation obligations — make an enquiry: info@vetrovpartners.com |
The localisation obligation applies to personal data of Russian citizens and, by extension, individuals located in Russia at the point of collection. In practice, Roskomnadzor applies the obligation to any operator — regardless of where it is incorporated — that targets or services Russian users. A foreign technology company with no Russian entity but with a Russian-language product or Russian payment processing is treated as an operator subject to Russian data protection law.
The initial step for in-house counsel is to commission a data inventory specific to Russian-user data. This inventory should identify: which data categories are collected, at which system layer they are first recorded, whether that first recording occurs on a Russian server or a foreign one, and which downstream systems receive the data. The inventory does not need to be exhaustive as to global data flows, but it must be precise as to the point of first processing for Russian-user data.
A critical point for technology companies: the obligation attaches at first recording — not at the point of transfer or long-term storage. Cloud architectures that route all data through a non-Russian primary region and only replicate to Russia do not satisfy the requirement. The primary recording location must be a Russian database instance.
Russian data protection legislation, in its current form, requires that the database of initial collection for personal data of Russian users be located in Russia. The categories most relevant to technology and software operators include:
Strictly aggregated analytics data — where individual users cannot be re-identified from the dataset — falls outside the localisation requirement. Many technology companies draw the compliance perimeter here. However, the line between pseudonymised and fully anonymised data is treated narrowly by Russian supervisors, and technology counsel should not assume that pseudonymisation alone removes the data from scope.
Once the data inventory is complete, the next step is to map the current processing architecture against the Russian requirement. This is primarily an engineering and vendor assessment exercise, but in-house counsel must own the outcome as a compliance deliverable.
The architecture review should address four questions. First, where is the initial write operation for Russian-user data taking place today? Second, is that location within the Russian Federation? Third, if not, what is the minimum architectural change required to relocate the initial write to Russia? Fourth, what are the data residency capabilities of your current cloud provider in Russia, and what contractual or regulatory constraints govern that provider's Russian infrastructure?
Major cloud providers have varying positions on Russian data residency. Some offer dedicated Russia regions; others do not. For companies whose primary cloud provider cannot offer compliant Russian hosting, the options are: migration to a provider with a Russian data centre; deployment of a hybrid architecture using a Russian colocation facility for the initial recording layer; or engagement with a Russian cloud operator as a processing sub-contractor, with the foreign operator retaining the controller role. Each option has different implementation timelines, cost profiles, and contractual implications.
For software companies operating a SaaS model, the most common compliant architecture places a Russian database cluster as the primary write endpoint for Russian-user data, with replication to the global system permitted once the initial localisation requirement is met.
Foreign companies that process personal data of Russian users are required to notify Roskomnadzor of their operator status before commencing processing. This notification is submitted through the regulatory portal and requires the operator to specify: the categories of personal data processed, the purposes of processing, the legal grounds for processing, the location of the database used for Russian-user data, and the identity and location of any third-party processors engaged.
For technology companies, the database location field is material — it must identify a server or data centre address within Russia. A foreign address here is not merely non-compliant; it is the primary trigger for enforcement action and potential inclusion on the Roskomnadzor blocking register.
The notification process itself is not technically complex, but several points require legal review before submission. The description of processing purposes must be consistent with the company's privacy notice presented to Russian users. The legal grounds for processing must be mapped correctly — consent is the default, but Russian law recognises additional grounds analogous to legitimate interests and contractual necessity, and these must be characterised accurately. A notification submitted with material inaccuracies can be challenged by Roskomnadzor and may itself evidence non-compliance.
For companies that have been operating in Russia without notification, the priority is to complete the notification concurrently with the technical localisation work, rather than waiting for technical completion. Roskomnadzor views active data collection without notification more seriously than a notification that post-dates the commencement of operations by a short period.
For companies whose Russian data infrastructure is not yet in place, counsel familiar with Roskomnadzor expectations can help sequence the notification and technical workstreams appropriately — make an enquiry: info@vetrovpartners.com |
Once Russian-user personal data has been initially recorded in Russia, the operator may transfer that data to foreign systems, subject to two conditions. First, the transfer must have a valid legal ground — in most cases, this is either the user's explicit consent for the specific transfer or an applicable inter-state agreement. Russia has acceded to the Council of Europe Convention on the protection of personal data, which provides a basis for transfers to states that have also ratified the Convention. For transfers to states that have not ratified, or to the United States, additional arrangements are required.
Second, the transfer must be documented and, in the case of certain categories of sensitive data or large-scale transfers, notified to Roskomnadzor in advance. Technology companies frequently underestimate this requirement, having assumed that once localisation is achieved, the cross-border transfer question is resolved. It is not. The two obligations — localisation and cross-border transfer governance — are parallel and independent.
For SaaS and cloud platform operators specifically, the cross-border transfer question arises continuously: every time Russian-user data is replicated to a foreign data centre, processed by a foreign analytics tool, or accessed by engineering teams outside Russia, there is a potential transfer event. The compliance programme should include a data transfer map specific to Russian-user data and a register of the legal grounds relied upon for each transfer category.
In-house counsel managing a technology company's Russian compliance posture should treat this as an ongoing operational obligation rather than a one-time project. Staff access from non-Russian locations to Russian-user data, customer support ticket processing involving Russian-user data, and third-party integrations all require periodic review.
Roskomnadzor has statutory authority to add non-compliant operators to a register of websites and services subject to access restriction. In practice, this means that Russian internet service providers are required to block access to the company's platform from within Russia. The blocking can be implemented within days of a formal decision and affects Russian users regardless of whether the company has a Russian entity or assets in Russia.
Beyond blocking, the penalty regime for data localisation violations has been substantially strengthened. Fines are applied on a per-violation basis and can be imposed for each instance of unlawful processing. For technology companies with large Russian user bases, the aggregate exposure can be significant. Repeated violations attract higher penalty bands.
In-house counsel should note that the risk is not theoretical: Roskomnadzor has blocked major international platforms for localisation non-compliance, and the political and commercial cost of a blocking event — lost Russian revenue, reputational impact, and the operational burden of restoration — substantially exceeds the cost of prior compliance. The blocking register is public, and inclusion on it is visible to Russian business partners, customers, and regulators in adjacent proceedings.
Companies that have been operating in non-compliance and are now seeking to regularise their position should act before a formal Roskomnadzor investigation is opened. Once an investigation is initiated, the timeline for voluntary compliance narrows materially, and the outcome depends in part on the regulator's assessment of good faith.
Data localisation is not a project milestone — it is a continuing obligation. For technology and software companies, the compliance programme must address three ongoing requirements after initial localisation and notification are complete.
First, privacy notices presented to Russian users must accurately reflect the data processing carried out in Russia. Many technology companies use a single global privacy policy that does not address Russian-specific processing or localisation. Russian data protection law requires that users be informed, in clear terms, of the location of the database in which their data is stored, the purposes for which it is processed, and the categories of third parties to whom it may be transferred. A globally standardised notice that omits these elements does not satisfy Russian requirements and can itself trigger regulatory inquiry.
Second, consent mechanisms for Russian users must meet Russian law standards, which differ from GDPR requirements in several respects. Consent must be specific to each processing purpose and must be capable of being withdrawn independently for each purpose. Bundled consent — a single tick-box covering multiple purposes — is not compliant. For technology products that rely on analytics, personalisation, or targeted advertising, this requires separate consent flows for each processing purpose affecting Russian users.
Third, companies should conduct a periodic internal review — at minimum annually — of their Russian data processing posture. Architecture changes, new product features, new third-party integrations, and personnel changes (particularly in data access roles) can each create new compliance exposure without a systematic review process.
Vetrov & Partners assists foreign technology companies in establishing and maintaining a defensible Russian data compliance programme — make an enquiry: info@vetrovpartners.com |
Q: How long does the Roskomnadzor notification process take, and does it need to be completed before data collection starts?
A: The notification itself can be submitted in a matter of days once the required information is assembled. In principle, Russian data protection law requires that the notification be submitted before data processing commences. In practice, many foreign technology companies begin processing before submitting notification, and Roskomnadzor's enforcement focus has been on localisation compliance rather than notification timing alone. That said, in-house counsel should treat notification as a concurrent workstream with technical localisation — not a subsequent step. A company that can demonstrate that it submitted notification while actively building compliant infrastructure is in a materially better position than one that has done neither.
Q: What documents and records should a technology company maintain to demonstrate localisation compliance?
A: A defensible compliance file should include: the Roskomnadzor notification confirmation, a current data processing inventory identifying the Russian database instance used for initial recording of Russian-user data, a data transfer map with legal grounds specified for each cross-border transfer category, copies of the privacy notices presented to Russian users in the relevant periods, and records of consent collection where consent is the legal ground. Engineering documentation showing the architecture of the Russian data tier — server location, database configuration, and replication settings — is also valuable. Roskomnadzor does not prescribe a specific form for this documentation, but in any enforcement context, the ability to produce it promptly demonstrates good faith and operational seriousness.
Q: What happens to existing Russian-user data that was stored outside Russia before a company became compliant?
A: Russian data protection law does not provide a formal grandfathering mechanism for historical data stored outside Russia. The obligation applies to data currently held and to all future collection. In practice, companies regularising their position should migrate existing Russian-user data to the Russian database instance as part of the localisation project, so that at the point of notification submission the declared database location accurately reflects where all Russian-user data is held. Retaining historical data in a foreign location while collecting new data in Russia creates a split architecture that Roskomnadzor is likely to treat as ongoing non-compliance. The migration timeline should be documented and, if extended, flagged proactively in communications with the regulator.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry