Skip to content

Personal-data consent at a website form

Key idea:

A form collecting a name, phone or email must obtain consent before submission: an unchecked-by-default checkbox with a consent wording and a policy link right at the form. The fact of consent is recorded server-side with the date and the exact text the visitor agreed to — otherwise there is nothing to prove it with.

Check your site →

What the form must carry

  • An unchecked checkbox — a pre-ticked one reads as no expression of will in an audit
  • The wording: "I consent to the processing of my personal data" with a policy link
  • The policy link at the form itself, not only in the footer
  • Submission blocked until the box is ticked

An implicit wording ("By pressing the button you agree to the policy…") next to the button is also recognised — scanners, including ours, accept both — but an explicit checkbox is stronger in a dispute.

Ready-made code

<label class="consent">\n  <input type="checkbox" name="pd_consent" required>\n  I <a href="/consent" target="_blank">consent</a>\n  to the processing of my personal data under the\n  <a href="/privacy" target="_blank">policy</a>\n</label>\n\n// server side — record the fact:\n// user id/email, timestamp, IP, consent text version

required is front-end protection only; validate server-side too — forms submit without a browser.

Checking the whole site at once

The compliance scanner finds every PII form across multiple pages and shows which lack a consent element or a policy link — the most common critical finding, with exposure under Art. 13.11(1) (up to ₽300k for legal entities).

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

Is a checkbox needed for a simple callback form?

Yes: a phone number is personal data. Either a checkbox or an explicit wording at the button with a policy link.

One checkbox for consent and newsletter?

No. Processing to answer the request and marketing mail are different purposes — each gets its own checkbox.

What do I store as proof?

Timestamp, visitor identifier (email/phone), IP, and the version of the text the consent was given under.

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.