Privacy notices vs cookie banners: what customers expect to see
Short answer: A privacy notice explains what you collect and why; a cookie banner is only one UX pattern for consent or transparency—what you need depends on your tools and legal advice.
NZ customers increasingly expect plain English, not walls of legalese copied from overseas templates.
What a useful privacy notice covers
- Who you are and how to contact you about privacy.
- Personal information types collected via forms, analytics, ads, and support.
- Purposes, retention, sharing—including typical SaaS subprocessors at a high level.
Cookie banners: avoid theatre
If analytics or ads set non-essential cookies or read similar identifiers, your implementation should match your legal position—blocking scripts until consent where required, not only displaying text while tags still fire.
SEO and trust angle
Clear policies reduce bounce from cautious buyers (B2B, health-adjacent services) and support brand searches where people vet you before calling.
Frequently asked questions
Can I copy a UK GDPR banner verbatim?
Risky—NZ law and your actual data flows may differ. Use counsel for regulated cases.
Do all sites need a banner?
Not always; essential-only sites differ from those running remarketing pixels. Document reality.