How Do Websites Use My Data? (Best Practices For Data Sharing)

Tanya Wetson-Catt • 30 June 2025

Websites store and use user data in many ways, usually to personalise content, show ads, and make the user experience better. This can include everything from basic data like the type of browser and IP address to more private data like names and credit card numbers. It's important for people to know how this information is gathered, used, and shared. In this piece, we'll talk about how websites use user data, the best ways to share data, and why data privacy is important.


What Is Data Collection on Websites?


It is normal for websites to collect data, which means getting information about the people who use them. This can be done in a number of ways, such as by using cookies, which store information on your computer so that they can recognise you on different websites. Websites also get information from the things people do on them, like when they click, scroll, and fill out forms. This information is often used to improve the user experience by showing them more relevant ads and custom content.


Websites usually gather two kinds of information: first-party data, which comes from the website itself, and third-party data, which comes from outside sources like advertising. First-party data includes things like past purchases and browsing history. Third-party data, on the other hand, could include demographic information or hobbies gathered from other websites.


Not only does the website gather information about its users, but it also shares that information with other businesses. For example, social media sites like Google and Facebook put tracking codes on other websites to learn more about how people use the internet. After that, this information is used to better target ads.


Gathering data brings up important concerns about safety and privacy. People who use the service should know how their information is being shared and used. This knowledge is very important for keeping users' trust in websites.


In the next section, we'll discuss how data sharing works and its implications.


How Does Data Sharing Work?


Data sharing is the process of making data available to multiple users or applications. It is a common practice among businesses and institutions, often facilitated through methods like File Transfer Protocol (FTP), Application Programming Interfaces (APIs), and cloud services. Data sharing can enhance collaboration and provide valuable insights but also poses significant privacy risks if not managed properly.


Understanding Data Sharing Methods


Data sharing methods vary based on the type of data and the parties involved. For instance, APIs are widely used for real-time data exchange between different systems, while cloud services provide a centralised platform for accessing shared data. Each method has its advantages and challenges, particularly in terms of security and privacy.


Challenges In Data Sharing


One of the main challenges in data sharing is ensuring that sensitive information remains secure. Implementing robust security measures, such as encryption and access controls, is crucial to prevent unauthorised access. Additionally, data sharing must comply with privacy laws like GDPR and CCPA, which require transparency and user consent.


Data sharing also involves ethical considerations, such as ensuring that data is used for its intended purpose and that users have control over their information. This requires establishing clear data governance policies and maintaining detailed records of shared data.


In the next section, we'll delve into the best practices for managing user data on websites.


How Should Websites Manage User Data?


Managing user data effectively is essential for building trust and ensuring compliance with privacy regulations. Collecting only necessary data reduces the risk of breaches and simplifies compliance. Websites should also implement secure data storage solutions, such as encryption, to protect user information.


Best Practices for Data Management


  1. Transparency and Consent: Websites should clearly communicate how user data is collected and used. Users should have the option to opt-in or opt-out of data collection, and they should be able to access, modify, or delete their personal information.
  2. Data Minimisation: Collecting only the data that is necessary for the website's functionality helps reduce the risk of data breaches and improves compliance with privacy laws.
  3. Secure Data Storage: Encrypting data both at rest and in transit ensures that it remains secure even if intercepted. Regular security audits and updates are also crucial to prevent vulnerabilities.
  4. User Control: Providing users with tools to manage their data preferences fosters trust and accountability. This includes options to download, edit, or delete personal information.


By following these best practices, websites can ensure that user data is handled responsibly and securely.


In the next section, we'll explore the importance of data privacy and compliance.


Why Is Data Privacy Important?


Data privacy is a fundamental right that ensures individuals have control over their personal information. Organisations must implement processes and controls to protect the confidentiality and integrity of user data. This includes training employees on compliance requirements and using technical tools like encryption and access management.


Data privacy regulations, such as GDPR and CCPA, impose strict penalties for non-compliance. Therefore, it's essential for organisations to develop comprehensive data privacy frameworks that include obtaining informed consent, implementing data encryption, and ensuring transparency in data usage.


Ensuring Compliance


Ensuring compliance with data privacy laws requires ongoing efforts. This includes regularly reviewing and updating privacy policies, conducting security audits, and maintaining detailed records of data processing activities.


Building Trust Through Transparency


