Re: Action 368 - Definition of Service Provider/Data Processor

This is very helpful.  Thanks and I look forward to discussion.  But lots of "red" flags for me when such data enriched targeting companies may get a pass.  This will clearly need to be the subject of an intensive review on the current dimensions of the data platform ecosystem.


Jeffrey Chester
Center for Digital Democracy
1621 Connecticut Ave, NW, Suite 550
Washington, DC 20009
www.democraticmedia.org
www.digitalads.org
202-986-2220

On Feb 27, 2013, at 10:52 AM, Vinay Goel wrote:

> Hi Jeff,
> 
> I think two issues may be conflated together in your questions -- the topic of a Service Provider and the topic of data appends.  The language below doesn't speak to data appends.  I believe that topic is on the agenda for today's call where Peter asks whether we need text around appends.  Depending on how the DSPs and SSPs operate, they could qualify as a Service Provider if they meet the conditions outlined below.  The question of whether/how the DSP/SSP could enhance their customer's data should be handled when dealing with data appends.
> 
> -Vinay
> 
> On Feb 27, 2013, at 8:45 AM, Jeffrey Chester <jeff@democraticmedia.org> wrote:
> 
>> Chris:  Thanks for this.  Could you give the list some examples of service providers/data processors?  For instance, do you consider DSPs, SSPs to be such a provider?  Would they have any limits at all in how much third party data they could provide their client?  Use cases would be useful, so we can understand the dimensions possible in relationship to a meaningful DNT standard.
>> 
>> I missed the Boston meeting, so if this was covered I would appreciate the reference to review.
>> 
>> Thanks,
>> 
>> Jeff
>> 
>> 
>> 
>> 
>> Jeffrey Chester
>> Center for Digital Democracy
>> 1621 Connecticut Ave, NW, Suite 550
>> Washington, DC 20009
>> www.democraticmedia.org
>> www.digitalads.org
>> 202-986-2220
>> 
>> On Feb 27, 2013, at 10:35 AM, Chris Pedigo wrote:
>> 
>>> Hello all, I worked with Vinay Goel to come up with a definition of Service Provider/Data Processor.  We also solicited feedback from Justin Brookman and Rigo Wenning.  Below is the normative text that we ultimately decided upon.  One of the discussions centered around whether service providers or data processors should be allowed to utilize the Permitted Uses.  We decided not to include that language, because it would not fly in the EU and because it does not appear to be common practice among service providers in the US.  Finally, I am still gathering feedback from my member companies.  So, while expect this language will work for publishers, I am reserving the right to come back with tweaks.  Looking forward to today’s call and the ensuing discussion.
>>>  
>>> Action 368 – Definition of Service Provider/Data Processor
>>>  
>>> A Data Processor is any party, in a specific network interaction, that both operates on behalf of another party and meets the following conditions: 
>>> - Data that is collected and/or retained is separated by both technical means and organizational process, AND
>>> - Uses and shares data only as directed by that other party, AND
>>> - Enters into a contract with the other party that outlines and mandates these requirements.
>>>  
>>> A Data Processor is subject to the same restrictions as the other party.  If a Data Processor were to violate any of these conditions, it will then be a third party.
>>>  
>>>  
>>> Chris Pedigo
>>> VP, Government Affairs
>>> Online Publishers Association
>>> (202) 744-2967
>>>  
>> 
>