User Data Policies
Last updated
Was this helpful?
Last updated
Was this helpful?
freeRASP collects anonymized security diagnostics data from apps. These data contain:
Application state and security.
Device state and security.
Anonymous app instance ID and device ID.
This information allows Talsec to provide a , improve the freeRASP product and even the , or prepare mobile security reports and articles.
All the data collected by the freeRASP is technical diagnostics information and anonymous, but depending on the regulations applied, it could be considered sensitive and/or personal data.
Talsec recommends adding the statement below to the dedicated privacy policy page of your app. You can also use the text below while filling in the or publishing.
Google Play requires all app publishers to declare how they collect and handle user data for the apps they publish on Google Play. They should inform users properly of the data collected by the apps and how the data is shared and processed. Google will reject the apps which do not comply with the policy.
The checks for the Google Play and details about data are specified above in Privacy Policy Statement.
Apple requires that all app developers disclose their data collection and handling practices for apps published on the App Store. Developers must clearly inform users about the data their apps collect, as well as how this data is shared and processed. Apps that do not adhere to Apple's data privacy guidelines will be rejected.
To comply with the policy, in the App Privacy section, it is important to check the following:
Identifiers -> Device ID -> App Functionality
Talsec Security SDK can not link the device identifier to the user
Diagnostics -> Performance Data -> App Functionality, Other Purposes, No for linking to the user
Diagnostics -> Other diagnostics data -> App Functionality, Other Purposes, No for linking to the user
Other data -> App Functionality, No for linking to the user
Security diagnostics data (such as jailbreak)
Google Playβs User Data policy indicates that a prominent disclosure should be presented to the users in case of an app collecting personal or sensitive data.
Although freeRASP collects diagnostical data (anonymous and not user-related), you (as the app publisher) should consider adding a disclosure screen, describing why the security diagnostic data is needed, what data, and how the data is used.
More about Apple App privacy .
It is an anonymous device identifier for the App vendor as per:
More about Google's best practices for prominent disclosure and consent .