Skip to content

Home

Jump to bottom
Rahmadi Trimananda edited this page Sep 29, 2021 · 23 revisions

OVRseen

The above figure is the overview of OVRseen. It describes the parts of OVRseen as the following.

Network Traffic

  • Traffic collection: (1) we obtain raw data in PCAPNG and JSON.
  • Post-processing: (2) we extract data flows <app, data type, destination>; and (3) we analyze them w.r.t. data types and ATS ecosystem.

Privacy Policy

  • Network-to-policy consistency: (4) we build VR-specific data and entity ontologies, informed both by network traffic and privacy policy text; and (5) we extract collection statements (app, data type, entity) from the privacy policy; (6) using our improved PoliCheck, we map each data flow to a collection statement, and we perform network-to-policy consistency analysis.
  • Purpose extraction: (7) we translate the sentence containing the collection statement into a text segment that Polisis can use to extract the data collection purpose.

The individual Wiki page explains how to run each part of OVRseen in detail. Please also check out the corresponding directories in this repository: OVRseen/network_traffic and OVRseen/privacy_policy.

Please visit the page A Glance at OVRseen to quickly run and see OVRseen in action.

Supplementary Items

We also release supplementary items such as:

  • Supplementary code: we wrote scripts that use Selenium and ChromeDriver to crawl the app stores. Please look into OVRseen/supplementary_code and this Wiki page about our app corpus.
  • Supplementary materials: we also release spreadsheets that contain the lists of top apps that we used during our experiments (we extracted them using the crawler script and selected the top ones based on their reviews/popularity), and the manual validation statistics for both PoliCheck and Polisis. Please have a look at OVRseen/supplementary_materials.
Clone this wiki locally