DesignPass

Cookie Policy

This page lists the cookies and similar technologies DesignPass.dev uses, including first-party storage keys we set ourselves.

Last updated July 17, 2026

What we mean by cookies

Cookies are small text files stored on your device. We also use similar technologies such as local storage, session storage, pixels, and script-based identifiers used by analytics tools. For simplicity, this policy calls all of them "cookies" unless a distinction matters.

Why we use them

  • Keep the site working and secure (including basic abuse controls on the server)
  • Understand how people use pages, playgrounds, components, and signup flows
  • Support newsletter subscription and Beehiiv recommendation features when shown
  • Remember campaign attribution (UTM values) for the browser session when relevant
  • Remember lightweight UI preferences in the component library

Categories

  • Essential / functional. Short-lived client state for attribution and UI preferences. The site does not currently use login session cookies for a customer account.
  • Analytics. Google Analytics and (on production hosts) PostHog help us see traffic and product usage.
  • Newsletter / recommendations. Beehiiv may set cookies when you interact with subscribe flows or the recommendations widget.

We do not run third-party advertising networks on the site today.

Inventory (what we know we set or load)

  • Google Analytics via googletagmanager.com / gtag (measurement ID configured in our app). Typically sets cookies such as _ga and related identifiers. May involve Google domains including DoubleClick endpoints allowed by our content security policy.
  • PostHog on designpass.dev / www.designpass.dev when configured: first-party proxy under /ingest, and an identity cookie in the form ph_<project-key>_posthog (long-lived, on the order of one year). Skipped on localhost and typical preview hosts.
  • Beehiiv recommendations script from subscribe-forms.beehiiv.com (loaded site-wide; the recommendations modal only opens after an intentional post-subscribe trigger). Beehiiv may set its own cookies when the widget runs.
  • sessionStorage keys designpass-utm-attribution for UTM campaign values during the browser session, and dp-subscribe-popup-visit-start for when the delayed subscribe dialog becomes eligible; playground text may also use session storage.
  • localStorage keys for library UI preferences, including dp-sidebar-collapsed, dp-library-scope, dp-code-package-manager, and dp-code-language, plus dp-subscribe-popup-dismissed when you close or complete the delayed subscribe dialog.
  • Vercel may set operational cookies as part of hosting and platform features.
  • Font providers (for example Google Fonts) may receive technical request data when a font file is fetched; that is request metadata, not a cookie we set ourselves.

Vendor cookie names and lifetimes can change on their side. This list is our best current description of DesignPass behavior.

Your choices

You can block or delete cookies and site data through your browser settings. Blocking analytics may limit what we can measure, but the library docs should still work. Clearing site data removes our localStorage / sessionStorage preferences and attribution until they are set again.

To stop newsletter email, use the unsubscribe link in any issue. That is separate from clearing cookies. Recommendation enrollments you confirmed with Beehiiv are managed through those other publications' unsubscribe flows.

Updates

If we add vendors, change storage keys, or introduce a consent banner or paid checkout, we will update this page and the Privacy Policy.