Online privacy guide

For everyone

• Your browsing leaves a trail — Sites, networks, and Wi‑Fi operators can see where you go and link sessions together. Privacy tools limit what is collected and how easily it is tied back to you.
• Tracking follows you across sites — Third-party cookies, analytics, and embedded widgets build profiles for ads and analytics. A privacy-focused browser blocks or reduces much of that by default.
• Work devices are not personal space — Employers may monitor corporate equipment and traffic. Personal privacy tools on work laptops can violate policy—know the rules before you install anything.
• Breaches and over-collection hurt trust — For businesses, sloppy data handling damages reputation and invites regulatory scrutiny. Privacy posture is risk reduction, not a nice-to-have.
• Small changes add up — Switching browser, tightening search defaults, or using Tor for specific tasks does not require rebuilding your digital life. Start with one habit and expand.

When you browse the web, several parties can observe what you do: the sites you visit, your network provider, whoever runs the Wi‑Fi you are on, and—on a work device—your employer’s security tooling. Privacy tools reduce how much of your activity is visible or how easily it can be linked to you.

Privacy is not the same as anonymity. A privacy-focused browser limits tracking and data collection. Anonymity tools such as Tor (The Onion Router) go further by trying to hide who is connecting. This guide covers both, in that order.

For most people, the first practical step is browser choice. Everything else—virtual private networks (VPNs), Tor, messaging apps—builds on that foundation.

Reusing passwords across sites bridges privacy and security risks—see our password management guide for credential hygiene basics.

For businesses — treat privacy as a priority

• Trust is a product feature — Customers, partners, and procurement increasingly ask what you collect, where data lives, and which subprocessors you use. Privacy posture affects deals, not just compliance tick-boxes. This guide complements—not replaces—compliance-aware engineering work on the systems you ship.
• Regulation is a design constraint, not a late audit — EU and UK frameworks (for example the General Data Protection Regulation (GDPR), UK GDPR, and emerging AI rules) reward data protection by design. Engineering teams need room to build that way from the start. This is engineering alignment—not legal advice.
• Incidents are expensive in money and reputation — Breaches, over-collection, and sloppy retention destroy trust faster than features create it. Privacy investment is risk reduction.
• Workplace policy should be deliberate — Blocking every privacy browser by default, while allowing unchecked trackers, sends the wrong signal. Policies should distinguish approved work tools, personal use on personal devices, and clear rules for corporate equipment.
• Recommend sensible defaults for staff — If the organisation cares about privacy, say so: supported browsers, VPN guidance where appropriate, and training on phishing and data handling. The tools in this guide are reputable options—not shadow-IT workarounds.
• What you ship reflects your values — B2B vendors who minimise data, document flows, and test in privacy-hardened browsers are easier for enterprise customers to adopt. Privacy-aware engineering is a competitive advantage.
• Cross-border and vendor due diligence — Where data goes—UK, EU, US clouds, analytics SDKs—matters to customers and regulators. Treating privacy as a priority means asking those questions before launch.

If you want software built with EU and UK compliance constraints in mind, discuss requirements, read our regulatory focus on the homepage, or see compliance-aware engineering for how we embed regulation in system design.