Topic
Consent and privacy
Plain-language notes on consent text, privacy notices, and records of what a visitor was shown.
The articles in this topic are about the words that sit beside a form and the record of what the visitor could see. They explain how to read consent language out loud, how a privacy notice should describe the same activity the form performs, and why a team keeps a copy of the page as it was shown. They are written for operators, not as a legal opinion.
Use them when you are pasting text into a page and you want to know whether the text matches the button, the fields, and the follow-up you actually plan. A sentence that mentions calls, texts, and prerecorded messages is doing something specific. If your team only plans to email, the sentence is broader than the operation. If your team plans to call, a sentence that never mentions calls is too narrow. The match is the point.
Limits
Statutes, carrier rules, and platform terms change, and they apply differently to voice, SMS, and email. Nothing here is a determination that a campaign complies. Have counsel review live copy. Use these guides to arrive at that review with a page whose parts agree with each other.
Read consent language out loud
Consent text should match the call, text, or email you actually plan to send. Reading it aloud is the fastest audit.
1127 wordsPut a privacy notice on the same page as the form
The notice should describe the fields on that page, who receives them, and how to ask a question. A footer link to the wrong policy does not count.
1053 wordsKeep a record of what the visitor saw
When someone asks what the page said on a given day, you need the page, not a recollection.