Cookie Policy

Introduction

This Cookie Policy explains how TZION MEDIA SLU ("we" or "us") uses cookies and similar tracking technologies on Mileapps (the "Website"). It also explains your choices regarding these technologies. We are providing this policy to be transparent about our data practices and to comply with relevant laws and guidelines in Andorra (which closely align with European standards on cookies and privacy).

By using our Website, you consent to the use of cookies and other tracking technologies as described in this policy, unless you disable them using the methods explained below. If you do not agree with our use of these technologies, you should adjust your browser settings or decline non-essential cookies using our consent management tool (which we display when you first visit the site).

Please note that any personal data collected via cookies is processed in accordance with our Privacy Policy. This Cookie Policy is part of and incorporated into our Privacy Policy.

What are Cookies and Why We Use Them

Cookies are small text files that are placed on your computer or mobile device when you visit a website. They allow the website (or a third party that sets the cookie) to recognize your device and store some information about your preferences or past actions. Cookies serve many purposes: enabling core site functionality, improving user experience, keeping track of your preferences, and helping us understand which parts of the website are used most.

We use cookies for several reasons:

• To ensure our Website functions properly: Some cookies are essential for the operation of our site. For example, we use cookies to remember that you have consented (or not consented) to cookies, so we don’t repeatedly ask you; these also help us comply with regulations by storing your preferences.

• To enhance user experience: Cookies allow us to remember choices you make (like language or region selection) and provide enhanced features. If our site has user-specific settings (like a dark mode toggle or text size preference), cookies may be used to store those choices so that when you return, your preferences are intact.

• For analytics and performance: We use cookies to collect information about how visitors use our Website. This helps us improve how the Website works (for example, seeing which pages are popular, how users navigate between pages, etc.). These cookies, set by third-party analytics providers, help us understand and improve our site’s performance.

• For advertising and marketing: Advertising cookies may be set to personalize the ads you see on our site or to measure the effectiveness of ad campaigns. These cookies can track your browsing habits and sometimes your approximate location to present more relevant ads. We primarily use these for working with our ad partners like Google AdSense and others, as detailed below, and only with your consent.

We categorize the cookies we use into a few categories (detailed in the next section):

1. Essential Cookies (also called Strictly Necessary Cookies)

2. Analytics Cookies

3. Advertising Cookies

We will describe each category and list representative cookies belonging to them, including their purpose, provider, and duration.

Types of Cookies We Use

1. Essential Cookies (Strictly Necessary)

These cookies are necessary for the Website to function and cannot be switched off (without significantly affecting your use of the site). They are typically set only in response to actions you take, such as setting your privacy preferences, logging in, or filling in forms. Essential cookies do not store any personally identifiable information, except perhaps an identifier necessary for the service (which is usually not tied to your real identity).

• Consent Preference Cookie – e.g., FCCDCF (provided by Google’s Funding Choices CMP).
  Purpose: Stores your cookie consent preferences (which categories of cookies you accepted or declined). This cookie ensures that your choices are remembered so we don’t ask for consent on every page load, and it helps us comply with regulations by keeping a record.
  Provider: Mileapps (First-party via our CMP integration, though provided by Google CMP framework).
  Expiration: 13 months (consistent with IAB TCF guidelines and Andorran/EU rules for consent storage).

• Consent String Cookie – e.g., euconsent-v2.
  Purpose: This cookie contains an encoded string that communicates your consent selections under the IAB Transparency & Consent Framework (TCF). It is used by our advertising and analytics partners to determine what has been consented to. Essentially, it tells third-party vendors which cookies and processing you’ve agreed to.
  Provider: Mileapps (First-party, shared with TCF vendors via the CMP).
  Expiration: 13 months.

• Cloudflare Security Cookie – e.g., __cf_bm.
  Purpose: Set by Cloudflare, our security/performance provider, this cookie helps manage incoming traffic that matches criteria associated with bots. It is a necessary cookie for our protection, ensuring that malicious bots are filtered out and legitimate users can access the site. It does not collect personal info beyond assigning a temporary identification to assess requests.
  Provider: Cloudflare (Third-party cookie, but considered essential for site security).
  Expiration: 30 minutes (the cookie is automatically removed after a short period of inactivity).

• Session Identifier Cookie – e.g., PHPSESSID or similar (if our site runs on PHP or a specific platform that uses such a cookie).
  Purpose: Preserves user session state across page requests. For example, if we had login functionality or multi-step forms, this cookie would maintain continuity. (Currently, our site is informational, so we may not have a persistent session cookie, but we mention it in case.)
  Provider: Mileapps (First-party).
  Expiration: Session (expires when you close your browser).

