Project

General

Profile

Privacy Policy » History » Version 3

Daniel, 05/07/2021 02:47 PM
Added temporary note stating that phone numbers stored in build properties might be uploaded to us

1 1 Luca
h1. Privacy Policy
2
3 2 Patrick
Last Update: 2018-04-10
4 1 Luca
5
h2. Introduction
6
7 2 Patrick
This document is the privacy policy for the *SnoopSnitch* Android security application. 
8 1 Luca
9 2 Patrick
SnoopSnitch offers users several tests they can use to assess the overall security of their mobile devices. These tests are focused on two areas: 
10 1 Luca
11 2 Patrick
First, SnoopSnitch offers analysis on whether the testing device’s build of the Android mobile operating system is missing security patches. The *primary* goal of this test is to identify if any patches are missing relative to the device’s current security patch level date. Our *secondary* goal is to provide a fact-based incentive to device vendors to further improve their patching processes.
12 1 Luca
13 2 Patrick
Second, SnoopSnitch offers tests to assess whether a device is exposed to attacks or surveillance from the mobile network. Here, the *primary* goal is to help mobile users detect network originated attacks, such as via SS7, SMS, or ISMI catchers. Our *secondary* goal is to provide a fact-based incentive to Mobile Network Operators to better improve the security of their networks. In doing this we also respect your privacy concerns from using the app itself.
14 1 Luca
15 2 Patrick
Please note that the dual feature nature of SnoopSnitch results in different types of action, information collected, and permissions requested, depending on the security tests selected. The Android patch level analysis will work on devices running Android version 5.0 or higher. The mobile network tests will only work on a smaller set of devices (See [[DeviceList]]) and requires root permission using Superuser (SU) access.
16 1 Luca
17 2 Patrick
Here, we specify what kind of information SnoopSnitch is collecting while in operation, and how this information is treated.
18 1 Luca
19 2 Patrick
h2. Privacy Summary
20 1 Luca
21 2 Patrick
By default, we do not collect or transmit any personally identifiable information. 
22 1 Luca
23 2 Patrick
After manually triggering the Android security patch analysis, anonymous results and firmware build details are collected and uploaded to our server.
24 1 Luca
25 2 Patrick
For mobile network security tests, the user may choose to upload detailed event logs, which are encrypted by default. These logs may contain some personally identifiable information, such as phone numbers, GPS locations, IMEI, IMSI or other mobile network data, even though we have implemented methods to remove such information. 
26 1 Luca
27 2 Patrick
We do not share any personally identifiable data with anyone and do not use any advertisements or any other 3rd-party plug-ins that could do so.
28 1 Luca
29 2 Patrick
h2. Google Privacy Ambiguity
30 1 Luca
31 2 Patrick
Even though SnoopSnitch does not collect any personally identifiable data, we cannot guarantee that Google does not. As SnoopSnitch is provided by Google on the Google Play store, we do not know what kind of information is collected from this acquisition and subsequent app installation when using their services. We do know that they provide our Play Store developer account with detailed hardware information about the devices that SnoopSnitch has been installed on. This also includes some crash and error logs. For example, ANR ("Application Not Responding") and FC ("Forced Closed") logs are provided by the Android Operating System. 
32
Alternatively, the pre-compiled APK can be downloaded from the SnoopSnitch open source page https://opensource.srlabs.de/projects/snoopsnitch, you may compile and install the app by yourself following the instructions available on the same web page.
33 1 Luca
34 2 Patrick
h2. Logging of ANR and FC Events
35 1 Luca
36 2 Patrick
If you experience an ANR or FC event while using SnoopSnitch, you may be asked for permission to upload a crash report. If you agree, some information about the crash will be uploaded. This information is designed to not contain any personally identifiable information, but may include information such as the stack trace of what the program was trying to do when it crashed, as well as limited information about your phone's software (such as which version of SnoopSnitch you are using) and the hardware.
37 1 Luca
38 2 Patrick
h2. What information is collected
39 1 Luca
40 2 Patrick
For Android security patch analysis:
41
* SnoopSnitch application version
42
* Detailed information about the device’s firmware build
43 3 Daniel
* Phone numbers stored in your build properties. The build.prop file contains the detailed information about your device's firmware build. This file might contain phone numbers, which will be sent to our servers. In a future SnoopSnitch release those phone numbers will be stripped out and not uploaded to our server
44 2 Patrick
* Patch test results
45
46
For mobile network security tests:
47
* Information provided directly by the user. This may include: 
48
* personal data such as: phone number and email.
49
* Information provided indirectly by the user. This may include: 
50
* hardware details: phone model and processor information. 
51
* software details: detailed AOS, Kernel and SnoopSnitch application versions.
52
* GPS locations, IMEI, IMSI and other mobile network data (LAC,CID, encryption status etc.)
53
* Complete radio network (signalling) traces related to detection events
54
* We may also collect other information intentionally provided to us by the user, for example through the Send Feedback feature. Transfer of these data is not mandatory.
55
*  SnoopSnitch does not use cookies.
56
57 1 Luca
h2. Why is this data collected and how is it used?
58
59 2 Patrick
For Android security patch analysis: 
60
* Efficiently pre-select relevant patch tests for a given device
61
* Improving the SnoopSnitch application and individual patch tests
62
* Provide a fact-based incentive to device vendors to further improve their patching processes
63 1 Luca
64 2 Patrick
For mobile network security tests:
65
* Providing and improving the SnoopSnitch application 
66
* Analyzing and securing mobile networks & services, worldwide
67
* Provide mobile network statistics (through GSMMap) that help us understand how secure various Mobile Network Operators (MNOs) are
68
* Provide statistics of how, where, and when mobile networks are being attacked
69
* Provide a warning to users when their phones and network is being attacked by IMSI catchers and user tracking by SS7 or Silent SMS
70 1 Luca
71
h2. Information sharing
72
73 2 Patrick
Anonymously collected analytics are kept safe on a database while personal data provided by e-mail are used only for users support purposes and nothing else. No data are sold or shared with third party entities or companies.
74 1 Luca
75
h2. Application Permissions
76
77 2 Patrick
SnoopSnitch requests different levels of permissions depending on the types of security tests being conducted.
78 1 Luca
79 2 Patrick
For Android security patch analysis, the level of permissions requested are:
80
* ACCESS_NETWORK_STATE: To check for available network
81
* INTERNET: To download patch tests and upload test results
82
* RECEIVE_BOOT_COMPLETED: To check whether build version has changed since last test
83
84
For mobile network security tests, the level of permissions requested are:
85 1 Luca
* ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION: Allow you to record your location when IMSI catchers and security events are detected
86
* ACCESS_NETWORK_STATE: Is used to check for available network so that up or downloads can proceed
87
* ACCESS_SUPERUSER: To use the non API supported Qualcomm diagnosis interface to capture radio data, you need root access. See below.
88
* CALL_PHONE/ SEND_SMS / RECEIVE_SMS: Needed to make the test calls used to generate the network traffic to be analyzed
89
* GET_TASKS: Retrieve state of helper processes interacting with diagnostic interface
90
* INTERNET: Is used to download new data from gsmmap.org and to upload radio traces and debug logs upon user request
91
* READ/WRITE_EXTERNAL_STORAGE: To allow saving debug/trace logs to your SD card
92
* READ_PHONE_STATE: Used to detect what kind of network you are currently using (GSM,UMTS,LTE etc)
93
* RECEIVE_BOOT_COMPLETED: To start app automatically when phone is restarted 
94
* GET_TASKS: Retrieve state of helper processes interacting with diagnostic interface
95
* WAKE_LOCK: Stop phone from falling asleep during long-running analysis steps
96
97
h2. Root and Superuser access
98
99 2 Patrick
Some SnoopSnitch security tests require root and superuser access to function. However, the app can still be installed and some security tests will function without that level of access. 
100 1 Luca
101 2 Patrick
Android security patch analysis *does not require root access* to function. 
102 1 Luca
103 2 Patrick
Mobile network security tests *require root access* to function. These tests collect data directly from the radio diagnostics interface, they require your phone to be rooted and ask for root permission using Superuser (SU) access. This is required for the mobile security tests to function as the Android API does not provide enough network details for the analysis to be performed. This permission is not a standard Android system permission and is ignored by normal Android devices. It is an informal standard developed by the Android developer community. It allows a program to indicate that it would like to acquire super-user permission. SnoopSnitch does nothing else with this permission. It simply asks for the permission in order to allow command-line tools to run as root. The "su" command is an example of a command that will use this permission.
104
105 1 Luca
h2. What are my opt-out rights?
106
107 2 Patrick
You can easily stop all collection of information by either deleting the application, or disabling the app from the Android OS settings. 
108
You can also limit the scope of uploaded data in the app’s settings.
109 1 Luca
110
h2. Data Retention Policy
111
112 2 Patrick
We will retain user provided data for as long as you use the application and for a reasonable time thereafter. We will retain (user approved) collected information for up to 24 months and thereafter may store it in aggregate (in backups). If you would like us to delete any data provided by you, please contact us at the email below.
113 1 Luca
114
h2. Children
115
116
We do not use the application to knowingly solicit data from or market to children under the age of 13. If a parent or guardian becomes aware that his or her child has provided us with information without their consent, he or she should contact us at the email provided below and we will remove that information from our servers within a reasonable time.
117
118
h2. Security
119
120 2 Patrick
We are concerned about safeguarding the confidentiality of your information. We provide electronic safeguards to protect information we process and maintain. For example, we limit access to this information to authorized persons who need to know that information in order to operate, develop, or improve our application. Please be aware that, although we seek to provide reasonable security for the information we process and maintain, no security system can prevent all potential security breaches.
121 1 Luca
122
h2. Your Consent
123
124 2 Patrick
By using the application, you are consenting to our processing of your information as set forth in this Privacy Policy now and as amended by us.
125 1 Luca
126
h2. Changes
127
128 2 Patrick
This Privacy Policy may be updated from time to time for any reason. You are advised to consult this Privacy Policy regularly for any changes, as continued use is deemed approval of all changes.
129 1 Luca
130
h2. Contact
131
132 2 Patrick
If you have questions or concerns regarding this policy, please contact us via email at snoopsnitch @srlabs.de