Trusted Privacy Manager. This central pillar provides abstraction for a personal and trusted privacy enforcement system. The role of the Trusted Privacy Manager is to orchestrate any disclosure of personal data and to manage the collaboration between entities with the goal to protect an individual's privacy. Thus, it must provide functionality for the evaluation of service-side privacy policies (data collectors and data consumers), the enforcement of its users' privacy policies, for guiding the negotiation of agreements on secondary use, and facilitating the monitoring of disclosed data.
Trusted Privacy Manager. This central pillar provides abstraction for a personal and trusted privacy enforcement system. The role of the users. The communication between a CAMS and the UCPF services is realized by the Sentry’s PEP component implementing an Interceptor pattern on messages passing through the system. The Context Handler provides access control to the system repositories and acts as a mediator between the Sentry and external context collectors. It also manages the semantic models used to represent policies and context data in the system. The interaction of end-users with the UCPF is made possible through the Sentry Manager Interface. It is implemented as an API used to generate, upgrade or delete privacy policies, receive information about the current applicable policies, or getting feedback on potential privacy risks and obligations state. The Noise Module is a modular functional component that injects additional information into the policy matching mechanism, typically for altering the data disclosed. Currently implemented are different levels of obfuscation, called Transformations [16], within the Local Transformation Point (LTP) and a disclosure mechanism for a Virtual Context within the White Lying Generator (WLG) [17]. The Sentry Registry is the only component that is not co-located with the rest of the elements in the gateway. This component is shared among Sentries and thus must be hosted in the Internet. It tracks the availability of people’s context and provides the pointer to the appropriate Sentry service instance. Services, organizations and Sentries need to be registered with the UCPF before starting any context request, which is done in the Sentry Registry. The Sentry Registry has an important role in making interactions possible between CAMS and Sentries, and also between different Sentry instances, providing Flexibility to deal with distributed and changing entities. Finally, the Obligation Manager, see next section, negotiates agreements and tracks the obligations agreed on by third parties.
