Currently, the Centralized Consent API explainer reads:
GPC actively pushes the Sec-GPC value to all sites via HTTP header
While GPC can be applied to send signals to all sites users visit, they can select only individual sites as well. Also, in addition to the header, GPC defines a DOM property that can be used to indicate GPC preferences as well.
I am also not 100% sure if the following is really a difference as described in the Centralized Consent API explainer
The Centralized Consent API avoids adding a global fingerprinting bit by making per-site and global preferences indistinguishable
There should be only minor changes to clarify the relationship a bit. I can open a PR accordingly, but if anyone wants to weigh in ... .
(cc'ing GPC draft spec fellow co-authors @darobin, @asoltani, @dharb, @pes10k)
Currently, the Centralized Consent API explainer reads:
While GPC can be applied to send signals to all sites users visit, they can select only individual sites as well. Also, in addition to the header, GPC defines a DOM property that can be used to indicate GPC preferences as well.
I am also not 100% sure if the following is really a difference as described in the Centralized Consent API explainer
There should be only minor changes to clarify the relationship a bit. I can open a PR accordingly, but if anyone wants to weigh in ... .
(cc'ing GPC draft spec fellow co-authors @darobin, @asoltani, @dharb, @pes10k)