Data Processing and Cookie Usage Consent (152-FZ)

What this solution does

According to Federal Law No. 152 "On Personal Data," website visitors must be informed about what information is collected about them and provide explicit consent. Personal data includes not only phone numbers and names, but also cookies, IP addresses, and identifiers set by counters and advertising pixels.

Any website built on the 1C-Bitrix platform uses cookies to operate internal mechanisms such as the shopping cart, user authorization, and sorting preferences. In addition, sites almost always have Yandex.Metrica, Google Analytics, VK pixels, Mail.ru, Meta, and other scripts connected, which begin collecting data immediately upon page load, before the visitor makes any decisions. The "Consent for Data Processing and Cookie Usage (152-FZ)" module addresses both tasks: it displays a notification to the visitor and prevents metrics and pixels from running until consent is given.

The solution is universal: texts, buttons, and design can be customized, allowing the banner to be used for other notifications unrelated to cookies.

Module capabilities

The Data Processing and Cookie Consent (152-FZ) module implements a notification with three buttons: Accept, Configure, and Decline. The button set is configurable, allowing the Decline and Configure buttons to be enabled or disabled independently. The notification supports a header, additional explanatory text, and a link to the privacy policy. Five layout options are available: a full-width bar at the bottom, a window centered at the bottom, windows in the bottom-left corner, windows in the bottom-right corner, and a modal window centered on the screen with a darkened background.

The Configure button allows visitors to select cookie categories manually. The system supports three types: mandatory cookies (always enabled and cannot be disabled), analytics cookies, and marketing cookies. Category names, descriptions, and default checkbox states are set in the module settings. The Accept button allows all categories, while the Decline button retains only mandatory cookies.

Metrics and pixels do not load until consent is obtained. Known trackers, including Yandex.Metrica, Google Analytics, Google Tag Manager, VK pixels, Mail.ru and Top.Mail.Ru pixels, Meta, TikTok, X, Pinterest, LinkedIn, Hotjar, Clarity, Criteo, Retail Rocket, and call tracking systems such as Calltouch, Roistat, and Comagic, are converted into dormant tags. The browser does not execute their code or load their resources. After consent is given, tags are activated in their original order. For returning visitors, they are triggered immediately upon page load. Each tracker belongs to a specific category and is launched only when that category is permitted. The list can be extended with custom addresses and code snippets, including chat widgets, interface components, and any third-party scripts. Upon refusal, tracker cookies such as _ym_*, _ga*, and _fbp are deleted.

The admin panel maintains a consent log. Each record includes the date, site address, user decision (accepted, refused, analytics only, marketing only), consent text version, a random browser token, and the page URL. With a specific setting enabled, the system can store the IP address (fully or anonymized), the User-Agent string, and the ID of an authorized user. The Service → Cookie Consent Log section offers filters, a link to all records for a single browser, CSV export, and automatic cleanup based on the retention period.

The module provides consent for personal data processing and cookie usage in compliance with Federal Law 152-FZ.

An admin panel preview is available: on the settings page, a banner window and a category configuration panel open. Field changes are reflected instantly, even before saving settings.

Customizable design. Background, text, header, border, and link colors can be modified. The buttons "Accept", "Configure", and "Decline" are styled independently. Width, margins, font sizes, border radius, shadow, and border thickness are adjustable. The z-index value controls element layering. Appearance animations include fade-in, slide-up from the bottom, and zoom. On mobile devices, a dedicated bottom margin prevents the banner from overlapping the template's bottom panel. The system warns if text-to-background contrast is insufficient upon saving.

Display conditions. The banner can be shown with a time delay and, optionally, after the page has been scrolled by a specified amount. A list of pages where the banner should not appear can be defined. Consent and refusal are stored with separate expiration periods. The "Consent Version" feature allows forcing the banner to appear for all visitors by changing the version number. Any link on the site can be converted into a button to reopen settings, such as a "Cookie Settings" link in the footer.

Key features.

Metrics and pixels do not load until user consent is obtained, ensuring actual data protection rather than a mere visual warning.

The ability to select cookie categories: essential, analytical, and marketing.

The module stores consent and refusal records in the admin panel journal with CSV export capability. A banner preview is available in settings, allowing design adjustments without modifying the site template. The solution is built using pure JavaScript and does not rely on third-party libraries, external fonts, or CDN connections. It supports multisite environments with independent settings for each site. Compatibility includes the Composite system (static HTML cache): the cached page remains identical for all visitors, with automatic cache clearing triggered by configuration changes. PHP version 8.2 or higher is required. Banner styles are isolated from the main site template styles. The module assists in meeting legal requirements but does not guarantee full site compliance with legislation; the content and wording of the notification, privacy policy, and list of used cookies are determined by the site owner.

If “Data Processing and Cookie Usage Consent (152-FZ)” fits the task, General iT can install the module, configure it and verify the result in the project.