Abstract:
Privacy setting metadata for application developers is described, including receiving, from a user, a request to submit an application; requesting, from the user, identification of one or more permissions and information associated with the one or more permissions; receiving the application, the one or more permissions, and the information associated with the one or more permissions, wherein the one or more permissions are associated with one or more functions of the application; storing the application, the permissions, and the information associated with the permissions; receiving a request to install the application to a device of another user; providing the application, the one or more permissions, and the information associated with the one or more permissions to the device; and receiving, from the device, one or more consents to the one or more permissions, the one or more consents indicate activation of the one or more functions of the application.
Abstract:
Service profiles for associating data services with applications are described, including receiving a first input from a user identifying a first service to include in a service profile; receiving a second input from the user identifying a second service to include in the service profile, the second service is associated with the user; receiving a third input from the user defining one or more boundaries of one or more of the first service and the second service; receiving a fourth input from the user indicating association of the service profile with one of the at least one application; storing the service profile with information of the first service, the second service, and the association with the one of the at least one application; and based on the service profile, determining whether to grant access to the first service and second service by the at least one application.
Abstract:
On-demand application permissions is described, including obtaining one or more consents associated with one or more functions of an application, where the application does not allow using the functions without associated consents; receiving, from a user, a consent associated with a function; activating to allow that function to be executed; when a request from the user to use another function is received, determining that the another function requires an associated consent to activate; determining that there is no consent from the user associated with the another function; prompting for a consent associated with the another function; receiving the consent associated with another function; and activating to allow the another function to be executed.
Abstract:
Control and enforcement of access of user data are described, including receiving a request from an application to access data associated with a user; determining that a service profile and another service profile are associated with the user, the service profile includes at least one data service specified by the user and the another service profile includes at least another data service specified by the user; identifying the service profile being associated, by the user, with at least the application; determining whether the data requested by the application are provided by the at least one data service included in the service profile; and performing an action with respect to access by the application to the data requested, based on a result of the determining.
Abstract:
Service profiles for associating data services with applications are described, including receiving a first input from a user identifying a first service to include in a service profile; receiving a second input from the user identifying a second service to include in the service profile, the second service is associated with the user; receiving a third input from the user defining one or more boundaries of one or more of the first service and the second service; receiving a fourth input from the user indicating association of the service profile with one of the at least one application; storing the service profile with information of the first service, the second service, and the association with the one of the at least one application; and based on the service profile, determining whether to grant access to the first service and second service by the at least one application.