Transparency is key to building trust with users. Websites should provide clear and accessible information about how personal data is used and shared. Users should also have easy options to withdraw consent or manage their data preferences.


In the final section, we'll discuss how users can protect their data and what steps they can take to ensure their privacy online.


How Can Users Protect Their Data?


Users can take several steps to protect their data online. Using privacy-focused browsers and extensions can help block tracking cookies and scripts. Additionally, being cautious with personal information shared online and regularly reviewing privacy settings on social media platforms are important practices.


Users should also be aware of the data collection policies of websites they visit. Reading privacy policies and understanding how data is used can help users make informed decisions about their online activities.


Tools For Data Protection


Several tools are available to help users protect their data. VPNs can mask IP addresses and encrypt internet traffic, while password managers can secure login credentials. Regularly updating software and using strong, unique passwords are also essential for maintaining online security.


Educating Yourself


Educating oneself about data privacy and security is crucial in today's digital age. Understanding how data is collected and used can empower users to make better choices about their online activities.


Understanding how websites use and share user data is essential for maintaining privacy and security online. By following best practices for data sharing and privacy, both websites and users can ensure a safer and more transparent digital environment.


Take Action to Protect Your Data


If you're concerned about how your data is being used online, it's time to take action. At our company, we specialise in helping individuals and businesses navigate the complex world of data privacy and security. Whether you need guidance on implementing privacy policies or securing your online presence, we're here to help.


Contact us today to learn more about how you can protect your data and ensure a safer digital experience.

Let's Talk Tech

More from our blog

by Tanya Wetson-Catt 25 May 2026
Browser add-ons have a funny reputation. They feel “small”. A quick install. A tiny productivity boost. A harmless little helper that lives in your toolbar. But in practice, a browser extension is more like a micro-SaaS vendor sitting inside your browser session. It can see what you see, interact with the pages you open, and sometimes access the same cloud apps your business runs on all day. That’s why a browser extension security check matters. Not because every extension is bad, but because it only takes one over-permissioned add-on or one bad update to turn “helpful” into exposure. The good news is you don’t need a 40-page policy to reduce the risk. A simple five-minute check can prevent most extension problems before they start. Why Browser Extensions Are a High-Leverage Risk Browser extensions sit in the most sensitive place in modern work: the browser tab where your staff live all day. That matters because extensions aren’t just “apps”. They’re granted special authorisations inside the browser. That makes them attractive targets and gives them leverage that’s disproportionate to how “small” they feel. UC Berkeley’s guidance says extensions get “special authorisations,” and the more you install, the bigger the attack surface becomes. The risk is often permission-based. OWASP calls out “permissions overreach” as a core problem. Extensions can request more access than they need, including access to “all tabs, browsing history, and even sensitive user data.” When an extension can read and modify what happens in the browser, it can potentially see data in cloud tools, capture what’s typed into forms, or alter content on a page. It’s also a “change over time” risk. A useful extension today can become a different extension tomorrow. The 5-Minute Browser Extension Security Check This browser extension security check is designed to be fast, repeatable, and realistic. It helps staff make safe decisions in minutes without turning every extension into a big IT ticket. Vet the developer like a real vendor If you wouldn’t give a random supplier access to your customer records, don’t give a random extension access to your browser. Start with the basics: Confirm the developer has a real website, support details, and a consistent name across listings Look for a track record (other products, a clear company presence, updates that look normal) Prefer official stores and trusted sources over “download this .zip” links
by Tanya Wetson-Catt 22 May 2026
A fake recruiter message is one of the cleanest social engineering tricks around because it doesn’t look like a trick. That’s why LinkedIn recruitment scams work so well inside real businesses. They don’t arrive as malware. They arrive as a normal conversation that nudges someone toward one small action: click this link, open this file, “verify” this detail, move the chat to a different app. A few simple checks, a couple of hard-stop rules, and an easy way to report suspicious outreach can shut these scams down without slowing anyone down. LinkedIn Recruitment Scams LinkedIn recruitment scams artfully blend into normal professional behaviour. The message doesn’t look like a “cyber attack.” It looks like networking, and it borrows credibility from recognisable brands, polished profiles, and familiar hiring language. At platform scale, the volume is also hard to wrap your head around. Rest of World reports that LinkedIn said it “identified and removed 80.6 million fake accounts” at registration from July to December 2024. A LinkedIn spokesperson claimed “over 99%” of the fake accounts they remove are detected proactively before anyone reports them. Even with that level of detection, enough scam activity still leaks through to reach real employees. That’s especially true when scammers tailor their approach to what looks credible in a specific industry and location. The other reason these scams succeed is that they follow a predictable persuasion pattern: urgency, authority, and a quick push to “do the next step.” The FTC describes scammers impersonating well-known companies and then steering targets toward actions that create leverage. These actions include handing over sensitive personal information or sending money for “equipment” or other upfront costs. Once someone is rushed into treating the process as real, the scam doesn’t need to be technically sophisticated. It just needs the victim to keep moving. The Scam Pattern Most Teams Miss 1. A polished approach on LinkedIn The profile looks credible enough, the role sounds plausible, and the message is written in a professional tone. The job post itself may still be oddly generic, though. Amoria Bond notes that fake job postings often “lack details” and lean on broad language to catch as many people as possible. 2. A quick push off-platform The conversation shifts to email, WhatsApp/Telegram, or a “recruitment portal” link. That shift is important because it removes the built-in friction of LinkedIn’s environment and makes it easier to send links, files, and instructions.

