Cookie Policy

Overview

This Cookie Policy explains how OpsBlip uses cookies and similar browser storage technologies across the public website and the signed-in Org portal.

Essential authentication cookies

We use secure HTTP-only cookies for login state, refresh flows, and core session security. These cookies are necessary for the signed-in product experience and cannot be disabled without losing access to protected routes.

Browser storage used by the product

The web app also uses browser storage for product preferences and lightweight UX state, including:

• theme preference
• dismissed onboarding or announcement UI state where applicable
• read or seen reminder state for the in-app notification surface

CDN and bot management (Cloudflare)

The site is served through Cloudflare. Cloudflare may set the following cookies for bot management, challenge state, and abuse protection. These are not analytics cookies and contain no personal profile data:

• __cf_bm — short-lived bot-mitigation token.
• cf_clearance — set only after a security challenge is passed.

Analytics and diagnostics

We use Sentry for error and performance diagnostics. When a Google Analytics 4 measurement ID is configured, the site also sets the following analytics cookies to measure aggregate traffic and usage. GA4 is loaded with IP anonymization and with advertising signals disabled.

• _ga — client identifier used to distinguish visitors.
• _ga_<id> — per-property GA4 session state.

These tools are used for product operation and improvement, not for ad-network profiling.

What we do not use

OpsBlip does not use advertising cookies for third-party behavioral advertising in the current MVP and free-tier product.

Contact

Questions about cookies or browser storage can be sent to support@opsblip.io or through /app/support.