What consent text a lead form needs
Most lead forms need two different pieces of text, and mixing them up is the most common mistake.
- A privacy notice tells people who you are, what you do with their details, and where to read more. It's information, so it doesn't need a checkbox.
- A consent checkbox asks permission for something the form doesn't need to do its job, such as marketing emails or passing details to another company. It has to be a real choice.
Replying to someone who asked you a question is the reason the form exists, so it usually goes in the notice. A required "I agree to the privacy policy" box doesn't work as consent. People can't refuse it and still get an answer, and GDPR Article 7(4) warns against making a service depend on consent to processing the service doesn't need.
Rules the wording follows
EU and UK GDPR
- Pre-ticked boxes, silence, and inactivity don't count as consent (Recital 32). Every box the generator writes starts unticked.
- Consent asked alongside other matters must be clearly separate from them (Article 7(2)), and each purpose needs its own consent (Recital 32). That's why marketing and partner sharing get separate boxes.
- People must know who is asking and why (Recital 42), and must be told they can withdraw before they agree (Article 7(3)). The labels name the business and say how to unsubscribe.
- The full list of what to tell people when you collect their data is in Article 13. A short notice can't hold all of it, so the notice links to the privacy policy for the rest.
In the UK, marketing emails are also covered by PECR regulation 22. You need prior consent unless the soft opt-in applies: the person gave you their details while buying or negotiating to buy from you, you only market similar products, and you offer an opt-out every time. A new lead from a contact form usually hasn't bought anything yet, so the generator asks for consent.
Canada (CASL)
CASL section 10(1) says a request for express consent must state the purpose and identify who is asking. The CRTC's regulations (SOR/2012-36, section 4) add a mailing address, one more contact method such as an email address, and a statement that consent can be withdrawn. The CRTC also says express consent can't come from a pre-checked box and shouldn't be bundled with agreeing to terms and conditions. When you tick Canada, the generator adds the mailing address line and keeps the marketing box separate.
California (CCPA)
The CCPA mostly relies on opt-outs rather than opt-in consent, but a business covered by it must give a notice at collection. Under the CCPA regulations (§7012), that notice lists the categories of personal information, why you collect each one, whether it's sold or shared, and how long you keep it, with a link to the privacy policy. On a web form, the notice can be a link placed near the fields or the submit button, as long as it goes straight to the section with that information. When you tick California, the notice covers sale and retention, and the checklist reminds you about the link.
Common mistakes
- One box for everything. "I agree to the terms, privacy policy, and marketing" bundles separate choices into one. Split them.
- Making the marketing box required. If the form won't submit without it, people haven't chosen anything.
- "Our trusted partners." People can't agree to share their details with companies they can't see. Name them.
- No record of what people agreed to. GDPR Article 7(1) puts the burden on you to show consent was given. Store the checkbox value with the submission and keep a copy of the wording you used.
- Reusing one client's text for another. The business name, contact details, and partners change per client. UseNew client in the generator to clear them and keep the rest of the settings.
For a wider look at forms and data protection, read our guide tobuilding GDPR compliant forms. If you need a signed consent form rather than a checkbox, seehow to create an online consent form.
Sources
The templates are based on these primary sources. Check them for the full text and any updates.
- GDPR (Regulation (EU) 2016/679): Article 7, Article 13, Recitals 32 and 42
- UK PECR, regulation 22
- Canada's Anti-Spam Legislation (S.C. 2010, c. 23): sections 10 and 11
- Electronic Commerce Protection Regulations (CRTC), SOR/2012-36: section 4
- CRTC Compliance and Enforcement Information Bulletin 2012-549
- California CCPA regulations: 11 CCR §7012, Notice at Collection