IRI: http://ciolaws.com/ontologies/eulr-consent#Consent
IRI: http://ciolaws.com/ontologies/eulr-consent#Information
NEED TO ADD REFERENCE to art 10 and 11 of Dir 95/46/EC
IRI: http://ciolaws.com/ontologies/eulr-consent#ValidConsent
What are the modalities of the prior informed consent?
Consent must be collected in a way that assures its validity. The Regulations does not prescribe how consent is to be obtained. Each Member State DPO provides its own guidance.
IRI: http://ciolaws.com/ontologies/eulr-consent#givesConsent
When must the consent be provided?
Consent must be provided before the processing of personal data starts, but it can also be required in the course of a processing, where there is a new purpose. This is stressed in various provisions of Directive 2002/58/EC, either through the requirement "prior" (e.g. Article 6.3) or through the wording of the provisions (e.g. Article 5.3).
Until when is the consent valid?
Individuals who have consented should be able to withdraw their consent, preventing further processing of their data. This is confirmed also under the ePrivacy Directive for specific data processing operations based on consent, such as the processing of location data other than traffic data.
IRI: http://ciolaws.com/ontologies/eulr-consent#isReceivedBy
IRI: http://ciolaws.com/ontologies/eulr-consent#isSeekedBy
IRI: http://ciolaws.com/ontologies/eulr-consent#providesInformation
IRI: http://ciolaws.com/ontologies/eulr-consent#Explicit
As to how consent must be provided, Article 8.2(a) requires explicit consent to process sensitive data, meaning an active response, oral or in writing, whereby the individual expresses his/her wish to have his/her data processed for certain purposes. Therefore, express consent cannot be obtained by the presence of a pre-ticked box. The data subject must take some positive action to signify consent and must be free not to consent.
has characteristics: functional
IRI: http://ciolaws.com/ontologies/eulr-consent#FreelyGiven
For consent to be valid, it must be freely given. This means that there must be no risk of deception, intimidation or significant negative consequences for the data subject if he/she does not consent. Data processing operations in the employment environment where there is an element of subordination, as well as in the context of government services such as health may require careful assessment of whether individuals are free to consent.
has characteristics: functional
IRI: http://ciolaws.com/ontologies/eulr-consent#hasLegalCapacity
Valid consent presupposes individuals' capacity to consent. Rules regarding the capacity to consent are not harmonised and may therefore vary from Member State to Member State.
IRI: http://ciolaws.com/ontologies/eulr-consent#Informed
Consent must be informed. Articles 10 and 11 of the Directive lists the type of information that must necessarily be provided to individuals. In any event, the information provided must be sufficient to guarantee that individuals can make well informed decisions about the processing of their personal data. The need for consent to be "informed" translates into two additional requirements. First, the way in which the information is given must ensure the use of appropriate language so that data subjects understand what they are consenting to and for what purposes. This is contextual. The use of overly complicated legal or technical jargon would not meet the requirements of the law. Second, the information provided to users should be clear and sufficiently conspicuous so that users cannot overlook it. The information must be provided directly to individuals. It is not enough for it to be merely available somewhere.
has characteristics: functional
IRI: http://ciolaws.com/ontologies/eulr-consent#Specific
Consent must be specific. Blanket consent without determination of the exact purposes does not meet the threshold. Rather than inserting the information in the general conditions of the contract, this calls for the use of specific consent clauses, separated from the general terms and conditions.
has characteristics: functional
IRI: http://ciolaws.com/ontologies/eulr-consent#Unambiguous
For data other than sensitive data, Article 7(a) requires consent to be unambiguous. "Unambiguous" calls for the use of mechanisms to obtain consent that leave no doubt as to the individual's intention to provide consent. In practical terms, this requirement enables data controllers to use different types of mechanisms to seek consent, ranging from statements to indicate agreement (express consent), to mechanisms that rely on actions that aim at indicating agreement.
Consent based on an individual's inaction or silence would normally not constitute valid consent, especially in an on-line context. This is an issue that arises in particular with regard to the use of default settings which the data subject is required to modify in order to reject the processing. For example, this is the case with the use of pre-ticked boxes or Internet browser settings that are set by default to collect data.
has characteristics: functional
This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.
Directive 95/46/EC Article 2 (h) of Directive 95/46/EC defines consent as "any freely given specific and informed indication of his wishes by which the data subject signifies his agreement to personal data relating to him being processed"