3. A credibility wrapper: “assessment”, “interview pack”, or “onboarding”

Airswift flags link/attachment requests and urgency tactics as common red flags. The story is usually something like: “Download this assessment,” “Review these onboarding steps,” or “Log in here to schedule.” Tag Apps Make decisions visible and repeatable by tagging apps. Microsoft explicitly calls tagging apps as sanctioned or unsanctioned an important step, because it lets you filter, track progress, and drive consistent action over time. 4. The pivot: money, sensitive info, or account takeover Scammers impersonate well-known companies and then ask for things legitimate employers typically don’t: payment for “equipment” or early requests for personal information. Another variation is more subtle: “verification” steps that are really designed to steal identity details or compromise accounts. 5. Pressure to keep moving If someone hesitates, the scam leans on urgency: “limited slots,” “fast-track hiring,” “complete this today.” That’s why Forbes frames the key skill as slowing down and checking details, because the scam depends on momentum. Red Flags Checklist for Staff Here are the red flags to look out for. Red flags in the job posting The role is oddly vague or overly broad. Generic responsibilities, unclear reporting lines, and “we’ll share details later” language are common in fake listings. The company's presence doesn’t match the brand name. Thin company pages, inconsistent logos/branding, or a web presence that feels incomplete are worth pausing on. The process is “too easy, too fast.” If the listing implies immediate hiring with minimal steps, treat it as suspicious. Red flags in recruiter behaviour They push you off LinkedIn quickly. Moving to WhatsApp/Telegram or personal email early is a common tactic. They use a personal email address or unusual contact details. Be specifically cautious of recruiters using free webmail accounts instead of a company domain. They avoid verification. If they dodge basic questions, treat that as a signal, not a scheduling issue Hard-stop requests Any request for money or fees. Application fees, equipment purchases, “training costs”, gift cards, crypto, that’s a hard stop. Requests for sensitive personal info early. Bank details, identity documents, tax forms, or “background checks” before a real interview process is established. Requests for verification codes. If anyone asks you to read back a one-time code sent to your phone/email, assume they’re trying to take over an account. Requests for non-public company information like org charts, internal system details, client lists, invoice processes and security tools. Look out for requisitions for anything beyond what a recruiter would reasonably need. Stop Scams With Simple Defaults LinkedIn recruitment scams don’t succeed because staff are careless. They succeed because the outreach looks normal, the process feels familiar, and the next step is always framed as urgent. The fix isn’t turning everyone into an investigator. It’s setting simple defaults that make scams harder to complete: slow down before clicking, verify the recruiter and role through official channels, keep conversations on-platform until identity checks out, and treat money requests, code requests, and early personal data demands as hard stops.  When those habits are standardised, the scam loses its leverage.
by Tanya Wetson-Catt 18 May 2026
The most dangerous thing in a server room is often the phrase, “Don’t touch that.” It’s usually said with a half-joke and a grimace. It refers to the old box that “still works”, runs something important, and has survived so many fixes and workarounds that nobody feels confident changing it anymore. That’s legacy debt. Not just “old tech”, but old tech that’s become a dependency. It’s the kind that quietly accumulates risk until it turns into downtime, security exposure, or an emergency upgrade at the worst possible time. A legacy debt audit is the fast way to bring that risk back into the light. What Legacy Debt Really Looks Like Legacy debt isn’t “old gear”. It’s old gear that has become normal. It’s the server that runs a critical app, the edge device nobody remembers buying, the workaround that turned into a dependency. Over time, that debt stacks up quietly. Infinite Lambda describes legacy debt as something that “happens even to the best systems,” “silently accruing costs and constraints,” and it can “accumulate basically unnoticed until it is too costly to ignore.” That’s why a legacy debt audit isn’t a theoretical exercise. It’s a visibility exercise to bring the oldest, highest-leverage risks back onto the list of things you actively manage. The security problem shows up when “old” becomes “unpatchable.” The UK’s NCSC guidance on obsolete products says, “Ideally, once out of date, technology should not be used,” and “the only fully effective way to mitigate this risk is to stop using the obsolete product.” If something can’t be updated, weaknesses don’t age out. They sit there, waiting for the wrong day. Legacy debt also looks like basic server hygiene slipping. NIST SP 800-123 frames secure server operations as an ongoing process: “Maintaining the secure configuration through application of appropriate patches and upgrades, security testing, monitoring of logs, and backups…” It also calls out foundational hardening steps like “Patch and upgrade the operating system” and “Remove or disable unnecessary services, applications, and network protocols.” When those basics become inconsistent, legacy debt turns into a reliability and incident-response problem, not just a security one. Finally, legacy debt often hides at the edge. If you have end-of-support internet-facing devices, you’ve got high-leverage risk in the most exposed place. The 3 Oldest Risks to Find First These three categories are where “old” most often turns into outsized risk, because they combine age with leverage: they either sit at the front door, can’t be fixed anymore, or have quietly drifted out of a safe baseline. Risk #1: End-of-support edge devices If you’re looking for high-leverage legacy debt, start at the edge. Firewalls, VPN gateways, routers, and other internet-facing devices are the front door to your environment. When they reach end-of-support (EOS), they don’t just become outdated. They become harder to defend because security fixes stop arriving. What to check in your audit List every edge device (firewall, VPN, router) and the support status for each one Confirm which ones are internet-facing and which services are exposed Identify devices that can’t run the current firmware or no longer receive updates. Risk #2: Obsolete products that can’t be fixed anymore Obsolete products are the purest form of legacy debt: things that are still operating but no longer receive security updates. That means every new vulnerability becomes permanent. In other words, there’s no clever workaround that makes an unsupported system “safe”. There are only risk reductions until you can replace it. What to check in your audit Identify anything past support: server OS versions, appliances, old hypervisors, and line-of-business apps Flag systems that require exceptions, like the ones with old protocols, weak auth, and special firewall rules Find the “business-critical but unsupported” systems. Risk #3: “It still works” servers with neglected basics This is the sneakiest risk because it looks normal. The server is supported. The hardware runs. Nobody’s complaining. But the basics have drifted: patching is inconsistent, unnecessary services are still running, and backups haven’t been proven under pressure. SP 800-123 Guide to General Server Security frames secure server operations as an ongoing discipline, including “patches and upgrades,” “monitoring of logs,” and “backups.” It also calls out core hardening steps like “Patch and upgrade the operating system” and “Remove or disable unnecessary services, applications, and network protocols.” Those are the unglamorous fundamentals that stop small problems from turning into long outages. What to check in your audit Patch reality: what’s the current patch level and how often do updates slip? Service sprawl: what’s running that doesn’t need to be running? Admin and service accounts: where are the broad permissions and shared credentials? Backup confidence: when was the last restore test and did it succeed? Change control: who can make changes, and how are they tracked? Stop Carrying Silent Risk Legacy debt doesn’t announce itself. It sits quietly in the background until the day it becomes downtime, exposure, or an emergency upgrade you didn’t plan for. A legacy debt audit gives you control back by turning “we should deal with that someday” into a shortlist you can act on. Start with the highest-leverage risks: end-of-support edge devices, obsolete products that can’t be patched, and servers where the basics have drifted. Then assign owners, set dates, and move one item at a time from “too scary to touch” to “handled”.  Contact us for help running your next legacy debt audit.