US companies collecting personal data in Russia face strict consent obligations under Federal Law 152-FZ. A guide for in-house counsel. Make an enquiry.
Unlike the predominantly opt-out and legitimate-interest model that US-based general counsel encounter under federal and state privacy frameworks, Russian personal data law operates on a mandatory opt-in basis: processing is prohibited unless a lawful ground exists, and for the majority of processing activities affecting data subjects in Russia, that ground is affirmative, documented consent. US companies operating Russian subsidiaries, running e-commerce platforms accessible from Russia, or processing the personal data of Russian employees and customers through centralised systems face this obligation directly under Federal Law No. 152-FZ. Understanding what Russian consent law requires — and where it diverges from GDPR consent standards that many in-house teams already apply — is the practical starting point for any compliance review.
The threshold question for a US controller is whether Russian law governs any part of its processing operations at all. Federal Law No. 152-FZ applies where personal data of Russian data subjects is collected, recorded, accumulated, stored, clarified, retrieved, used, transferred, depersonalised, blocked, or deleted by any operator, including foreign legal entities, where that processing relates to activities directed at persons located in the territory of Russia.
In practice, this means a US parent company processing the personal data of Russian employees of its subsidiary, managing a customer database that includes Russian residents, or operating a website that collects registration or usage data from Russian users will typically fall within the scope of Russian data protection requirements. The fact that processing servers are located outside Russia does not, as a general rule, remove the obligation — though it does give rise to separate cross-border transfer obligations addressed in Step 4 below.
A US controller should begin its compliance assessment by mapping every data flow in which a Russian data subject appears. Relevant categories include employee data (including HR system records, payroll, and benefit administration), customer and prospect data, contractor and vendor contact data, and website behavioural data where it is linked to an identifiable individual. This mapping exercise is not optional: Roskomnadzor, Russia's data protection regulator, maintains a register of operators and expects companies to have completed this analysis before any incident or audit occurs.
Not all processing under Russian personal data law requires the same form of consent. The baseline rule is that standard processing of general-category personal data requires the data subject's consent — which may, in certain circumstances, be given in electronic form or inferred from conduct, provided the operator can demonstrate its existence. However, Russian law imposes a materially stricter requirement for two categories of data that in-house counsel must distinguish with care.
Special categories of personal data — covering health, racial or ethnic origin, political views, religious or philosophical beliefs, and intimate life data — require written consent as a mandatory form. Similarly, biometric personal data (data characterising physiological and biological features of a person that allow identification) requires a separate written consent that cannot be bundled into a general privacy notice.
The written consent requirement under Russian law is substantively different from a GDPR "freely given, specific, informed and unambiguous indication" standard. Russian law prescribes the minimum content that a written consent document must contain, and courts and Roskomnadzor have held that missing any required element renders the consent void. The prescribed elements are set out in the checklist below.
Before collecting personal data from Russian data subjects, verify that each consent instrument contains the following:
For US controllers relying on electronic consent through web forms, app interfaces, or HR system workflows, the critical point is that the consent screen or document must reproduce these elements — abbreviated or bundled notices referencing a general privacy policy alone will not satisfy Russian law requirements in most audit scenarios.
If your company's current consent forms were designed for GDPR or US state privacy compliance, they are likely to require material amendment before they satisfy Russian law. To have your existing consent documentation reviewed against Russian requirements — make an enquiry: info@vetrovpartners.com |
Once a US controller has identified the personal data categories it processes and the applicable consent standard, the practical task is to produce instruments that meet Russian law requirements in the operational context of an international business. Several structural points arise consistently in this work.
Language. Russian data protection law does not mandate that consent documents be in the Russian language where a foreign data subject is involved, but for Russian-resident data subjects — employees, customers, or users — producing consent in Russian is strongly advisable. Roskomnadzor inspections and judicial proceedings will scrutinise consent documents in the language accessible to the subject. Dual-language instruments are workable where the Russian text is primary and any translation is subordinate.
Bundling and unbundling. Russian law has moved progressively towards unbundled consent — each distinct processing purpose ideally supported by a separate consent act. A global privacy notice that aggregates consent for marketing, HR, vendor management, and website analytics into a single click will face challenge in a Roskomnadzor audit. US controllers with consolidated global notice frameworks should assess whether the Russian-specific consent can be extracted and presented as a distinct instrument without creating operational fragmentation.
Children's data. For data subjects under 18, consent must be given by a parent or legal representative. For children under 14, the representative consent is mandatory for all processing categories. US companies running consumer platforms accessible from Russia should verify that their age-gating and representative consent mechanisms satisfy Russian law, which sets out specific requirements for this scenario.
Retention and audit trail. The operator must be able to produce proof of consent on demand. For US controllers storing records outside Russia, this means ensuring that the consent record — including the date, method, and content of consent given — is retained in accessible form for the period of processing plus a reasonable audit buffer, and that it can be produced in a format legible to Roskomnadzor inspectors.
Cross-border transfer of personal data from Russia to the United States raises a specific compliance layer that operates independently of, but in addition to, the general consent regime. Russian law establishes a procedure for cross-border transfers that US controllers operating Russian data flows must observe.
Under the cross-border transfer framework, operators must notify Roskomnadzor before initiating a cross-border transfer to a foreign state. The notification procedure requires the operator to confirm, amongst other things, the purpose of the transfer, the categories of data to be transferred, the identity of the foreign recipient, and whether adequate data protection standards are maintained in the recipient country. The United States is not on the list of countries recognised by Russia as providing adequate protection, which means transfers to US recipients require the operator to take additional steps — most commonly, reliance on data subject consent to the specific cross-border transfer, or on contractual safeguards assessed by the operator and documented before the transfer occurs.
The critical enforcement risk here is one that US controllers consistently underestimate. An operator that transfers personal data to a US parent or group company in the ordinary course of business — through HR systems, CRM platforms, shared IT infrastructure, or cloud services — without having completed the notification procedure and without a documented lawful basis for cross-border transfer is exposed to enforcement action by Roskomnadzor, which has increased inspection activity in this area in recent periods. The requirement to localise the primary database of Russian personal data within Russia (the localisation obligation under Russian law) compounds this exposure: non-compliant operators may find that both the transfer and the localisation issues arise simultaneously in an audit.
Firms advising US companies with Russian HR, customer, or operational data flows will often need to establish the cross-border transfer compliance position before any audit trigger occurs. To review your company's cross-border transfer arrangements under Russian law — make an enquiry: info@vetrovpartners.com |
Russian personal data law gives data subjects the right to withdraw consent at any time. Withdrawal triggers a specific set of obligations on the operator: processing must cease within a prescribed period from receipt of the withdrawal, and the data must be destroyed or depersonalised within a further defined period unless another lawful ground for retention applies. US controllers whose processing relies principally on consent — rather than on contract performance, legal obligation, or other recognised grounds — face the most acute operational disruption from a withdrawal, because they will lack an alternative legal basis to continue processing.
In practice, US companies should audit their consent-dependent processing to identify where consent is the sole legal ground. Where that is the case, the compliance strategy should either introduce a complementary lawful basis (where one genuinely exists on the facts) or establish operational procedures for the prompt cessation and deletion workflow required on withdrawal.
Data subject requests under Russian law include rights of access, correction, and deletion. A request from a Russian employee or customer must be responded to within the period prescribed by law. US controllers processing data through group systems may face a structural challenge: the data is held centrally outside Russia, response requires coordination across IT and HR functions, and the legal deadline runs from receipt regardless of internal complexity. This is a common gap identified in compliance reviews of US-headquartered groups with Russian subsidiaries.
Roskomnadzor oversight takes several forms: prior notification of processing activities (operators are generally required to notify Roskomnadzor before commencing processing unless an exemption applies), scheduled and unscheduled inspections, and responses to data subject complaints. For US controllers, the most common trigger for regulatory attention is a data subject complaint lodged with Roskomnadzor after a withdrawal request is not handled correctly or a data subject access request is not answered within the prescribed timeframe. Maintaining robust records of consent, withdrawal, and request handling is the primary mitigation.
Q: How long does a valid consent remain effective under Russian personal data law?
A: Russian personal data law does not prescribe a universal maximum duration for consent. Consent remains valid for the period stated in the consent instrument itself, or — where no period is stated — until the data subject withdraws it or the processing purpose is achieved. In practice, Roskomnadzor has scrutinised instruments that specify no validity period at all, treating the absence of a defined term as a potential form defect. The advisable approach for US controllers is to specify a defined validity period in every consent document, with a renewal or reconfirmation mechanism where ongoing processing is commercially necessary. For employee data, consent given at the point of hire should be reviewed when the employment relationship changes materially, as the original scope may no longer cover new processing activities introduced subsequently.
Q: What documents must a US company hold to demonstrate consent compliance in Russia?
A: To demonstrate compliance in a Roskomnadzor inspection or judicial proceeding, a US company should hold: the original consent instrument (or a reliable record of electronic consent, including the version of the consent text presented, the date and time of consent, and the identifier linking the record to the data subject); evidence that the consent met the prescribed content requirements at the time it was given; records of any withdrawal requests and the operator's response, including the date processing ceased; and documentation of the cross-border transfer notification filed with Roskomnadzor where data is transferred to the United States. Records should be held in a form that can be produced in Russian-language proceedings, which may require translation of consent instruments and correspondence. Retention for the duration of processing plus a reasonable additional period is the minimum; where a specific statutory retention period applies, that period governs.
Q: What happens if a Russian data subject withdraws consent from a US-based processor?
A: Withdrawal must be accepted regardless of where the operator is located. Once a valid withdrawal is received, the operator must cease the processing activities that were authorised by the withdrawn consent within the timeframe prescribed by Russian law, and must destroy or depersonalise the data within a further prescribed period unless another lawful ground for continued retention exists — such as a legal obligation to retain records or the necessity of retention for defence of legal claims. For US-based processors, the practical challenge is ensuring that the withdrawal instruction propagates through all systems in which the data is held, including cloud platforms, group IT infrastructure, and third-party processors. Failure to cease processing after a withdrawal, or failure to respond to a data subject within the prescribed period, is the most common basis for Roskomnadzor enforcement action arising from individual complaints.
For in-house counsel managing a Russian subsidiary's data compliance position from a US headquarters — particularly where consent infrastructure was built to US or GDPR standards rather than Russian requirements — an early compliance review avoids the more costly process of remediation under regulatory pressure. To discuss your situation in confidence: 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