We handle the technical side of Russia’s personal data law: consents are stored the way inspectors will ask for them, trackers don’t load before consent, and forms can’t be sent without a checked box. Works with WordPress, MODX and Laravel.
Since 2025, fines for personal data violations have increased several times over, and Roskomnadzor (Russia’s data protection authority) now inspects ordinary websites: online stores, landing pages with a request form, corporate sites running Yandex Metrica. Formally, it already counts as a violation if Yandex Metrica or the VK Pixel loads before the visitor has given consent.
We make websites that serve users in Russia technically compliant with Federal Law No. 152-FZ (Russia’s personal data law), so that you have proof of who gave consent, when and to which version of the policy, and so that no tracker fires too early. You or your lawyer prepare the policy and consent texts; we make sure the site follows them to the letter.
You need to resolve the findings quickly and provably: the banner, consent storage, tracker blocking, form checkboxes. We treat it as a priority and deliver an implementation report.
It’s easier to build compliance in from the start than to rework the site before an inspection. We install a ready-made module for your CMS and set up consent categories for the services you use.
A “we use cookies” bar with no choice of categories, no consent records and no script blocking doesn’t protect you. We replace it with mechanics that actually work.
CF7 forms, WooCommerce checkout, chats, call tracking, ad pixels, CRM. We take stock of everything that collects data and put it under consent control.
We find every point where personal data is collected: forms, checkout, sign-up, chats, call tracking, analytics, ad pixels, embedded maps and videos. We map what is sent where, and why.
Necessary, functional, analytics and advertising. Users choose; you get a detailed consent record. We adapt the design to your site; the texts are yours.
Yandex Metrica, Google Analytics, the VK Pixel, Top.Mail.Ru, ad network pixels and any third-party scripts physically don’t load until there’s consent for their category.
Checkboxes with links to the policy and the consent text on every form — inquiries, sign-up, checkout. A form can’t be sent without the box checked, and the consent is saved together with the submission.
Every consent is stored on your server with the date, IP address, categories and policy version. CSV export when Roskomnadzor asks. Updated your policy? Consent is requested again.
We document what was done and how: the list of collection points, the blocking setup, where consents are stored. Useful for internal control and for answering a regulator’s inquiry.
The privacy policy, the consent to personal data processing and the notification to Roskomnadzor about the processing are the legal part — you or your lawyer prepare them. We’re responsible for the technical part: making sure the site follows your documents to the letter and can prove it.
We go through the site the way an inspector would: what data is collected, which scripts load before consent, what state the forms and the policy are in. You get a list of findings.
We install our 152-FZ Compliance module for your CMS — WordPress, MODX or Laravel — and set up the categories for your services.
We add consent to every form and to checkout, put trackers, chats and pixels under the banner’s control, and check what data goes to the CRM.
We test the scenarios: refusal, partial consent, withdrawn consent, a new policy version. You get an implementation report.
A cookie banner with 4 categories, consent records with the date and policy version, and scripts and forms blocked until consent. Ready for WordPress, MODX and Laravel. Prefer to implement it yourself? The plugin is available as a standalone product.
We’ll estimate the scope and propose a solution and a timeline. No strings attached.
Discuss a projectTell us about your project — we’ll estimate the timeline and propose a solution
