How do I write a privacy note beside a form without making unsupported promises?
Quick answer
State only what you have verified: what information the form asks for, what the organization says it uses it for, and where readers can find more details. Use plain language and keep the note beside the form, but do not promise confidentiality, security, deletion, or limited sharing unless current organizational materials support that exact claim. Mark unknown details for review rather than guessing.
The question, the details, the next step.
I need a short privacy note beside a form. How can I make it reassuring without claiming more than I know, and what should I check before drafting?
Aim for clarity, not reassurance at any cost. Say what the form asks for and describe its purpose only when you have confirmed those details. Use direct, ordinary words, and give readers a useful next step, such as where to find the organization’s approved privacy information. W3C privacy principles support presenting privacy-relevant practices in accessible plain language; they do not establish what your organization collects, uses, or promises. [S1] Treat every statement about your organization as something to verify, not something to fill in from assumption.
Start with the current form and official materials describing your organization’s practices. Check the information requested, the stated purpose, and the approved place to send readers for more details. Confirm that the form and those materials still match. If you cannot verify a detail, leave it out or mark it for review.
Could you show me a cautious draft that uses placeholders rather than inventing facts?
Use this as a starting point, replacing each bracketed item only after checking it against current organizational materials:
“ This form asks for [verified information]. We use it for [verified purpose]. For more information about our privacy practices, see [approved privacy information location]. ”
If you cannot verify the purpose or an approved information location, do not silently substitute a guess. Ask the responsible person or team to confirm the wording, or use only the verified portion while the rest is reviewed. Keep the note visibly associated with the form it describes.
What wording should make me pause during review? I want the note short, but readers should still know what to do next.
Flag broad assurances such as “your information is completely safe,” “we never share your information,” or “we will delete it immediately.” These are examples to review, not claims about your organization. Keep them only if current official materials support the exact statement and the appropriate reviewer approves it. Also question vague phrases such as “we use your information responsibly”: they may sound comforting without telling readers what the form is for.
Keep the note focused: identify the information requested, give the verified purpose if available, and point to the approved place for more information. Avoid adding claims about confidentiality, security, sharing, retention, or deletion just to make the note sound complete. If those details matter, ask the responsible reviewer for approved wording. Plain-language presentation is supported by the W3C principles, but that guidance does not verify your organization’s practices. [S1] A concise note can be clear while leaving unconfirmed details out.
Can you give me a final review pass I can reuse?
Read each sentence as a factual claim and ask, “What current official material supports this?” Confirm that any referenced location is approved and current. Then read the note as a form user: can you tell what information is being requested, why it is requested if that purpose is stated, and where to look for more? If not, revise for clarity or request a factual review. Do not treat a clear sentence as proof that its underlying claim is accurate; wording and verification are separate checks.
A practical checklist
List the information the form requests and confirm it against the current form.
Include a purpose only when it is supported by current organizational materials.
Use plain language and keep the note visibly associated with the form.
Remove or verify promises about safety, confidentiality, sharing, retention, and deletion.
Check that any referenced privacy-information location is approved and current.
Mark unknown details for review instead of completing them by assumption.
A few more useful answers
Should I say that the information will be kept confidential?
Only if current official materials support that exact statement and it has been approved for this use. Otherwise, leave it out and ask the responsible reviewer for verified wording.
What if I cannot confirm why the form asks for a particular detail?
Do not invent a purpose. Omit that explanation until the responsible person or team confirms it, and flag the gap for review.
Does plain language establish that the privacy note is accurate?
No. Plain language helps make stated practices accessible, but it does not verify an organization’s practices or establish what it collects, uses, or promises. [S1]
Sources
References used for this guide.
- [S1] W3C Privacy Principles w3.org · Checked