Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
5Activity
0 of .
Results for:
No results containing your search query
P. 1
Compromise Proposal Pde Tl Jm

Compromise Proposal Pde Tl Jm

Ratings: (0)|Views: 23,685 |Likes:
Published by vincepci

More info:

Published by: vincepci on Jun 07, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

06/07/2012

pdf

text

original

 
Do Not Track — Compromise Proposal
Unofficial Draft 06 June 2012
Editors:
Peter Eckersley, Electronic Frontier FoundationTom Lowenthal, MozillaJonathan Mayer, Stanford University
This document is licensed under aCreative Commons Attribution 3.0 License.
Abstract
Abstract, version, and status information are not relevant in this partial draft.
Status of This Document
This document is merely a public working draft of a potential specification. It has noofficial standing of any kind and does not represent the support or consensus of anystandards organisation.
Table of Contents
1.User Agents1.1Explicit Consent Requirement2.Parties, First Parties and Third Parties2.1Parties2.1.1Definitions2.1.2Transparency2.1.2.1Requirement2.1.2.2Non-Normative Discussion2.2Network Interaction2.2.1Definition2.2.2Non-Normative Discussion2.3First Parties and Third Parties2.3.1Definitions2.3.2Non-Normative Discussion2.3.2.1Overview2.3.2.2Common Examples and Use Cases2.3.2.3Multiple First Parties2.3.2.4User Interaction with Third-Party Content2.3.2.4.1Examples and Use Cases3.Information Practices
 
3.1Reception, Retention, Use, and Sharing3.2First Party3.3Third Party3.3.1General Rule3.3.2Exceptions3.3.2.1Protocol Information3.3.2.1.1Definition3.3.2.1.2In General3.3.2.1.3Non-Normative Discussion: ContextualPersonalization3.3.2.1.4Additional Limit on Geolocation3.3.2.1.5Security and Fraud Prevention3.3.2.2Unlinkable Data3.3.2.2.1Definitions3.3.2.2.2Validation3.3.2.2.3Information That Is Unlinkable When Received3.3.2.2.4Information That Is Unlinkable After Aggregation3.3.2.3Outsourcing3.3.2.3.1Technical Precautions3.3.2.3.1.1Operative Text3.3.2.3.1.2Non-Normative Discussion3.3.2.3.1.2.1Siloing in the Browser3.3.2.3.1.2.1.1Same-Origin Policy3.3.2.3.1.2.1.2Cookie Path Attribute3.3.2.3.1.2.1.3Storage Key3.3.2.3.1.2.2Siloing in the Backend3.3.2.3.1.2.2.1Encryption Keys3.3.2.3.1.2.2.2Access Controls3.3.2.3.1.2.2.3Access Monitoring3.3.2.3.1.2.3Retention in the Backend3.3.2.3.2Internal Practices3.3.2.3.2.1Operative Text3.3.2.3.2.2Non-Normative Discussion3.3.2.3.2.2.1Policy3.3.2.3.2.2.2Training3.3.2.3.2.2.3Supervision and Reporting3.3.2.3.2.2.4Auditing3.3.2.3.3Use Direction3.3.2.3.4First-Party Requirements3.3.2.3.4.1Representation3.3.2.3.4.2Contract3.3.2.4User Permission3.3.2.5Security3.3.2.5.1Operative Text3.3.2.5.2Non-Normative Discussion3.3.2.6Fraud Prevention3.3.2.6.1Operative Text3.3.2.6.2Non-Normative Discussion3.3.2.7Unknowing Information PracticesA.ReferencesA.1Normative references
 
A.2Informative references
1. User Agents
1.1 Explicit Consent Requirement
Note:
This section was recently added and has not been extensively discussed withstakeholders. Please consider it a preliminary position.An ordinary user agent
MUST
 
NOT
send a Tracking Preference signal without a user'sexplicit consent.
Example:
The user agent's privacy preferences pane includes controls for configuringthe Tracking Preference signal.
Example:
On first run, the user agent prompts the user to configure the TrackingPreference signal.
2. Parties, First Parties and Third Parties
2.1 Parties
2.1.1 Definitions
A
functional entity 
is any commercial, nonprofit, or governmental organization, asubsidiary or unit of such an organization, or a person.Functional entities are
affiliated 
when they are related by both common majorityownership and common control.A
party 
is a set of functional entities that are affiliated.
2.1.2 Transparency
2.1.2.1 Requirement 
A functional entity must make its affiliated functional entities easily discoverable by auser.
2.1.2.2 Non-Normative Discussion 
Affiliation may be made easily discoverable by a user in many ways, including but notlimited to: prominent and common branding on pages, one click away within a privacypolicy, or a machine-readable format in a well-known location.
2.2 Network Interaction

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->