Difference between revisions of "Project:Adtech/SITRA call"
Jump to navigation
Jump to search
| (9 intermediate revisions by the same user not shown) | |||
| Line 24: | Line 24: | ||
* data management platforms | * data management platforms | ||
* identity resolution services | * identity resolution services | ||
| − | + | === Adtech overview === | |
| − | = | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == Adtech overview == | ||
{{SPARQL|state=collapsed | {{SPARQL|state=collapsed | ||
|query=#defaultView:Graph | |query=#defaultView:Graph | ||
| Line 68: | Line 57: | ||
}} | }} | ||
| − | == Technical standards == | + | {{SPARQL|state=collapsed |
| + | |query=#defaultView:Graph | ||
| + | SELECT ?item ?itemLabel ?third ?thirdLabel ?rgb WHERE { | ||
| + | ?item pdiot:P260 ?third. | ||
| + | BIND( "FFA500" AS ?rgb) | ||
| + | SERVICE wikibase:label { | ||
| + | bd:serviceParam wikibase:language "en" . | ||
| + | } | ||
| + | } | ||
| + | |label=some publishers and their trackers}} | ||
| + | |||
| + | === Technical standards === | ||
| + | * [https://www.hs.fi/ads.txt hs.fi ads.txt implementation] | ||
| + | * includes `adform.com,583,DIRECT` | ||
| + | * [https://adform.com/sellers.json adform.com sellers.json implementation] | ||
| + | * includes | ||
| + | {{#tag:syntaxhighlight| | ||
| + | seller_id "583" | ||
| + | seller_type "PUBLISHER" | ||
| + | domain "sanoma.com" | ||
| + | name "Sanoma Oyj" | ||
| + | }} | ||
| + | |||
| + | == Right of Access == | ||
| + | {{SPARQL|state=collapsed | ||
| + | |query=SELECT ?item ?itemLabel ?service ?serviceLabel ?web WHERE { | ||
| + | ?item pdiop:P144 ?statement. | ||
| + | ?statement pdiops:P144 ?service. | ||
| + | ?service pdiot:P4* pdio:Q188. | ||
| + | OPTIONAL {?statement pdiopq:P15 ?web} | ||
| + | SERVICE wikibase:label { bd:serviceParam wikibase:language "en" . } | ||
| + | }|label=actors with some form of data rights portal}} | ||
| + | |||
| + | * https://www.quantcast.com/privacy/data-subject-rights/ | ||
| + | * https://access.triplelift.com/ | ||
| + | * https://mydata.appnexus.com | ||
| + | * https://www.captify.co.uk/data-subject-rights-request/ | ||
| + | * https://registry.mplatform.com/ | ||
| + | * https://datacloudoptout.oracle.com/registry/ | ||
| + | * https://cross-device-privacy.adobe.com | ||
| + | * {{Q|1184}} | ||
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)