All Set MOCs Events Games Minifigs Parts Themes Posts Members

Start typing to search.
Policy

Cookie policy

How Brickzip uses cookies, local storage, service-worker caches, and similar technologies for login, preferences, security, analytics, ads, affiliate attribution, and product operation.

Effective date

May 27, 2026

This Cookie Policy covers browser and app storage used by Brickzip and by providers that help operate the service. It should be read together with the Privacy Policy.

Storage categories

Strictly necessary

Required

Session, authentication, CSRF, security, rate-limit, routing, service-worker, and load-balancing storage required for the service to work.

Preferences

Product

Theme, currency, locale, sidebar state, and selected brand preferences that make repeated browsing consistent.

Analytics

Optional

Measurement that helps understand performance, errors, app usage, and product quality when analytics are enabled.

Advertising and affiliate

Optional

Ad delivery, frequency controls, affiliate click attribution, conversion reporting, and fraud prevention when monetization providers are enabled.

How long storage lasts

  • Session and security storage usually lasts until sign-out, expiry, or browser cleanup.
  • Preference storage can last until you change the setting, clear local storage, or reset the app.
  • Service-worker caches may store app shell files so Brickzip can load faster or show an offline page.
  • Analytics, advertising, and affiliate storage follows the retention settings of the relevant provider and applicable consent choices.

Managing choices

  • You can clear or block cookies and local storage through your browser settings.
  • Installed app users can clear site data from the browser or operating-system app settings used by the installed web app.
  • If consent controls are shown in your region, you can use them to accept, reject, or adjust optional categories.
  • Blocking required storage can break login, saved preferences, posting, chat, notifications, or security protections.
  • Some browsers send Do Not Track or similar signals. Brickzip does not currently respond to those signals separately from the consent and browser controls described here.

Examples used by the app

  • Theme preference for light, dark, or automatic mode.
  • Currency and locale preferences for catalog and pricing surfaces.
  • Brand preference storage for default catalog filtering.
  • Authentication and security cookies for signed-in workflows.
  • Affiliate click and advertising storage when a deal or ad provider requires it.