Cookie Notice

Cookies are small text files stored on your device to remember preferences, keep sessions secure, and understand how documentation pages are used. Similar technologies include local storage entries and pixel tags; this notice uses “cookies” as shorthand for all storage governed by the banner. First-party cookies are set by Pipeline Harbor domains; third-party cookies may appear when embedded content loads from approved vendors. You can delete cookies through browser settings at any time, though some features may require reauthentication. Essential cookies are needed for login, load balancing, and abuse prevention; they are not used for optional marketing. This explanation stays plain-language on purpose; deeper technical specs are available on request for security reviewers.

Questions about cookies or similar storage should go to hello@browse-feedview.digital with “Cookies” in the subject line. If you believe a cookie was set outside the disclosed list, include screenshots and approximate timestamps so engineers can trace the session. Enterprise customers may request custom data processing schedules referencing cookie inventories. We do not operate a call center for cookie issues; written channels keep an auditable trail. Accessibility assistance for the banner is available through the same inbox. Response targets mirror privacy requests unless urgent security incidents require prioritization.

Strictly necessary cookies keep sessions authenticated and protect forms from forgery. Functional cookies remember UI choices such as collapsed navigation states. Analytics cookies measure aggregate traffic when you opt in through the banner. We do not deploy advertising cookies on core learning surfaces. Representative rows: ph_session (necessary, session auth), ph_csrf (necessary, form forgery), ph_pref (functional, 180 days), ph_anon_id (optional analytics, 90 days), vendor_embed_vid (optional playback diagnostics, 30 days when enabled). Vendors may update cookie names for security rotation; we refresh this page quarterly.

Non-essential cookies load only after you interact with the banner in a way that records consent in local storage. Rejecting optional cookies does not remove access to coursework or documentation. You may reopen preferences through the footer link labeled Cookie Settings to change your decision. Consent records include a timestamp and version identifier of this notice for auditability. If local storage is cleared, the banner reappears so you can reaffirm choices. We do not use pre-ticked boxes for optional categories.

The preference center lists toggles per category with short explanations and links to vendor policies. Saving preferences triggers a refresh of analytics tags so prior optional scripts unload. Some browsers send Global Privacy Control signals; we treat compatible signals as a request to deny optional cookies where technically feasible. If you authenticate across subdomains, preference cookies may sync using first-party endpoints only. You can export a plain-text summary of your stored preference state on request. Misconfigured browsers that block all cookies may still use essential server-side session identifiers limited to login flows.

Embedded video players may set vendor cookies when you opt into analytics; otherwise they load privacy-enhanced modes where available. Support chat widgets, when enabled, use session cookies scoped to short troubleshooting windows. We review subprocessors that set cookies and require data minimization clauses. If a vendor introduces new cookies, deployment is blocked until documentation updates ship. You may request a machine-readable inventory for enterprise security questionnaires. Blocking third-party cookies entirely may limit embedded walkthrough videos until you allowlist the domain temporarily.