Defining Collection (ISSUE-16)

(retitled for issue tracking)

Here's the PENDING REVIEW text in the compliance document:

> A party "collects" data if the data comes within its control.
> A party "retains" data if data remains within a party's control.
> A party "uses" data if the party processes the data for any purpose other than storage.
> A party "shares" data if the party enables another party to collect the data.
> 
> The definitions of collection, retention, use, and sharing are drafted expansively so as to comprehensively cover a party's user-information practices.  These definitions do not require a party's intent; a party may inadvertently collect, retain, use, or share data.  The definition of collection includes information that a party did not cause to be transmitted, such as protocol headers.


I think these definitions make a lot of sense in both plain meaning and analytical structure—they compel us to be precise with our exceptions.

If there's disagreement, I'm listening.

On Mar 7, 2012, at 10:17 AM, Kevin Smith wrote:

> I have a request.  To me, 'collection' is synonymous to 'retention' and I automatically translate the 1st into the latter.  From a lot of responses over the last few months (not necessarily on this thread), I think many others have a hard time separating these two terms as well.  However, usually when Jonathon uses the term 'collection' he is not referring to 'retention', but rather the actual request that goes over the wire, and I quickly get confused.  Jonathon, any chance you can use a different word (transmission perhaps) to refer to the request?

Received on Wednesday, 7 March 2012 21:33:09 UTC