Skip to content

Commit

Permalink
Opt out example with header
Browse files Browse the repository at this point in the history
This is an alternate version of  WICG#47 covering only the HTTP header.

In the future when an opt-out that does not require setting a header is available, the alternate method might be a better example to include here.
  • Loading branch information
dmarti authored Mar 1, 2021
1 parent 0dbb92b commit b034c70
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,12 @@ It should be clear that FLoC will never be able to prevent all misuse. There wil
### Opting Out of Computation
A site should be able to declare that it does not want to be included in the user's list of sites for cohort calculation. This can be accomplished via a new `interest-cohort` [permissions policy](https://www.w3.org/TR/permissions-policy-1/). This policy will be default allow. Any frame that is not allowed `interest-cohort` permission will have a default value returned when they call `document.interestCohort()`. If the main frame does not have `interest-cohort` permission then the page visit will not be included in interest cohort calculation.

For example, a site can opt out of all FLoC cohort calculation by sending the HTTP response header:

```
Permissions-Policy: interest-cohort=()
```

## Proof of Concept Experiment
As a first step toward implementing FLoC, browsers will need to perform closed experiments in order to find a good clustering method to assign users to cohorts and to analyze them to ensure that they’re not revealing sensitive information about users. We consider this the proof-of-concept (POC) stage. The initial phase will be an experiment with cohorts to ensure that they are sufficiently private to be made publicly available to the web. This phase will inform any potential additional phases which would focus on other goals.

Expand Down

0 comments on commit b034c70

Please sign in to comment.