ISSUE-258: automatic expiration of a tracking preference
automatic expiration of a tracking preference
- State:
- PENDING REVIEW
- Product:
- TPE Last Call
- Raised by:
- Nick Doty
- Opened on:
- 2014-07-13
- Description:
- http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/att-0000/20140606_WP29_TS_standardisation_letter_to_W3C.pdf
Article 29 Working Party requests functionality for automatic expiration of preferences/exceptions.
With regard to some parallel initiatives, such as notice-and-choice programs, the Working Party acknowledges that they can function as supporting measures to remind users that they can withdraw their tracking preference at any time. But the Draft TPE Specification currently lacks a building block that ensures the automatic expiration of a tracking preference. Under European data protection law, personal data must be adequate and accurate, and stored no longer than necessary. In order to comply with these requirements, the introduction of an automatic expiration feature is necessary to allow users to exercise effective control. Therefore, the Working Party recommends adding this requirement to the building blocks. - Related Actions Items:
- No related actions
- Related emails:
- RE: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call] (from michael.oneill@baycloud.com on 2014-10-22)
- Re: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call] (from singer@apple.com on 2014-10-22)
- FW: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call] (from michael.oneill@baycloud.com on 2014-10-22)
- Re: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call] (from singer@apple.com on 2014-10-09)
- RE: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call] (from michael.oneill@baycloud.com on 2014-10-09)
- Re: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call] (from singer@apple.com on 2014-10-08)
- RE: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call] (from michael.oneill@baycloud.com on 2014-09-28)
- Re: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call] (from npdoty@w3.org on 2014-09-24)
- Re: tracking-ISSUE-258: automatic expiration of a tracking preference [TPE Last Call] (from singer@apple.com on 2014-09-24)
- Re: tracking-ISSUE-258: automatic expiration of a tracking preference [TPE Last Call] (from rob@blaeu.com on 2014-09-23)
- Re: tracking-ISSUE-258: automatic expiration of a tracking preference [TPE Last Call] (from fielding@gbiv.com on 2014-09-22)
- RE: tracking-ISSUE-258: automatic expiration of a tracking preference [TPE Last Call] (from michael.oneill@baycloud.com on 2014-09-22)
- Re: tracking-ISSUE-258: automatic expiration of a tracking preference [TPE Last Call] (from fielding@gbiv.com on 2014-09-22)
- tracking-ISSUE-258: automatic expiration of a tracking preference [TPE Last Call] (from sysbot+tracker@w3.org on 2014-07-13)
Related notes:
WONTFIX.
The Working Party appears to be assuming that TPE will work in the same
way as current opt-out technology, wherein the option is actually set
and managed by the server.
For TPE, the storage of user preference is (at all times) under the control
of the user. If the user agent configuration has an expiration associated
with it, that expiration would not be visible to the TPE protocol. Since
we do not specify how a user agent is configured, we cannot require that
such configuration has an expiration. Likewise, a server has no ability to
require a minimum time before expiration.
Display change log
