- Assisting app developers in understanding the privacy practices used by their apps and third party libraries
- Establishing standardized privacy policies in the iOS app ecosystem
PrivacyFlash Pro covers provisions of the following laws:
- California Consumer Privacy Act (CCPA)
- California Online Privacy Protection Act (CalOPPA)
- Children's Online Privacy Protection (COPPA)
- General Data Protection Regulation (GDPR).
PrivacyFlash Pro was written by David Baraka (@davebaraka), Rafael Goldstein (@rgoldstein01), Sarah Jin (@sj-in), and Sebastian Zimmeck (@SebastianZimmeck) as an academic project of the privacy-tech-lab at Wesleyan University. Kuba Alicki (@kalicki1) wrote the unit tests.
Installing and Running PrivacyFlash Pro
You can install and run PrivacyFlash Pro from the packaged release or from the source files.
Installing from the Packaged Release
You will find the releases of PrivacyFlash Pro in the releases section. Download the latest one here (you may need to allow downloading the zip file in your browser settings, e.g., under Google Chrome's Downloads settings). Unzip the file
privacyflash-pro.zip and then click the PrivacyFlash Pro icon. You will have to agree to open PrivacyFlash Pro in your macOS security settings. After a few seconds PrivacyFlash Pro should run in your default browser.
Installing from the Source Files
Ensure that Python 3 is installed. PrivacyFlash Pro does not support Python 2. You can check in your terminal if you have Python 3 installed by running
python3. You can get Python 3 on the official Python website.
Clone this repo by
cding into the directory in which you want to store PrivacyFlash Pro and run
git clone [email protected]:privacy-tech-lab/privacyflash-pro.git.
Optional Create and activate a Python virtual environment. Ensure that your Python virtual environment is outside of the
privacyflash-prodirectory to avoid git tracking.
privacyflash-pro/policygeneratordirectory. If you are using a Python virtual environment, run
pip3 install -r requirements.txt. Otherwise, run
pip3 install --user -r requirements.txt. If you continue to get errors, run
pip3 install -r requirements.txt. If you still get errors, run
sudo pip3 install -r requirements.txt.
Run PrivacyFlash Pro with
Using PrivacyFlash Pro's directory navigation, navigate to your iOS Swift project directory (the directory that contains your
You can test PrivacyFlash Pro on the projects in the iOS-sample-projects. For example, you can analyze the AdColony sample project. Start PrivacyFlash Pro, in your browser navigate to the AdColony directory using PrivacyFlash Pro's directory navigation, and click OK to start the analysis. The analysis results should be available within a minute.
If your browser does not connect to the localhost, try disabling any antivirus software (e.g., eset) that you may be running.
PrivacyFlash Pro analyzes iOS app source code in Swift and third party libraries in Swift and Objective-C. The library analysis works for uncompiled and compiled libraries. PrivacyFlash Pro does not analyze iOS app source code in Objective-C.
PrivacyFlash Pro (1.0.2) was tested to run on macOS Catalina (10.15.5) and the Brave Browser (1.9.80, Chromium: 81.0.4044.138 (Official Build) (64-bit)).
PrivacyFlash Pro is from the people for the people. Everyone can contribute. In particular, feel free to open a pull request to add additional privacy practices and third party libraries. You can also make a feature request by opening a new issue with the
feature request label. If you have other ideas or feedback, let us know. We are looking forward to hear from you!
Privacy Practice Analysis
The specification for the privacy practice analysis is contained in
policygenerator/spec/privacy_practices.yaml. PrivacyFlash Pro flags a privacy practice in an app or a third party library if it identifies the use of a relevant API, i.e., all of the following are present for the app or a library:
- PLIST value (e.g.,
- FRAMEWORK import (e.g.,
- CLASS instantiation (e.g.,
- AUTHORIZATION METHOD call (e.g.,
For the analysis of the app code, the AUTHORIZATION METHOD can also be in a library as long as there is ADDITIONAL EVIDENCE (e.g.,
startUpdatingLocation) in the app code. Vice versa, for the analysis of a library, the AUTHORIZATION METHOD can also be in the app code as long as there is ADDITIONAL EVIDENCE (e.g.,
startUpdatingLocation) in the library.
Also, for some practices, for example, Health, an ENTITLEMENT (e.g., com.apple.developer.healthkit) is required. For more details see the privacy_practices.yaml.
Third Party Library Analysis
PrivacyFlash Pro identifies any library integrated in the analyzed app. The specification for the third party library analysis is contained in
policygenerator/spec/third_parties.yaml. PrivacyFlash Pro is using this specification for determining the purpose of a library. A library name is given by its name on CocoaPods. For example,
AdColony has the purpose
Advertising. PrivacyFlash Pro currently identifies the purposes of 300 libraries using the following purpose categories:
Social Network Integration
Note that even if a library is is not contained in
Our unit tests for PrivacyFlash Pro have been built with the Python unittest framework. In order to run the built-in tests for PrivacyFlash Pro, use
python3 -m unittest from within the root directory of your local copy of this repo.
Files and Directories in this Repo
- The latest release of PrivacyFlash Pro is contained in the releases section.
iOS-sample-projects: Sample projects for PrivacyFlash Pro to analyze and test.
policygenerator/: Contains the code of PrivacyFlash Pro.
policygenerator/interface: Contains all code related to the user interface for displaying the policy to the user.
policygenerator/spec: Third party and privacy practices specifications.
policygenerator/spec/third_parties.yaml: Contains the specification for ad networks and other third parties.
policygenerator/spec/privacy_practices.yaml: Contains the specification for detecting privacy practice usage.
policygenerator/src/analysis.py: The module for analyzing the project looks for instances of privacy practice usage.
policygenerator/src/constants.py: The constants class used internally to identify a privacy practice by an index value.
policygenerator/src/evidence.py: The evidence class is used for keeping track of privacy practice usages in an app's files.
policygenerator/src/privacy_practices.py: Loads data from the app project to be analyzed.
policygenerator/requirements.txt: Dependencies of PrivacyFlash Pro.
Third Party Libraries
PrivacyFlash Pro uses the following third party libraries. We thank the developers.