Cookies

Running the service

• cookie_consent, cookie, one hundred and eighty days. Remembers your choice about trackers. It is placed on the root domain, so that a choice made on the site also applies to the application, and the other way round.
• sb-...-auth-token, local storage, until you sign out. Your session token, which keeps you signed in. This is not a cookie, it is an entry in the local storage of your browser.
• locale, cookie and local storage, three hundred and sixty-five days for the cookie, permanent until changed for the local storage. Remembers the language in which you use the service. The cookie is only placed when you choose a language. It is placed on the root domain, so that a choice made on the site also applies to the application, and the other way round.
• Display preferences, local storage, permanent until changed. Remembers for example the expanded state of an administration menu or the muting of a display screen.
• ph_internal, cookie, three hundred and sixty-five days. Placed only if you open an address carrying the matching parameter. It serves to exclude a browser from the audience measurement, or to include ours back in it. It is an exclusion tracker, it measures nothing.

Security and payment

• Technical security cookie, session duration or a few hours. We observe none today, but our host and our content delivery network, Cloudflare, may place one to protect the service against abuse and automated traffic.
• __stripe_mid and __stripe_sid, cookies from our payment provider, one year and thirty minutes. They serve to prevent payment fraud. They are placed only at the moment you open a payment form, never on plain browsing.

PostHog

A tool hosted in the European Union, on a separate project for each brand. It records the pages viewed, the interactions and the errors encountered, it may record the course of a session in order to understand an incident, and it links those measurements to your account when you are signed in. Trackers placed, entries named ph_ followed by an identifier, thirteen months at most.

What we must tell you plainly. That measurement starts when the page opens, without waiting for your agreement. It is a choice we stand behind, the measurement serving only to run and to improve our own service, and being passed to no advertiser. You may object to it, and article 7 says how.

Google Analytics 4

Google's audience measurement tool. It is loaded in the throwdown.live application and in the mobile applications that wrap it, never on the www.throwdown.live site. It runs in a worker thread isolated from the page.

It is driven by Google's consent mechanism, known as Consent Mode, set to refusal by default for measurement as well as for advertising. In the web application, as long as you have not accepted, it places no cookie and sends only a measurement with no identifier. After acceptance, it places the cookies _ga and _ga_ followed by an identifier, thirteen months at most. In the mobile applications, which show no banner, the measurement is active by default and these cookies are placed in the storage of the application, as article 5 specifies.

Our own measurement of event pages

We count the visits to each event page and the time during which the tab stays open, in order to report to the organizer the audience of that page. That measurement uses no cookie, no local storage, no IP address and no account identifier. We record only the moment of the visit, its duration and the site that sent you. It cannot recognize you and therefore does not fall under the regulations on trackers.

Where your first visit came from

On your first visit, we keep a record of where you came from, that is to say the site that sent you, the campaign tags present in the address and the page on which you arrived. That information is held in a cookie named td_first, placed on the root domain for thirty days and never rewritten. It is attached to the registration you pay for or to the event you create, so that the organizer and we know which communication bore fruit. That cookie is placed without waiting for your agreement, it is read only by us and it is passed to no advertiser.

Google Ads

Measures the effectiveness of our campaigns and attributes registrations to the ads. It is loaded on the www.throwdown.live site and in the application. On both surfaces, the tag is preceded by a setting that refuses by default advertising storage, advertising data, personalization and measurement storage. Nothing is therefore placed on your device before your acceptance, and the setting is updated only at that moment. Cookies placed after acceptance, _gcl_au, _gcl_aw and _gac_ followed by an identifier, thirteen months at most.

A campaign identifier, known as gclid, taken from the address through which you arrive, is also kept in the local storage of your browser under the names td_gclid and td_gclid_ts, used for ninety days at most and passed on from the site to the application, in order to attribute a registration to the ad that preceded it. It is neither read nor written before your advertising agreement. When you create an account or an event after that agreement, that identifier is passed to our server, which reports to Google Ads the steps completed, the creation of the account, the creation of the event, its publication and its first paid registration, in order to measure what our ads bring in.

Meta pixel

Measures the effectiveness of our campaigns on the Meta services. It is loaded on the www.throwdown.live site and in the application, only after your agreement for advertising. It then passes to Meta the pages viewed and certain steps, the creation of an account, the creation of an event, a contact request or the booking of a demonstration and, when a spot is purchased, the amount, the currency and the reference of the transaction. After that same agreement, our server also reports to Meta the creation of the account, the creation of the event, its publication and its first paid registration, together with the cookies below, your email address and your account identifier, the last two being passed in a hashed form that does not allow them to be read back. Cookies placed, _fbp and _fbc, thirteen months at most. Meta is established in the United States, and that transfer is framed by the safeguards described in our privacy policy.

In the application, where the address through which you arrive carries a Meta click identifier, known as fbclid, we store it in the local storage of your browser under the name td_fbc. It is neither read nor written before your advertising agreement. It accompanies the reports described above where the _fbc cookie does not exist yet. It has no duration of its own and remains until the data of the site is cleared.

If you withdraw your advertising agreement, the entries td_gclid, td_gclid_ts and td_fbc are no longer read or passed on. They are not deleted automatically, you may delete them by clearing the local storage of the site from your browser.

ChatGPT Ads pixel

Measures how our ads shown inside ChatGPT perform. It is loaded on the www.throwdown.live site and in the application, only after your advertising agreement. It sends OpenAI the address of the landing page, the attribution identifier the ad carries in its address, called oppref, and the only step we report there, the creation of a competition. Where automatic advanced matching is active, it also sends the SHA-256 fingerprint of contact details present on the page, never their value. Cookies dropped after acceptance, __oppref, thirty days, and __obref, one year. OpenAI is established in the United States, that transfer is covered by the guarantees described in our privacy policy.

On the www.throwdown.live site

On your first visit, a window offers you three choices, continue without accepting, customize or accept. Customizing separates the audience measurement from advertising, so you may accept one and refuse the other. You may reopen that window at any time from the cookie management link, in the footer, and change your choice.

In the throwdown.live web application

The banner offers two choices of equal standing, refuse or accept. As long as you have not chosen, nothing is accepted, no advertising tracker is loaded and Google's consent mechanism stays on refusal. Your choice, agreement or refusal, is kept for one hundred and eighty days. That application does not yet have a preference management screen. To customize or to change your choice, use the cookie management link in the footer of the site, your choice being recorded on the root domain and applying to both surfaces.

In the mobile applications

No banner is shown. The Meta and ChatGPT Ads pixels are never loaded and Google's advertising storage stays refused, so no advertising tracker works on that surface. The audience measurement described in article 3, PostHog and Google Analytics 4, is active there by default, without your agreement being collected beforehand, and Google Analytics 4 places its _ga cookies there in the storage of the application. The mobile application has no setting to switch it off. You may object to it by writing to us, under the conditions of article 7, or use the web application, where Google Analytics 4 remains subject to your agreement.

From your browser or your device

You may at any time delete the cookies already placed and block new ones from the settings of your browser, and clear the local storage of the site. Some functions of the service, including your signed-in session, will then stop working.