PrivSTRUCT: Untangling Data Purpose Compliance of Privacy Policies in Google Play Store

arXiv cs.AI / 4/27/2026

💬 OpinionIdeas & Deep AnalysisModels & Research

Key Points

  • The paper argues that treating privacy policies as flat text causes automated systems to mix different data practices, especially when mapping sensitive data to their intended purposes.
  • It introduces PrivSTRUCT, a structured encoder–decoder framework designed to preserve the document’s logical hierarchy (e.g., section cues) while extracting data-item and purpose information.
  • Experiments against the state-of-the-art PoliGrapher show PrivSTRUCT extracts more than twice the number of data-item and purpose excerpts while retaining developer-defined structural cues.
  • Analyzing 3,756 Android apps, the study finds a transparency gap: developers are more likely to overstate data purposes when using globally defined purposes (20.4% higher for first-party collection and 9.7% higher for third-party sharing).
  • The authors also report that sensitive third-party flows (e.g., sharing financial data for analytics) are often diluted and entangled into generic or unrelated categories, indicating ongoing shortcomings in current purpose disclosures.

Abstract

Existing research typically treats privacy policies as flat, uniform text, extracting information without regard for the document's logical hierarchy. Disregard for structural cues of section headings designed to guide the reader, often leads automated methods to entangle distinct data practices, particularly when linking sensitive data items to their specific purposes. To address this, we introduce PrivSTRUCT, a novel and systematic encoder and decoder combined framework that to untangle complex privacy disclosures. Benchmarking against the state-of-the-art tool PoliGrapher reveals that PrivSTRUCT robustly extracts more than x2 the number of data item and purpose excerpts while retaining developer-defined structural cues. By applying PrivSTRUCT to a large-scale dataset of 3,756 Android apps, we uncover a critical transparency gap: the probability of developers overstating a data purpose is 20.4% higher for first-party collection and 9.7% higher for third-party sharing when they rely on globally defined purposes rather than specific, locally scoped disclosures. Alarmingly, we find that sensitive third-party data flows such as sharing financial data for analytics are frequently diluted and entangled into generic or unrelated categories, highlighting a persistent failure in the current purpose disclosure landscape.