Cookies

What is not here

There are no social-network cookies. Ads, if present, sit in a fixed slot at the end of the page: they do not break course cards or cover the go-to-course button.

Counting the “Go to the course” button

It happens on the server: it notes the course and the date, not a cookie of yours.

Google Analytics

If the site has a measurement ID configured, public pages load Google Analytics 4. It may store first-party cookies such as `_ga` and `_ga_<id>` to distinguish visits. We do not enable advertising signals or ad personalization.

Google AdSense

If the site has a publisher ID configured, the public HTML includes the `adsbygoogle.js` script and the `google-adsense-account` meta. It is used to verify the AdSense account. Google may set first-party cookies from its network when that script loads.

Today there are no AdSense ad units in the catalog.

Adcash

If ads are enabled, the banner loads the Adcash library (`aclib.js`) and a 300×250 Display unit below the content. That network may set first-party or third-party cookies to measure impressions and choose the ad. We do not mount pop-under or interstitial ads.

Technical cookies

There may be technical cookies from the site itself (for example, the internal panel session, which is not part of the public catalog).

If you delete them in the browser, the public catalog still works.

More context in privacy.