Cookies and storage
This English version is an informational translation, not a certified legal translation. The Spanish text is the editorial reference; mandatory privacy and consumer rights are not limited by that reference. Spanish original
Version 2026-09-05.2 · Updated: 2026-09-05
Review draft: contains information awaiting confirmation by Mundimar and requires legal review before final publication.
1. What was checked
Audit visits to the published page and local version found zero cookies and no application use of localStorage or sessionStorage. Network requests, loaded resources, the form and served JavaScript were checked. This does not constitute an internal audit of Netlify’s servers.
No preference, analytics or advertising cookies were identified. No cookie list with invented lifetimes is provided: where a category is unused, provider, name and duration do not apply.
2. Cookies, storage and caching
A cookie is a small item of data retained by the browser that may be sent with later requests. localStorage and sessionStorage hold information accessible to website code; they are not cookies, although equivalent device-access rules may apply.
HTTP caching may retain images, fonts and files to avoid repeated downloads. This website does not use it to assign an advertising identifier. Server connection logs are not cookies and are not necessarily removed when browser data is cleared.
3. Technology inventory
First- and third-party cookies: none observed on audited routes and under tested conditions. Language preference: the URL determines ES or EN; no persistent preference is saved and no browser-language redirect is forced.
localStorage, sessionStorage and IndexedDB: the application has no mechanism for saving drafts, enquiries or identifiers. No service worker is installed for notifications, tracking or offline use; icons and a manifest do not imply one is installed.
Fonts and images are hosted with the website, without automatic requests to Google Fonts or the photo sources. The map is a Google Maps link, not an iframe. WhatsApp opens only on user action, with no preloaded SDK or widget; its own service may use its own cookies and technologies. The form uses a local honeypot, not Netlify Forms, Akismet or a third-party CAPTCHA.
Analytics and advertising: no client-side Google Analytics, Tag Manager, Meta Pixel or equivalent tracking scripts were identified. Any statistics or logs available in the hosting account require separate review; the server is not presumed to process no data.
4. Why there is no banner
The reviewed configuration includes no non-essential technologies requiring prior consent. An acceptance banner with no actual purpose is therefore not added. This conclusion depends on retaining the audited configuration, not on the website being static.
Before introducing analytics, advertising, embedded content, a persistent preference or other device access, its purpose and necessity must be assessed. Where consent is required, resources must remain blocked until a valid choice, with similarly easy acceptance, rejection and configuration, no preselected boxes and no penalty for rejection.
There are currently no application cookie consents to withdraw. If consent management is introduced, users must be able to change or withdraw their choice through a permanent access point as easily as giving it.
5. Browser controls and external services
You can inspect, block or delete cookies and site data through your browser’s privacy settings. Clearing the cache requires some resources to be downloaded again. These actions do not automatically delete an email already sent or an enquiry stored in Netlify; contact Mundimar to exercise the relevant rights.
Following a link to Google Maps, iRyx or another external site may expose you to that destination’s own technologies. They are not preloaded merely because the link is shown; consult the destination’s terms. This website’s external links are configured not to send the referring URL.
6. Contact and review
For questions about these technologies or associated data, contact mundimar@mundimarportals.com. The version and date reflect the reviewed configuration. Changes to hosting, scripts, forms or external services require a new inventory before retaining this statement.