Privacy Risks of Opaque Third-Party Software Dependencies

17 concepts10 papers1 proposal

Modern software is rarely written from scratch. Instead, it is assembled from a complex web of third-party Software Development Kits (SDKs), libraries, and modular services. While this modularity accelerates development, it creates a "black box" problem: developers integrate external code to gain functionality—like analytics, ads, or video playback—often without a clear understanding of the data collection mechanisms hidden inside those dependencies.

This research direction explores the privacy friction inherent in the software supply chain, where the opacity of third-party components leads to a systemic gap between intended and actual data practices.

The Black Box Problem

The primary challenge is that third-party libraries often operate with the same permissions as the host application but without the same level of developer oversight. Dexin Liu et al. characterize these SDKs as a critical but opaque part of the software supply chain, identifying pervasive privacy violations in iOS SDKs that are difficult for developers to track or manage.

This opacity creates a significant "awareness gap." In a study of Extended Reality (XR) developers, Jinghuai Zhang et al. and the authors found that developers often fly blind, relying on external infrastructure they cannot audit. This leads to a "diffusion of responsibility," where developers assume that either the platform or the third-party provider is handling privacy, even as sensitive user data leaks through integrated services.

The Transparency Gap

The friction manifests as a transparency gap at two levels: between the developer and the library, and between the application and the user.

  1. Developer Underreporting: Many developers mistakenly believe they are only responsible for disclosing data handled by their own first-party code. Rishabh Khandelwal et al. found that nearly half of Android apps lacked mandatory privacy labels, often because developers failed to account for data collection performed by integrated SDKs.
  2. Misleading User Explanations: Even when transparency mechanisms exist, they are often insufficient. Athanasios Andreou et al. audited Facebook’s transparency tools and found that explanations for targeted ads frequently excluded attributes derived from external data brokers, providing users with a "veneer" of transparency that masks the full extent of third-party data usage.

Accountability and Functional Creep

The scale of this issue is immense. Duc Cuong Nguyen et al. demonstrated that nearly half of all privacy-relevant code changes in mobile apps are attributed to third-party libraries rather than the core application logic. This creates an accountability paradox: users hold the primary developer responsible for the entire app's behavior, yet the developer may not even know which libraries are harvesting data.

Furthermore, the shift toward modular web services has led to "functional creep." Zhan Su et al. observed that educational websites saw a 94.5% increase in tracking over a decade, largely because essential features like audio-video players inadvertently introduced tracking mechanisms. As Tianshi Li argues, traditional privacy frameworks—which focus on first-party data practices—are ill-equipped for this reality, as they assume developers have full control over their application's data lifecycle.

Toward Traceability and Control

To bridge these gaps, researchers are developing automated tools to audit the supply chain and architectural fixes to isolate third-party risks.

  • Automated Auditing: Tools like iHunter (Liu et al.) and SkillVet (Jide S. Edu et al.) use automated traceability analysis to detect when third-party components (like iOS SDKs or Alexa Skills) request permissions that contradict their stated privacy policies.
  • Architectural Protection: Rather than relying on developer awareness, Dolière Francis Somé et al. propose server-side architectures that rewrite web requests to neutralize tracking mechanisms before they reach the third-party provider.
  • Incentivizing Fixes: There is evidence that public pressure works. Duc Cuong Nguyen et al. found that developers respond to security-related user reviews in 76% of cases, suggesting that increasing user awareness of third-party risks can force developers to better vet their dependencies.

Ultimately, addressing supply chain privacy friction requires moving beyond "Privacy by Design" for first-party code and developing robust systems for managing the inherent risks of external software dependencies.

Key Foundational Work

Control What You Include! Server-Side Protection against Third Party Web Tracking (2017) — contributed 1 concept elements to this direction.
Investigating Ad Transparency Mechanisms in Social Media: A Case Study of Facebooks Explanations (2018) — contributed 1 concept elements to this direction.
History & citationVersion 1 · 2026-10-04

Current · Permanent link

View frozen version 1

Cite this direction

Latest version (a living page):

@misc{lacuna_supply_chain_privacy_friction_9bf5caa5,
  title = {supply chain privacy friction},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/supply-chain-privacy-friction/rdr_9bf5caa5e22c465c8ca4e2bb5e86e684},
  note = {Latest version of a living research direction; cite a version for a fixed text. Accessed 2026-11-19},
}

This exact version (version 1, frozen text):

@misc{lacuna_supply_chain_privacy_friction_9bf5caa5_v1,
  title = {supply chain privacy friction},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/supply-chain-privacy-friction/rdr_9bf5caa5e22c465c8ca4e2bb5e86e684/v/1},
  note = {Version 1, frozen 2026-10-04. Accessed 2026-11-19},
}
About

These directions overlap with this one through shared papers.

See something wrong? Report a mistake