Skip to content
RU

152-FZ on a 1C-Bitrix website

Key idea:

In Bitrix, consents are a stock mechanism, not custom work: the personal-data consents module stores agreement texts, adds the checkbox to web and CRM forms, and records every consent in the database — who signed, when, and under which text revision. The job reduces to configuration: create the agreement, bind it to every form, publish the policy, and audit custom forms built outside the core.

Check your site →

The stock consents module

In the admin area: Settings → Product settings → Agreements. A created agreement attaches to web forms, CRM forms (for Bitrix24), registration and checkout. The key benefit is automatic recording: the consent register keeps the subject, date and text revision — closing the "prove it" question in an audit or dispute.

  • An unchecked-by-default box is an agreement setting — verify it
  • Changing the text creates a new revision; old consents stay bound to theirs

Custom forms — the main hole

The module covers only what goes through it. Hand-built template forms (the header callback, a quiz, a marketer's popup) bypass the consent register: the checkbox is missing or decorative — no consent is recorded anywhere. Links like #SITE_DIR#company/consent/ in unfilled templates also stay as raw macros. Inventory every form on the site, not only the stock ones.

Checking the whole site

The compliance scanner renders pages in a real browser, so it sees Bitrix forms injected by JS — composite mode included. It finds forms without a consent element, pages without a policy link, and counters loading before consent — across several pages in one run.

Related

Cookies Before ConsentWhat is written without permission
Consent BannerIs there an equal Reject option
PII FormsConsent and policy at the form
Projections152-FZ and GDPR grades

Why teams trust us

A–F
grade + 152-FZ/GDPR
3
browser sessions per page
PDF
integrity-signed report
Free
scan without signup

How it works

1

Enter your site URL

2

The scanner opens pages in a browser

3

Get a grade and a fix list

Why check your site for privacy compliance?

Regulators fine sites for processing personal data without consent — and a site starts processing earlier than it seems: analytics, pixels and widgets write cookies the moment the page loads. The scanner shows the auditor's view: what leaves for third parties before consent, whether the banner works, and whether forms collect data correctly.

Real Browser

Three sessions per page: no action, banner accepted, banner rejected.

Trackers and Jurisdiction

Service catalogue: who receives visitor data and in which country.

Policy at Collection Point

The policy link and consent element are checked next to the form, not in the footer.

Signed PDF

Report with an HMAC integrity stamp — hand it to your lawyer or contractor.

Who uses this

Business

preparing for an audit

Lawyers

technical facts for an opinion

Web Studios

client site handover

DevOps

consent regression monitoring

Common Mistakes

Loading analytics before consentA counter in writes cookies before any banner. This is exactly what an audit records.
Banner without a Reject buttonConsent is voluntary only when refusing is as easy as agreeing.
Policy only in the footerThe visitor must see who receives their data at the moment of submission — next to the form itself.
Checking once and forgettingA new widget or tag manager quietly adds trackers. Only a re-check catches the regression.

Best Practices

Delay trackers until consentInitialise analytics from the CMP accept callback, not on page load.
Offer an equal RejectAccept and Reject buttons — same size, same level.
Consent checkbox at every formUnchecked by default, with the processing policy linked right there.
Turn on monitoringA standing watch alerts you when the grade drops — before an auditor notices.

Monitor compliance automatically

Scheduled re-checks with an alert when pre-consent trackers appear on your site.

Sign up free

Learn more

Frequently Asked Questions

We use Bitrix24 forms on the site. Same thing?

Same mechanics: the CRM form gets a consent field with a bound agreement, and the fact is recorded on the Bitrix24 side. Verify an agreement is actually selected in every form.

Consent is recorded, but there is no policy on the site. Enough?

No: the policy is a standalone requirement (Art. 18.1); its absence is a separate offence. Publish the document and reference it from the agreement text.

Do composite mode and caching break the checkbox?

The checkbox itself — no, but test forms in a real browser: a cached page may serve an outdated form without the consent block.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.