(Note: The above are examples. We list any essential cookies we actually use. If our site platform sets any cookie for load balancing, route, CMS, or similar, we include it here. e.g., if using WordPress: wordpress_logged_in_*, wp-settings-* might appear, though those are for logged-in users/admins mostly.)

These essential cookies don’t require consent under APDA guidelines and ePrivacy rules because they have minimal privacy impact and are needed for service. However, we still list them here for transparency. You can set your browser to block these cookies, but then some parts of the site might not work (like our ability to remember your cookie settings, ironically, or to distinguish you from a bot for security).

2. Analytics Cookies

Analytics cookies help us understand how visitors engage with our Website. We use the insights to improve content and user experience. We only set these cookies if you opt-in (consent) to analytics via our cookie banner. Data collected via these cookies is aggregated and anonymized by our analytics providers – we do not see your personal details, rather we see overall trends.

Our primary analytics tools are Google Analytics and Microsoft Clarity. Here are some key analytics cookies they use:

• Google Analytics (_ga) – e.g., _ga.
  Purpose: Registers a unique ID that is used to generate statistical data on how the visitor uses the website. This cookie distinguishes users (assigns a random number as user identifier). It helps count how many people visit, whether they are new or returning, and how they navigate the site.
  Provider: Google (via our domain – it's a first-party cookie in the context of our site, but Google has access).
  Expiration: 2 years from set/update. (We have configured Google Analytics to anonymize IP addresses, and we respect the "Do Not Track" signal for GA where possible.)

• Google Analytics (_gid) – e.g., gid.
  Purpose: Registers a unique ID used to generate statistical data on how the visitor uses the website, similar to ga but for a shorter term – typically used to distinguish users within a 24-hour period. It counts user visits and tracks behavior during that day.
  Provider: Google.
  Expiration: 24 hours.

• Google Analytics (_gat) – e.g., gat (or gat_UA-XXXX).
  Purpose: Used to throttle the request rate to Google Analytics. If our site has a lot of hits, this cookie ensures Google Analytics doesn't get overwhelmed by limiting the number of requests. It does not store user data.
  Provider: Google.
  Expiration: 1 minute.

(Google Analytics may set other cookies like AMP_TOKEN (for AMP linkages, 30 seconds to 1 year), or legacy cookies like utma, utmb etc., if we used older GA libraries, but currently we use GA4 which primarily uses ga, gid, and _gat. Also note: Google Analytics cookies might use our domain as first-party cookies.)

• Microsoft Clarity (_clck) – e.g., _clck.
  Purpose: Persists the Clarity user ID and preferences for that site. Clarity uses this to connect multiple page views by a user into a single session record and to recognize returning users on subsequent visits. Essentially, it helps Clarity stitch together session recordings over time for the same user (via an anonymized ID).
  Provider: Microsoft (through our domain).
  Expiration: 1 year.

• Microsoft Clarity (_clsk) – e.g., _clsk.
  Purpose: Connects multiple page views by a user into a single Clarity session recording. It basically groups a user’s actions within a short period (session) so that Clarity can replay the whole visit at once. After the session ends, Clarity sends the data and resets the cookie.
  Provider: Microsoft (through our domain).
  Expiration: 1 day (or until end of session).

• CLID (Clarity) – e.g., CLID.
  Purpose: Indicates the first time Clarity saw this user on any site using Clarity. It’s a third-party cookie (set on . clarity.ms domain) and contains a Clarity User ID across sites. It helps Microsoft understand if a user is new or returning to the Clarity network. On our site, it's not essential for our analytics, but Clarity might set it for their own usage.
  Provider: Microsoft (Third-party).
  Expiration: 1 year (persistent).

(Clarity also involves other MS cookies like ANONCHK, MR, MUID, SM which relate to Microsoft’s broader analytics/advertising integration. For analytics, Clarity mainly uses the above first-party cookies, but for completeness we mention: MUID is a Microsoft user identifier across their services, used in Clarity and Bing Ads for analytics/ads – 1 year expiry; ANONCHK indicates if MUID was transferred to ANID (ads cookie) – it’s short-lived; MR indicates whether to refresh MUID – ~7 days; SM for synchronizing MUID – session. These might appear due to Clarity script calling Microsoft domains.)

Important: We have configured our analytics services in compliance with Andorran and EU regulations. Google Analytics IP anonymization is enabled. We do not use analytics to track or collect personal data such as names or emails. Data collected is used in aggregate form. Additionally, these cookies will not be set unless you opt in.

3. Advertising Cookies

Advertising cookies are used to make advertising messages more relevant to you and to measure the effectiveness of ad campaigns. They perform functions like preventing the same ad from continuously reappearing (frequency capping), ensuring ads are properly displayed for advertisers, selecting advertisements based on your interests, and measuring the number of ads displayed and their performance (clicks, conversions, etc.).

We primarily work with the following advertising partners and their cookies:

• Google AdSense / DoubleClick Cookies:

• IDE (DoubleClick cookie) – e.g., IDE.
  Purpose: Used by Google’s DoubleClick to remember your preferences and provide personalized ads on non-Google sites (like ours). It stores a unique ID that identifies a returning user's browser and device. This ID helps Google and its partners show you relevant ads across the web (for example, if you've visited travel sites, you might see travel-related ads on our site). It also helps with ad serving functions like measuring ad performance (conversions, etc.) and fraud detection.
  Provider: Google (DoubleClick.net domain, which is a third-party on our site).
  Expiration: 13 months (in EEA, UK, and Switzerland) / 24 months elsewhere. Google uses 13 months to comply with EU privacy guidelines for ad cookies.

