Privacy & Cookies Policy

Identification data

The data collected from registered and non-registered users of the CS TRACK project fall within the scope of the standard operation of research projects funded under H2020.

The research team uses this information to guide its work in communicating and creating a community of interest in Citizen Science. The authors of the entries and information published both on the website and on the Community Platform are responsible for the data on individuals that may contain or appear in their communications.

The researchers of the CS TRACK project comply with industry standards of data privacy, specifically the provision of the European Union’s General Data Protection Regulation (GDPR) for “data subject rights” which include (a) notice of breach; (b) right of access; (c) right to be forgotten; (d) data portability; and (e) privacy by design. The GDPR also allows for the recognition of the “public interest in the availability of the data”, which is of relevance to those involved in maintaining, with the greatest possible integrity, the public record of scholarly publications.

Who is responsible for the data?

  • The person responsible for the processing is the IP of the Ciberimaginario Research Group of the Rey Juan Carlos University.
  • Contact:

What information do we collect and for what purpose do we process your data?

  • Send communications about the results of the project and the activity of the community.
  • Guide users on models of community participation.
  • Improve the retrieval of information and content of interest by users through the collection of aggregated data on their behaviour on Community Platform.
  • Manage the correspondence with the users of the community of interest.
  • Send information and informative communications related to the scientific research, the areas of interest and focus of the project through various means, including the project newsletter, managed by means of the external application Mailchimp.
  • To carry out statistical studies related to the areas of interest and the focus of the project.

How long do we keep your data?

The personal data provided will be deleted at the end of the project and the deletion is made in accordance with the provisions of Regulation EU 2016/679 of the European Parliament and of the Council of 27 April 2016, (Art 17, 1a)

What is the legitimacy for the processing of your data?

The legal basis for the processing of your data is the provision of information service on the Community Platform and/or consent of the person concerned

In order to send you newsletters via the e-mail address you provide in order to contact you personally or to recognise you on your next visit, we rely on your informed consent.

The treatment of the information that our cookies collect is based on the informed consent that you give us, in accordance with current legislation.

To which recipients will your data be communicated?

Data may be shared with CS Track project partners on an anonymous, aggregated basis, with appropriate exceptions, such as community publication metrics.

Personal metadata linked to the publication of an article (authors’ names, professional affiliation, country) are deposited and distributed, associated with those of the public content of the publication.

The data will not be transferred or sold, nor will they be used for purposes other than those established here.

Is there an obligation to provide data or any consequences it not doing so?

Failure to provide the data explicitly requested will prevent registration and participation on the community platform, sending messages and exploring the results of the project.

How do we protect your data?

The CS Track project’s website and community platform use information security techniques generally accepted in the industry, such as firewalls, access control procedures and cryptographic mechanisms, all with the aim of preventing unauthorized access to data. To achieve these purposes, the user accepts that the provider obtains data for the purposes of the corresponding authentication of access controls. All information is always transmitted via secure communication protocol (https, SSL), so that no third party has access to the information transmitted electronically.

All personal data is stored securely in accordance with the general EU data protection regulation (Regulation (EU) 2016/679) (GDPR).

What are your rights when you provide us with your data?

Data subjects have the right to access their personal data, as well as the right to request that inaccurate data be corrected or, where appropriate, that it be deleted. The deletion of the minimum data required to be registered on the platform (username, first name and surname, and e-mail) will result in the effective removal of the user profile from the platform.

You have the right to file a complaint with the Control Authority – Spanish Data Protection Agency.

How to exercise your rights?

You can exercise these rights by using the contact form on the website or by sending a request or message to the address

Right to withdraw consent: You have the right to withdraw your consent sending a request or message to the address

Right to complain to the Control Authority: Spanish Data Protection Agency (AEPD),

Cookie Policy

The CS Track project website uses cookies to manage user sessions, which are necessary if you are a member of the community platform. Cookies are not used if you only access the community platform or the website as a reader, without registration. On some pages we use cookies to remember issues such as: a) your presentation preferences; b) the processing status of your activity on the platform; c) the reading of notifications related to communications with other users or information alerts on the community platform; d) whether or not you have given your consent for us to use cookies on our website; or e) the reading access made previously. In addition, some multimedia resources, such as the videos embedded in our pages, use cookies to produce anonymous statistics on how you have reached them and which videos you have viewed. Although cookies are not essential for the website to function, enabling them will provide you with a better browsing experience. You can delete or block cookies, but if you do so, some of the features of this website may not work properly. These cookies are essential for access to certain platform functions, so if they are not enabled you will not be able to use this system. In addition, we keep the data on your web browsing patterns fully under our control. These cookies are used exclusively for the purposes indicated here.

