Add a privacy policy
Legally required in most jurisdictions, and a visible honesty signal.
What it means
A privacy policy explains what data you collect and what you do with it. GDPR/CCPA require one if you have any visitors from those regions, and every analytics or ad tool's terms require it too.
Why it matters
Beyond legal exposure, missing privacy policies fail trust reviews, block ad-platform approval, and make the site look unfinished to careful buyers.
How to fix it
- Generate a baseline policy with a free generator (Termly, iubenda, or your national data authority's template).
- Adapt it to reality: list the analytics/ad tools you actually use and any contact form storage.
- Publish it at /privacy and link it in the footer of every page.
- If you use cookies for analytics or ads, add a consent banner (we do — see the banner on this site).
Helpful tools
- Termly
- iubenda
- Google Privacy & Terms generator
Not sure if this affects your site? Analyze your website for free or compare it with a competitor.
Related guides
- Serve the site over HTTPS: The padlock in the address bar — table stakes for trust, SEO, and browser features.
- Fix mixed content warnings: Some assets on your HTTPS page are still loaded over insecure HTTP.
- Add missing security headers: A few lines of server config that block common attacks and remove browser warnings.