Cookie Policy
Last updated: 12 October 2026
This English version is provided for information only. In the event of any discrepancy, the Spanish version shall prevail. Ver la versión en español.
1. What are cookies?
Cookies are small files or pieces of data that a website can store on your device and read when you visit it again. They are used, for example, to keep you signed in, remember certain preferences or measure how a website is used.
There are also similar storage technologies, such as the browser’s local storage. In this policy we refer to all of them together as “cookies” when they serve an equivalent purpose.
2. Who is responsible for this website?
FEIDERS is owned by Carlos Falconi, with tax ID (NIF/NIE) Y6982199B and address at Calle Corona 19, 28054 Madrid, Spain. You can write to contacto@feiders.com with any question about this policy.
3. What do we use cookies for?
Technical or necessary cookies. They make the features you request work, such as keeping you signed in, protecting access to an account or keeping the status of a purchase process. These cookies are used only when they are needed to provide the corresponding feature and do not require prior consent.
We do not currently use optional cookies. The website does not set analytics, advertising or personalisation cookies, so there is no cookie choice to accept or reject. Nor is there a preferences panel to access.
Third-party cookies linked to specific features. Some external services, such as a payment gateway, may use cookies when you access their features. In the next section we identify the ones involved on the FEIDERS website and explain when they are used.
A cookie’s classification depends on its actual purpose, not only on the name of the provider that sets it.
4. Cookies and technologies used
The following list shows the cookies and equivalent technologies used on FEIDERS, their purpose and when they are involved.
| Name or pattern | Provider | Purpose and when it is used | Duration | Consent required? |
|---|---|---|---|---|
| hglo_guest_session | FEIDERS (first-party cookie) | Guest access to a booking made without an account: viewing, managing or cancelling it and downloading its receipts. It is only created when you open the secure link received by email. | 60 minutes | No (strictly necessary) |
| sb-<reference>-auth-token (if it does not fit, it may be split into fragments “-auth-token.0”, “-auth-token.1”…) | Supabase | Private area session: keeping you signed in and protecting access to the account. It is created when you sign in or register and deleted when you sign out. | Up to 400 days; deleted when you sign out | No (strictly necessary) |
| hglo-cart-v2 — local storage (not a cookie) | FEIDERS (first-party) | Store cart: keeping the selected products while you browse the website. | Until the cart is emptied or the browser data is cleared | No (strictly necessary) |
| hglo_chat_session_id, hglo_chat_verified — session storage (not cookies) | FEIDERS (first-party) | Website chat: identifying the current conversation and remembering that the security check has already been passed while the tab is open. | While the tab remains open | No (strictly necessary) |
| chat_<scope> — session storage (not a cookie) | FEIDERS (first-party) | Assistant history on the pages that show it (store and private area) so the thread is not lost while browsing. | While the tab remains open | No (strictly necessary) |
| hglo_notes_<lesson> — local storage (not a cookie) | FEIDERS (first-party) | Personal notes the user writes in a lesson of the training area. | Until the user deletes them or clears the browser data | No (strictly necessary) |
| hglo_cookies_notice — local storage (not a cookie) | FEIDERS (first-party) | Remembering that you have already seen and closed the cookie notice, so it is not shown again on every page. It is only created when you click “Got it” and contains no personal data. | Up to 6 months after you close the notice, or until you clear the browser data | No (strictly necessary) |
| Verification script from challenges.cloudflare.com (Cloudflare Turnstile) | Cloudflare | Checking that whoever submits a form, books an appointment or opens the chat is a person and not an automated submission. The script is only loaded when the protected feature is opened; the verification is provided by Cloudflare with its own technologies. | Managed by Cloudflare | No (technical security measure) |
| Payment page hosted by Stripe (checkout.stripe.com) | Stripe | Payment for a booking or a purchase: on confirming, the browser goes to Stripe’s payment page, which uses its own cookies on its domain. No Stripe cookies are set on feiders.com before that step. | Managed by Stripe | Outside feiders.com: managed on Stripe’s domain when the payment starts |
| Video player player.vimeo.com | Vimeo | Playing the lesson videos in the training area. It is only loaded when a video is played, and Vimeo uses its own cookies on its domain. | Managed by Vimeo | Outside feiders.com: managed on Vimeo’s domain when the video is played |
5. The cookie notice and how to manage it
The first time you visit FEIDERS, a notice appears at the bottom of the screen with the title “Cookies at FEIDERS”, a link to this policy and a “Got it” button. It is an informative notice, not a request for consent: it describes the cookies and storage the website uses and does not enable any measurement. That is why it does not include options to accept or reject categories.
“Got it” only closes the notice and stores in your browser that you have already seen it, so it is not shown on every page. This is the hglo_cookies_notice record described in the previous section; it is kept for up to 6 months and does not enable any analytics or optional cookie. If you clear the browsing data for feiders.com, or once those 6 months have passed, the notice appears again.
In the footer of every page you also have “Cookie preferences”: it opens a panel with this website’s categories. Today it shows the necessary cookies (always on) and analytics as not available, because it is not installed; that is why there is no decision to save yet.
The current version of the website does not use any type of cookie that requires consent. If optional cookies (for example, analytics) are added in the future, this page will be updated at the same time they are enabled: it will explain their purpose, their cookies and periods, and how to accept them, reject them and change your decision at any time. When that happens, the notice will ask for an explicit choice —even if you had already closed it with “Got it”— and analytics will remain blocked until you allow or reject it.
Strictly necessary technical cookies keep working in any case. Some features you request, such as staying signed in, may stop working if you block necessary cookies in your browser.
6. Browser settings
You can also view, block or delete cookies from your browser settings. This option affects cookies from other sites as well as those from FEIDERS and may make some features unavailable.
7. Personal data and changes to this policy
Where the use of cookies involves processing personal data, you will find more information about your rights and how we process that data in our Privacy Policy.
We will update this policy when the cookies used, their purposes or the services integrated into the website change. The date at the top will show when it was last reviewed.