# Cookies and similar technologies

Version 1.0 · Updated 2026-11-09 (UTC)

This notice accompanies the [Privacy Notice](/legal/privacy/) and applies from publication. A cookie is a small item stored by a browser; local storage and similar technologies can serve related purposes. Network requests can transmit information even when no cookie is set.

## 1. Public website

The public website is delivered by Vercel. Opening a page sends the requested URL and technical connection/browser information to the hosting infrastructure. Our published site code does not implement an advertising cookie or cross-site advertising profile. Hosting security and delivery processing is distinct from a promise that no provider uses any storage or collects technical information.

Ordinary page controls, such as menus and example selectors, use the current page's state. Their source does not create a persistent visitor profile. Service UX analytics, if offered, uses a separate consent choice and is described in the Privacy Notice; visiting a page is not that consent.

## 2. Homepage film

The film thumbnail loads from `i.ytimg.com` when the homepage opens, before playback. That request sends connection/browser information to Google/YouTube. The embedded player is created only after you activate playback. It uses `youtube-nocookie.com`, with YouTube's player API loaded from `youtube.com`; playback can make further media, security and measurement requests and use browser storage.

Google describes this as privacy-enhanced embedding. It is not a promise of no information transfer, no storage or no third-party processing. Google explains the mode in its [embedding guide](https://support.google.com/youtube/answer/171780) and its handling in the [Google Privacy Policy](https://policies.google.com/privacy).

To avoid loading the player, do not activate the film. This does not prevent the thumbnail request already made on the homepage. Browser/site-content controls can block third-party resources and cookies; blocking them may prevent playback. Closing or leaving the page ends the embedded player; browser settings let you clear stored information. Reloading without playback does not activate the player again.

Provider-controlled storage lifetimes depend on the browser, playback state and provider. We do not assign one fixed expiry to every YouTube item or claim that deleting a browser cookie deletes a provider's server records.

## 3. Authentication and other sites

SciGround authentication uses Auth0 / Okta. When you enter the issued sign-in flow, that provider and any identity provider you select may use storage needed for login, session security or your selected sign-in method. The applicable flow and provider terms determine those items and their lifetimes. This is separate from reading this public website. Blocking necessary sign-in storage can prevent access.

Following an ordinary external link, including Prighter or GitHub, opens a separate service with its own policy. A link is different from an automatically loaded image or an activated embedded video.

## 4. Browser choices and questions

You can block or clear cookies and site data in your browser, control third-party resources and decline optional service analytics. Our site code does not implement a special response to legacy Do Not Track. That statement does not override any legally required signal, consent or opt-out duty; contact us to exercise an applicable right.

Questions about actual technologies, relevant provider information or your rights: [contact@licklider.ai](mailto:contact@licklider.ai). See the [Privacy Notice](/legal/privacy/) for recipients, countries, retention and request handling.