DATA EXPLOITATION. The Customer owns all the Data. The customer is solely responsible for the quality, lawfulness and relevance of the Data that it transmits to the Service Provider as well as for their use with the Application Service and the results thereof. In addition, the Customer guarantees to be the owner of all rights (including intellectual property rights and authorization of third parties) allowing him/her to use the Data. The Customer guarantees that the Data does not violate the laws and regulations in force, the rights of third parties and is free from any virus or malicious code likely to harm the Solution or the Application Service. If the Service Provider becomes aware that an element of the Data violates the above stipulations, the Service Provider is entitled to remove or render unavailable such an element. The Customer guarantees the Service Provider in the event of failure to comply with the stipulations of this article. The customer undertakes to defend the Service Provider at its own expense and indemnify the Service Provider against any costs, claims or damages incurred by the Service Provider or for which the Service Provider may be liable due to the customer's default.
DATA EXPLOITATION. The Licensee owns all the Data. The Licensee is solely responsible for the quality, lawfulness and relevance of the Data that it transmits to the Processor as well as for their use with the Application Service and the results thereof. In addition, the Licensee guarantees to be the owner of all rights (including intellectual property rights and authorization of third parties) allowing him/her to use the Data. The Licensee guarantees that the Data does not violate the laws and regulations in force, the rights of third parties and is free from any virus or malicious code likely to harm the Solution or the Application Service. If the Processor becomes aware that an element of the Data violates the above stipulations, the Processor is entitled to remove or render unavailable such an element. The Licensee guarantees the Processor in the event of failure to comply with the stipulations of this article. The Licensee undertakes to defend the Processor at its own expense and indemnify the Processor against any costs, claims or damages incurred by the Processor or for which the Processor may be liable due to the Licensee's default.
DATA EXPLOITATION. The Business Model of Data Collection Big Data Business models are usually based on Data-as-a-Service (DaaS). Such models could be classified into three main categories: Data collection by devel- oping digital products, e.g. collected data by users’ interaction with a platform. Machine Learning as a service, i.e. algorithm application to analyse aggregated data. And finally, data monetization, that is selling access to information for diverse goals, but mainly advertising purposes targeting individual people [9]. Data collection business can be identified as a complex dynamic system. As new actors, roles, activities and industrial agreements take place, the data market situation is constantly changing. To conduct data collection, the purposes should be reflected in the privacy policies as some the protection laws require. That is, the data subject should be informed about the data collection purposes, along with data sharing practices (e.g. purposes of collection and storage, third parties with whom datasets are shared) and be able to revoke this agreement. A close concept to this idea is the dynamic consent [10], whilst context around datasets changes, conditions for data processing also must change. A global scenario —in this case, based on GDPR elements [11], though it is applicable for any law framework such as CCPA [12]— which is identified as a distributed system. An overview of the global scenario is shown in Figure 1. The elements are also described in some legal ontologies based on GDPR [13–16]. There are entities who perform actions (i.e. data processing, dataset storage, data sharing, permission request, purpose definition etc.) according to their role defined by business processes. Adopting GDPR definitions, the roles are: Data Subject, Data Controller, Data Recipient, Data Protection Officer (DPO), and Data Processor. Each actor, except the data subject, is represented as a reposi- tory which may store a data subject’s dataset, and interacts with other actors’ repositories within their business processes model. Within this model, we iden- tify, up to four, information exchange channels described as interactions: – Data flow: The channel where data is transferred from one entity to another. A dataset is shared across several repositories. Each repository holds an Rethinking Privacy-Knowledge Modeling 7
DATA EXPLOITATION
