Clym

Overview

Clym is a consent management platform and privacy compliance tool that site operators deploy to satisfy GDPR, CCPA, and related regulatory requirements. Its scripts display cookie banners, collect and record visitor consent decisions, and expose mechanisms for data subject access requests. As a consent management platform, Clym's own scripts are categorized as essential infrastructure rather than tracking.

What This Script Does

The Clym script loads a consent UI widget from Clym's CDN and performs several consent-lifecycle functions on the host page. On first visit, it renders a banner or preference center allowing the visitor to accept, reject, or customize cookie categories. The visitor's choice is stored in a first-party cookie (typically named clym_consent or similar) scoped to the host domain, with a duration of 12 months in most default configurations.

On subsequent visits, the script reads the stored consent record and conditionally fires or blocks other third-party scripts based on the categories the visitor accepted. Clym may also set a unique visitor identifier to associate the consent record with the specific browser session for audit logging purposes.

Data transmitted to Clym servers includes: the consent decision (accept/reject per category), timestamp, visitor identifier hash, and the page URL where consent was captured. This data forms the consent audit log required to demonstrate compliance under GDPR Article 7(1).

The Clym widget also renders a "Do Not Sell My Personal Information" link for CCPA compliance and supports data subject request intake forms.

Consent & Compliance

Clym is itself a consent management platform, so its own operation is covered by the "strictly necessary" exemption under ePrivacy. A consent management script cannot logically require prior consent to load, because it is the mechanism by which consent is collected. This position is consistent with guidance from the ICO, CNIL, and other DPAs.

Under GDPR Article 7, controllers must maintain records of consent. The Clym audit log data transmitted to its servers satisfies this obligation. The legal basis for Clym's own data processing is compliance with a legal obligation (Article 6(1)(c)).

Under CCPA/CPRA, Clym's operation supports the site operator's compliance obligations and does not constitute a "sale" or "sharing" of personal information.

The consent category is essential.

Should You Block This Without Consent?

No. Blocking Clym would disable the consent management mechanism itself, making it impossible to collect or honor visitor consent for other scripts. Essential consent infrastructure must load unconditionally. Clym's own data transmissions are strictly limited to consent audit logging and do not constitute tracking.