Privacy as Expected is a legal standard, explained technically as legal standard for human expectation used here to apply rights in Online context. This use case for proving a general took for identity and trust governance interoperability. E.g. the use of rights based controls
le decentralized identity and data governance semantic standards for notice and consent. (Human centric Identity & Trust) The ISO standardized notice and consent definition and terms provide an international basis for legal notice and consent governance semantics and interabioity. These are used to standardize (or provider transparency over) system identity permissions and data controls, independent of the service, to provide a privacy as expected signs.
Simply put, standardized notice infrastructure, for messaging (aka receipt) architectures. These semantics standards are usable to enhance privacy policies with semantics made with privacy law.
As humans we are decentralized, in the physical world the trust framework is local to a person. To extend this digitally, these set of interoperable semantic standards ( are used to provide a broadcasted identity and trust UI) that is human 'Consent Centric" and a legal baseline for notice and consent receipts.
This PaE signalling operates on a public set of rules/laws that people can use locally to see, share and communicate about data surveillance, security and privacy risks. Independently of a digital identity management system or protocol. Another term for this, is co-regulationhere as a notice signalling protocol for the managing human expectation for personal data processing.
Signalling Protocol for Active State for dynamic Risk Transparency
...
The privacy and consent is what is expected. The first step, is display the PII Controller's credential for a specific service and data processing context. Privacy as Expected, can also be seen as a legal expression of the active state of notice relative to the individual, so the person can see if this the privacy they expect.
Online, these privacy risks extend to digital identity, surveillance and the security of the surveillance. Without transparency over these relationships, the technology is un-trustworthy.
...
https://privacy-as-expected.org/
...
In the PaE.G project we specify the use of the Active State Tranparency Transparency Privacy Risk signal for use with web browsers , and aim to show and demonstrated transparency over the active state of Surveillance capitalism is what people expect, and to provide a way for people to use their rights (with a receipt) independent of the websitethe PII Controller in order to present a privacy as expected signal, which include disclosures, to managed what people can expect. If people object, the PasE protocol can be used to implement privacy rights so that an invidiual can directly manage their own privacy expectations.
What is the Challenge?
...
In essence, it is this technology that is advance for active state for online services, which like money on a credit card is invisible to the person in context. The receipt fulfils the same purpose of a record and it required an international standard so that it can be used across technical, legal and social domains.
Overview of Contribution
NGI - Trust project - we focused on developing a privacy rights signalling protocol that is human centric (notice based) to implement ISO/W3C/Kantara/ToiP standards and specifications for contribution to the Consent Receipt v1.2 Framework at the Kantara Initiative ANCR WG.
The rights protocol is called Privacy as Expected (PasE) and is a privacy notice signalling protocol the people can see and trust in order to automate the use of privacy rights in Online environments.
The PasE protocol implements international (ISO/IEC) standard semantics and W3C DPV legal ontology, to generate semantically standardized and linked record that produce consent notice receipts the first time a person interacts with or provides a digital identifier to a data controller via an online service, by creating an ANCR record..
PasE protocol is displayed as a signal the next time a Data Subject uses the same service online, (or encounters the same data controller online). Each new session interaction creates a linked consent notice receipt, which is compared against the previous receipt, to show a signal to indicate if privacy is as expected, or not.
How it works: The PasE protocol is implemented with a notice and notification best practice called 2 Factor Notice for Online Consent (2FC). Demonstrated with a browser add-on in the NGI-PasE Consent Gateway project. A first layer notification signal that is visual and accessible in context.
If privacy is as expected the receipt is used to signal a green light in order to streamline the service experience. The receipt works like a reverse cookie (is an ANCR record owned by the individual), eliminating the need for services to provide repetitive notices, notifications, or to make people read privacy policies to see what their rights are.
The first factor notice is provided by the PasE add-on, implementing standardized Notice semantics via the browser (independent of service providers). The first notice presented confirms, or registers the identity of data controller with a Consent Gateway.
- The Consent Gateway API, is called to validate the authenticity of notice of the controller (Data Controller identity and contact) inorder to validate the first factor notice receipt.
The second factor notice is a capture of the websites privacy notice upon Data Subject interaction (or personal data provision). e.g. an I agree, submit, cookie notice, privacy policy link, etc. This second factor interaction generates the consent notice receipt that is sent to the Consent Gateway to be notarized, before being sent to the Data Controller as a privacy rights notice. The response performance of the Data Controller is measured and reported by the gateway back to the Data Subject when the next receipt for this Data Controller is sent to be verified. Along with any notification of changes to the privacy status of the data controller (as monitored by the Consent Gateway) and the service’s data controller with whom the Data Subject is interacting with.
The result, people are able to see how/who is controlling their personal data with this protocol and as a result be able to asser privacy rights in context, and when instructed, automagically, independent of the service provider t&c’s.
To complete the project the PasE protocol is contributed back to the Kantara Initiative ANCR WG, where the PasE protocol will be published under a FRAND license. The protocol is then able to include controls from ISO/IEC 29184, Online Privacy Notice & Consent” which are then implemented in notice, notifications and disclosures with the W3C Data Privacy Control Vocabulary.
And finally, contributed as comments via a Kantara Liaison agreement to ISO/IEC 27560 Consent Record Structure Standard (for receipts) by Aug 16, in comments via the Kantara Liaison for working draft 3.
UI : Basic Active State - Visual Signal
...
Specification
a person generates a notice receipt for an online website based interaction, and then when returning to this website, generates another receipt. The 2 receipts are compared for changes in the known active state. This then provides the active state signal to indicate if privacy is as expected, (or not).
if the signal is green - their is no need for a cookie notice or privacy ritual
- if the signal is yellow - then legally a notice is required to be provided, the person can ignore, accept, refuse these notices
- if the signal is red - then a notice is legally required to maintain system permissions and to manage a consent (which is technical no longer valid) for example a data breach.
- Extending the existing policy, security, technical laws and standards with PaeCG, is the design goal of the effort.
...