Last updated: October 7, 2026
This Cookie Policy explains how My Tenerife Experience uses cookies and similar technologies on https://mytenerifeexperience.com (the “Site”), the purposes for which those technologies may be used, and the choices available to visitors.
This policy should be read together with the Privacy Policy.
1. What cookies and similar technologies are
Cookies are small text files that a website or third-party service may store on, or read from, a browser or device. They can be used for a single browsing session or remain for a defined period. Similar technologies may include local storage, pixels, web beacons, SDK identifiers and other techniques that store or access information on a device.
2. Legal framework and consent
Where EU electronic-communications and data-protection rules apply, storing information on a user’s device or accessing information already stored generally requires prior consent unless the technology is strictly necessary to transmit a communication or provide a service explicitly requested by the user. Personal data generated through cookies or similar technologies is also subject to the GDPR where applicable.
Technical or strictly necessary technologies may be used without prior consent where the legal exemption applies, but visitors must still be informed about them. Profiling, advertising and other non-essential tracking technologies require prior consent where required by law. Analytics technologies must be assessed according to their configuration and applicable national rules; they are not automatically exempt merely because they are used for statistics.
3. First-party and third-party technologies
First-party cookies are set by the domain you are visiting. Third-party cookies or technologies are set or accessed by a different provider, for example a service embedded in the Site. Third parties determine their own purposes and retention periods for technologies under their control unless they act solely as processors on our behalf.
4. Session and persistent cookies
Session cookies normally expire when the browser session ends. Persistent cookies remain until their stated expiration date or until they are deleted. A provider may update the duration or name of a cookie when its software changes.
5. Categories used on or potentially relevant to this Site
Strictly necessary / technical
These technologies support functions such as website delivery, security, authentication, administrator sessions, fraud or abuse prevention, consent-preference storage and technical operation. Where they are strictly necessary for a service requested by the user, prior consent is normally not required.
Functional / preference
These technologies remember optional settings or choices, such as comment details or subscription status. Depending on the purpose and local law, some may require consent.
Analytics / measurement
Analytics technologies measure visits, referral sources, page popularity and technical performance. The Site currently has Jetpack Stats enabled. Whether an analytics technology requires consent depends on its implementation, data minimization, provider role, combination with other data and the law that applies.
Advertising / profiling
These technologies may build or infer interests, measure advertising, personalize ads or track behavior across websites. Where used, they require prior consent when applicable law requires it.
Affiliate / attribution
Affiliate links may contain referral identifiers in the URL. A plain outbound affiliate link does not necessarily store a cookie on this Site. After a visitor follows the link, the external provider may use cookies or similar technologies under its own policy to attribute a referral or transaction.
6. Services currently identified in the Site configuration
| Service | Purpose | Possible technology category |
|---|---|---|
| WordPress | Website operation, administrator authentication, user settings and optional comment convenience features | Necessary / functional |
| Jetpack / Automattic | Stats, Protect, contact forms, subscriptions and other enabled Jetpack functionality | Necessary, functional and/or analytics depending on the specific feature |
| Akismet | Spam and abuse detection for comments and compatible form submissions | Security / necessary processing; may also use technical identifiers |
| Gravatar | Avatar display associated with a commenter where comments are used | Third-party / functional |
| Booking.com and other external travel providers reached through affiliate links | Booking, travel services and referral attribution after a user chooses to leave the Site | Third-party / affiliate; provider-controlled after click-through |
7. WordPress cookies that may be relevant
The exact cookies present depend on whether a visitor logs in, comments, uses a password-protected page or enables an optional convenience feature. Typical WordPress cookies include:
| Cookie / pattern | Typical purpose | Typical duration | Category |
|---|---|---|---|
wordpress_test_cookie |
Checks whether the browser accepts cookies, generally in connection with the login page | Session | Necessary |
wordpress_[hash], wordpress_sec_[hash], wordpress_logged_in_[hash] |
Authentication and logged-in session management for registered users/administrators | Normally session or about 2 days; up to about 14 days where “Remember Me” is used | Necessary |
wp-settings-{user}, wp-settings-time-{user} |
Preserves WordPress administrator/user interface preferences | Typically up to 1 year | Functional / necessary for logged-in settings |
comment_author_{hash}, comment_author_email_{hash}, comment_author_url_{hash} |
Remembers commenter details when the visitor explicitly chooses the comment convenience option | Approximately 1 year | Functional / preference |
wp-postpass_{hash} |
Remembers access to a password-protected WordPress post or page | Typically about 10 days | Necessary / functional |
Cookie names can contain site-specific hashes or user identifiers and may differ slightly between WordPress versions or configurations.
8. Jetpack cookies and similar technologies
Jetpack is active on the Site. The database configuration currently includes Stats, Protect, contact forms and subscriptions. Jetpack may use different cookies depending on the feature and user interaction. According to Jetpack’s documentation, examples that can be relevant to enabled features include:
| Cookie / pattern | Purpose | Documented duration | When relevant |
|---|---|---|---|
jpp_math_pass |
Remembers that a user successfully completed a math challenge used by Brute Force Attack Protection | 1 day | When that protection challenge is presented |
stnojs |
Used in the administrator area when Stats reports are requested without JavaScript | 2 days | Admin-area Stats use |
jetpack_comments_subscribe_[post_id] |
Remembers a user’s choice to subscribe to comments on a post | Approximately 347 days | When comment subscriptions are used |
jetpack_blog_subscribe_[post_id] |
Remembers a user’s choice to subscribe to the Site | Approximately 347 days | When Site subscriptions are used |
tk_ai, tk_qs |
General analytics identifiers used by certain Jetpack features | Session | Only where a Jetpack feature that uses them on the front end is enabled |
This list is not a statement that every listed Jetpack cookie is set on every visit. Jetpack uses different technologies according to the modules enabled and the actions performed. For the provider’s current list, see Jetpack Cookies.
9. Jetpack Stats
Jetpack Stats is enabled in the Site configuration. It is used to understand traffic and content performance. Jetpack’s cookie documentation indicates that the Stats feature itself primarily documents an administrator-area cookie (stnojs) for viewing reports without JavaScript, while other Jetpack analytics cookies may be used by specific Jetpack features. Analytics processing can also occur through server-side or non-cookie techniques, so the absence of a particular cookie does not necessarily mean that no analytics data is processed.
10. Jetpack Protect
Jetpack Protect is enabled to help defend the Site against malicious login attempts and automated abuse. Security technology may process IP addresses, user-agent information, login-attempt metadata and similar technical data. Where a security cookie is strictly necessary to protect an authentication or requested service, the applicable legal exemption may apply.
11. Jetpack subscriptions
If you choose to subscribe to the Site or to comments, Jetpack may process your email address and subscription choices and may set a cookie that remembers the subscription state. Subscription functionality is optional and initiated by the user.
12. Akismet
Akismet is enabled for anti-spam protection. It may process IP address, user agent, referrer, form/comment content and other submission metadata to determine whether a message is spam. Akismet’s service is primarily an anti-abuse function. Additional information is available in the Akismet Privacy Policy.
13. Gravatar
Where comments are enabled, a hash derived from a commenter’s email address may be sent to Gravatar to determine whether an avatar is associated with that address. Gravatar may use cookies or other technologies under Automattic’s own policies. A profile image may be publicly displayed next to an approved comment.
14. Affiliate links and Booking.com
The Site contains affiliate links, including links to Booking.com. These links may contain an affiliate or partner identifier. Merely displaying a normal text affiliate link does not necessarily place a Booking.com cookie on your device from this Site. If you choose to click the link and visit Booking.com or another external provider, that provider may set or read cookies and process information according to its own privacy and cookie notices.
For more information about the Site’s commercial relationships, see the Affiliate Disclosure.
15. Embedded content and future third-party services
Pages may include or later add maps, videos, social-media content, booking widgets or other third-party components. Such content can allow the third party to receive technical information and potentially set or read cookies as if you visited that third party directly. Where a non-essential third-party component requires consent, it should not be activated before the required consent is obtained.
16. Consent requirements
Where prior consent is required, consent must be freely given, specific, informed and unambiguous. Non-essential technologies that require consent should not be activated merely because a user continues scrolling or browsing, and optional categories should not be pre-selected as accepted.
Refusing or withdrawing consent should not prevent access to ordinary Site content unless a particular third-party feature genuinely cannot operate without the relevant technology.
17. Withdrawing or changing consent
Where the Site provides a cookie-preferences or consent interface, you can use it to review or change your choices. Consent must be capable of being withdrawn as easily as it was given. You can also delete cookies through your browser; however, deleting cookies does not by itself communicate a withdrawal of consent to every third-party service and may also delete the record of your previous preference.
18. Browser controls
Most browsers allow you to inspect, delete, block or restrict cookies for all websites or for selected domains. Blocking all cookies may affect authentication, comment preferences or other Site functions. Browser manufacturers provide current instructions in their help and privacy settings.
19. Global privacy signals and browser preferences
Some browsers or extensions send privacy preference signals. The legal effect of these signals varies by jurisdiction and technology. Where a signal is legally binding on a particular processing activity, it should be honored as required by applicable law. Browser settings should not be assumed to replace a consent mechanism where the law requires an explicit Site-level choice.
20. Cookie duration and retention
The duration shown in the tables above is a typical or provider-documented duration and can change with software updates or configuration. Personal data derived from a cookie may also be retained separately by the relevant provider for a different period. See the Privacy Policy and the relevant provider’s documentation for information about personal-data retention.
21. Third-party responsibility
Third-party providers control cookies and other technologies that they set as independent controllers. Their cookie names, purposes and expiration periods may change without direct changes to this Site. Visitors should review the current privacy and cookie information of external services they choose to use.
22. Changes to the cookie inventory
The Site may add, remove or reconfigure plugins, widgets or external services. The cookie inventory should therefore be reviewed periodically and updated when technologies or purposes materially change. The presence of a cookie can also differ according to whether you are logged in, whether comments are enabled, whether you have subscribed to a feature and which consent choices you have made.
23. Changes to this Cookie Policy
This Cookie Policy may be updated to reflect changes in technologies, service providers, consent practices or legal requirements. The “Last updated” date at the top identifies the latest revision.
24. Contact
For questions about cookies, privacy or consent choices on this Site, contact mytenerifeexperience@gmail.com or use the Contact page.
25. Consent Management Platform (CMP)
This Site includes a first-party consent management interface integrated directly into the WordPress theme, without an additional cookie-banner plugin. On the first visit, optional categories are disabled by default. Visitors can Accept all, Reject non-essential technologies, or open Customize to make category-by-category choices.
The consent interface uses the first-party technical cookie mte_consent_v1 (and a local-storage copy as a resilience mechanism) solely to remember the visitor’s privacy choices. The consent record contains the policy version, category choices and the time of the choice. It is configured to expire after approximately 180 days. It is not used for advertising or audience profiling.
Consent categories used by the CMP
- Strictly necessary: always active for core site operation, security and storage of the privacy choice.
- Analytics: optional. This category controls audience-measurement technologies such as Jetpack Stats where consent is required.
- Preferences & external content: optional. Intended for non-essential features and third-party embedded content that may contact external services or remember preferences.
- Marketing: optional. Intended for advertising or marketing trackers if such technologies are used. Ordinary outbound affiliate links remain available without enabling this category; third-party processing may begin after the visitor chooses to follow an external link.
Visitors can reopen the preference panel at any time through the persistent Cookie settings control displayed on the Site. Revoking consent stops future optional activation where technically possible; it cannot undo processing that lawfully occurred before withdrawal.
Jetpack Stats consent control
The Site configures Jetpack Stats to honor the WordPress consent category for statistics. The CMP exposes the visitor’s Analytics choice through a WordPress Consent API-compatible browser interface. Until Analytics is allowed, the Jetpack Stats tracking event is not activated by the Site’s consent logic. If the visitor later allows Analytics, tracking can start from that point.
The CMP is a site-specific consent interface and is not presented as an IAB Transparency & Consent Framework certification or third-party compliance certification. The technologies actually used on the Site should be reviewed periodically, especially after adding new embeds, advertising systems, analytics services or plugins.