01
Common signs privacy information is needed
Contact and quote forms, newsletters, accounts, analytics, booking, payments, chat, uploaded files and recruitment all create information that should be mapped and explained.
02
Small websites still process data
A brochure site may collect names, email addresses, messages, IP-related logs and spam-prevention signals. Small scale does not make the processing invisible.
03
Put information where people need it
Use a full notice plus concise wording beside forms or account creation where appropriate. Avoid vague statements that do not identify purposes or providers.
04
Review the live journey
Compare the notice with form fields, network requests, providers and internal retention practices. Update both documentation and configuration when they diverge.
Practical next steps
Checklist
- 01List every form
- 02Review analytics and embeds
- 03Identify processors
- 04Document retention
- 05Add form-level information
- 06Publish a contact route
Common questions
Questions and answers
Do I need one without analytics?
You may still process enquiries, logs or other personal data.
Can it be in the footer?
A footer link is useful, with additional notice near important collection points where needed.
Does a generator make the site compliant?
No. The actual processing, controls and legal obligations must be reviewed.
Need a considered recommendation?
Discuss the website, not just the symptom.
AHANIX reviews each requirement manually. Technical recommendations may depend on access to the website, hosting or DNS configuration.
Continue learning