Costly Mistakes: How Russian Businesses Risk Millions in Fines for Personal Data Violations
A year after new fines for personal data protection violations came into force in Russia, many entrepreneurs still risk multimillion-ruble penalties from Roskomnadzor. The most frequent breaches involve improper collection, storage, and processing of personal data of Russian citizens.
Violation 1: Using Google Forms
Despite repeated warnings at conferences and webinars, businesses continue to use Google Forms. All personal data must be recorded, systematized, accumulated, stored, and processed using databases located on Russian territory under Part 5 of Article 18 of the Law on Personal Data. Googleβs servers are located outside Russia, violating localization requirements. Recommended fix: replace with domestic alternatives such as Yandex Forms. Fines range from 30,000β50,000 rubles for citizens and 1β6 million rubles for individual entrepreneurs and legal entities under Part 8 of Article 13.11 of the Code of Administrative Offenses.
Violation 2: Missing Cookie Banner
If a website uses cookies without displaying a proper banner, it violates the law because cookies qualify as personal data. The recommended banner text informs users about cookie usage for analytics and links to the privacy policy. Fines start at 10,000β15,000 rubles for citizens and reach 150,000β300,000 rubles for legal entities.
Violation 3: No Consent Under Data Collection Forms
Many sites lack valid consent for processing personal data or link only to a privacy policy instead. Consent must meet requirements of Article 9, including specific purpose, list of data, and validity period, plus a checkbox with linked consent text. Fines are identical to those for missing cookie banners.
Violation 4: Publishing Reviews Without Distribution Consent
Publishing reviews containing personal data without separate consent for dissemination violates Article 10.1. Consent must follow the form approved by Order No. 18, and the privacy policy must disclose processing conditions and any prohibitions set by the data subject.
Violation 5: Missing or Non-Compliant Privacy Policy
Every operator must publish a privacy policy in the site footer and under every data collection form, detailing categories of data, purposes, retention periods, destruction procedures, and third-party recipients per Part 2 of Article 18.1. Fines range from 1,500β3,000 rubles for citizens to 30,000β60,000 rubles for legal entities.
Violation 6: No Notification or Outdated Notification to Roskomnadzor
Operators must notify Roskomnadzor before processing personal data and keep the notification current using the form from Order No. 180 of 28 October 2022. Fines reach 100,000β300,000 rubles for legal entities.
Violation 7: Transferring Employee Data Without Separate Written Consent
Employers may not disclose employee personal data to third parties without written consent for each specific purpose, as required by Article 88 of the Labor Code and Part 4 of Article 9. Fines range from 100,000β300,000 rubles for individual entrepreneurs and 300,000β700,000 rubles for legal entities.
Violation 8: No Data Processing Agreement with Third Parties
When personal data are entrusted to third parties (mailing services, etc.), a separate agreement must list the data, operations, purposes, and confidentiality obligations per Part 3 of Article 6. Fines are the same as for missing cookie banners.
Violation 9: No Document on Paper Data Storage Locations
Operators must maintain a document specifying storage locations of paper-based personal data carriers and the list of persons with access, according to Government Resolution No. 687 of 15 September 2008. Fines range from 1,500β4,000 rubles for citizens to 50,000β100,000 rubles for legal entities.
Violation 10: Failure to Respond to Data Subject or Roskomnadzor Requests
Operators must respond within statutory deadlines under Article 21. Appointing a responsible person and maintaining clear internal instructions helps ensure timely replies. Fines range from 2,000β4,000 rubles for citizens to 50,000β90,000 rubles for legal entities.
A comprehensive audit followed by development and implementation of all required documents remains the most reliable way to eliminate these risks and protect profits in 2026.
Related articles
Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks
The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.
Russian Court Convicts Former IT Director for Unauthorized Access to Huawei Storage After Moving Servers Offsite
A former IT director at an Omsk manufacturing plant was found guilty under Part 3 of Article 272 of the Russian Criminal Code for blocking and modifying data on a Huawei Dorado 3000 v6 storage array after relocating the entire server infrastructure to a privately rented office. The court relied heavily on detailed logs from the Huawei system that recorded the exact sequence of disk removals, reinsertions in altered order, and the shutdown command, even after the administrator attempted to delete portions of the event journal. The incident occurred on the same day new management took over, causing immediate loss of access to corporate email, 1C systems, design software, and shared network resources. Despite the defendant's claims that he was preparing the array for cloud backup and that a script had frozen, the court rejected the explanation based on audit concealment, lack of notification to owners, and post-incident behavior. The ruling imposed a 400,000-ruble fine and a one-year ban on computer-information work involving protected secrets, while leaving a civil claim for 18.27 million rubles in recovery costs for separate proceedings. The case highlights how storage-array logs can serve as decisive forensic evidence and underscores the legal risks of retaining physical or logical access after employment ends.
False 50,000 Ruble Fine Claims Circulate About Russia's Unified Bank Card Registry
Social media posts falsely warn Russian citizens of a 50,000 ruble fine for failing to submit personal bank card data to a new unified registry. The claims have been identified as fabricated, with the project "Lapsa Media" noting that the accompanying images were likely generated by AI and contain multiple errors and typos. In reality, individual citizens are not required to take any action, as banks themselves will transmit the necessary information. The Bank of Russia has confirmed that banks must upload card numbers, card types, and owners' INN identifiers to the system operated by NSPK no later than September 1, 2027. Starting on that date, banks will begin enforcing a limit of 20 cards per client to hinder mass issuance of cards for fraudulent purposes. Previously issued cards exceeding this limit will remain valid and will not be forcibly closed.
Webiomed AI Platform Processes Millions of Medical Records Daily on Certified RED OS Infrastructure
The Russian Webiomed platform now serves more than 4,000 medical organizations across 55 regions and supports over 300,000 physicians. Its algorithms analyze up to one million electronic health records every day, generating recommendations that physicians must review and approve. The entire server infrastructure runs on RED OS, which holds FSTEC Russia certification for use in critical information infrastructure. Legal responsibility for any harm remains with the medical organization and, in some cases, the individual physician, even when AI suggestions are involved. The article highlights risks such as incomplete data, synchronization errors that could revoke physician access via RED ADM directory services, and the need for selective recovery tools like Granulex Recovery. Joint testing by MDIS and RED SOFT confirmed that Granulex Recovery can restore specific objects and attributes without stopping the directory service. Questions remain about where liability falls when errors occur at the intersection of the algorithm, medical systems, and underlying IT infrastructure.