Compliance & Legal Center
Privacy Policy
Effective date: November 11, 2026
BugFence is engineered with privacy-by-construction: customer diagnostics and session evidence are scrubbed client-side prior to network transmission, and self-hosted instances retain zero data on central servers.
1. Overview and Architecture Principles
BugFence ("BugFence", "we", "us", or "our") is a privacy-first visual bug reporting, session replay, and automated diagnostics platform, and the operator of bug-fence.com.
Unlike traditional monitoring or session recording tools that ingest raw, unredacted web pages, BugFence enforces privacy-by-construction: sensitive data is scrubbed in the browser before network transmission, and our self-hosted architecture ensures customer bug reports, video recordings, and diagnostic logs remain exclusively on your own infrastructure.
This Privacy Policy explains how information is handled across our marketing website (bug-fence.com), our software distribution, our customer support desk, our hosted SaaS services, and our ephemeral demo sandbox. All operations and commercial contracts are conducted by BugFence.
2. Data Controllership & Architectural Roles
Because BugFence supports multiple deployment topologies, our legal role depends on how your organization utilizes the software:
- Self-Hosted Community & Enterprise VPC: Your organization operates the BugFence server (via Docker, Kubernetes, or Node.js) on your own private cloud or bare-metal infrastructure. In this model, your organization is the sole Data Controller and sole Data Processor. BugFence central servers receive zero customer bug reports, zero diagnostic media, and zero telemetry.
- BugFence Cloud / Hosted SaaS: If you utilize our multi-tenant cloud offering, your organization acts as the Data Controller, and BugFence acts as the Data Processor pursuant to our Data Processing Addendum (DPA).
- Marketing Site & Commercial Accounts: BugFence acts as a Data Controller for visitors to bug-fence.com, purchaser billing contacts, customer support inquiries, and registered administrative accounts.
3. Data Collected via the BugFence SDK & Ingestion Service
When an end-user or QA engineer submits a bug report through an application running the BugFence SDK, the report may compile the following categories of technical context (subject to the reporter's explicit consent toggles):
- Issue Description: Title, problem description, and optional voice transcript.
- Visual Evidence: Optional viewport screenshot (canvas-rasterized with DOM fencing), native screenshot review, screen video recording (with in-studio region redaction options, timeline privacy trimming, and pre-submission reporter review), and 30-second DOM event replay (rrweb-compatible format with automated DOM fencing).
- Technical Diagnostics: Failed network requests (status code, duration, method, URL, and sanitized payload), browser console errors, unhandled exceptions, and user breadcrumb trails (clicks, navigation, and input changes).
- Device Telemetry: Browser family and version, operating system, viewport dimensions, screen pixel ratio, connection quality, and release/commit identifiers.
- Reporter Identity: Configurable by the server administrator (BUGFENCE_REPORTER_EMAIL=keep|hash|drop). When set to "keep", user email is stored and masked for read-only roles (j***@domain). When set to "hash", email is converted into a keyed HMAC-SHA256 pseudonym. When set to "drop", no email is persisted.
4. Client-Side Fencing and PII Sanitization Guarantees
The BugFence SDK neutralizes sensitive information locally on the reporter's device using dual-layer fencing:
- In-Browser DOM Fencing (DOMFence): All input fields of type="password", credit card autofill inputs ([autocomplete^="cc-"]), elements marked with data-bugfence-mask (obscured with solid blocks), and elements marked with data-bugfence-block (completely excised from the DOM tree) are masked prior to canvas rendering and session replay capture.
- Regular Expression Sanitizer (PIISanitizer): Text fields, console logs, error messages, and network URLs pass through a deep sanitization engine before transmission. The engine redacts JSON Web Tokens (JWTs), Bearer tokens, HTTP Authorization headers, cookie values, phone numbers, SSNs, and 13–19 digit payment card numbers validated via the Luhn checksum algorithm.
- Server-Side Secondary Scrubbing: The ingestion server re-sanitizes every payload and session replay stream upon receipt, ensuring that tampered or modified clients cannot bypass client-side scrubbing.
- Script-Less Sandboxed Replay: Session replays are re-rendered inside an iframe with sandbox="allow-same-origin" and a Content-Security-Policy that strictly forbids script execution, forms, and network requests.
5. Transparent Limitations & Boundaries
We believe in absolute engineering honesty regarding where automatic protection ends:
- Pattern-Based Scrubbing: Detection relies on heuristic regex and checksum matching. Unstructured customer names, street addresses, free-form medical notes, or bespoke internal IDs may pass through. BugFence must not serve as your sole compliance fence for unencrypted regulated records.
- Screen Video Recordings: BugFence provides in-studio video redaction options, region fencing tools, and timeline privacy trimming (with real-time client-side re-encoding). Reporters can drag redaction boxes over sensitive video regions across specific time scopes, trim leading or trailing seconds, or discard the recording prior to submission. If re-encoding fails, the raw unredacted clip is never uploaded.
- Storage Encryption at Rest: Reports and diagnostic media are stored as structured JSON or PostgreSQL jsonb records. BugFence does not implement application-level encryption for report payloads. Operators must enable host volume or disk encryption (e.g., AWS EBS encryption, dm-crypt/LUKS).
- Certifications: BugFence is architected to align with SOC 2 Type II, HIPAA, and ISO 27001 requirements; we do not currently hold independent third-party audit certifications.
6. Ephemeral Demo Sandbox Environment
To enable evaluation without infrastructure setup, BugFence operates a public demo sandbox (tenant key: novacloud-demo-prod-2026).
All reports and media submitted to the demo sandbox are routed to an isolated in-memory store (EphemeralDemoMediaStore) with a hard 50MB quota ceiling. The sandbox enforces a strict 30-report FIFO buffer (the oldest report is immediately purged upon the 31st submission).
An automated 15-minute background Janitor service purges demo reports older than 45 minutes. Demo data is never written to persistent PostgreSQL, never stored in AWS S3 or Cloudflare R2 buckets, and never submitted to external AI LLMs.
7. AI Triage & LLM Data Minimization
BugFence features optional AI triage capabilities to summarize crashes and suggest code fixes:
- Browser Triage: Runs entirely on-device without outbound network calls.
- Server Triage: Dispatches a minimal, re-scrubbed text excerpt containing only the title, description, and sanitized stack trace. Screenshots, video recordings, DOM replays, request headers, and customContext are never sent to AI providers.
- Provider Secrets: Third-party LLM API keys (OpenAI, Anthropic, Google Gemini) stay securely on your server and are never exposed to clients.
- No AI Training: Customer bug reports are never used to train public or foundational artificial intelligence models.
8. Website Visitors, Cookies, and Analytics
On bug-fence.com, we do not utilize behavioral advertising cookies, cross-site tracking beacons, or third-party marketing pixels.
Standard HTTP server logs (IP address, user-agent, requested URL, timestamp) are retained temporarily by our edge infrastructure solely for DDoS mitigation, load balancing, and operational defense.
If you submit a contact, demo, or licensing inquiry, we collect your name, business email, organization name, and message strictly to respond to your request.
9. Subprocessors and Payment Processors
For cloud subscriptions, customer billing, and website delivery, BugFence engages vetted subprocessors:
- Stripe, Inc. (United States): International credit card processing and subscription billing in USD.
- Razorpay Software Private Limited (India): Indian Rupee (INR) payment processing, UPI, NetBanking, and automated 18% GST B2B tax invoice generation.
- Cloudflare, Inc. (United States): Edge CDN delivery, DNS, and DDoS mitigation.
- Amazon Web Services, Inc. (United States / Europe): Cloud compute and encrypted backup infrastructure (applicable to BugFence Hosted SaaS only).
10. Data Subject Rights (GDPR, UK GDPR, CCPA/CPRA, DPDP)
Depending on your jurisdiction, you have statutory rights regarding personal data held by BugFence as a Data Controller:
- Access and Portability: The right to request copies of your personal information and commercial records.
- Rectification and Correction: The right to correct inaccurate or incomplete contact information.
- Erasure ("Right to be Forgotten"): The right to request permanent deletion of your account and personal correspondence.
- Non-Discrimination: We will never discriminate against you, alter service tiers, or degrade quality for exercising your privacy rights.
- Notice of Non-Sale: BugFence does not sell, rent, or share personal data with third-party data brokers or advertising exchanges.
11. Data Retention and Durable Erasure
Self-Hosted Retention: Configured by the server operator via BUGFENCE_RETENTION_DAYS (default 90 days; 0 disables). Expired reports are automatically purged by daily background cron sweeps.
Account & Workspace Erasure: BugFence provides built-in cryptographic deletion APIs (DELETE /api/v1/auth/account and DELETE /api/v1/auth/workspace) that remove user records, session credentials, tokens, and storage snapshots, issuing an authoritative 24-hour verification receipt.
12. Privacy Desk & Inquiries
For questions regarding this policy, to exercise your data subject rights, or to request a signed Data Processing Addendum (DPA), please reach our dedicated privacy team at support@bugfence.com.
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.