Outside Neutral, Non-compliance |
Does your application automatically pull information from the user or their device without consent? Answer "Yes" if your app automatically collects data from users without asking for consent. Note that for "full informed consent", it should be (a) clearly indicated by a user by performing an action, like checking a box or clicking a button, (b) have specific details on what is being collected and who will be receiving the information, and (b) be freely given without coercion.
Is it possible that this automatic collection may include data that is not needed for the functionality of your application? Answer "Yes" if your app also automatically collect data other than for functionality. Note that for "full informed consent", it should be (a) clearly indicated by a user by performing an action, like checking a box or clicking a button, (b) have specific details on what is being collected and who will be receiving the information, and (b) be freely given without coercion. |
+ Rectification/erasure (U.2.3), Preferences (U.2.1) |
Data Reduction, Transparency and Disclosure |
@@ -281,6 +310,7 @@ The questions are categorized by
Inside Neutral, Non-compliance |
If the application sends data to third parties, do you have a data loss prevention (DLP) control mechanism in place? Answer "Yes" if your app sends data to third parties and it deploys a DLP mechanism. A DLP mechanism, like an email filter for example, prevents unexpected and uncontrolled loss of internal data. |
+ Predetermined set of parties (DD.4.1.1), Improper personal data management (Nc.2) |
Privacy Logging and Reporting |
Inside Neutral, Unawareness |
If the application sends data to third parties, do customers know about this in their privacy policy? Answer "Yes" if your app collects data from users and sends them to third parties, and its privacy policy informs the users appropriately. To satisfy "customer knowledge", clarify the (a) type of third-party (which industry category), (b) clear purpose of transfer, and (c) frequency of transfer, (d) all personal information categories transferred either to or from a third-party, and (e) general source of the personal information obtained. Privacy Policy must be presented as a conspicuous link.
Have they consented to this extended use? Answer "Yes" if your app asks for user consent for the extended use. To satisfy "customer knowledge", clarify the (a) type of third-party (which industry category), (b) clear purpose of transfer, and (c) frequency of transfer, (d) all personal information categories transferred either to or from a third-party, and (e) general source of the personal information obtained. Privacy Policy must be presented as a conspicuous link. |
+ Unawareness as data subject (U.1.1) |
Transparency and Disclosure, Consumer Control |
Can customers limit their data from being shared by vendors to other applications? Answer "Yes" if your app allows users to limit the sharing of their collected data (e.g., the app has a feature that allows users to refuse data sharing). |
+ Preferences (U.2.1) |
Are customers able to access/modify their data that is sent to vendors? Answer "Yes" if your app allows users to access/modify their collected data that are sent to vendors. There should be a clear description of how to request a deletion or modification. |
+ Access (U.2.2) |
Does your application share data with third parties? Answer "Yes" if your app shares data with third parties. Customers cannot be refused service by organization if they restrict names and addresses from being used by third-parties for mailing list subscriptions.
Have they been approved through a third party security assessment? Answer "Yes" if your app shares data with third parties that have gone through a third-party security assessment.
Have they gone through the de-identification process? Answer "Yes" if your app shares data with third parties that have gone through de-identification process (i.e., you have consulted with a de-identification expert and completed the de-identification process).
If not, do they have measures in place to handle PI according to stipulated retention policies? Answer "Yes" if your app shares data with third parties that have measures to handle personal information based on organization retention policies (e.g., PI-related data are deleted at the end of the retention period, also by the third parties).
+ | Involved parties (DD.4.1), Insufficient cybersecurity risk management (Nc.3), Improper personal data management (Nc.2), Identifier (I.2.1.1) |
Is all of the shared data required for the third party to provide the required functionality? Answer "Yes" if your app shares data with third parties and the data are used to provide the required functionality. Unnecessary data can also include user data who are no longer customers. Such data should not be collected.
If not, do you remove unnecessary data elements before sending them to the third-party? Answer "Yes" if your app shares data (to provide other functionality) with third parties and unnecessary data elements have been removed prior to sending the data. Unnecessary data can also include user data who are no longer customers. Such data should not be collected. |
+ Data type sensitivity (DD.1.1), Data type granularity (DD.1.2) |
Does this application use personal data from third parties? Answer "Yes" if your app uses personal information from third parties (e.g., you obtain users' PI from a third party).
Do owners of the personal data (all users, including employees) know about the source of the data? Answer "Yes" if your app informs users of the source of the data (i.e., the third party involved).
Do you validate the correctness of the data received from the third party? Answer "Yes" if your app validates the correctness of the data (i.e., specifically checks for errors/mistakes in the data) received from the third party. |
+ Unawareness as data subject (U.1.1), Rectification/erasure (U.2.3) |