Last updated: October 7, 2026.
This Cookie Policy explains how My Greece Experience uses cookies and similar technologies on mygreeceexperience.com. It should be read together with our Privacy Policy.
1. What cookies and similar technologies are
A cookie is a small text file or piece of information stored by a website or service in a browser or device. Cookies can be session cookies, which normally expire when the browser session ends, or persistent cookies, which remain until their stated expiry date or until they are deleted. Similar technologies can include pixels, tags, local storage, scripts and other mechanisms that store information on, access information from, or recognise a browser or device.
2. Legal framework and consent
Under European ePrivacy rules and applicable national law, technologies that are strictly necessary to provide a service expressly requested by the user may generally be used without prior consent. Non-essential technologies used for purposes such as profiling or certain forms of analytics or tracking require prior consent where the law requires it. Where personal data is processed, the GDPR also applies to that processing.
Where consent is required, non-essential tracking should not be activated before the user has made a valid choice. Consent must be freely given, specific, informed and unambiguous, and it must be possible to withdraw it as easily as it was given. Rejecting non-essential cookies should not prevent access to ordinary content unless a lawful exception applies.
3. Categories of technologies used or potentially used on this website
Strictly necessary and technical
These technologies support essential functions such as WordPress authentication, security, session management, testing whether the browser accepts cookies, protecting forms and remembering necessary technical settings. They are not used for advertising profiling.
Preferences and comment convenience
If you choose the WordPress option to save your name, email address and website for future comments, WordPress can store those details in comment cookies. This is an optional convenience function and should be set only after the commenter actively opts in.
Analytics and audience measurement
Jetpack Stats is installed but is disabled in this database configuration so that audience-measurement tracking does not run before a visitor has made a consent choice. If analytics is enabled in the future, it should be connected to the Analytics category of the consent mechanism before it is allowed to track visitors. Jetpack Stats can process information such as IP address, WordPress.com user information when applicable, user agent, visited URL, referring URL, timestamp, browser language and country code. According to Jetpack, directly identifying Stats log data such as IP addresses may be retained by Automattic for approximately 28 days when the feature is active.
Because analytics technologies can fall within ePrivacy consent rules depending on how they operate and are configured, My Greece Experience should activate any non-exempt analytics technology only in accordance with the visitor’s consent where consent is legally required.
Security and anti-spam technologies
Jetpack Protect and Akismet are present in the website configuration. These services can process technical and interaction information to prevent malicious login attempts, spam and abuse. Akismet may process commenter IP address, user agent, referrer, site URL, comment content and information entered in the comment form. These functions can operate partly through server-side processing rather than browser cookies.
Affiliate and third-party destination technologies
My Greece Experience contains affiliate links, including Booking.com links. A normal outbound affiliate link may contain an affiliate identifier in the URL. Third-party cookies or tracking technologies are generally controlled by the destination website after you follow the link, rather than by My Greece Experience merely because the link is displayed. Once you visit the third party, its own cookie and privacy policies apply.
4. WordPress cookies
The following WordPress cookies may be set depending on how you interact with the site. Not every visitor receives every cookie, and names containing a hash or user ID vary by installation and account.
| Cookie or pattern | Purpose | Typical duration | Who receives it |
|---|---|---|---|
wordpress_test_cookie | Tests whether the browser accepts cookies, normally on the WordPress login page | Session | Visitors to the login flow |
wordpress_[hash] / wordpress_sec_[hash] | WordPress authentication and secure administration | Normally 2 days; up to 14 days when “Remember Me” is selected | Logged-in users |
wordpress_logged_in_[hash] | Recognises that a WordPress user is logged in | Normally 2 days; up to 14 days with “Remember Me” | Logged-in users |
wp-settings-{user_id} and wp-settings-time-{user_id} | Stores WordPress administration/interface preferences | Approximately 1 year | Logged-in users |
wp_lang | Stores the language selected on the WordPress login interface | Session | Users of the login interface |
comment_author_{HASH}, comment_author_email_{HASH}, comment_author_url_{HASH} | Remembers comment-form details only when the visitor chooses the save-details option | Approximately 1 year | Commenters who opt in |
WordPress cookie names and durations can change with software updates or site configuration. The table therefore describes standard WordPress behaviour rather than guaranteeing that every cookie will be present in every session.
CMP consent cookie
| Cookie | Purpose | Duration | Category |
|---|---|---|---|
mge_consent_v1 | Stores the CMP version, timestamp and the visitor’s choices for analytics, external media and marketing so the website can remember and apply them. | 180 days | Strictly necessary / consent preference |
This consent cookie is first-party and is not used for advertising profiling. Its purpose is to remember the privacy choice and avoid asking for the same decision on every page view. When the consent version changes materially or the cookie expires, the banner may be shown again.
5. Jetpack and Automattic technologies
Jetpack can use cookies, pixels, scripts and other technologies depending on the features enabled. On this website, Jetpack remains installed for functions that include Protect, contact forms and subscriptions, while Jetpack Stats is disabled by this CMP configuration. The exact cookies or identifiers can vary as Jetpack is updated or as features are enabled or disabled.
For current information about Jetpack and Automattic technologies, see the Jetpack Privacy Center and Automattic Cookie Policy.
6. Akismet
Akismet is used to help identify spam comments. It can process commenter and request data even when no advertising cookie is involved. Akismet states that most spam-related data is stored for relatively short periods, generally between two weeks and ninety days. See the Akismet Privacy Policy for current information.
7. Affiliate links and Booking.com
Some links include affiliate parameters used to identify My Greece Experience as the referring publisher. If you click a Booking.com or other affiliate link, the destination service may set its own cookies, pixels or other identifiers to measure referrals, remember preferences, prevent fraud, provide the booking service or perform advertising and analytics under its own rules. Those third-party technologies are controlled by the destination service once you leave our website.
8. Third-party embedded content
If the website introduces embedded maps, videos, booking widgets, social-media content or other third-party embeds, those services may receive technical information or place cookies when the embed loads. Where such an embed uses non-essential tracking that requires consent, it should be blocked until the appropriate consent has been obtained. The relevant provider’s privacy and cookie information will apply to its processing.
9. How to give, refuse or withdraw consent
My Greece Experience uses a custom consent-management interface (CMP). On a first visit, optional categories are off by default. The banner offers equally accessible controls to Accept all, Reject non-essential technologies, or Customize individual categories. Closing the banner with the X has the same effect as rejecting non-essential technologies. Essential technologies cannot be disabled through the CMP because they are required to provide the requested website function.
The available optional categories are Analytics, External media, and Marketing and affiliate widgets. Normal outbound affiliate links remain usable when marketing consent is refused; a third-party destination may apply its own cookies after you choose to leave this website.
You can reopen the preference panel at any time through the Cookie settings control displayed in the website footer.
Withdrawing consent affects future use of the relevant technologies and does not make earlier consent-based processing unlawful. When optional consent is refused or withdrawn, the CMP attempts to remove known first-party optional cookies that are accessible to the website. Third-party or HTTP-only cookies may also need to be removed through the relevant provider or browser settings. A technical record of the current consent choice is stored in the mge_consent_v1 cookie.
10. Browser and device controls
Most browsers allow you to view, block or delete cookies through their privacy or site-data settings. Blocking all cookies can affect login, comments and other website functions. Browser deletion does not necessarily communicate withdrawal of consent to every external service, so where a website consent interface is available it should also be used to update consent choices.
11. Do Not Track and similar signals
Some browsers transmit privacy signals such as Do Not Track or Global Privacy Control (GPC). The CMP treats an active GPC signal as a reason to keep the Marketing category disabled. Jetpack Stats is disabled in this database configuration. Browser signals do not replace the consent choices required under applicable law for other optional technologies.
12. Cookie retention
Cookie duration varies according to purpose. Session cookies normally end when the relevant browser session is closed. Persistent cookies remain for their configured duration or until deleted. Where a third party sets a cookie, that third party determines its retention period. WordPress examples are listed above; Jetpack and other provider-specific retention can change as those services are updated.
13. International processing
Providers connected to Jetpack, Akismet, Gravatar or external affiliate services may process information in countries outside the European Economic Area. Where the GDPR applies to a transfer under our responsibility, a lawful transfer mechanism must be used as described in our Privacy Policy.
14. How optional content is technically gated
Optional scripts and embeds that are integrated with the CMP are loaded only when their corresponding category is allowed. The current database configuration also disables Jetpack Stats at module level to avoid analytics tracking before consent. If new analytics, advertising, map, video or booking widgets are added later, they should be connected to the CMP before publication so that the policy and actual website behaviour remain aligned.
15. Updates to the cookie list
Plugins, browser behaviour and third-party services change over time. We may therefore update this Cookie Policy and, where a consent-management interface is used, the categories or vendor information displayed there. The “Last updated” date at the top of this page indicates the current version.
16. Contact and privacy rights
Questions about cookies, consent or personal-data processing can be sent to mygreeceexperience@gmail.com. Information about access, erasure, objection and other data-protection rights is available in our Privacy Policy.
17. Regulatory information
For additional information about consent and tracking technologies, you may consult the European Data Protection Board Guidelines 05/2020 on consent and the Italian Data Protection Authority guidelines on cookies and other tracking tools.
”’ def hexsql(s: str) -> str: return ‘CONVERT(0x’ + s.encode(‘utf-8’).hex() + ‘ USING utf8mb4)’ privacy_meta = ‘Privacy Policy for My Greece Experience: GDPR rights, legal bases, retention, Jetpack Stats, Akismet, WordPress cookies, affiliate links and international transfers.’ cookie_meta = ‘Cookie Policy for My Greece Experience: WordPress cookies, Jetpack Stats, Akismet, affiliate links, consent choices, retention and EU ePrivacy information.’ patch = f”’\n– ——————————————————–\n– ENHANCED PRIVACY + COOKIE POLICY PATCH (2026-10-07)\n– Based on the services evidenced in the supplied database.\n– Updates existing pages only; no duplicate pages are created.\n– ——————————————————–\n\nSET NAMES utf8mb4;\nSTART TRANSACTION;\n\nUPDATE `wpuv_posts`\nSET `post_content`={hexsql(privacy)},\n `post_excerpt`={hexsql(privacy_meta)},\n `post_status`=’publish’,\n `comment_status`=’closed’,\n `post_modified`=’2026-10-07 18:18:00′,\n `post_modified_gmt`=’2026-10-07 16:18:00’\nWHERE `ID`=3 AND `post_type`=’page’;\n\nUPDATE `wpuv_posts`\nSET `post_content`={hexsql(cookie)},\n `post_excerpt`={hexsql(cookie_meta)},\n `post_status`=’publish’,\n `comment_status`=’closed’,\n `post_modified`=’2026-10-07 18:18:00′,\n `post_modified_gmt`=’2026-10-07 16:18:00’\nWHERE `ID`=5479 AND `post_type`=’page’;\n\nUPDATE `wpuv_postmeta` SET `meta_value`={hexsql(privacy_meta)} WHERE `post_id`=3 AND `meta_key`=’_yoast_wpseo_metadesc’;\nUPDATE `wpuv_postmeta` SET `meta_value`={hexsql(cookie_meta)} WHERE `post_id`=5479 AND `meta_key`=’_yoast_wpseo_metadesc’;\n\nCOMMIT;\n”’ patch_sql.write_text(patch, encoding=’utf-8′) shutil.copyfile(src, out_sql) with out_sql.open(‘a’, encoding=’utf-8′) as f: f.write(patch) # ZIP both for file in [out_sql, patch_sql]: z = file.with_suffix(file.suffix + ‘.zip’) with zipfile.ZipFile(z, ‘w’, compression=zipfile.ZIP_DEFLATED, compresslevel=9) as zz: zz.write(file, arcname=file.name) print(‘privacy chars’, len(privacy), ‘cookie chars’, len(cookie)) print(‘patch bytes’, patch_sql.stat().st_size) print(‘full bytes’, out_sql.stat().st_size) print(‘outputs’) for x in [out_sql.with_suffix(out_sql.suffix+’.zip’), patch_sql.with_suffix(patch_sql.suffix+’.zip’)]: print(x, x.stat().st_size)