Revisit global opt out, fix #231 (#296)

* 'iterate on explanation of GOO'

* Update index.html

Co-authored-by: Michael Kleber <[email protected]>

* Update index.html

---------

Co-authored-by: Robin Berjon <[email protected]>
Co-authored-by: Michael Kleber <[email protected]>

index.html

@@ -684,11 +684,13 @@
 [=person=] has with a site, or more generally conveys an expression of the [=person=]'s
 rights in a relevant jurisdiction. (For instance, the [=person=] may be objecting to [=processing=]
 based on legitimate interest, withdrawing [=consent=] to specific [=purposes=], or requesting that
-their data not be sold or shared.) It should be noted that, since a
-[=global opt-out=] signal is reaffirmed automatically with every interaction, it will take precedence
-in terms of specificity over any general obtention of [=consent=] by a site,
-and only superseded by specific [=consent=] obtained through a deliberate action taken by
-the user with the intent of overriding their global opt-out.
+their data not be sold or shared.) The [=user=] is effectively delegating the expression
+of their [=opt-out=] to their [=user agent=], which helps rectify [=automation asymmetry=].
+
+Under this model, a [=global opt-out=] signal should not be understood as a decision that a
+[=person=] made a while ago when they flipped a setting or chose to use a specific
+[=user agent=] but rather as a preference that they have chosen to automatically reaffirm with
+every interaction.
 
 One implementation strategy for [=opt-outs=] and other <a href="#data-rights">data rights</a> is
 to assign [=people=] stable [=identifiers=] and to maintain a central registry to map these