Cookies required

Cookies will only store the information necessary to make the platform usable by activating basic functions such as page navigation and access to secure areas of the site.

The following table indicate the cookies used on the CS-Track site.

Cookie name Purpose Category Expiration Third party
phrasesActiveTabIndex For user page settings. Strictly necessary Temporary (1 week) No. Own
Seopress-user-consent-accept This cookie is set when you accept or deny cookies when you first visit the website. This cookie does not store any personal information. Strictly necessary Temporary (1 month) No. Own
WordPress_logged_in It indicates when you have connected and who you are, being used for the WordPress interface. Strictly necessary Session No. Own
WordPress_sec Used by WordPress to maintain the session for a registered user. Strictly necessary Session No. Own
WordPress_test_cookie Used by WordPress to test if the browser used can accept cookies. Strictly necessary Session No. Own
Wp-icwp-wpsf WordPress Security. Strictly necessary Permanent No. Own
Wp-settings-time It is used to customize your view of the admin interface, and possibly the main site interface as well. Strictly necessary Temporary (1 year) No. Own
APISID, HSID, SAPISID Technical cookies used by YouTube Purpose Session Youtube
CONSENT, NID, SAPISID, SID, SIDCC It collects information for the Google search engine included in the web (Google CSE). Purpose 20 years
SAMESITE It reduces the risk of information leakage and, consequently, it will improve the protection of cross-site attacks through false requests. Purpose 2 month Google
_utma It is used to distinguish users and sessions. The cookie is created when the JavaScript library executes and there is no __utma cookie. The cookie is updated every time data is sent to Google Analytics. Analysis Every sesión Google
_ga [x4] Records a unique ID that is used to generate data statistics about how the visitor uses the website- Analysis Temporary (2 years) Google
gid [x4] Records a unique identification that is used to generate data statistics about how the visitor uses the website Analysis Temporary (1 year) Google
_currentTime Records the date and time of the user’s last visit to the website Analysis Session Google
Userlang Remembers the language selected by a user to display a web page. Preferences Temporary (1 year) No. Own
1P_JAR Google advertising cookie that is used in order to track the user and provide personalized ads Advertising Temporary (1 month) Google
ANID These cookies have an advertising purpose for the Google Adwords service. Advertising Temporary (1 month) Google
DV It is used by Google to provide services and extract anonymous information about browsing. Advertising Temporary (1 day) Google




These cookies are used to deliver advertisements more relevant to you and your interests. Advertising Temporary (2 years) Google
SSID Measure ads performance and provide recommendations. Advertising Persistent Google
_hjSessionUser{site_id} Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. Analysis 1 year Hotjar
_hjSession{site_id} A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. Analysis 30 minutes Hotjar
Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. Analysis 1 year Hotjar


Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in

Analysis 1 year Hotjar


Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.

Analysis 1 year Hotjar


Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.

Analysis 1 year Hotjar


Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.

Analysis Session Hotjar


If present, this cookie will be set to ‘1’ for the duration of a user’s session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.

Analysis Session Hotjar


A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.

Analysis Session Hotjar


Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.

Analysis 1 year Hotjar


This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).

Analysis Session Hotjar


This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.

Analysis Session Hotjar

Web metrics analysis

The website’s servers will automatically detect the IP address and domain name used by the user. An IP address is a number that is automatically assigned to a computer when it connects to the Internet. All this information is recorded in a server activity file that allows subsequent processing of the data in order to obtain only statistical measurements that allow us to know the number of page impressions, the number of visits made to the web services, the order of visits, the point of access, etc. For this purpose, both internal WordPress analytical systems and the external service of Google Analytics are used.

Help us disseminate our research results

Be the first to receive updates about CS Track project results, opinion pieces and News&Events related to Citizen Science.

Email Address
Twitter Account

Subscribe to our newsletter

Why we ask for profiles?

We ask for your profile for research purposes only. Filling in your profile does not imply to filtering the content you will receive.

I do not know which is my profile
  1. Policy-maker: Regional, national or international policy-maker or influencer.
  2. Academic: Academic engaged in research related to Citizen Science.
  3. Citizen Scientist: Citizen Scientist involved in or managing/planning one or more Citizen Science project.
  4. Organisational representative: member of a civil society organisation or NGO supporting Citizen Science (including science centres and musea, CS clubs and platforms etc.).
  5. Company representative: company employee supporting and/or funding Citizen Science projects or activities.
  6. Educator: Educator interested in supporting and promoting Citizen Science in an educational setting.
  7. Other.