Proving data localisation compliance in Russia requires more than internal policy documents. A practical guide for in-house counsel. Make an enquiry.
Foreign companies operating in Russia as data operators face a compliance obligation that is widely understood in outline — personal data of Russian citizens must be stored on servers located within Russian territory — yet the evidentiary dimension of that obligation is consistently underestimated. When Roskomnadzor initiates an inspection, the question is not merely whether the company has localised its data, but whether it can demonstrate that localisation to the standard the regulator applies. Policy documents and internal declarations, standing alone, are insufficient.
The data localisation obligation under Russian personal data legislation applies to any operator — including foreign entities — that collects or processes the personal data of Russian citizens in connection with goods or services offered to individuals in Russia, or that monitors the behaviour of individuals within Russian territory. The rule requires that the initial recording, systematisation, accumulation, storage, modification, and retrieval of such data take place using databases physically located in Russia.
The evidentiary standard applied during Roskomnadzor inspections has become more demanding since the regulator's enforcement powers were significantly strengthened in 2022. An operator must be prepared to demonstrate three discrete matters: first, that a Russian-based database exists and is technically capable of performing each of the data processing operations listed under the applicable legislative framework; second, that the Russian database was used as the primary location for the relevant processing from the point at which data collection began; and third, that any subsequent transfer of data to a database located outside Russia occurred in accordance with the grounds and procedures permitted under Russian personal data legislation.
Regulators distinguish between an operator that maintains a genuine localised processing environment and one that has created a nominal Russian database while routing substantive processing offshore. The distinction is drawn on the basis of technical and documentary evidence, not on the operator's characterisation of its own arrangements.
Note: Roskomnadzor may block access to a foreign company's services in Russia pending compliance, and may refer material to the administrative courts for imposition of fines. These measures do not require a preliminary warning and may be taken on the basis of a desk review of publicly available information, without an on-site inspection. Foreign company legal issue Russia: the absence of a Russian legal entity does not exempt a foreign operator from the obligation or from enforcement action.
In practice, the evidentiary package that an operator should hold — and be capable of producing within the timeframe specified in an inspection notice — comprises the following categories of material.
Technical records are the primary evidential layer. These include infrastructure agreements with the Russian data centre or cloud provider, server configuration documentation showing the geographic location of processing resources, and system logs demonstrating that the relevant data flows have been directed to the Russian environment. Where a global system architecture is used, network topology diagrams identifying the Russian segment are ordinarily required.
Contractual and policy documentation forms the secondary layer. This covers data processing agreements with the Russian hosting provider, internal data processing records identifying the categories of data subject to localisation, and data flow maps prepared to a standard of specificity sufficient to distinguish localised data from data legitimately held offshore.
Governance records are increasingly relevant in desk reviews. Roskomnadzor has in recent matters examined records of internal compliance decisions, including the dates on which localisation arrangements were put in place and the responsible individuals within the operator's organisation. An undated policy that cannot be linked to system implementation records carries limited evidential weight.
For foreign companies operating without a Russian legal entity, a recurring practical difficulty is the absence of a designated Russian point of contact for inspection purposes. Under Russian personal data legislation, the appointment of a representative within Russia is a substantive obligation for certain categories of foreign operator, and the failure to make that appointment is itself an enforceable breach. In-house counsel managing Russian data protection compliance should treat the representative appointment as a precondition to evidential readiness, not as an administrative formality.
Russian court practice in administrative proceedings arising from data localisation enforcement confirms that courts apply a standard of proof closer to a balance of probabilities on the factual question of whether localisation has occurred, but apply a more demanding standard when the operator asserts a specific exemption or exception. The burden of establishing the factual basis for any exception — including the grounds for cross-border transfer — rests with the operator.
For a fuller analysis of data localisation obligations for foreign companies operating in Russia, including the scope of the obligation and the categories of data to which it applies, see Data Localisation Obligations for Foreign Companies in Russia and Ministry of Finance Guidance on Data Localisation. The firm's Data Protection practice page sets out the broader advisory framework.
For in-house counsel reviewing the evidentiary readiness of their Russian data localisation arrangements — make an enquiry: info@vetrovpartners.com |
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