
Which data laws apply in Russia in 2026
7 min readUpdated
Federal Law No. 152-FZ governs personal data processing in Russia, while No. 149-FZ addresses information and its protection. Constitutional guarantees are supplemented by liability provisions and sector-specific requirements. The relevant rule depends on the data operation and the participant’s role.
Sources were read on 23 October 2026. The following is a map of selected provisions, not a complete list of changes introduced in 2026. Contracts, processing operations and individual cases were not examined; a legally significant decision requires a review of your circumstances.
Constitution of the Russian Federation: privacy baseline
Article 23 protects private life, personal and family privacy, and the confidentiality of correspondence and other communications. Restrictions on the confidentiality of communications require a court decision. Article 24 prohibits collecting, storing, using or disseminating information about a person’s private life without their consent.
For a particular processing activity, also check the applicable statutory provision. These guarantees do not replace the conditions and exceptions in specific provisions.
| Metric | Result | max | avg | min |
|---|---|---|---|---|
| Ping | —ms | — | — | — |
| Download | —Mbps | — | — | — |
| Upload | —Mbps | — | — | — |
Federal Law No. 152-FZ “On Personal Data”
For each operation, identify its purpose, the data involved and its legal basis. Article 5 requires processing to be limited to predetermined lawful purposes and prohibits excessive data collection. Article 6 lists legal bases, including consent and cases necessary for contractual performance; a contract does not authorise every processing activity.
Article 14 provides for obtaining processing information and requesting correction, blocking or destruction under its stated conditions. It is not an unconditional right to delete every record. The request procedure appears below.
Article 19 requires the operator to take or ensure legal, organisational and technical protective measures. For an incident covered by Article 21(3.1), the supervisory authority must be notified within 24 hours and receive the internal investigation results within 72 hours of detection.
These deadlines concern the provision’s specified unlawful or accidental data disclosure resulting in a violation of rights. Do not apply them to every technical failure without checking the statutory conditions.
How Consent Is Documented
Under Article 9, consent must be specific, informed and unambiguous. It must be documented separately from other information and documents that the person confirms or signs. The law does not require written consent in every case; check the applicable provision.
Withdrawing consent does not always end processing. The operator may continue where statutory grounds permit it.
Localisation When Collecting Data
When collecting Russian citizens’ data, including online, Article 18(5) prohibits using databases outside Russia for recording, systematisation, accumulation, storage, updating and retrieval of that data. The provision specifies exceptions in Article 6(1), points 2, 3, 4 and 8.
Do not reduce the rule to one initial recording or only to services provided in Russia. Check any exception and the particular processing arrangement separately.
Cross-Border Transfers
Article 12 sets separate requirements for cross-border transfers. Before starting this activity, the operator must notify the supervisory authority of its intention to transfer data; this is separate from the notification under Article 22.
Check recipient information, the country, the permitted start time and possible restrictions under Article 12. Compliance with localisation alone does not establish compliance with these requirements. Consent does not replace checking the other conditions.
Federal Law No. 149-FZ “On Information, IT, and Information Protection”
Federal Law No. 149-FZ addresses access to information, its dissemination and protection. For an organiser of information dissemination, check Article 10.1; for the prohibited-information register, Article 15.1; for information protection, Article 16.
First identify the participant’s role and the type of information system. An organiser’s duties cannot automatically be applied to every user or website owner. This overview does not assess the lawfulness of a particular resource’s blocking.
Criminal liability: unlawful access and malware (Criminal Code)
| Criminal Code provision | What to check in the text |
|---|---|
| 272 | Unlawful access to protected information and the specified consequences; the provision excludes cases under Article 272.1. |
| 272.1 | Unlawful acts involving computer information containing personal data obtained unlawfully; the conditions of the relevant subsection. |
| 273 | Creating, using or distributing programs or information knowingly intended for the harmful purposes specified in the article. |
Article 274 also addresses violations of operating rules; its first subsection requires the specified consequences and major damage. A password, file or error alone does not establish a criminal offence. Classification depends on the facts and the particular provision’s conditions.
Administrative liability (Code of Administrative Offenses)
Article 13.11 of the Code of Administrative Offences contains distinct personal-data offences. They include processing without a required legal basis, breaches of written-consent requirements, failures to notify and unlawful data disclosure under the conditions of the relevant subsections.
The article also provides sanctions for individuals. The amount depends on the subsection, offender category, repetition and other circumstances. Do not apply one maximum fine to every case; first identify the offence and the version in force on the relevant date.
Sector-specific laws
| Area | Where to check the specific rule |
|---|---|
| Communications | No. 126-FZ: Article 63 on communications confidentiality; Article 64 on operator duties, including retention and provision of information in specified cases. |
| Banking and medicine | Article 26 of Law No. 395-1 on banking secrecy; Article 13 of No. 323-FZ on medical confidentiality. |
| Government and municipal systems | Article 13 of No. 152-FZ and protection requirements under Article 16 of No. 149-FZ. |
Check your sector alongside the general rules. A confidentiality regime does not mean there are no lawful cases for providing information. This table does not replace checking the particular recipient and disclosure basis.
International context
For the GDPR, first check Article 3. EDPB guidance distinguishes processing in the context of an EU establishment’s activities from activities outside the EU directed at people in the EU: offering them goods or services, or monitoring their behaviour in the EU.
Citizenship or residence alone is insufficient for the second criterion. International-transfer requirements must be checked separately. GDPR applicability does not mean Russian requirements can be disregarded; overlapping duties require a review of the particular process.
What end users should notice
- Identify the operator and the activity you want to check. Save the policy, consent and event date.
- Find the operator’s official channel. Check the requirements for an enquiry or request under Article 14(3); do not send identity-document details to an unknown intermediary.
- Request information relating to you: purposes, legal bases, data categories, source, processing and retention periods, recipients and cross-border transfers.
- Save the request and proof of receipt. Information under Article 14(7) is due within 10 working days; an extension of no more than 5 working days requires a reasoned notification.
- If you believe your rights have been violated, use the appeal route under Article 17, through the supervisory authority or a court. Where there are signs of a crime, consider contacting law enforcement separately according to the circumstances.
Article 14(8) provides access restrictions. Withdrawing consent or submitting a request does not guarantee destruction of all data. If you suspect a breach, preserve the facts without publishing other people’s data or documents.
How to Check the Rule for Your Situation
First identify the data operation, the participant’s role and the event date. Then open the relevant provision and check its conditions, exceptions and the effective dates of amendments. Before deciding to start processing, transfer data or pursue a dispute, compare the rule with the documents and actual process; this overview does not establish a particular service’s compliance.
Author: Adam Jensen — Cybersecurity specialist, VPNON