Cookie Policy

Cookies are small text files or similar identifiers stored on a browser, device, or related client storage layer. Fred also uses related technologies such as local storage, scripts, pixels, server-side identifiers, and consent preferences where appropriate.

This policy covers the main public marketing site in this repository and related public surfaces operated under the Fred web perimeter. Some public content under /resources is delivered from a separate runtime surface and may not use the exact same implementation, but remains part of the overall public legal perimeter.

Fred uses CookieScript as the consent management platform for the public website. CookieScript stores consent state and exposes events that Fred uses to align analytics activation with the user's consent choices.

Most third-party website scripts are managed through Google Tag Manager. PostHog is initialized directly in the website code rather than through GTM, but should still follow the same consent boundary for non-essential use.

Where a visitor rejects non-essential categories, only strictly necessary cookies and security-related technologies should remain active. Where a visitor grants the relevant categories, analytics, advertising measurement, and related optional technologies may activate according to configuration.

The current production inventory is based on a CookieScript cookie report reviewed on June 19, 2026 together with repo and runtime evidence. Exact cookies may still vary by page, region, consent state, and public surface.

Cloudflare supports public-site edge protection and Web Analytics and may set security or traffic-related cookies. CookieScript stores and manages consent preferences. Google services support tag management, analytics, advertising measurement, and related infrastructure where configured. HubSpot cookies indicate active marketing, analytics, meeting, banner, form, or related website tooling on at least part of the public perimeter. Meta targeting cookies indicate advertising or conversion-measurement tooling where enabled.

PostHog is used for website or product analytics in app code. Additional PostHog capabilities such as session recording or heatmaps must remain consent-gated and should only be enabled where Fred has configured them for the relevant surface and considers that use appropriate.

Visitors can manage cookie preferences through the CookieScript controls exposed on the site where available. Browser settings may also be used to delete or block cookies, although blocking strictly necessary cookies can affect site functionality, security, or session continuity.

Because some public pages can be served through different public surfaces, a cookie choice made on one part of the Fred public perimeter may need to be refreshed or re-checked on another surface depending on implementation and browser behavior.

Fred may update this Cookie Policy when providers, tracking configurations, consent tooling, public-site architecture, or legal requirements change. The latest version will be posted here with the revised date and version reference.

Questions about cookies, consent, or public-site tracking can be sent to the contact address below.