This Cookie Policy was last updated on May 18, 2026 and applies to citizens and legal permanent residents of the European Economic Area and Switzerland.
Introduction
Our website, https://lagunasdeballesteros.org/en (Hereinafter referred to as "the Website") uses cookies and other related technologies (for convenience, all technologies are referred to as "cookies"). Cookies are also placed by third parties we have engaged. In the document below, we inform you about the use of cookies on our Website.
2. What are cookies?
A cookie is a small, simple file that is sent along with pages of this website and stored by your browser on your computer's hard drive or another device. The information stored within it can be returned to our servers or the servers of relevant third parties during a subsequent visit.
3. What are scripts?
A script is a piece of program code used to make our website function properly and interactively. This code is executed on our server or on your device.
4. What is a web beacon?
A web beacon (or pixel tag) is a small, invisible piece of text or image on a website used to monitor traffic. Web beacons store various data about you for this purpose.
5. Cookies
5.1 Technical or functional cookies
Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website, and for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.
5.2 Statistics cookies
We use statistics cookies to optimize the website experience for our users. With these statistics cookies, we gain insights into the usage of our website. We ask for your permission to place statistics cookies.
5.3 Marketing/Tracking Cookies
Marketing/tracking cookies are cookies or any other form of local storage used to create user profiles for displaying advertising or for tracking the user on this website or across several websites for similar marketing purposes.
6. Placed cookies
Sharing data
This data is not shared with third parties.
Functional
persistent
Store user preferences
persistent
Store user preferences
persistent
Store logged-in users
Statistics
1 year
Store and count pageviews
2 years
Store and count pageviews
Sharing data
This data is not shared with third parties.
Statistics
1 day
Referrer website
session
Store which page was visited first
Sharing data
This data is not shared with third parties.
Functional
Two days
To prevent cached pages, you can use HTTP headers such as `Cache-Control`, `Expires`, and `Pragma`. Here's a breakdown of common methods:1. **`Cache-Control` Header:** This is the most comprehensive header for controlling caching.
* **`no-cache`:** This directive tells the cache that it must revalidate the cached version with the origin server before using it. The response can be cached, but the cache must check with the origin server if the response is still valid.
* **`no-store`:** This directive instructs the cache to not store the response at all. The browser and any intermediate caches will not cache the content. This is the most restrictive setting for preventing caching.
* **`max-age=0`:** Similar to `no-cache`, this tells the cache that the content is immediately stale and needs to be revalidated.
* **`s-maxage=0`:** This is the shared cache equivalent of `max-age`. It's useful for controlling caches like CDNs.**Example `Cache-Control` usage:**
```
Cache-Control: no-store, no-cache, must-revalidate
```
or more commonly:
```
Cache-Control: no-cache
```
(if you want to allow revalidation but not store stale content).2. **`Pragma` Header:** This is an older HTTP/1.0 header. While `Cache-Control` is preferred, `Pragma` is sometimes used for backward compatibility.
* **`Pragma: no-cache`:** This directive serves a similar purpose to `Cache-Control: no-cache` for older clients.**Example `Pragma` usage:**
```
Pragma: no-cache
```3. **`Expires` Header:** This header specifies a date and time after which the response is considered stale. Setting it to a past date effectively disables caching for that resource.
* **`Expires: 0` or `Expires: -1` or `Expires: Thu, 01 Jan 1970 00:00:00 GMT`:** Setting the expiration date to a past time tells the browser that the content is already expired and should not be used from the cache.**Example `Expires` usage:**
```
Expires: 0
```**How to Implement:**You would typically set these headers in your web server configuration (e.g., Apache, Nginx) or within your application code (e.g., PHP, Python, Node.js).**Server-side Example (Nginx):**```nginx
location /no-cache-resource {
add_header Cache-Control "no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0";
add_header Pragma "no-cache";
add_header Expires "0";
# ... your resource serving directives
}
```**Server-side Example (Apache):**```apache
Header set Cache-Control "no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0"
Header set Pragma "no-cache"
Header set Expires "0"```**Client-side (JavaScript) - Less recommended for preventing caching, more for forcing refresh:**While not ideal for preventing caching in the first place, you can use JavaScript to force a refresh by including a dynamic query parameter (like a timestamp) to your URL when reloading a page. This makes the browser think it's a new URL.```javascript
window.location.href = window.location.href + "?v=" + new Date().getTime();
```
However, this is more of a workaround and doesn't fundamentally prevent caching at the HTTP header level.**Important Considerations:*** **Network Caches (Proxies, CDNs):** `Cache-Control` directives like `no-store` and `no-cache` are generally respected by intermediate caches. `s-maxage` is specifically for these shared caches.
* **Browser Cache:** The described headers are the primary way to control browser caching behavior.
* **User Confusion:** Aggressively disabling caching can lead to slower load times for users, as every resource has to be fetched from the server. Use it only when necessary (e.g., for sensitive data, frequently changing content that must be real-time).
* **Combined Directives:** It's common and recommended to combine `no-cache`, `no-store`, and `must-revalidate` for strong cache prevention.Choose the method that best suits your needs and the environment where your application is deployed. For most cases, using `Cache-Control: no-store, no-cache, must-revalidate` is the most effective way to prevent caching.
Functional
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
Marketing
expires immediately
Read user IP address
Marketing
expires immediately
Read user IP address
Marketing
session
Store location data
six months
Provide ad delivery or retargeting
session
Store and track interaction
8 months
Store user preferences
Sharing data
Sharing of data is pending investigation
Purpose pending investigation
brx_builder_dynamic_data_active_groups
HappyFilesExpandIds
brx_builder_control_spacing_view
brx_active_window
ff_entries_date_filter
brx_builder_dynamic_data_pinned_tags
brx_builder_color_palette_view
brx_state_globalClasses
brx_state_colorPalette
brx_builder_color_palette_id
brx_state_globalVariables
brx_state_themeStyles
brx_state_pinnedElements
brx_state_components
brx_builder_popuptab
brx_builder_global_variables_active_categories
brx_builder_panel_width
pys_advanced_form_data
wp-settings-time-1
pys_start_session
pys_first_visit
last_pysTrafficSource
last_pys_landing_page
_fbp
pys_session_limit
session ID
trp_language
cmplz_consented_services
365 days
cmplz_policy_id
365 days
cmplz_banner-status
365 days
_gid
/wp-admin/admin.php-elfinder-toolbarhideswp_file_manager
/wp-admin/admin.php-elfinder-lastdirwp_file_manager
PHPSESSID
wordpress_test_cookie
wp_lang
litespeed_qc_hide_banner
brx_builder_structure_width
WP_DATA_USER_3
AdobeCleanFontAdded
7. Consent
When you visit our website for the first time, we will show you a pop-up with an explanation about cookies. As soon as you click on "Save preferences," you consent to us using the categories of cookies and plug-ins you selected in the pop-up, as described in this Cookie Policy. You can disable the use of cookies via your browser, but please note that our website may no longer work properly.
7.1 Manage your consent settings
You have loaded the Cookie Policy without javascript support. On AMP, you can use the manage consent button on the bottom of the page.
8. Enabling/disabling and deleting cookies
You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.
Please note that our website may not function properly if all cookies are disabled. If you delete the cookies in your browser, they will be re-enabled after you give your consent when you visit our website again.
9. Your Rights Regarding Personal Data
You have the following rights regarding your personal data:
- You have the right to know why your personal data is needed, what will happen to it, and how long it will be retained.
- Right of access: You have the right to access your personal data that we have.
- Right to rectification: You have the right to supplement, correct, delete, or block your personal data at any time.
- If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
- Right to data portability: You have the right to request all of your personal data from the controller and to transfer it in its entirety to another controller.
- Right to object: You have the right to object to the processing of your data. We will comply with your objection unless we have compelling legitimate grounds for processing.
To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you, but you also have the right to submit a complaint to the supervisory authority (the Data Protection Authority).
10. Contact information
For questions and/or comments about our Cookie Policy and this statement, please contact us using the following contact details:
Global Nature Foundation
Corro del Postigo 1, Fuentes de Nava, 34337, Palencia, Spain
Spain
Website https://lagunasdeballesteros.org/en
Email: info@ex.comfundacionglobalnature.org
This Cookie Policy was synchronized with cookiedatabase.org on May 23, 2026.
Spanish
English
French
German
Italian
Portuguese