INFOMARTION ABOUT COOKIES
Due to the entry into force of the amendment to the “Law on Information Society Services” (LSSICE) established by Royal Decree 13/2012, it is mandatory to obtain the express consent of the user of all websites that use disposable cookies, before the user navigates through them.
WHAT ARE COOKIES?
Cookies and other similar technologies such as local shared objects, flash cookies or pixels, are tools used by web servers to store and retrieve information about your
visitors, as well as to offer a correct operation of the site. Through the use of these devices the web server is allowed to remember some data concerning the user, such as his preferences for the visualization of the pages of that server, name and password, products he is most interested in, etc.
COOKIES AFFECTED BY, AND COOKIES EXEMPT FROM REGULATIONS
According to the EU directive, the cookies that require the user’s informed consent are analysis, advertising and affiliation cookies, while technical cookies and those that are necessary for the operation of the website or the provision of services expressly requested by the user are exempt.
TYPES OF COOKIES
DEPENDING ON THE PURPOSE
Technical and functional cookies: allow the user to navigate through a website, platform or application and the use of different options or services available in it.
Analysis cookies: allow the controller to monitor and analyse the behaviour of the users of the websites they are linked to. The information collected by this type of cookie is used to measure the activity of the websites, application or platform and to carry out browsing profiling of the users of said sites, applications and platforms, with the purpose of introducing improvements in the analysis of the user data carried out by service users.
Advertising cookies: allow management, in the most efficient way possible, of advertising spaces which, if applicable, the editor has included in a website, application or platform from where requested service is provided based on data such as the edited content or frequency with which advertisements are made.
Behavioural advertising cookies: collect information on the user’s personal preferences and choices (retargeting ) in order to allow management, in the most efficient way possible, of the advertising spaces which, if applicable, the editor has included in a website, application or platform from where the requested service is provided.
Social cookies: established by the social network platforms in the services to allow content to be shared with friends and networks. The social media platforms have the ability to track activity online outside the Services. This may affect the content and messages seen in other services used.
Affiliate cookies: allow you to track visits through links from other websites, with which the website establishes affiliate agreements (affiliate companies).
Security cookies: store encrypted information to avoid the stored data in them being vulnerable to malicious attacks by third parties.
ACCORDING TO THE PROPERTY
- Own cookies: are sent to the user’s terminal team from a team or power managed by the own editor and from where the requested service is provided by the user.
- Third party cookies: are sent to the user’s terminal team from a team or power which is not managed by the editor, but by another body which processes data obtained through the cookies.
DEPENDING ON THE STORAGE PERIOD
- Session cookies: are a type of cookie designed to collect and store data as long as the user accesses a website.
- Permanent cookies: are a type of cookies where data continues to be stored in the terminal and may be accessed and processed for a period of time defined by the cookie controller, and that can range from a few minutes to several years.
PROCESSING OF PERSONAL DATA
REALISTA DIGITAL SERVICES S.L. is the Controller of the personal data of the Data Subject and informs them that these data will be processed in accordance with the provisions of Regulation (EU) 2016/679, of 27 April 2016 (GDPR), and therefore the following information on the processing is provided:
Purposes of the data processing: as specified in the cookies section which are used on this website.
Legitimisation of the processing: by consent of the data subject (art. 6.1 GDPR).
Data storage criteria: as specified in the cookies section used on the website.
Data communication: data will not be disclosed to third parties, except in cookies owned by third parties or under legal obligation.
Derechos que asisten al Interesado:
- Derecho a retirar el consentimiento en cualquier momento.
- Derecho de acceso, rectificación, portabilidad y supresión de sus datos y a la limitación u oposición a su tratamiento.
- Derecho a presentar una reclamación ante la Autoridad de control (www.aepd.es) si considera que el tratamiento no se ajusta a la normativa vigente.
Rights of the Data Subject:
– Right to withdraw consent at any time.
– Right of access, rectification, portability and erasure of data and the limitation or objection to their processing.
The right to file a claim with the Spanish Supervisory Authority (www.aepd.es) if you consider that the processing does not comply with current legislation.
Contact information to exercise their rights:
REALISTA DIGITAL SERVICES S.L. Camino de los claveles, 147, puerta 3, 33203 Gijón. E-mail: hola@Realista.io
COOKIES USED ON THIS WEBSITE
Technical and functional:
| PROPERTY | COOKIE | PURPOSE | TERM | ||
|---|---|---|---|---|---|
| google.com | CONSENT | Google cookie consent tracker | in 17 years | ||
| realista.io | _gat_gtag_UA_ 167995355_1 |
Cookie required to use website options and services | Sesion | ||
| realista.io | pll_language | Cookie required to use website options and services | in a year |
Analytics:
| PROPERTY | COOKIE | PURPOSE | TERM | ||
|---|---|---|---|---|---|
| realista.io | _ga | ID used to identify users | in 2 years | ||
| realista.io | _gid | ID used to identify users for 24 hours after last activity |
in 22 hours |
Marketing:
| PROPERTY | COOKIE | PURPOSE | TERM | ||
|---|---|---|---|---|---|
| google.com | NID | This cookies is used to collect website statistics and track conversion rates and Google ad personalisation | In 7 months | ||
| realista.io | _fbp | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers | In 3 months |
THIRD PARTY COOKIES: Third-party services are beyond the control of the editor. Suppliers may at any time modify their service conditions, the purpose and use of cookies, etc.
| EDITOR | POLÍTICA DE PRIVACIDAD | ||||
|---|---|---|---|---|---|
| https://www.facebook.com/about/privacy/ | |||||
| Google Analytics | https://privacy.google.com/take-control.html | ||||
| https://privacy.google.com/take-control.html |
COOKIES CONFIGURATION PANEL: From this panel the user will be able to configure the cookies that the website can install in their browser, except for the technical or functional cookies that are necessary for browsing and using the different options or services that are offered.
HOW TO MANAGE COOKIES FROM YOUR BROWSER
Delete cookies from your device: Cookies that are already on a device can be deleted by clearing the browser history, thus deleting the cookies from all websites visited. However, some of the saved information (e.g. login data or website preferences) may also be lost.
Manage site specific cookies: For more precise control of site specific cookies, users can adjust their privacy settings and cookies in their browser.
Blocking cookies: While most modern browsers can be configured to prevent cookies from being installed on a device, this may require the manual adjustment of certain preferences each time a site or page is visited. In addition, some services and features may not work properly (for example, profile logins).
HOW TO DELETE COOKIES FROM MOST COMMON BROWSERS
- Chrome: http://support.google.com/chrome/answer/95647?hl=es
- Internet Explorer. Versión 11: https://support.microsoft.com/es-es/help/278835/how-to-delete-cookie-files-in-internet-explorer
- Firefox. Versión 65.0.1: https://www.mozilla.org/es-ES/privacy/websites/#cookies
- Safari Versión 5.1: https://support.apple.com/es-es/guide/safari/sfri11471/mac
- Opera: https://help.opera.com/en/latest/security-and-privacy/#clearBrowsingData
FUNCTIONALITY THAT INSERTS A COOKIE CONSENT PANEL AND BLOCKS THE ELEMENTS THAT COULD INSERT THEM
“PDCookieConsent” is a JavaScript library through which it is intended to facilitate the blocking of those elements that can embed cookies.
“PDCookieConsent” is used so that the website technician can insert a pop-up window (banner) notifying the visitor of the existence of cookies, as well as providing a means to manage cookies.
those elements that can generate them, blocking them and preventing them from being generated until their subsequent unblocking by the visitor.
How to insert the library on our website?
Insert the following script between the “head” and “/head” tags, on top of any other script that may be between the mentioned tags.
<rel link=”style sheet” href=”https://pdcc.gdpr.es/pdcc.min.css”>
<script src=”https://pdcc.gdpr.es/pdcc.min.js”></script>
<script type=”text/javascript”>
PDCookieConsent.config({
“brand”: {
“dev”: false,
“name”: “LEGAL VERITAS®”,
“url” : “https://legalveritas.es”,
“owner of the website”: “LEGAL VERITAS ®”
},
“cookiePolicyLink”: “…………………………………………..”,
“hideModalIn”: [
“…………………………………………..”
],
“styles”: {
“main button”: {
“bgColor”: “#A1FFA1”,
“txtColor”: “#036900”
},
“secondary button”: {
“bgColor”: “#EEEEEE”,
“txtColor”: “#333333”
}
}
});
</script>
How are the elements that insert cookies blocked?
Through “PD Cookie Consent” all “”iframe”” and “”script”” elements that contain a text string (a word, a fragment of a URL or a text) that are not allowed are blocked. The reason for not blocking all the elements by default is to avoid breaking functionalities of the website that do not already generate cookies.
The text string that will define if an element is going to be blocked exists predefined in a list of the library itself, it is elaborated taking into account those text strings that, in general, are part of elements that always insert cookies.
Also, as each website is a different world, we may come across elements that contain a non-permitted text string but do not insert cookies. We can also find elements of a website that insert cookies, but since they are not common elements between websites, the library does not take them into account. In both situations, the technician is offered the possibility of expanding or modifying the library list.
Text strings that are currently not allowed are: “facebook.”, “linkedin.”, “twitter.”, “vimeo.”, “youtube.”, “ytimg”, “google.com/maps”, “googleusercontent ”, “gstatic”, “maps.google.com”, “maps.googleapis”, “analytics”, “googletagmanager”, “urchin”, “adwords”, “doubleclick”, “googleadservices”, “googlesyndication”, “googletagservices ”, “googletraveladservices”.
Note that some of the text strings are words with a period after them (eg “facebook.”).
How does “PD Cookie Consent” work?
When a visitor accesses our website, the “PD Cookie Consent” library observes each of the elements on the visited page and if any of these meets the necessary requirements to be blocked, it is blocked (see the section “How do I block the elements that insert cookies?” of this same document).
Once all the elements of the page have been observed, the library will display the “PD Cookie Consent” panel and will generate a session cookie named “pd_cc”, which is necessary for its proper functioning.
In the first view of the panel, the website visitor will be able to:
1. Read the notice that informs about cookies.
2. Click on the “Cookie Policy” link.
In order to generate the “cookiePolicyLink” link that is displayed in the banner “For more
information consult the cookie policy”, it is necessary that the URL of the cookie policy exists.
domain cookies in the “URL Cookies Policy” field available in the website file
(DOCUMENTATION/INTERNET/WEB SITE).
If there is no data in the “cookiePolicyLink” field, the paragraph with the link is not displayed
to the “Cookie Policy”. To avoid this, you can put the link manually, for example
“https://demo.com/politica-cookies”.
3. Accept all cookies on the website by clicking “Accept”.
4. Go to the configuration view by clicking on “Configure”.
5. Close the panel.
If the website visitor presses the “Configure” button, they will get a new view
In the configuration view the visitor will be able to:
1. Go back to the previous view by clicking on the «<- Go back» link.
2. View the list with all domains not allowed, being able to:
Accept them independently.
Reject them independently.
View those that are new and were not listed in an old view. The text “(new)” appears next to it.
3. Accept all domains at once by pressing the “Accept all” button.
4. Reject all domains at once by pressing the “Reject All” button.
5. Save the changes made using the “Save Settings” button. Necessary
save the changes for these to be effective.
Once the panel is closed, there is the possibility of opening it again manually.
The library offers a CSS property for this purpose and any element that contains it will act as a button that opens the panel. We just have to choose any DOM element, such as a link, and insert the property (class=”pdcc-open-modal”).
<a href=”#” class=”pdcc-open-modal”>Panel Cookies</a>
Once the visitor clicks on the link, or on another element that contains the aforementioned property, the Configuration view of the “PD Cookie Consent” panel will open.
In addition to the “PD Cookie Consent” panel, the bookstore also provides a message that will appear at the top of the website and which will inform the visitor of the visual elements that have been blocked and therefore are not being displayed.
Before this message the visitor will be able to:
Find out about blocked content that is not being viewed, including the list of blocked items (in the case of the image provided, YouTube).
In relation to the list of blocked items, you can perform the following actions:
Accept all the blocked elements of the visited page by clicking “Accept all”, leaving these active in the rest of the website (if they exist). Once the button is pressed, the message will be hidden.
Open the configuration view by pressing the “Configure” button, being able to carry out any of the actions already mentioned in this same section of the document. The message will be hidden once the “Save configuration” button is pressed, as long as all the elements listed in the same message have been accepted.
