Skip to content
BugFence

Compliance & Legal Center

Cookie Policy

Effective date: November 11, 2026

Architecture & Privacy Boundary

BugFence does not use behavioral advertising cookies or third-party tracking pixels. We use only strictly necessary local storage keys for UI preferences and secure session authentication.

Client-Side Redaction Air-Gapped Offline Licensing Zero Advertising Cookies

1. Zero Advertising Trackers Pledge

BugFence is committed to transparent, privacy-respecting engineering. We do not use third-party advertising cookies, behavioral tracking pixels (e.g., Meta Pixel, TikTok Pixel, Google Remarketing), or cross-site data broker scripts anywhere on bug-fence.com or within our software.

We believe developers and engineering teams deserve an experience that respects their digital sovereignty.

2. First-Party Local Storage Keys

The BugFence SDK and marketing website use local browser storage (localStorage) exclusively to preserve your personal interface preferences locally on your machine. This data is never sent to third parties:

  • bf_theme: Stores your preferred color appearance mode ("light" or "dark").
  • bf_launcher_pos: Remembers where you placed the floating BugFence reporter widget on your screen.
  • bf_reporter_email: Conveniently saves the reporter's typed email address in the reporting dialog so you do not need to retype it on subsequent submissions.

3. Essential Authentication Cookies

When signing into the BugFence engineering dashboard, the server sets a single, strictly necessary session cookie to authenticate your requests:

  • __Host-bf_session (Production): Encrypted session identifier with HttpOnly, Secure, SameSite=Strict, and Path=/ flags. The __Host- prefix guarantees the cookie is only accepted over HTTPS for the exact origin, protecting against cookie hijacking and CSRF attacks.
  • bf_session (Local Development): Used exclusively on plain HTTP loopback addresses during local development.
  • Lifetime: Matches your configured session duration (default: 7 days via BUGFENCE_SESSION_TTL_HOURS). Cleared immediately upon sign-out.

4. Managing and Disabling Storage

You can clear cookies and local storage at any time through your browser's security settings.

The BugFence SDK is engineered defensively: if storage access is blocked (for example, in Safari Private Browsing mode or strict container environments), the widget operates smoothly in memory without throwing runtime errors.

Need a Signed DPA or Enterprise Procurement Terms?

We execute mutual DPAs with Standard Contractual Clauses (SCCs), custom Master Services Agreements (MSAs), and Indian 18% GST tax invoices.