Existing Wording: All discussion in 6.4.1 - 6.4.3

Proposed Wording: 1. Replace the undefined term "consent to share" with a specific type of Consent Directive - i.e., an agreement authorizing information disclosure. It is not a synonym for a Consent Directive. "Consent to share" is vernacular for a Consent Directive that authorizes information disclosure only. A Consent Directive may authorize other privacy actions, such as authorization to collect, access, use, as well as disclose.

2. Replace the undefined term "privacy statement" with an appropriate consent term. A "privacy statement" is not a consent directive. It's a statement of some entities privacy policies, which may be the basis for a consent directive or not, e.g., the Privacy Statement on a mobile App. It is not a contract, just a notification

Comment:

Discussion in the beginning of Section 6.4 deals with policy matters, and should be more rigorously structured by providing guidance using distinct terms which are properly defined so as to be understandable by policy analysts, policy makers and implementers. As it is, it may sound good to some implementers, but those who understand privacy policy and consent directives will likely be critical. And if implementers privacy officers and legal staff don't get it, it won't matter that it was easy or implementers to deploy. Below are two terms that need to be replace. Terms that need definitions, revised definitions, and missing terms with definitions will be commented on separately.

Generally, the front matter is confused and confusing, in particular because of the random use of undefined terms, which are swapped in and out with other defined terms used as if they are synonyms.

Summary:

Front matter is confusing due to undefined terms