-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed
Description
"Confusing" is one way to put it.
Edit:
@zzo38 articulated my personal opinion better than I could so I'll quote part of their comment here:
der to reduce tracking, or deleted entirely if GitHub does not use the DNT header. If it does so only in some cases, it should mention what cases these are. The privacy policy made sense before the change in the section about DNT, although the change mentioned above makes it confusing (as other comments already mention). > > [..] > > I have no problem with adding these non-essential cookies to the enterprise marketing pages, as long as the rest of GitHub can be used without it and it is documented which pages these are (and if the cookie domain is the same, also which cookies). Moving the enterprise marketing pages to a separate domain seems to me to be a good idea though, in order to be clearly distinguished (although a subdomain is probably good enough, in my opinion; as long as it is documented clearly which subdomains these are).I also think that they should avoid using confusing privacy policies; the mention of DNT should either be kept as is if GitHub uses the DNT hea.
Emphasis are mine.
In my opinion, documented
should mean being very specific and being part of a legally binding document like the privacy policy.
An example for not being specific is this part of the changes:
As described below, we may use non-essential cookies on certain pages of our website
Originally posted by @Consolatis in github/site-policy#582 (comment)
Metadata
Metadata
Assignees
Labels
No labels