Website security headers: a practical setup guide
What HTTP security headers do, which ones every website should have, how to set them up without breaking features, and how to test them.
How privacy-focused analytics tools differ from traditional analytics, what you gain and lose, and how to choose an approach that fits your legal and business needs.
Privacy-friendly analytics tools measure visits, pages, referrers and conversions without tracking individuals across sites or building personal profiles, often without cookies. They're simpler, lighter and can reduce consent requirements in some jurisdictions. The trade-off is less detail about individual journeys and limited integration with advertising platforms. Many businesses use them alongside, or instead of, traditional analytics depending on their needs.
Traditional analytics tools can collect a lot of detail about visitors, often using cookies and sharing data with advertising systems. That raises privacy concerns, consent requirements and performance costs. Privacy-friendly analytics offers a lighter alternative.
Typical characteristics:
The market includes hosted privacy-focused tools such as Plausible, Fathom and Simple Analytics, open-source and self-hostable options such as Matomo and Umami, and server-side analytics based on log files. Features, pricing and data handling differ, so check each provider's documentation and hosting location.
For many small and medium businesses, that covers most of what they actually look at.
If you rely heavily on paid advertising optimisation, you may still need traditional tools, configured with appropriate consent.
Rules differ by country. In the UK and EU, storing or accessing information on a user's device generally needs consent unless an exemption applies, and data protection law applies to personal data. Recent law changes in some places have introduced exemptions for certain low-risk analytics. Cookieless, non-identifying analytics can reduce consent requirements, but it doesn't automatically remove all obligations. Check current guidance from your regulator and take legal advice where needed.
Privacy-focused scripts are often a fraction of the size of traditional analytics tags. Fewer scripts mean faster pages and fewer third-party connections, which also simplifies security policies. Our guide to website security headers explains why limiting third-party scripts helps.
All analytics have gaps. Ad blockers, privacy settings and consent choices reduce what traditional tools see. Cookieless tools may count some visitors more than once or estimate uniques differently. Compare trends over time rather than obsessing over exact numbers, and cross-check key conversions with your own records, such as orders and form submissions.
Hosted services are easy to set up, with no maintenance. Check where data is stored.
Self-hosted tools give full control over data and location but need servers, updates and security.
Ask:
Some businesses use privacy-friendly analytics as their main tool and add traditional analytics only on specific campaign pages with consent.
Another privacy-friendly option is analysing your server or CDN logs. Logs record every request without any script running in the browser, so they're unaffected by ad blockers. They're less detailed about user behaviour, and bots need filtering out, but they're a useful cross-check on other analytics.
Clear answers make it easier to describe your setup accurately in your privacy policy.
Our web development team sets up analytics that match your needs and legal context, from privacy-focused tools to traditional platforms with consent. Our e-commerce team configures conversion tracking, and our maintenance plans keep tracking working after site changes.
Sometimes not, depending on how they work and your jurisdiction's rules. Check current regulator guidance.
They're accurate enough for trends and decisions, though all analytics tools have gaps from blockers and privacy settings.
Integration is limited. Businesses relying on ad optimisation often use traditional tools with consent for those needs.
This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.
Tell us about your project and get a free, fixed quote.
Get a free quoteWhat HTTP security headers do, which ones every website should have, how to set them up without breaking features, and how to test them.
A comprehensive pre-launch checklist covering content, design, functionality, SEO, performance, accessibility, security, analytics and the launch itself.
What the Jamstack approach is, how pre-built pages and APIs make sites faster and more secure, and when it's the right choice for a business website.