Difference between revisions of "Project:Adtech/SITRA call"
Jump to navigation
Jump to search
| Line 58: | Line 58: | ||
{{SPARQL|state=collapsed | {{SPARQL|state=collapsed | ||
| − | |query=SELECT ?item ?itemLabel ?third ?thirdLabel ?rgb WHERE { | + | |query=#defaultView:Graph |
| + | SELECT ?item ?itemLabel ?third ?thirdLabel ?rgb WHERE { | ||
?item pdiot:P260 ?third. | ?item pdiot:P260 ?third. | ||
BIND( "FFA500" AS ?rgb) | BIND( "FFA500" AS ?rgb) | ||
Latest revision as of 20:18, 8 January 2020
Goals
- trace personal data
- understand how it is used dynamically
- understand what is stored statically
Techniques
- technical audit through use
- limitation: we don't know what occurs behind the scenes
- legal through request (right of access)
- limitation: slow, cumbersome, uncertain
- but: some places it is easier
- combination (right of access at places where audit says it will be interesting)
- limitation: still time-consuming
Questions
- which device?
- which browser?
Actors
We focus on adtech industry, which has different roles:
- publisher
- advertisers
- ad exchanges
- data management platforms
- identity resolution services
Adtech overview
some publishers and their trackers (embedded)
Technical standards
- hs.fi ads.txt implementation
- includes `adform.com,583,DIRECT`
- adform.com sellers.json implementation
- includes
seller_id "583"
seller_type "PUBLISHER"
domain "sanoma.com"
name "Sanoma Oyj"Right of Access
actors with some form of data rights portal (embedded)