ACTION-122, ISSUE-125: Pro-actively requesting exceptions

My proposal for potentially using the JavaScript site-specific exception API to pro-actively request exceptions. The overview section documents what I interpreted to be the potential use cases here.

This would go towards the end of the Site-Specific Exception section of tracking-dnt.html. If we decide on an API for Web-wide exception, we would likely want to update this proposal to apply to that method in the same way.


# Exceptions when Do Not Track is not enabled

## Overview (non-normative)
Sites may wish to pro-actively request exceptions (site-specific or Web-wide) for tracking elements even when a user arrives without Do Not Track enabled on their user agent. Users may wish to grant affirmative permission to tracking on or by certain sites even without expressing a preference about tracking in general.

## Pro-actively requesting exceptions
User agents MAY instantiate <code>NavigatorDoNotTrack.requestSiteSpecificTrackingException()</code> even when <code>navigator.doNotTrack</code> is null. Sites SHOULD test for the existence of <code>requestSiteSpecificTrackingException</code> before calling the method. Exceptions granted in this context MAY be persisted, for example, when a user later enables Do Not Track in their browser. User agents MAY send a DNT:0 header even when Do Not Track has not been enabled to express the user's affirmative consent for tracking by this entity.

Note: users may not configure their agents to have simple "default" values for DNT, but use different browsing modes or other contextual information to decide on a DNT value. What algorithm a user agent employs to determine DNT values (or the lack thereof) is out of the scope of this specification.

Received on Wednesday, 15 February 2012 07:00:39 UTC