Legal · IFHA
Cookie Policy
Which cookies we use on ifha.com.ar, what each one is for, how long it lasts, and how you can turn them off at any time.
This site uses cookies. Some are essential for it to work —for example, so that a payment reaches its destination— and others help us understand which content is useful and measure our campaigns. Here we tell you exactly which ones they are, who sets them, how long they last and how to turn them off.
Who is responsible
- Company name
- Eido S.A.S.
- CUIT (Argentine tax ID)
- 30-71934933-8
- Address
- Av. Libertador 405, San Fernando (B1646), Buenos Aires Province, Argentina
- Brand
- IFHA – Artisan Ice Cream Training Institute (Instituto de Formación del Helado Artesanal)
- Site covered
- ifha.com.ar
- Contact
- info@ifha.com.ar
IFHA is a brand of Eido S.A.S. (eido.com.ar). This policy complements the Privacy Policy and the Terms and Conditions, and should be read together with them.
What cookies are
A cookie is a small text file that a website stores in your browser when you visit it. On later visits the site can read it and remember information: the language you chose, whether you’re already logged in, or what was in your cart.
Under the same name we group other similar technologies that do the same job: tracking pixels, tags, localStorage, sessionStorage and device identifiers.
Cookies are classified by who sets them —first-party, if this site sets them; third-party, if another domain does— and by how long they last: session cookies are deleted when you close the browser, and persistent cookies remain until they expire or until you delete them.
Categories we use
- Technical or necessary. They make the site work: keeping your session, remembering the cart, processing a payment, serving the right version of the page from the cache and protecting forms from automated submissions. Without them the site can’t work properly.
- Preferences. They remember your choices, such as language or display settings.
- Analytics. They tell us how many people visit us, which pages they read, how long they stay and where they get stuck, so we can improve our content and navigation.
- Advertising. They measure the results of our campaigns, avoid showing you the same ad too many times and make it possible to show more relevant ads on third-party platforms.
Cookies on this site, in detail
The following inventory reflects the configuration in force on the date of this policy. Durations are those declared by each provider and may change if the provider changes them; they may also differ depending on whether you browse as a visitor or logged in.
Technical and necessary
| Cookie | Owner | Purpose | Duration |
|---|---|---|---|
_lscache_vary | IFHA (first-party) | Serve the right version of the page from the cache | 2 days |
wordpress_logged_in_*wordpress_sec_* | IFHA (first-party) | Keep registered users logged in. Not set for visitors | Session or 14 days |
wp-settings-* | IFHA (first-party) | Remember display preferences in the admin dashboard | 1 year |
woocommerce_cart_hashwoocommerce_items_in_cart | IFHA (first-party) | Remember the order in progress during enrollment | Session |
wp_woocommerce_session_* | IFHA (first-party) | Link your browser to your payment order | 2 days |
sbjs_* (seven cookies) | IFHA (first-party, WooCommerce) | Attribute the order to its source: they store the origin of the visit, the UTM parameters, the referring site, the browser and the number of visits | Session |
ifha_ok_*ifha_mcifha_fi | IFHA (first-party) | Confirm that you are the person who started this order or form when you come back from the payment page | 2 hours to 7 days |
__cf_bm | Cloudflare | Anti-bot protection for the enrollment forms | 30 minutes |
Swipe the table sideways to see all columns.
Forms are protected with Cloudflare Turnstile, which loads only when a submission needs to be verified.
Analytics
| Cookie | Owner | Purpose | Duration |
|---|---|---|---|
_ga | Google Analytics | Distinguish unique visitors | Up to 2 years (400 days in Chrome) |
_ga_DG81EZW6B1 | Google Analytics | Keep the session state in our Analytics property. Analytics data also feeds Google Ads audiences (advertising use) | Up to 2 years (400 days in Chrome) |
_clck | Microsoft Clarity | Keep a Clarity user identifier | 1 year |
_clsk | Microsoft Clarity | Group the visits of one session into a single recording | 1 day |
CLID | Microsoft Clarity | Identify the first time the site is visited | 1 year |
MUID, ANONCHK, SM | Microsoft | Browser identification and syncing across services | From 10 minutes to 13 months |
MR | Microsoft (Clarity and Bing) | Sync the Clarity identifier with Bing | 7 days |
SRM_B | Microsoft (Bing) | Syncing identifiers across Microsoft services | 390 days |
Swipe the table sideways to see all columns.
Session replay
Microsoft Clarity records browsing sessions: it records mouse movements, clicks and scrolling to build heatmaps and anonymous replays that help us find usability problems. The tool masks the content of form fields by default, so we don’t capture what you type in them, and we don’t record payment screens. You can prevent it by blocking analytics cookies, as explained in section 07.
Advertising
| Cookie | Owner | Purpose | Duration |
|---|---|---|---|
_fbp | Meta | Identify the browser to measure conversions and show ads | 90 days |
fr | Meta (.facebook.com) | Deliver ads, measure them and improve their relevance | 90 days |
_gcl_au | Google Ads | Attribute site conversions to a campaign | 90 days |
NID, IDE, test_cookie | Google / DoubleClick | Ad measurement, frequency capping and personalization | From 15 minutes to 13 months |
Swipe the table sideways to see all columns.
Where your visit comes from
On every visit, the site’s code stores where you came from (and, if you come in through a campaign link with utm_* or fbclid parameters, that campaign) so it can attribute your inquiry or enrollment to its source:
| Cookie | Owner | Purpose | Duration |
|---|---|---|---|
ifha_origen | IFHA (first-party) | Remember the first and the last source of your visit (campaign, referring site and landing page) and attach it to your inquiry or enrollment | 180 days |
_fbc | IFHA (first-party, for Meta) | Record the Meta ad you came from and send it with your conversions | 90 days |
Swipe the table sideways to see all columns.
Local browser storage
Besides cookies, the site and its providers store this data in your browser’s localStorage or sessionStorage:
| Key | Owner | Purpose | Duration |
|---|---|---|---|
ifha_xid | IFHA (first-party) | Measurement identifier sent to Meta (as external_id) with inquiries, forms and the start of an enrollment | Persistent |
ifha_ref | IFHA (first-party) | Remember the referring site during the visit | Session |
ifha_inscripcion_draft_v1_en | IFHA (first-party) | Keep the enrollment form you started on this device (name, email, WhatsApp, country and ID document), so you don’t lose it if you leave; deleted when you finish | Persistent |
ifha_sb_x | IFHA (first-party) | Remember that you closed the sticky bar | Session |
_gcl_ls | Google Ads | Attribute conversions to a campaign | Persistent |
lastExternalReferrer, lastExternalReferrerTime | Meta | Record the last external site you came from | Persistent |
_cltk | Microsoft Clarity | Session recording control | Session |
litespeed_docref, litespeed_reloaded | IFHA (first-party, LiteSpeed) | Serve the page from the cache | Session |
ifha-webinar-en-unlockedifha-webinar-en-etapa | IFHA (first-party) | Remember that you already signed up for the webinar and the stage you chose, so the video stays unlocked | Persistent |
ifha_funnel_* | IFHA (first-party) | Avoid counting the same enrollment step twice in our measurement | Session |
Swipe the table sideways to see all columns.
Third-party services that set cookies
Third-party cookies are managed by their own owners, who act as controllers of the processing they carry out through them. IFHA doesn’t control their content or duration. You can read their policies here:
- Google (Analytics and Ads) — policies.google.com/technologies/cookies
- Meta (Facebook and Instagram pixel) — facebook.com/policies/cookies
- Microsoft (Clarity and Bing) — privacy.microsoft.com
- YouTube (Google), the video player embedded in the webinar page, in privacy-enhanced mode (youtube-nocookie.com) — policies.google.com/technologies/cookies
- Cloudflare (Turnstile and web analytics) — cloudflare.com/privacypolicy
- Ahrefs (cookieless web analytics) — ahrefs.com/legal/privacy-policy
- DMCA.com (content protection badge) — dmca.com/privacy-policy
- Meta, CAPI Gateway (sending measurement events from a Google Cloud server) — facebook.com/privacy/policy
Legal basis and consent
Technical and necessary cookies are set because without them the site can’t provide the service you request: they are essential to browse, enroll and pay.
Analytics and advertising cookies are set when the page loads, unless you have blocked them in your browser. You can prevent or reverse this at any time with the options in the next section, without affecting your access to the content or the programs.
Visitors from the EEA and the UK
If you visit us from the European Economic Area or the United Kingdom, the site applies Google Consent Mode with restrictive default settings: analytics storage, ad storage, user data for advertising purposes and ad personalization are sent as denied unless consent is given. The Meta pixel and Microsoft Clarity don’t follow Google Consent Mode: you can block them in your browser, as explained in section 07.
How to turn off or delete cookies
From your browser
Every browser lets you accept, block or delete cookies, and also browse in private mode. Here are the official instructions:
Directly in each service
- Google Analytics: by installing the browser opt-out add-on — tools.google.com/dlpage/gaoptout
- Google ads: from your ad settings — myadcenter.google.com
- Meta ads: from your account’s ad preferences — facebook.com/adpreferences
- Behavioral advertising in general: youronlinechoices.com and optout.aboutads.info
What happens if you turn them off
If you block all cookies, including technical ones, you probably won’t be able to complete an enrollment or a payment, and some parts of the site may not work as expected. Blocking only analytics and advertising cookies doesn’t affect normal use of the site.
What data cookies generate and for how long
The information collected by analytics and advertising cookies is mainly technical and aggregated: pages viewed, time on site, traffic source, device and browser type, and an identifier that recognizes the browser across visits. When you fill in a form, Meta and Google may receive your email, phone and name in hashed form to match conversions with their accounts. The exception is our own ifha_origen cookie: when you send an inquiry or enroll, the source of your visit (campaign, referring site and landing page) is saved with that inquiry or enrollment.
Retention periods are those shown in the tables in section 04. Purposes, recipients, international transfers and your rights are detailed in the Privacy Policy.
Updates to this policy
The tools we use change over time, and so do the cookies. We review this policy regularly and publish the version in force on this same page, with its update date.
We recommend checking it from time to time. If you find a cookie from this site in your browser that isn’t in the inventory, write to info@ifha.com.ar and we’ll fix it.
Contact
For questions about the use of cookies or the processing of your data, write to info@ifha.com.ar or call +54 9 11 2892 4489.
Last updated: October 14, 2026 · Version: 3.1 (English)
Based on the Spanish original, version 3.1 of September 25, 2026, updated on October 14, 2026 for the English site (hosting location, legal bases and cookie inventory). For the factual information about providers, locations and cookies, this version is the current one; as to your rights, the version more favorable to you prevails.
3.1 — Sep 25, 2026: inventory updated (Meta fr, WooCommerce sbjs_*, Microsoft MR and SRM_B, local storage, campaign cookies, Ahrefs, DMCA.com and CAPI Gateway); reCAPTCHA replaced by Turnstile. Oct 14, 2026 (English version): the ifha_origen cookie, the webinar and enrollment storage keys, the YouTube player, and the hashed form data that Meta and Google may receive.
Controller: Eido S.A.S. — CUIT 30-71934933-8 — Av. Libertador 405, San Fernando (B1646), Buenos Aires Province, Argentina
IFHA is a brand of Eido S.A.S. (eido.com.ar).
+54 9 11 2892 4489