Inserting Contracts into ChatGPT Risks Major Fines Under Russia's 152-FZ Personal Data Law
A Russian operator registered in the Roskomnadzor personal data registry (number 24-26-055344) has published a detailed breakdown of risks that arise when contracts are pasted into foreign AI chatbots. The author notes that ordinary supply or transportation agreements routinely contain ФИО of signatories, passport data of individual entrepreneurs, INN numbers, phone numbers and emails of managers and drivers.
These elements remain personal data even when the information is already published in the Unified State Register of Legal Entities. Russian regulator practice holds that public availability does not convert the data into “publicly accessible” for the purposes of the law.
Updated administrative fines after 420-FZ
From 30 May 2025 the following penalties under Article 13.11 of the Code of Administrative Offenses apply to legal entities:
- Part 1 – processing without legal basis or for incompatible purposes: 150–300 thousand rubles
- Part 1.1 – repeated violation: 300–500 thousand rubles
- Part 10 – failure to notify Roskomnadzor of processing: 100–300 thousand rubles
- Part 8 – storage of Russian citizens’ data outside Russia: 1–6 million rubles
Individual entrepreneurs are treated as legal entities for most of these provisions. Million-ruble “leak” fines under parts 12–18 do not apply to a single contract or even several dozen contracts per month.
Cross-border transfer obligations
Any transmission of personal data to an entity located in another country constitutes a cross-border transfer under Article 12 of 152-FZ. Providing access to ChatGPT, Claude, Gemini or DeepSeek is sufficient; no physical file transfer is required. Since 1 March 2023 a separate notification must be filed with Roskomnadzor before such transfers begin. For the United States and the European Union a ten-working-day waiting period applies, during which the regulator may prohibit or restrict the transfer.
In addition, Russian law requires a data-processing agreement with any third party that receives personal data. Standard user agreements of OpenAI, Anthropic or Google do not satisfy this requirement.
Court practice and real incidents
No administrative cases specifically concerning AI chatbots have yet reached public court records. However, on 27 July 2026 the Babushkinsky District Court in Moscow upheld the dismissal of a sales director who uploaded transaction reports and financial data to DeepSeek, ruling that the action amounted to disclosure of trade secrets.
Earlier incidents at Samsung in 2023 demonstrated that source code, meeting transcripts and test sequences were uploaded to ChatGPT within weeks of internal approval, prompting the company to ban external AI tools on corporate devices. A U.S. federal court order in the New York Times v. OpenAI litigation temporarily required preservation of all ChatGPT logs, including deleted conversations, for five months in 2025.
Related articles
EnvSpec Naming Standard Introduces Strict Six-Environment Hierarchy for Zero Trust Infrastructure
The EnvSpec Naming 1.0.0 standard proposes replacing ad-hoc hostnames with a strict hierarchical naming system based on environment, perimeter, system, slot and node. It defines exactly six environments—dev, test, stage, prod, infrastructure and workplace—and treats any test or pilot system processing real data as prod. The model projects names into SPIFFE IDs, Kubernetes namespaces, cloud projects and mandatory tags for automated policy enforcement. Rules prohibit direct communication between different linear environments and require all access from workplace devices through dedicated gateways. The standard is published under CC BY-SA 4.0 and includes machine-checkable criteria for compliance.
Russian Woman Fined 30,000 Rubles and Loses iPhone 11 for Posting AI-Generated Bear Photo
A resident of Duldurga village in Zabaykalsky Krai was fined 30,000 rubles under part 9 of article 13.15 of the Russian Code of Administrative Offenses for publishing an AI-generated image of a bear presented as authentic. The court also ordered confiscation of her iPhone 11 as the instrument of the administrative violation. The woman knew the photograph was fake before posting it, yet the image spread widely online and was even shared by a local Ministry of Natural Resources channel on 10 September. Local authorities used the case to warn residents that publishing neural-network-generated fake images carries real legal consequences. The incident highlights ongoing enforcement of Russian legislation against the distribution of knowingly false socially significant information under the guise of credible reports. Meanwhile, wildlife specialists continue to investigate separate reports of actual bears near populated areas in the region.
Ideco NGFW Novum Earns Highest Customer Rating in Quadrant Technologies Import Substitution Study
Ideco NGFW Novum achieved the top customer score of 6.9 out of 10 in the Matrix of Import Substitution 2026: NGFW research conducted by Quadrant Technologies, surpassing the market average of 6.3 and outperforming seven competing Russian solutions. The study evaluated vendors based on specialized revenue alongside 18 criteria covering product quality and functionality, with ratings provided directly by specialists who deploy and operate the firewalls in production environments. Ideco excelled in 11 parameters above seven points, including administration convenience at 7.9, technical support and partner network at 7.6, Zero Trust segmentation at 7.3, and both integration capabilities and core NGFW functionality at 7.2. Despite strong product scores, Ideco remains in the Development quadrant rather than Leadership due to lower profile revenue volume, positioning the company as a prime candidate for advancement with increased sales and large-scale deployments. Complementary testing by Infosystems Jet laboratory showed Ideco NGFW Novum passing 189 of 242 checks under Methodology 3.0 and becoming the sole participant to complete an eight-hour stress test. The broader Russian NGFW market is shifting away from emergency import substitution toward demands for real-world stability, updates, documentation, support, and usability, with product cost cited as a rejection factor by 37.5 percent of respondents.
Kubernetes Audit Policy Review: Checklist Targets Common Blind Spots in Rules
An experienced Kubernetes administrator shared a detailed review process for audit policies that often remain untouched for years after initial deployment. The 580-line policy was rebuilt using the Kubernetes Threat Matrix from RedGuard as the primary reference. The author highlights recurring issues such as outdated exceptions, missing coverage for new components, and legacy comments that obscure actual security intent. The resulting checklist focuses on principles rather than cluster-specific findings to help other teams perform effective policy audits. Key recommendations address rule completeness, exception management, and periodic full-scale reviews instead of incremental patching. The approach aims to restore audit policies as active security controls rather than accumulated technical debt.