A caveat we can’t skip
We are marketers, not lawyers. Below is a breakdown of what we regularly see on clients’ websites and a list of things worth checking on your own. This is not legal advice.
Separately: personal data legislation changed noticeably in 2025, including the amounts of liability. We don’t quote specific fine amounts here — any figure in an article goes out of date faster than the article. Check the current ones in the version of Article 13.11 of the Russian Code of Administrative Offenses currently in force.
Where the banner everyone has came from
The strip saying “we use cookies, by clicking OK you agree” came from European regulation, where the status of cookies and the requirement for explicit consent are spelled out directly.
Russian regulation works differently: it talks not about cookies as such but about personal data — information relating to an identified or identifiable person. When exactly an identifier in a browser becomes personal data is not settled by a single line of law here, and specialists answer the question differently.
The practical conclusion is not “the banner is unnecessary” but something else: the banner on its own does not cover any of the three real obligations. An owner who put up the strip and stopped there has usually done none of what is actually required.
Three obligations of an ordinary website
We are talking about the most ordinary case: a company website with Yandex Metrica and a contact form with “name” and “phone” fields.
1. Notification to Roskomnadzor
A contact form is a collection of personal data, and collection is processing. Under the current rules, a notification of intent to process personal data is filed before processing begins, through the regulator’s portal.
The exemptions owners used to cite — “we only have a business-card site”, “we only process our own employees’ data” — have almost disappeared after the 2025 changes. This is the most frequently missed of the three: almost everyone puts up some kind of policy, but only a minority file the notification.
2. Personal Data Processing Policy
The document must be published and accessible — in practice, linked from the footer of every page. The requirement is specifically about accessibility: a policy buried somewhere deep in the site with no links to it is considered unpublished.
And separately: the policy must describe your actual processing. A downloaded template that still has someone else’s name, someone else’s purposes and someone else’s list of data is worse than none — it documents a mismatch.
3. The person’s consent
Consent must be specific, informed and conscious. On a website this is checked by eye:
- there is a consent checkbox on every form;
- it is not pre-ticked — the person ticks it themselves;
- there is a link to the policy next to it, and it opens;
- the text next to the form says who processes the data and why.
A pre-ticked checkbox is the most common mistake and the cheapest to fix.
A separate note on Metrica
A counter means that visitor data is processed not only by your company, and this must be reflected in the policy: which services you use and for what purpose.
A second point that comes up less often: if besides Metrica the site uses foreign services — third-party maps, fonts, chats, video hosting — data leaves the country, and cross-border transfer must be reflected separately in the notification.
This is checked not from memory but from the page code: open the source code and see which external addresses the site calls. Owners regularly find services there that a previous contractor connected three years ago.
The cookie strip is the most visible and least significant thing you can do. The notification, an honest policy and an unticked checkbox are invisible to visitors altogether — and those are exactly what you get asked about.
A half-hour check
- Does the policy open from a link in the footer of any page?
- Does the policy state your real name, your purposes and your list of data — or someone else’s?
- Does every form have a consent checkbox, and is it unticked by default?
- Has a notification been filed with Roskomnadzor? If you don’t know, then no.
- Which external services are connected to the site? Check the source code.
- Are any of them foreign?
Six answers make a ready-made task for a developer or a lawyer. The first three items are fixed in an hour, the fourth is a procedure, and the fifth and sixth require a decision worth making deliberately.
What to do with the banner itself
If you have one, let it stay — it does no harm. But check two things: that it doesn’t cover half the screen on a phone and that the text isn’t set in a tiny font. A strip that every visitor sees affects behavior more than people tend to think, and on mobile it often covers a button.
We got caught by this ourselves: our consent strip was set in 14-point type, and on some pages it became the dominant text size. We fixed it to 16.
If there is no banner, its absence alone does not violate the three obligations above. Start with those.