{"id":50506,"date":"2022-08-02T21:47:54","date_gmt":"2022-08-02T13:47:54","guid":{"rendered":"http:\/\/www.upgrademag.com\/web\/?p=50506"},"modified":"2022-08-02T21:47:57","modified_gmt":"2022-08-02T13:47:57","slug":"life-hacks-from-kaspersky-on-how-to-strengthen-google-privacy-controls","status":"publish","type":"post","link":"http:\/\/www.upgrademag.com\/web\/2022\/08\/02\/life-hacks-from-kaspersky-on-how-to-strengthen-google-privacy-controls\/","title":{"rendered":"Life hacks from Kaspersky on how to strengthen Google privacy controls"},"content":{"rendered":"\n

Google recently launched a new privacy section called Data Safety, and it now appears<\/a> that another security section \u2013 App Permissions \u2013 is hidden from users. It seems that moving forward, Google will rely solely on developers and their responsible actions in relation to the Data Safety section.\u00a0<\/strong><\/p>\n\n\n\n

In light of the new rule, Kaspersky experts explore possible risks for users and how the situation will change in the future:<\/p>\n\n\n\n

  1. The permission model in Android has become more complicated over time. Sensitive permissions are now dynamic, and requested while the application is running. In addition, most permission values no longer include just \u201callowed\/not allowed\u201d options but additional ones, depending on the permission itself. For example, \u201callow only while using the app\u201d, \u201cask every time\u201d, \u201cnot allowed\u201d. This makes the process of managing apps\u2019 permissions and accessing personal data more accurate and reduces the risk of leaking any sensitive information.<\/li>
  2. In general, the Google initiative helps users check what will happen to their personal information and brings more clarity to the understanding of all stages of data processing. Users also have the ability to abandon the app in favor of an alternative, if they believe that the disclosure of data is unreasonable. <\/li>
  3. Data Safety and App Permission sections relate to Google Store information that the user should receive before installing an app. Nevertheless, if some points in this section cause concern, users still have the option to manage permissions on their devices in the Settings app under Apps. Moreover, apps have no access to any APIs or personal data before being installed on the device, so confidential information will be protected and kept private, ensuring there is no recourse for users. <\/li>
  4. As for further improvements to personal data protection, the next steps could include not just controlling app access to sensitive information (such as received, used and \u201cforgotten\u201d data) but understanding its future fate (such as saving, storing, transferring to third parties etc.). In particular, key aspects could relate to:<\/li><\/ol>\n\n\n\n

    a. What data an app collects (and not just one-time access, but future storage. It must have a purpose)<\/p>\n\n\n\n

    b. Where does app transfer such information – to whom, why and under what conditions?<\/p>\n\n\n\n

    c. Handling – an explanation to the user, what access to data is necessary for the app to operate (without which it cannot work), and what is optional<\/p>\n\n\n\n

    d. Additional information – such as whether there is the ability to revoke or delete information, or the app and whether data is encrypted during transmission, etc.<\/p>\n\n\n\n

    1. Another practice that can lead to enhanced user data protection is providing more checks (e.g., a compliance audit) to ensure a high level of defense and a clear way of processing sensitive information. We see that Google is making steps in this direction by connecting to MASVS<\/a>.<\/li><\/ol>\n\n\n\n

      Additional tips and lifehacks from Kaspersky on how to strengthen privacy controls:<\/p>\n\n\n\n