10 ways your data is secretly being tracked online | Compilation | #AskFirefox

Summary of the video’s main points

• Health data can leak through third parties (even from “secure” devices). A report cited in the video says over 61 million fitness tracker users had exposed health data because some apps shared data with third-party services that didn’t protect it well. The video emphasizes that Apple Health and Fitbit data were also reportedly leaked, attributing the problem to sketchy partners/integrations, not the wearables themselves.

• Cookies enable tracking—especially third-party cookies. The video explains that cookies store information to improve browsing, but highlights third-party cookies as the real issue: they track what you view across sites and create persistent profiles using unique identifiers stored on servers, supporting targeted ads. It argues the number of third-party cookies has no practical limit, allowing extensive profiling.

• Defenses against third-party tracking (cookie “smashing”). The video recommends practical approaches:

  • Deny/Block third-party cookies
  • Delete cookies regularly
  • Disguise/Use browser extensions that restrict cross-site tracking It also suggests private browsing and using browsers that reduce traditional cookie tracking.

• Use privacy-conscious browsing for online shopping. It advises avoiding checkout directly inside social media apps (e.g., Instagram/TikTok) because doing so can expose sensitive information. Safer behavior suggested: copy the link and complete purchases in a more secure browser.

• Secure connections and reduce snooping on public networks. The video warns that using the internet involves device identifiers like IP addresses, and that traffic can be intercepted via packet sniffing. It recommends:

  • Ensure URLs use HTTPS
  • Use a VPN to protect against interception and reduce exposure

• Algorithms on social media and streaming platforms track you using multiple data types. The video describes how recommendation systems build “profiles” using:

  • Voluntary data (what you subscribe/click intentionally)
  • Observed data (how you interact, e.g., slowing down on an item)
  • Inferred data (educated guesses based on patterns) The core claim: algorithms can feel “creepy” because they rely heavily on your interactions.

• Password storage and authentication hygiene. It warns against storing passwords in easily accessible digital places (like text files/notes apps). It suggests using a physical notebook as an example of a non-digital risk path (with the caveat you must physically protect it).

• Privacy policies for health/therapy and sensitive apps may be weak. The video argues many apps (including mental health/therapy-adjacent and health data services) have privacy practices that may share or enable tracking of sensitive metadata. It specifically mentions policies where tracking of message metadata (not contents) could reveal when you talk to a therapist.

• Email masking to limit spam and data exposure. It recommends using tools like Firefox Relay: generating temporary/fake email addresses that forward to your real one, then disabling them when done—distinct from simple unsubscribe (which may not affect all email types).

• Smart speakers can be triggered—but the “wake word” behavior still raises privacy concerns. The video says smart devices can wake due to false positives (words or TV dialogue resembling wake phrases). It notes microphones may shut off quickly after false activation, but argues that the learning/data from false triggers still exists. Mitigation suggested: mute the mic when not in use, and choose devices emphasizing local storage over cloud.

• Period tracking apps and government requests (post-Roe context). The video claims that period tracking apps, especially free ones with weaker privacy protections, can be vulnerable to government data requests in states where abortion is restricted/illegal. It advises:

  • Read privacy policies (or assume they’re designed to be confusing)
  • Avoid unnecessary data disclosure
  • Use anonymous/guest modes if available

Presenters / contributors

• Firefox / #AskFirefox hosts and contributors (unnamed in the subtitles)
• Said character-style “Cookie Masterson” / “Cookie Smasher” (narration/bit within the video; not a distinct real-name contributor in the subtitles)