Home
The above figure is the overview of OVRseen (taken from Figure 1 in our paper). It describes the parts of OVRseen as the following (please consult our paper for more information on each part).
- 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.
- 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.
We also release some 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. This crawler corresponds to the description of app stores and app selection in Section 2 in our paper.
Please see OVRseen's dependencies in the respective Wiki pages for each part:
These dependencies have been taken care of in the provided Ubuntu 20.04.3 LTS virtual machine (VM).