• test_cookie (DoubleClick) – e.g., test_cookie.
  Purpose: This cookie is used by DoubleClick (Google) to test whether the user's browser supports cookies. It's a simple check – not used for ad targeting itself, but simply to see if it can set an IDE cookie or not. It contains no identifying info beyond a boolean (true/false).
  Provider: Google (DoubleClick.net).
  Expiration: 15 minutes (it's set and quickly expires).

• gclau (Google AdSense/Ads) – e.g., gclau.
  Purpose: This is a Google Ads conversion linker cookie. It helps us understand how you navigate to our site via advertising. Specifically, when you click on one of our Google ads on another site, this cookie stores a unique identifier that links the click to a conversion action on our site (like clicking an app download link). It's used to attribute conversions back to ads for campaign measurement. It may also be used by AdSense to experiment with ad efficiency across websites.
  Provider: Google (First-party, as it's set on our domain by Google Tag Manager or Ads scripts).
  Expiration: 90 days (approximately 3 months).

• ANID and NID (Google) – e.g., ANID, NID.
  Purpose: These cookies are used by Google to store user preferences and information when viewing pages with Google ads. NID is commonly used on Google sites to remember preferences like language or SafeSearch, but can appear with ads on our site if you have a Google account. ANID is an advertising cookie used if personalized ads are disabled; it stores that preference (ANID = "Opt-Out"). They may appear due to Google’s ad personalization choices.
  Provider: Google.
  Expiration: NID – ~6 months; ANID – 13 months in EU (or 24 months outside) or “Opt-Out” fixed long-term value.

• Microsoft Advertising (Bing Ads) Cookies:

• uetvid – e.g., uetvid.
  Purpose: This cookie is set by Microsoft’s Universal Event Tracking (UET) for Bing Ads. It stores a unique, anonymized visitor ID, allowing us to track what happens after ad clicks (conversions) on our site and to retarget visitors with ads on the Microsoft/Bing network. If you consent to advertising, this helps ensure, for example, if you came via a Bing ad, we record a conversion when appropriate.
  Provider: Microsoft (first-party cookie on our site via UET script).
  Expiration: 13 months (or 390 days as some docs say, roughly the same).

• uetsid – e.g., uetsid.
  Purpose: Also set by UET, this is a session identifier used to track a single browsing session on our site. It groups activities that happen in one session (multiple pages) for conversion tracking and analytics on the Microsoft Ads platform.
  Provider: Microsoft.
  Expiration: Session (expires after the browsing session ends, or within 30 minutes of inactivity).

• MUID – e.g., MUID.
  Purpose: "Microsoft User ID" cookie. Widely used by Microsoft as a unique user identifier across their sites and services (including Bing, Clarity, etc.). In advertising context, it helps with user recognition across browsing sessions and Microsoft domains, enabling features like ad personalization and frequency capping on the Microsoft Ad network. If you consented, Microsoft can use MUID on our site to link your behavior to a profile for better ad targeting on their network.
  Provider: Microsoft (third-party cookie on domains like . clarity.ms or .bing.com).
  Expiration: 1 year (often noted as 390 days, or "1 year and 24 days" as some sources state).

• ANONCHK – e.g., ANONCHK.
  Purpose: Indicates whether MUID is transferred to ANID (Microsoft Advertising Identifier). Clarity sets it to always 0 (meaning MUID wasn't forwarded to an older ANID system). In advertising terms, it helps track that an ID sync happened. It's used for security and ad fraud detection as well.
  Provider: Microsoft ( clarity.ms domain).
  Expiration: 10 minutes (short-lived flag).

• MR – e.g., MR.
  Purpose: This cookie is used by Microsoft to indicate if a user’s MUID needs to be refreshed. It is part of both Clarity and Bing Ads/LinkedIn tracking. For ads, it might also help with anonymized user session data for cross-domain analysis.
  Provider: Microsoft.
  Expiration: 7 days.

• Yahoo Japan Ads Cookie:

• yjsuyjad – e.g., yjsuyjad.
  Purpose: This cookie is associated with Yahoo! JAPAN Ads and is used for conversion tracking and improving the performance of ad delivery. If we run ads on Yahoo Japan's network and you interact with our site via those ads, this cookie helps link your actions back to the ad. It collects data like page visits and possibly conversions related to Yahoo Ads. Essentially, it allows Yahoo Japan to determine ad effectiveness (e.g., did you do the intended action after coming from a Yahoo ad?). It's also used to avoid showing you redundant ads and perhaps for retargeting on Yahoo's network.
  Provider: Yahoo Japan (first-party on our domain via their tag script, likely, or as a third-party cookie if their domain writes it).
  Expiration: ~1 year (364 days).

• (Note: Yahoo Japan may also use additional cookies or local storage. But yjsuyjad is a primary one documented. We mention that to cover the integration.)

• Other Third-Party Advertising Cookies:
  We might have integrations with other advertising platforms or affiliate programs that set cookies. For example, if we ever include YouTube videos, YouTube might set cookies; if we had affiliate links, those networks might use cookies for tracking commissions. As of now, our focus is AdSense and similar, but we include this category for completeness. We will disclose any such cookie if present.

Consent and Control: Advertising cookies will be set only if you opt-in through our cookie consent banner. If you opt-out, you may still see ads on our site (if we have ad placements), but they will be non-personalized (contextual or generic ads) and many of the above cookies either will not be set at all, or will contain values indicating no tracking (like ANID=OptOut).

You can manage your ad preferences as well:

• Google Ads: You can visit Google Ad Settings to customize or opt-out of personalized Google ads (which will apply not just to our site but all sites using Google Ads, when you're signed in or via cookies in your browser).

• Microsoft Ads: See the Microsoft privacy dashboard or opt-out page to adjust personalized ad settings for Microsoft.

• Yahoo Japan: See Yahoo Japan’s advertising privacy page (which should have opt-out info likely in Japanese; we can provide a link).

• Industry opt-outs: You can opt-out of many ad cookies via industry sites like YourOnlineChoices (EU) or Network Advertising Initiative (global), etc. Keep in mind opt-outs often rely on setting an opt-out cookie.

Third-Party vs First-Party:

• First-party cookies are set by our domain (Mileapps). Cookies like ga, gid, FCCDCF, uetvid appear as first-party in your browser for Mileapps.

• Third-party cookies are set by external domains. For example, IDE appears as coming from doubleclick.net, MUID from clarity.ms or bing.com, yjsu_yjad might come from yahoo.co.jp or our domain depending on implementation. Your browser might block some third-party cookies by default if you have strict settings; our site should still function if those are blocked (you'll just get less relevant ads perhaps).

Below is a summary table of key cookies for quick reference (for readability; in actual text we might format as a table or list depending on the medium):

(Only essential cookies do not require consent. Analytics & Advertising cookies require affirmative consent to operate.)

Managing and Disabling Cookies

Consent Management (CMP): On your first visit to our site, we present a cookie consent banner (via "Managed by Google" CMP compliant with IAB TCF, CMP ID: 300). This banner allows you to accept all cookies, reject non-essential cookies, or customize your choices category by category. We honor your selection. If you want to change your preferences later, you can do so by clicking on the "Privacy Settings", "Cookie Preferences", or similar link on our Website (typically in the footer or the banner icon if still visible). This will bring up the consent management interface again so you can modify your choices.

If you choose to reject analytics and advertising cookies, we will not set those on your browser. You will still get essential cookies. If you accept them and later change your mind, you can withdraw consent via our CMP and we will cease those processing and future cookies for those categories (and you can delete existing cookies as needed).

Browser Settings: Most web browsers allow you to control cookies through their settings preferences. You can usually:

• View what cookies are set on your device and their values.

• Delete all or specific cookies.

• Block third-party cookies (or even all cookies).

• Set exceptions for specific sites.

• Receive notifications when cookies are being set.

For example:

• Google Chrome: Settings > Privacy and Security > Cookies and other site data. You can block third-party cookies, or block all cookies (not recommended as it breaks many sites), and clear cookies on exit or manually.

• Firefox: Options > Privacy & Security > Enhanced Tracking Protection or Custom settings for cookies. Firefox also has strict modes to block trackers.

• Safari (Desktop): Preferences > Privacy > Cookies and website data.

• Safari (iOS): Settings > Safari > Privacy & Security.

• Edge: Settings > Cookies and site permissions.

• Internet Explorer (legacy): Internet Options > Privacy > Advanced (though IE is outdated).

• Opera: Settings > Privacy & Security > Cookies.

Each browser’s documentation provides specific instructions. For convenience, here are some support articles:

• Chrome: Clear, enable, and manage cookies in Chrome

• Firefox: Cookies and site data in Firefox

• Safari: Manage cookies and website data in Safari

• Edge: Delete and manage cookies

• Opera: Security and Privacy

Effect of Disabling Cookies: If you disable cookies entirely, please note that some features of our Website may not function properly. For instance, if you block all cookies:

• Our site might not remember your cookie consent choice (so you may be asked again or it may assume no consent and default to minimal functionality).

• Security defenses might treat you as a new user each time or might not function optimally (e.g., Cloudflare might challenge you with CAPTCHAs more frequently if it can’t use its cookie).

• Any preference like language or dark mode won’t be saved.

• Analytics will naturally not run (which is fine).

• Advertisements may be less relevant (you may still see generic ads if we display them, but with strict blocking, third-party ad content might not load at all, which could leave blank spaces).

We set essential cookies irrespective of consent because they are needed, but you can manually delete or block them via browser if you choose (just be aware of the consequences, such as the consent banner reappearing or being unable to log in if that was relevant, etc.).

Do Not Track & Global Privacy Control: Currently, our site’s behavior regarding DNT/GPC signals: If your browser sends a "Do Not Track" signal, we treat it as an indication of preference but since cookie consent is explicitly handled via our banner in compliance with APDA/EU rules, we rely on that mechanism. However, we minimize tracking by default and only enable advanced tracking on consent anyway. If Global Privacy Control (GPC) signals are detected (a newer mechanism in some browsers to indicate opt-out of sale/sharing under certain privacy laws), since our context is GDPR/Andorra, we interpret it as equivalent to "do not use non-essential cookies" and would accordingly not drop advertising cookies if GPC is enabled (to the extent our CMP supports it). We will update our practices as these technologies become more recognized legally.

Third-Party Opt-Outs: Beyond our site:

• Google offers an opt-out for Google Analytics via a browser add-on: Google Analytics Opt-out Browser Add-on. Installing it will prevent GA from running on any site (including ours).

• Google Ads and AdSense: as mentioned, adjust in Google Ad Settings when signed in.

• For interest-based ads from many networks, you can visit YourOnlineChoices EU or NAI Opt-Out (though NAI is more US-focused, the concept is similar).

• Microsoft Ads opt-out link: optout.aboutads.info/?c=2&lang=EN (should cover Bing Ads).

• Yahoo Japan: they have a site (in Japanese) to opt out of interest-based ads: Yahoo! JAPAN Interest-based Advertising Opt-out.

Remember, opting out through those means often relies on cookies too (an opt-out cookie). If you clear cookies, you may remove the opt-out and need to do it again.

Changes to this Cookie Policy

We may update this Cookie Policy from time to time, for example to reflect changes in the cookies we use or for other operational, legal, or regulatory reasons. The "Last updated" date at the bottom of this Policy indicates when it was last revised.

If the changes are significant, we will provide a more prominent notice (such as adding a notice on the Website or sending an email notification if applicable) to inform you of the updates. We encourage you to review this Cookie Policy periodically to stay informed about our use of cookies and related technologies.

By continuing to use our Website after we post any modifications to this Cookie Policy, you acknowledge the updates.

Contact Us

If you have any questions or concerns about our use of cookies or this Cookie Policy, feel free to contact us:

• Email: TZION MEDIA SLU can be reached at [email protected] for privacy inquiries. Please put "Cookie Policy Inquiry" in the subject line if possible.

• Mail: TZION MEDIA SLU, Carretera dels Cortals, Edifici Cirerer-Griu, Atic 3, AD200, AD.

• Phone: +376 62 60 15.

For general information about how we handle personal data (beyond cookies), please see our Privacy Policy.

Thank you for visiting Mileapps and for reviewing our Cookie Policy!

Last updated: 11/18/2025