Last updated: November 6, 2026
SnapBug ("we", "us") provides a browser extension for capturing and annotating visual bug reports, and a companion website for account and subscription management. This page explains what data we collect and how it is used.
When you create an account on the SnapBug website, we collect your email address and a hashed password, stored and managed by our authentication provider, Supabase. This is used solely to identify your account and license status.
The browser extension stores your license key and a usage counter locally in your browser (via Chrome's storage APIs). To check whether a license is active, the extension sends the license key to our verification server. No browsing history, page content, or personal data is included in this request.
Screenshots, annotations, and generated bug reports are created and processed within your browser. They are exported directly to a file on your device and are not stored on our servers. The only exceptions are the optional AI features and the integrations you choose to connect, both described below.
When you capture a screenshot, the extension inspects the page you are capturing (for example, for broken images, missing labels or low-contrast text) so it can offer to mark those issues. This scan runs entirely in your browser and its results are kept only in your browser's local storage. Nothing from it is sent to us unless you use an AI feature, as described below.
When you start a video bug report, the extension records the browser tab you are on (picture and sound) until you stop it, for up to five minutes. While recording, it also notes which buttons, links and fields you interact with, the page's console errors and warnings, failed network requests, and page navigations, so it can build a timeline and steps to reproduce. It records which field you typed in, never what you typed.
The recording and its timeline are processed and stored only in your browser (in its local IndexedDB storage), and only the most recent recording is kept. Nothing from a video report leaves your browser unless you use a video AI feature or send the report through an integration, both described below. Downloads and shareable report files are saved directly to your device, and you decide who to share them with.
AI Detect only runs when you click it, and asks for your confirmation the first time. When used, the extension sends the current screenshot (with any areas you covered using the Pixelate tool blacked out), the page title, and the names of issues found by the page scan to our server, which forwards them to Google's Gemini API to identify visual issues. We do not store the screenshot; it is processed in memory and discarded. Google processes this data under the Gemini API Additional Terms of Service, and Google may use content sent through its free tier to improve its products. Do not use AI Detect on screenshots containing sensitive information unless it has been pixelated first.
AI tickets works the same way: when you click it in the report window, the extension sends the screenshot (with pixelated areas blacked out), your annotations' titles, descriptions, severities and positions, and the captured page's URL, title, viewport size and your browser name and version to our server, which forwards them to Google's Gemini API to write bug tickets. Nothing is stored on our servers.
The instant AI summary on the annotation page works the same way. It runs automatically on new captures only after you have agreed to AI uploads, and you can switch it off on the summary card. It sends the screenshot (with pixelated areas blacked out), the page URL with sensitive parameters removed, the page title, the viewport size and the names of issues found by the page scan.
The video AI features (AI ticket and Explain this error) ask for their own confirmation the first time. They send the recording's text timeline: the steps you took, console messages, failed request URLs, the page URL and title, your browser name and viewport size, and the bug title and notes you typed. The video itself is never sent. Before anything leaves your browser, email addresses, tokens, API keys, card numbers and sensitive URL parameters are replaced with placeholders. Our server forwards this to Google's Gemini API and does not store it.
To enforce daily usage limits, our server keeps a daily counter keyed by a one-way hash of your IP address (or of your license key, for Pro users). Raw IP addresses are not stored.
You can connect Jira, ClickUp, GitHub, Linear or Slack so that "Send to…" creates a ticket or posts a message for you. Each service is connected with an API token you create in that service. Tokens are stored only in your browser's local storage and are sent only to the service they belong to. Chrome asks you to allow access to each service when you connect it.
When you click Send, the extension sends the report directly from your browser to the service you chose: the title, the report text (including the page URL and environment details), severity, labels and the files you selected, such as the annotated screenshot or the video recording. None of this passes through or is stored on our servers. Once sent, it is handled under that service's own privacy policy and your organisation's settings there. Disconnecting a service in SnapBug deletes its token from your browser and removes SnapBug's access to that service.
Subscription payments are processed by Stripe. SnapBug does not receive or store your card details.
You can request deletion of your account and associated data at any time by contacting us below.
For privacy questions or data deletion requests, contact: sarmad@articheck.com