Abstract
This publication describes an operating system (OS) that uses a privacy layer for handling a user’s preferences on permissions required by an application software (application). The privacy layer injects mock data into application programming interface (API) calls when the application requests a permission-protected resource. As described herein, a permission-protected resource may include user data (e.g., calendar, contacts data, notes, user-biometric data) and access to user equipment (UE) hardware (e.g., gyroscopes, magnetometers, barometers, global navigation satellite system (GNSS) technology, proximity sensors, touchscreen sensors, biometric sensors, heart-rate sensors, thermometers, humidity sensors, radar technology, cameras, microphones) that the user does not want to grant access to the application. The OS gives the user the choice to enable the privacy layer for each application or enable the privacy layer across the OS. This privacy layer protects the user’s privacy and allows the user to utilize the application without sharing information that the user wants to keep private.
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.
Recommended Citation
Carbune, Victor and Feuz, Sandro, "Handling a User’s Preferences on Permissions Required by an Application Software", Technical Disclosure Commons, (June 21, 2019)
https://www.tdcommons.org/dpubs_series/2299