Cookie Policy (EU)

Last updated: 27 October 2026

1. What are cookies?

Cookies are small files that websites may store in a user’s browser or device when they visit a page. Among other functions, they allow websites to remember certain preferences, maintain the operation of services and manage privacy settings.

In addition to cookies, a website may use similar technologies, such as browser local storage, scripts, pixels or resources embedded from other websites.

This policy explains which cookies and related services have been identified on **OPK – Opistobranquis.info**, what they are used for and how visitors can manage their consent.

2. Who is responsible for this website?

The website covered by this policy is:

  • Website: https://opistobranquis.info/
  • Name: OPK – Opistobranquis
  • Website operator: Miquel Pontes
  • Contact: mpontes(at)marenostrum.org

The contact details should be completed with the information of the person responsible for the website.

3. What types of cookies do we use?

OPK uses a consent management system that allows visitors to decide whether to authorise optional services that may use cookies or similar technologies.

The categories used in the current configuration are as follows:

Technical or necessary cookies

These cookies enable the basic operation of the website, the management of browsing preferences and the storage of the choices made in the consent panel.

When they are strictly necessary to provide a service requested by the user or to transmit a communication, they do not require prior consent, although their use must be disclosed where applicable.

Marketing cookies and services

This category includes external services configured on OPK to remain blocked until visitors give their consent to the marketing category.

Currently, blocking is configured for the YouTube and Vimeo video players. If visitors do not authorise this category, embedded videos remain hidden. If they authorise it, the players may load from the providers’ servers.

Assigning these services to the marketing category reflects the current configuration of OPK’s consent management system. It does not necessarily mean that every cookie or technical operation performed by these providers has an advertising purpose.

4. Cookies identified on OPK

The following cookies were observed during browser checks. This list reflects the observations made up to the date of this policy’s latest update and may vary depending on the pages visited, the external services loaded and the consent choices made.

4.1. First-party cookies from opistobranquis.info
Name Known or likely purpose Category
qtrans_front_language Remembers the language preference used on the website. Technical or personalisation requested by the user.
cookieconsent_status Stores the overall status of the consent decision. Technical.
cookieconsent_status_marketing Stores the decision relating to the marketing category. Technical, for consent management.
cookieconsent_status_tech Stores the decision relating to the technical category. Technical, for consent management.

The consent cookies observed had an approximate expiry date of one year after their creation. Their effective duration may depend on the plugin configuration and should be checked again if that configuration changes.

4.2. YouTube cookies and services

The following cookies associated with the youtube.com domain were observed on pages containing YouTube videos:

Name Available information
_secure_enid A Google/YouTube cookie whose exact purpose and duration should be confirmed in the provider’s documentation.
_secure-Rollout_token A cookie associated with service operation or rollout mechanisms. Its exact purpose and duration should be confirmed.
_secure-ynid A provider cookie whose exact purpose and duration should be confirmed.
AEC A Google cookie related to security controls and protection against abusive requests.
DV A Google cookie whose specific purpose may depend on the service and context.
SEARCH_SAMESITE A cookie associated with security mechanisms and the control of requests between sites.
SOCS A Google cookie related to storing certain consent preferences.
VISITOR_INFO1_LIVE A cookie related to player functions and service preferences or measurements.
VISITOR_PRIVACY_METADATA A cookie related to users’ privacy preferences on YouTube.
YSC A cookie used by YouTube in connection with the player session.

This list records the cookies observed during testing. It does not mean that all of them are set on every visit or that they all have a fixed duration. Their purposes and retention periods may change depending on provider updates and the features of the player.

OPK uses the consent system’s service-blocking functionality to prevent YouTube videos from loading until visitors authorise the category configured for these services.

4.3. Vimeo cookies and services

The following cookies were observed on the player.vimeo.com domain on pages containing Vimeo videos:

Name Available information
_cf_bm A Cloudflare security cookie used to help distinguish automated traffic from legitimate traffic.
_cf_ob A cookie related to Cloudflare security or protection mechanisms. Its exact purpose should be confirmed.
cf_clearance A Cloudflare cookie related to passing certain security checks.

These cookies appeared while the Vimeo player and resources associated with its security infrastructure were loading. This observation alone does not establish whether they are set on every visit or what their exact duration is in each case.

Vimeo videos are configured to remain blocked until visitors authorise the marketing category. The player URLs observed included the dnt=1 parameter, which requests Vimeo’s Do Not Track mode. This parameter should not be interpreted as a guarantee that no cookies will be used or no data will be processed.

4.4. Other external services

OPK uses maps based on OpenStreetMap and the Leaflet library to display geographical information. During testing, requests to OpenStreetMap tile servers were observed.

Loading external maps may disclose technical information to the provider, such as the visitor’s IP address and the data required to deliver the requested resources. No OpenStreetMap first-party cookies were identified during the tests. However, this does not guarantee that no provider associated with mapping services uses cookies or similar technologies under any circumstances.

5. How is consent managed?

OPK uses the Beautiful and Responsive Cookie Consent plugin to display the cookie notice and store visitors’ preferences.

The system allows consent categories to be managed. In the current configuration, the options are presented through a differentiated consent system with two buttons and an option to save the settings.

Optional cookies or services should not load before the relevant consent has been obtained. Simply browsing the website, remaining on a page or closing the notice should not be interpreted as acceptance.

Visitors can accept or reject optional categories and subsequently change their decision using the cookie settings controls available on the website.

When consent is changed, the page may need to be reloaded for the blocking or activation of external services to take effect correctly. In particular, the current YouTube and Vimeo blocking configuration requires the page to be reloaded after changing the decision so that the players are hidden or displayed again.

6. How can I withdraw or change my consent?

Consent can subsequently be changed or withdrawn through the cookie settings mechanism available on OPK, provided that it is enabled and accessible.

When consent for the marketing category is withdrawn, YouTube and Vimeo players should remain blocked after the page is reloaded. Withdrawing consent does not affect cookies that are strictly necessary for the basic operation of the website or for remembering the privacy decision itself.

Visitors can also configure their browser to block or delete cookies. However, blocking all cookies may affect certain preferences or website features.

7. Third-party cookies and international data transfers

Some OPK content is provided through third-party services, such as YouTube, Vimeo, Google, Cloudflare and OpenStreetMap map servers.

These providers may receive technical information about visitors’ connections and devices when their resources are requested. Depending on the service, they may also process identifiers or other data in accordance with their own policies.

The use of external services may involve the processing of data outside the European Economic Area. Where applicable, the provider must have a legal basis and the safeguards required by the applicable legislation for international data transfers.

For further information about each provider’s practices, please consult their respective policies:

Including a provider in this list does not mean that all of its services are used on every OPK page.

8. Legal basis and applicable legislation

The use of cookies and similar technologies is governed, among other provisions, by Article 22.2 of Spanish Law 34/2002 on Information Society Services and Electronic Commerce (LSSI-CE), the General Data Protection Regulation (GDPR) where personal data is processed, and the applicable rules on privacy and electronic communications.

Cookies that are not strictly necessary generally require prior, freely given, specific, informed and unambiguous consent. Users must be able to reject optional cookies as easily as they can accept them and must be able to withdraw their consent subsequently.

Cookies that are strictly necessary to provide a service requested by the user or to transmit a communication do not require this consent, without prejudice to any applicable information obligations.

This policy should be read together with OPK’s Privacy Policy, which provides further information about the data controller, the exercise of data protection rights and the processing of personal data.

9. Updates to this policy

This policy may be amended when the cookies used, the integrated external services, the consent management system configuration or the applicable legal requirements change.

The update date shown at the beginning indicates the date of the latest editorial review of this document.