Skip to content

Commit

Permalink
Update code formatting in explainer (issue #56)
Browse files Browse the repository at this point in the history
  • Loading branch information
SebastianZimmeck committed Nov 17, 2023
1 parent 0d6c4a7 commit 72092e8
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion explainer.md
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,16 @@ Given the complexities of existing privacy choice and consent frameworks, sites

Where industry standards set specific strings or signals that are needed to communicate people’s privacy choices, sites should anticipate translating GPC into the downstream signal. A good example of such setting is handling GPC to set California-based US Privacy Strings for advertising technology:

![USPAPI](assets/images/USPAPI.png)
```javascript
if (
navigator.globalPrivacyControl &&
identityObject.geoState === 'CA'
) {
this.uspapi.uspStringSet = true;
this.uspapi.setUSPString(`1YYY`);
} else if
```

Setting the USPAPI for propagating GPC downstream.

Generally website developers should consider GPC signals to be identical to a user flipping the opt out switch on their website and take action accordingly.
Expand Down

0 comments on commit 72092e8

Please sign in to comment.