Wikidata:WikiProject PersonalData/DataModel
Items edit
From GDPR edit
Data controllers edit
Main categories edit
Industry edit
- Q61984598
- real-time ridesharing (Q16985745)
- media company (Q1331793)
- political party (Q7278)
- social networking service (Q3220391)
Instrument used edit
Data edit
Types of data edit
- user account (Q3604202)
- telephone number (Q214995)
- Advertising ID (Q48791487)
- browsing history (Q60533537)
- market segment (Q60533610)
- app usage measurements (Q60533636)
- geopositioning (Q638949)
- profiling information (Q60534050)
- notification system (Q3962191)
- unique identifier (Q6545185)
Uses of data edit
- identifier (Q853614)
- authentication (Q212108)
- user matching (Q60533572)
- two-factor authentication (Q17086335)
- targeted advertising (Q1628411)
- service personalisation (Q60533594)
- fraud prevention and detection (Q1451528)
- web analytics (Q15935024)
- Customer interaction management (Q5196462)
- advertising (Q37038)
Sources of data edit
Data subjects edit
Third parties edit
Sources of mapping edit
Properties edit
- instance of (P31)
- subclass of (P279)
- complies with (P5009)
- reference URL (P854)
- uses (P2283)
- object has role (P3831)
- has use (P366)
- of (P642)
- owner of (P1830)
- owned by (P127)
The following properties are not in WikiData yet:
- dpo email (using email address (P968) instead)
- source (using fabrication method (P2079) instead)
- contracts (using partnership with (P2652) instead)
- for (using has use (P366) instead)
Statements edit
Defining a data controller edit
- A data controller (Q59859818) is any natural or legal person, public authority, agency or other body which determines the purposes and means of personal data processing (except for AdTech companies, see discussion):
- The data controller (Q59859818) category is diverse. Data controllers can be social network services, media companies, political parties, etc (see Items, Industry). To show this, we say:
- We assume that each of the items listed under section Items, Industry are subclass of (P279) items listed under section Items, Main Categories
- The instrument used by a data controller (Q59859818) to manage data can be different Items, Instrument used. To show this, we say:
- The instrument is owned by an organization, which is why we state:
- And the reverse statement:
GDPR statements edit
- Any data controller (Q59859818) must have a privacy policy (Q1999831) published, which we link this way:
reference URL (P854) ⟨ https://www.theguardian.com/help/privacy-policy ⟩
- The data protection officer (Q30682903) e-mail address is the point of contact for exercising the right of access to personal data (Q60520997), and it should be added as a qualifier of the previous statement:
email address (P968) ⟨ mailto:dataprotection@theguardian.com ⟩
Note: we're using email address (P968) because "DPO e-mail", which is preferred, is not yet a property in WikiData.
Data use by data controllers edit
- A data controller (Q59859818) uses different kinds of data (see Data, Types of data), we show it through this main statement:
- The use or purpose of the data (see Data, Uses of data) used by data controller (Q59859818) is shown by qualifying the main statement:
Note: we're using has use (P366) because "for", which is preferred, is not yet a property in WikiData.
has use (P366) ⟨ targeted advertising (Q1628411) ⟩
- The source of the data (see Data, Sources of data) used by data controller (Q59859818) is shown by qualifying the main statement:
Note: we're using fabrication method (P2079) because "source", which is preferred, is not yet a property in WikiData.
fabrication method (P2079) ⟨ provided data (Q61151656) ⟩
- To whom belongs the data (see Data, Data subjects) used data controller (Q59859818) is shown by qualifying the main statement:
of (P642) ⟨ registered user (Q2642775) ⟩
- Some kinds of data have specific roles (see Data, Roles of data), like being a unique identifier (Q6545185), which is shown by qualifying the main statement:
object has role (P3831) ⟨ unique identifier (Q6545185) ⟩
Third parties edit
- A data controller (Q59859818) can hire an Q61984598 to provide advertising technology services (which imply working with personal data (Q43402563)), this relationship is stated by this main statement:
Note: we're using partnership with (P2652) because "contracts", which is preferred, is not yet a property in WikiData.
- The source of this information is diverse (see DataModel, Sources of mapping and is stated by qualifying the main statement:
Note: we're using fabrication method (P2079) because "source", which is preferred, is not yet a property in WikiData.
fabrication method (P2079) ⟨ Privacy Badger (Q17559386) ⟩
- If we have the information about which is the use an Q61984598 gives to certain data (e.g. from Privacy Badger (Q17559386) and its categories, see DataModel, Product), we state it by qualifying the main statement:
Note: we're using has use (P366) because "for", which is preferred, is not yet a property in WikiData.
List of other items relevant to this effort edit
This list is created automatically from WikiProject PersonalData (Q60228333):
This list is periodically updated by a bot. Manual changes to the list will be removed on the next update!
WDQS | PetScan | TABernacle | Find images | Recent changes | Query:SELECT ?item ?q { wd:Q60228333 wdt:P2650 ?item. OPTIONAL {?item wdt:P3921 ?q.} SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" } }
zzzother edit
Article | description |
---|---|
Adequacy decision | Data protection adequacy decision by the European Commission |
ads.txt protocol | |
agent processing personal data | entity performing actions on personal data |
An Ontology-based Platform to Collaboratively Manage Supply Chains | scholarly article |
Android permission | Permission used in the Android operating system |
AppCensus | project covering privacy issues in the Android app ecosystem |
Blinding Identity Taxonomy (BIT) | Taxonomy of Personally Identifiable Information, that should be most often encrypted to ensure proper privacy protection |
computing platform | hardware architecture and/or software framework |
data controller | natural or legal person, public authority, agency or other body which determines the purposes and means of personal data processing |
data protection officer according to GDPR | |
data protection supervisory authority | an independent public authority which is established by a EEA Member State (including EU Member States) pursuant to Article 51 General Data Protection Regulation |
Data Transfer Agreement | Agreement governing data transfers, and facilitating compliance with the General Data Protection Regulation in B2B contexts. |
Data Value Networks: Enabling a New Data Ecosystem | |
DataPolitics | database of data-driven consultants and companies in the context of politics |
Ethereum ontology | ontology of the Ethereum protocol |
EU-US Privacy Shield | an informal framework applicable to the transfer of data between the U.S. and the EU that was negotiated in 2015/2016 after the Safe Harbor framework had been declared null and void by the European Court of Justice |
European Data Protection Board | |
Exodus Privacy | project covering privacy issues in the Android app ecosystem |
Exploiting the Value of Data through Data Value Networks | scholarly article |
General Data Protection Regulation | European Union regulation on the processing of personal data |
Local ontologies for semantic interoperability in supply chain networks | scholarly article |
official app | official downloadable application of an element |
privacy policy | statement or a legal document |
RapidOWL - an Agile Knowledge Engineering Methodology | scholarly article |
Shattering one-way mirrors – data subject access rights in practice | scholarly article |
surveillance capitalism | monetization of personal information |
The Linked Data Value Chain: A Lightweight Model for Business Engineers | scholarly article |
Towards a Meta-model for Data Ecosystems | scholarly article |
Towards a value theory for personal data | scholarly article |
Two birds with one stone. An economically viablesolution for linked open data platforms | scholarly article |
Web API | HTTP based API used in web development |
Webxray project | project tracking third party tracking on the web |