Changes

Jump to navigation Jump to search
no edit summary
Line 1: Line 1:  
= Overall strategy =
 
= Overall strategy =
 
== Philosophy ==  
 
== Philosophy ==  
The right of access is a tool to provide accountability for profiling, beyond questioning consent or legal basis. It is actually complementary.  
+
The right of access is a tool to provide accountability for profiling, beyond challenging consent or legal basis. It is actually complementary.  
    
The right of access allows to probe the entire ecosystem, strategically. Using this strategy requires to blend knowledge of law and technology.
 
The right of access allows to probe the entire ecosystem, strategically. Using this strategy requires to blend knowledge of law and technology.
    
== Strategy ==
 
== Strategy ==
 +
* [https://lumapartners.com/wp-content/uploads/2017/01/2y103ITnIXmg2.lPu6ncZsis.wcn8DVuYIUfyLrC9cdQiWUhfOdDLq6-1024x768.png "historic" Lumascape picture]
 +
 
* Ignore the average end user. Focus on investigator, who is a blend of:
 
* Ignore the average end user. Focus on investigator, who is a blend of:
 
** legal scholar;
 
** legal scholar;
Line 29: Line 31:  
== Tactics ==
 
== Tactics ==
 
* Classify services, based on business presentations. Enter at each step of the process through access requests.  
 
* Classify services, based on business presentations. Enter at each step of the process through access requests.  
* Filing a SAR is cheap, but takes time. Makes it easier.
+
* Same service can exist at all scales, attack all of them
* Carpet bombing is A-OK, at high frequency.
+
* Filing a SAR is cheap, but takes time. Make it easier (schema.org lobbying, for instance --> Art 40.2.f).
* Makes it easier to file access requests (schema.org lobbying, for instance --> Art 40.2.f).  
+
* Carpet bombing is A-OK, at high frequency (reducing time lag for responses).  
 
* Makes it easy to comply with access requests (standards, such as openGDPR)
 
* Makes it easy to comply with access requests (standards, such as openGDPR)
   −
== Interesting queries ==
+
= The landscape =
* [{{SPARQLEmbed|query=
+
== Datasets about the adtech ecosystem ==  
#defaultView:Graph
+
* [[WebXray domain ownership list]]
SELECT ?item ?itemLabel ?_image WHERE {
+
* [[Related datasets]]
  ?item pdiot:P28 pdio:Q370.
+
 
  SERVICE wikibase:label {
+
= Visualizations =
    bd:serviceParam wikibase:language "en" .
+
{{Project:Adtech/Visualizations|state=collapsed}}
  }
+
 
OPTIONAL { ?item pdiot:P47 ?_image. }
+
= A prototype =
}
+
* {{Q|102}}
LIMIT 100
+
* [[Addressing_adtech/Guardian|An example request]], generated directly from {{Q|855}}.
}} adtech mess]
  −
* [https://query.personaldata.io/index.html#PREFIX%20pdio%3A%20%3Chttp%3A%2F%2Fwiki.personaldata.io%2Fentity%2F%3E%0APREFIX%20pdiot%3A%20%3Chttp%3A%2F%2Fwiki.personaldata.io%2Fprop%2Fdirect%2F%3E%0A%0ASELECT%20%3Fitem%20%3Flabel%20%3F_image%20WHERE%20%7B%0A%20%20%3Fitem%20pdiot%3AP3%20pdio:Q33.%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%0A%20%20%20%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%22%20.%20%0A%20%20%20%20%3Fitem%20rdfs%3Alabel%20%3Flabel%0A%20%20%7D%0A%20%20%0AOPTIONAL%20%7B%20%3Fitem%20pdiot%3AP47%20%3F_image.%20%7D%0A%7D%0ALIMIT%20100 datasets about the adtech ecosystem]
     −
* [https://lumapartners.com/wp-content/uploads/2017/01/2y103ITnIXmg2.lPu6ncZsis.wcn8DVuYIUfyLrC9cdQiWUhfOdDLq6-1024x768.png "historic" Lumascape picture]
+
= Ontology =
* [http://query.personaldata.io/embed.html#PREFIX%20pdio%3A%20%3Chttp%3A%2F%2Fwiki.personaldata.io%2Fentity%2F%3E%0APREFIX%20pdiot%3A%20%3Chttp%3A%2F%2Fwiki.personaldata.io%2Fprop%2Fdirect%2F%3E%0APREFIX%20pdiop%3A%20%3Chttp%3A%2F%2Fwiki.personaldata.io%2Fprop%2F%3E%0APREFIX%20pdiops%3A%20%3Chttp%3A%2F%2Fwiki.personaldata.io%2Fprop%2Fstatement%2F%3E%0APREFIX%20pdiopq%3A%20%3Chttp%3A%2F%2Fwiki.personaldata.io%2Fprop%2Fqualifier%2F%3E%0A%23defaultView%3AGraph%0ASELECT%20%20%3Fobject%20%3FobjectLabel%20%3Frgb%20%3Fsubject%20%3FsubjectLabel%20%0AWHERE%20%7B%0A%20%20VALUES%20%28%3Fobject%20%3Frgb%29%7B%0A%20%20%20%20%20%20%20%28pdio%3AQ110%20%22FF0000%22%29%0A%20%20%20%20%20%20%20%28pdio%3AQ495%20%2200FF00%22%29%0A%20%20%20%20%20%20%20%28pdio%3AQ559%20%220000FF%22%29%0A%20%20%20%20%20%20%20%28pdio%3AQ153%20%22333333%22%29%0A%20%20%20%20%20%20%20%28pdio%3AQ491%20%22888800%22%29%20%20%0A%20%20%20%20%20%20%20%28pdio%3AQ807%20%22008888%22%29%0A%20%20%20%20%20%20%20%28pdio%3AQ492%20%22880088%22%29%0A%20%20%20%20%20%20%20%28pdio%3AQ498%20%22440000%22%29%0A%20%20%20%20%20%20%20%28pdio%3AQ810%20%22004400%22%29%0A%20%20%20%20%20%20%20%28pdio%3AQ556%20%22000044%22%29%0A%20%20%20%20%7D%0A%20%20VALUES%20%3Fpredicate%20%7B%0A%20%20%20%20%20%20%20pdiot%3AP3%0A%20%20%20%20%20%20%20pdiot%3AP28%0A%20%20%20%20%7D%20%0A%20%20%3Fsubject%20%3Fpredicate%20%3Fobject%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%0A%20%20%20%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%22%20.%20%0A%20%20%7D%0A%7D%0ALIMIT%2010000 Lumascape]
+
See [[Project:Ontology/Adtech]]
   −
= {{Q|845}}-related questions =
+
= Precise questions =
 +
== {{Q|845}}-related questions ==
 
* What is the impact of a {{Q|839}} on a {{AllQ|495}}?
 
* What is the impact of a {{Q|839}} on a {{AllQ|495}}?
 
** Is this helpful for understanding {{Q|519}}? {{Q|520}}?
 
** Is this helpful for understanding {{Q|519}}? {{Q|520}}?
Line 62: Line 63:  
*** {{Q|546}} for instance facilitated the selling of an {{Q|496}} by {{Q|840}} of people more "likely to be constipated". This was determined (?) through the use of {{Q|539}}.  
 
*** {{Q|546}} for instance facilitated the selling of an {{Q|496}} by {{Q|840}} of people more "likely to be constipated". This was determined (?) through the use of {{Q|539}}.  
   −
* [[Addressing_adtech/Guardian|An example request]], generated directly from {{Q|855}}.
     −
== Tag management ==
+
=== Tag management ===
 
* What is the impact of an indirect SAR on a {{AllQ|504}}
 
* What is the impact of an indirect SAR on a {{AllQ|504}}
 
* Can a SAR tell you for whom an {{AllQ|503}} fired?
 
* Can a SAR tell you for whom an {{AllQ|503}} fired?
 
**  Is the legal situation different for a SAR on {{Q|70}}?  
 
**  Is the legal situation different for a SAR on {{Q|70}}?  
== Bidding process ==
+
=== Bidding process ===
 
* What is the impact of a(n indirect) SAR on a {{AllQ|498}}?  
 
* What is the impact of a(n indirect) SAR on a {{AllQ|498}}?  
 
* Can you know whether {{AllQ|497}} was triggered?
 
* Can you know whether {{AllQ|497}} was triggered?
 
* What was the value of the transaction?
 
* What was the value of the transaction?
   −
== Top-down, bottom-up, maximizing utility ==
+
=== Top-down, bottom-up, maximizing utility ===
 
The goal of SARs could be to maximize utility in understanding the ecosystem.  
 
The goal of SARs could be to maximize utility in understanding the ecosystem.  
   Line 82: Line 82:  
In particular, for every role, there is a possibility of picking a small player with this role, a huge one, or one with dual roles. '''Each of those situations will lead to different outcomes for the SAR, all valuable'''.
 
In particular, for every role, there is a possibility of picking a small player with this role, a huge one, or one with dual roles. '''Each of those situations will lead to different outcomes for the SAR, all valuable'''.
   −
== Scaling effects ==
+
=== Scaling effects ===
 
Indirect SARs sound complicated and unhelpful. I am not sure: you get a lot of allies in putting pressure on the service providers, who sometimes masquerade as {{Q|841}}. The costs and effects have a completely different scaling factor, and also an impact on the choice of jurisdiction.
 
Indirect SARs sound complicated and unhelpful. I am not sure: you get a lot of allies in putting pressure on the service providers, who sometimes masquerade as {{Q|841}}. The costs and effects have a completely different scaling factor, and also an impact on the choice of jurisdiction.
   Line 96: Line 96:     
== Adtech experiments ==
 
== Adtech experiments ==
* {{Q|188}} helps get feedback quicker
+
* {{Q|188}} and subclasses help get feedback quicker
 
* {{Q|858}} defines a {{Q|94}}
 
* {{Q|858}} defines a {{Q|94}}
 
** There are problems with the [https://vendorlist.consensu.org/vendorlist.json "purposes" defined in the consent framework].
 
** There are problems with the [https://vendorlist.consensu.org/vendorlist.json "purposes" defined in the consent framework].
 
* Through cookie manipulations you can consent very flexibly. A/B test on the entire IAB, agree to A on odd day, B on even day.
 
* Through cookie manipulations you can consent very flexibly. A/B test on the entire IAB, agree to A on odd day, B on even day.
  −
== Facebook's Replacement IDs ==
  −
Crucial in the context of WhatsApp/Messenger/Instagram merger.
  −
  −
Facebook implements the entire ecosystem. This is a challenge on pseudonymization.
      
== Consents ==  
 
== Consents ==  
Line 114: Line 109:  
Involves Europeans, but also Americans, whose data goes abroad. Drives a wedge between Facebook Ireland and Facebook Inc, etc.
 
Involves Europeans, but also Americans, whose data goes abroad. Drives a wedge between Facebook Ireland and Facebook Inc, etc.
   −
== What next? ==  
+
== Facebook's Replacement IDs ==
 +
Crucial in the context of WhatsApp/Messenger/Instagram merger.
 +
 
 +
Facebook implements the entire ecosystem into one product. This is a challenge for them in blurring between pseudonymization and anonymization. They implement all of this into one big association table. See {{Q|860}}, page 46 of 57.
   −
=== Links to competition ===
+
= What next? =
Privacy is a dead-end for enforcement. It will always boil down to consent and design, and always be abused in unaccountable ways, in order to get the first users. And then it will expand progressively to everyone (cf. Facebook's experiments to get my consent in order to use facial recognition).
     −
On the other hand, tracing data flows -- which is possible thanks to data protection law -- helps define exactly the assets that are being shared. It's not just about raw (personal) data, it's also about the consents associated to this data, as well as its identifiability. Once all this is taken into account, we will have a better understanding of the personal data market, and will be better able to assess dominance of some players over that market. This might open the door to a more reasoned antitrust action.
+
== Question on what is observable in RTB ==
 +
There is a bias in what researchers study. What is it?
    +
== Links to competition ==
 +
Privacy is a dead-end for enforcement. It will always boil down to consent and design, and always be abused in unaccountable ways, in order to get the first users to adopt new intrusive technologies. And then it will expand progressively to everyone (cf. Facebook's experiments to get my consent in order to use facial recognition).
    +
On the other hand, tracing data flows -- which is possible thanks to data protection law -- helps define exactly the assets that are being shared. It's not just about raw (personal) data, it's also about the consents associated to this data, as well as its identifiability. Once all this is taken into account, we will have a better understanding of the personal data market, and will be better able to assess dominance of some players over that market. This might open the door to a more reasoned antitrust action.
   −
=== Observations on right of access ===
+
== Observations on right of access ==
    
  GDPR Art. 15 (Right of Access)
 
  GDPR Art. 15 (Right of Access)
Line 140: Line 141:       −
=== Schema.org suggestion ===
+
== Schema.org suggestion ==
 
Someone should suggest to schema.org to add GDPR related terms (like "data controller", "access request email endpoint", etc).
 
Someone should suggest to schema.org to add GDPR related terms (like "data controller", "access request email endpoint", etc).
   −
=== Observation on OpenWPM ===
+
== Observation on OpenWPM ==
 
OpenWPM has split up into a testbed for mass crawling, and a web extension which is separate (currently used in a second project, for mass reporting to Mozilla).
 
OpenWPM has split up into a testbed for mass crawling, and a web extension which is separate (currently used in a second project, for mass reporting to Mozilla).
 
* [https://twitter.com/CartoCharles/status/1130367901767262209 Think OpenStreetMap, not Google Street View or Tesla]
 
* [https://twitter.com/CartoCharles/status/1130367901767262209 Think OpenStreetMap, not Google Street View or Tesla]
* --> Build toolkits!
+
* --> Build toolkits/diffuse computing?!
    
== Relevant items ==
 
== Relevant items ==
Line 158: Line 159:  
* {{Q|559}}
 
* {{Q|559}}
   −
== Interesting queries ==
+
== See also ==
* [{{SPARQLEmbed|query=
+
* [[Project:GetYourData]]
SELECT ?item ?label ?_image WHERE {
  −
  ?item pdiot:P3 pdio:Q110.
  −
  SERVICE wikibase:label {
  −
    bd:serviceParam wikibase:language "en" .
  −
    ?item rdfs:label ?label
  −
  }
  −
OPTIONAL { ?item pdiot:P47 ?_image. }
  −
}
  −
LIMIT 100}} adtech companies]
  −
* [{{SPARQLEmbed|query=
  −
SELECT ?item ?label ?_image WHERE {
  −
  ?item pdiot:P3 pdio:Q495.
  −
  SERVICE wikibase:label {
  −
    bd:serviceParam wikibase:language "en" .
  −
    ?item rdfs:label ?label
  −
  }
  −
OPTIONAL { ?item pdiot:P47 ?_image. }
  −
}
  −
LIMIT 100}} data management platforms]
  −
* [{{SPARQLEmbed|query=
  −
SELECT ?item ?label ?_image WHERE {
  −
  ?item pdiot:P3 pdio:Q559.
  −
  SERVICE wikibase:label {
  −
    bd:serviceParam wikibase:language "en" .
  −
    ?item rdfs:label ?label
  −
  }
  −
OPTIONAL { ?item pdiot:P47 ?_image. }
  −
}
  −
LIMIT 100}} identity resolution services]
  −
*[{{SPARQLEmbed|query={{SPARQLPredicateGraph
  −
|filter_values_colors=(pdio:Q110 "EEEEEE")(pdio:Q495 "222288")(pdio:Q559 "8822222")
  −
|predicate=pdiot:P3
  −
|predicates_subjects_objects_colors=(pdiot:P111 pdio:Q495 pdio:Q559 "EEEEEE")(pdiot:P111 pdio:Q495 pdio:Q559 "222288")
  −
|legend=true
  −
}}}} actors]
 

Navigation menu