Cookie Notice

Cookies are small text files stored on your device when you visit a site. They help remember preferences, keep sessions secure, and understand aggregate traffic patterns.

Similar technologies include local storage entries we use sparingly for theme selection when you opt in through the header control. These entries stay on device until cleared.

This notice explains what we set today; older browsers may mislabel some storage types, so we describe behavior in plain language rather than relying only on technical taxonomy.

Essential cookies support login sessions, load balancing, and abuse prevention. They do not track advertising profiles. Functional cookies remember choices such as cookie consent decisions themselves.

Analytics cookies, when allowed, collect pseudonymous usage metrics such as page views and scroll depth. We configure retention on vendor dashboards to the shortest practical period.

We do not deploy social advertising pixels on authenticated learning surfaces.

Use the cookie banner or footer link to reopen preferences. Declining analytics does not remove essential cookies required for basic operation.

Browser settings can block all cookies, though some lab portals may fail without session support. We publish compatibility guidance in the resources area.

Do-not-track signals are honored only where technically feasible alongside our consent model; inconsistent browser implementations may limit effectiveness.

Embedded videos or maps from vendors may set their own cookies when you interact with those embeds. Review vendor policies before enabling optional embeds.

We minimize embeds on pages where learners authenticate to reduce cross-site leakage.

If a vendor changes classification, we update this notice at least annually and sooner when we detect material changes.

Email hello@current-glow.one with the subject Cookie inquiry and include your browser version if troubleshooting.

We may ask for screenshots of consent dialogs when investigating mismatches between preferences and observed behavior.

Enterprise clients with separate compliance reviews can request a subprocessors spreadsheet covering cookie-related vendors.

Consent records include timestamp, coarse region derived from IP, and chosen categories. Withdrawal updates the same ledger.

Withdrawal does not erase server logs created before the change; those logs remain under retention rules in the Data Protection notice.

If you believe consent was captured incorrectly, we will work with you to reset identifiers tied to your account.