You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I'm not quite up to date on the work progress so far (but kudos on getting this in a WG), so I'm proposing the following with hope that there is time to change text. For the section on legal effects the content for GDPR is rather vague, and I propose it be changed to the following so that the interpretation is robust and clear, and so that the GPC is interpreted consistently and usefully within GDPR.
Original content: GPC could potentially be used to indicate rights in other jurisdictions as well. For example, the GDPR potentially affords data subjects the right to limit the sharing of personal information under Articles 7 and 21. Many other countries around the world have adopted affirmative privacy legislation — often modeled on the GDPR; a regulator in one of those countries could determine that GPC invokes a legal right that requires some response from a recipient.
GPC can be used to express or exercise rights in other jurisdictions as well. For example, GPC can be used with the EU's General Data Protection Regulation (GDPR) to withdraw consent under Article 7-3 and to object to the use of legitimate interests under Article 21-5, where the signal constitutes a decision by the 'data subject' regarding the do-not-sell-or-share preference. Further, in addition to the EU's GDPR, several countries around the world have also adopted affirmative privacy legislation — often modeled on the GDPR; such regulations or their enforcing authorities could assert the applicability of GPC and make it 'binding' for their jurisdiction, for example by stating that the use of GPC constitutes the exercise of a legal right or triggers an obligation that requires a response from the signal's recipient.
Separately, the link in Section 5 for legal explainer is broken / 404'd. Last working link seems to have been in June'24 archive.org. In this document, the above information is stated (though not with the same effect). I have added the point about how to make GPC binding based on that as it is useful for the uptake of the signal and for the recipients to respect it.
The text was updated successfully, but these errors were encountered:
On the broken link in the explainer, the current pointer is to the CG repository. We are in the process of agreeing to a more permanent home for the renamed Legal and Implementation Considerations guide, when that's settled we'll update the link.
Hi. I'm not quite up to date on the work progress so far (but kudos on getting this in a WG), so I'm proposing the following with hope that there is time to change text. For the section on legal effects the content for GDPR is rather vague, and I propose it be changed to the following so that the interpretation is robust and clear, and so that the GPC is interpreted consistently and usefully within GDPR.
GPC can be used to express or exercise rights in other jurisdictions as well. For example, GPC can be used with the EU's General Data Protection Regulation (GDPR) to withdraw consent under Article 7-3 and to object to the use of legitimate interests under Article 21-5, where the signal constitutes a decision by the 'data subject' regarding the do-not-sell-or-share preference. Further, in addition to the EU's GDPR, several countries around the world have also adopted affirmative privacy legislation — often modeled on the GDPR; such regulations or their enforcing authorities could assert the applicability of GPC and make it 'binding' for their jurisdiction, for example by stating that the use of GPC constitutes the exercise of a legal right or triggers an obligation that requires a response from the signal's recipient.
Separately, the link in Section 5 for legal explainer is broken / 404'd. Last working link seems to have been in June'24 archive.org. In this document, the above information is stated (though not with the same effect). I have added the point about how to make GPC binding based on that as it is useful for the uptake of the signal and for the recipients to respect it.
The text was updated successfully, but these errors were encountered: