Abstract: Contacts are created and stored with corresponding contact information in such a way that they can be accessed and utilized by applications from a single contact store. The contact store contains a complete contact definition for each contact so that each of the applications can obtain the appropriate contact information and in the appropriate format from the contact store that is required by the applications. Centralizing the storage of the contact information allows the contact store to incorporate and propagate the changes that are made by the applications to the contact information. Interfaces can also be provided to initiate communications using the contact information and for controlling what contact information will be made accessible to the applications.

Abstract: Systems and methods are disclosed for synchronizing data stored in remote stores. Data stored in locations such as computer applications, consumer electronic devices and Internet websites is synchronized with a central database within a computer device. The computer device may also store constraints that limit the type of data that may be synchronized with individual stores. A graphical user interface may use different formats or icons to distinguish between data stored in a store and data included within the central database.

Abstract: A user is able to informatively control how contact information is provided to one or more applications through the use of a persona interface object, corresponding personas and contact information, and an information picker interface. The persona interface identifies available personas, each persona having different contact information. The user can select a persona to use in response to an applications request for information. The personas can be modified and developed through the information picker interface, which can also be used to inform the user about what information is being requested and how it will be used.

Abstract: A method, system, and computer-readable medium are provided for managing consent between online entities to perform tasks. The consent mechanism uses an asynchronous protocol for submitting consent requests, managing consent requests, and resolving consent requests. An application that requires consent to perform a task submits a request for consent to the consent mechanism. The resolving authority obtains pending request information from the consent mechanism and sends the consent mechanism request resolution information. The application obtains resolved request information from the consent mechanism. If the resolved request is approved, the consent mechanism allows the application to perform the task. If the resolved request is denied, the consent mechanism does not allow the application to perform the task.