Cookie Policy

Exactly which cookies Grizzly Signal sets, what they do, and how to opt out. Short version: one first-party cookie, no advertising cookies, no third-party tracking.

Cookies we set

The Grizzly Signal pixel sets a single first-party cookie on the domain of the website where it's installed. We do not set any other cookies, and we do not deploy third-party advertising cookies through our service.

Cookies we do not set

• No advertising cookies from Grizzly Signal directly. We never set Meta's _fbp / _fbc cookies — those are set by Meta's own browser pixel if a client has it installed
• No analytics or marketing pixels — we don't load Google Analytics, Hotjar, Segment, or any other third-party tracker through our pixel
• No cross-site tracking cookies. grizzly_id is set on each client's domain and cannot be read by any other site

Server-side identifiers

Our server reads cookies that are already present in the browser to forward to Meta — specifically _fbc and _fbp if Meta's pixel set them, and the fbclid URL parameter. We do not set these cookies; we read them only to enable Meta's identity matching.

GDPR, CCPA, and consent

Grizzly Signal acts as a data processor on behalf of our clients (the data controllers). Our clients are responsible for obtaining any consent required from their visitors before deploying our pixel — including:

• EU/UK visitors: cookie banner and explicit opt-in for non-essential cookies under GDPR / ePrivacy
• California visitors: a "Do Not Sell or Share My Personal Information" link under CCPA / CPRA where required
• Other jurisdictions: whatever local consent rules apply

Most cookie consent management platforms (CookieYes, Osano, OneTrust, Cookiebot, Termly, etc.) can block or conditionally load our pixel based on a visitor's choices. Your consent banner should treat grizzly_id as a statistics / analytics cookie, not a strictly necessary one.

How to opt out

• Clear cookies in your browser settings — every browser provides a way to delete cookies for a specific site or all sites. After clearing, the next visit will receive a brand-new grizzly_id
• Use private / incognito browsing — most browsers don't persist cookies across private sessions, so a fresh grizzly_id is created each time and discarded when the window closes
• Block first-party cookies — most browsers can be configured to block cookies entirely or by site. Note this may break logins and other site features
• Browser privacy extensions (uBlock Origin, Privacy Badger, etc.) can block our pixel from loading
• Contact the site owner whose website you visited — they are the data controller and can honor a deletion request

Changes to this policy

We may update this policy as our infrastructure evolves. The current version is always available at grizzlysignal.com/cookies.

Contact

Questions: hello@grizzlysignal.com