Cookie policy

Last updated: 27 October 2026

This English version is a translation provided for convenience. In case of any discrepancy, the Spanish version prevails.

Document under legal review. The final content of this document is awaiting legal review for Competiciones Rítmica.

1. What cookies are

Cookies are small text files that websites store on your device. This policy also covers equivalent technologies, such as the browser’s local and session storage, IndexedDB and the venue mode caches. They let us remember your session, keep your preferences and, only with your permission, measure how Competiciones Rítmica is used. The controller is FlamaTech Consulting LTD.

2. Types we use

By default we only use strictly necessary storage and preferences that you trigger. Analytics is only activated with your explicit consent.

Your permission is stored separately on each site because the browser isolates each origin’s data. The competicionesritmica.com domain serves both the product website and the clubs’ app (club panel, venue mode and the public page of each competition), so your choice applies to that whole domain. On Clybo’ (clybo.app) it is stored separately. This website does not use Google Analytics.

Category	Purpose	Status
Necessary	Sign-in session, security of the access code (Cloudflare Turnstile), card payment (Stripe) and offline operation of venue mode. The platform does not work without these.	Required
Preferences	Chosen language, active club in the panel and podium visibility. They remember a choice you made and are not used for measurement.	Required
Analytics	PostHog, on the product website and in the app. We measure navigation, features used and performance to improve the product. We do not record how the screen is used: the app has no session recording, because participating clubs handle minors’ data.	With permission

3. Third-party cookies

We use the following providers, which may set cookies or their own storage:

PostHog (product and performance analytics) — only with permission: measures LCP, INP, CLS and FCP and usage activity. After you sign in it may link activity to your account; it does not receive form content or interface text. There is no session recording.
Stripe (payment gateway) — necessary. Loaded only when you open the card payment form of an entry; used to complete the payment and detect fraud. The charge goes to the club’s Stripe account.
Cloudflare Turnstile (anti-abuse check) — necessary. Loaded on the screen where you request the access code, to check that you are not a bot, without asking you to solve puzzles.
Supabase (authentication) — necessary. Keeps your session once you sign in with the code; stored in this domain’s local storage.

4. How to manage your preferences

You can review, give or withdraw consent at any time through , which is also in the footer of every page of the product website. Withdrawal applies immediately to PostHog and stops future measurement. Your choice is stored per origin, so you need to change it on each site you use.

If your browser sends a Global Privacy Control (GPC) signal, the website treats it as a refusal of optional analytics. We also configure PostHog to respect the browser’s Do Not Track signal. We do not sell or share personal data for behavioural advertising. You can clear the site’s storage at any time from your browser settings; you will be signed out and your preferences forgotten.

5. Cookie details

Key	Purpose	Duration
`clyb:analytics-consent`	Stores your analytics choice.	Until you change your preference or clear local storage.
`__ph_opt_in_out_*`	Syncs that choice with the PostHog SDK; it contains no activity.	Until you change your preference or clear local storage.
`ph_*`	Keeps PostHog’s anonymous identifier (or your account after sign-in) and the measurement session.	Up to 12 months; only created after you accept.
`clyb_locale`	Remembers the language you chose.	Until you change it or clear local storage.
`clyb_locale_suggestion_dismissed`	Remembers that you dismissed the suggestion to change language.	Until you close the tab (session storage).
`sb-*-auth-token`	Supabase sign-in session in the app: keeps you identified after entering the code.	Until you sign out or it expires; renewed while you use the app.
`cr:activeClubId`	Remembers the active club when you manage or enter from several clubs. It is only a convenience: the server checks your permissions on every request.	Until you switch club, sign out or clear local storage.
`cr-podium-visible:*`	Remembers in your browser which parts of a competition’s podium you showed or hid.	Until you clear local storage.
`clyb-venue-unlock*`	Remembers in that tab that you unlocked venue mode with the PIN; it does not store the PIN.	Until you close the tab (session storage).
IndexedDB `clyb-venue`	Working data of venue mode so it keeps working offline and syncs when the network returns.	Until synced and cleaned up, or you clear site data.
Caches `venue-*`	Venue mode Service Worker (`/pabellon/`): stores the app to open it offline and the offline simulation marker. It does not store API responses.	The current and previous versions are kept; the rest is deleted on update.
Stripe cookies	Completing card payment and detecting fraud. They only appear when you open the payment form.	Set by Stripe; see its cookie policy.
Cloudflare Turnstile cookies	Checking that the access code request is made by a person.	Set by Cloudflare; session or short-lived.

PostHog does not store analytics identifiers or capture events before you consent. Refusing or withdrawing permission stops capture; only the choice needed to respect it is kept. Pages of the Clybo’ platform are governed by their own cookie policy. More information on how we process your data in the privacy policy.