LEGAL / PRODUCT DATA
Privacy policy.
Breakpoint Capture processes your screenshots in Chrome. This page explains what stays in the browser and what the extension sends to account and licensing services.
Captures and temporary history
The extension captures the web page or element you choose and keeps screenshots and a snapshot of visible content in a temporary toolbar on that page. It retains the current capture and up to five previous captures, subject to a 32 MiB budget for encoded history data. Clear history removes previous captures. Reloading or navigating away clears all results. Hiding the toolbar keeps them available when you reopen it. This history is held in memory and is not saved to disk.
The snapshot can include text from the page, including sensitive text visible at capture time. Captures are processed locally in your browser. The extension does not send screenshots, page contents, or browsing history to a Breakpoint Capture server.
Settings and browser permissions
The extension saves your configured breakpoint widths in Chrome’s local extension storage. Capture uses Chrome’s debugger API while it captures, then detaches. Chrome displays its debugging notice during this time.
When you choose a download action, the download is saved to your device. The ZIP download contains PNG screenshots only.
Clipboard and Figma
When you choose Figma, the extension writes HTML design data to your clipboard. It can contain visible page text and embedded page assets, including sensitive content shown at capture time. If the editable design has missing images, Chrome may ask you to grant access to their external hosts. Those optional host permissions let the extension fetch artwork for the editable design. The image hosts receive requests for their images; screenshots and page text are not sent to them. You can decline or later revoke those permissions in Chrome’s extension settings.
The optional Figma importer plugin reads selected PNGs locally and has no network access.
Account and Free allowance
Account sign-in is required to capture. The extension sends your email address and verification code to Supabase Auth and stores your account email, user ID, access token, refresh token, and expiration time in Chrome’s local extension storage. Supabase processes sign-in and email delivery.
Before a capture, the extension sends your account token to Supabase to check and reserve a Free slot. Supabase stores your account ID, the UTC month, and the number of capture starts used that month. The Free limit is 20 starts per month; cancelled and failed captures count. Signing out removes credentials from this browser and asks Supabase to end the session. Screenshots, page text, and browsing history are not sent to Supabase.
License and payment
The extension stores your license key, license instance ID, license status, and check time in Chrome’s local extension storage. Activating or checking a license sends the key and instance ID to the configured billing service, which forwards them to Lemon Squeezy’s License API. Opening checkout sends you to Lemon Squeezy’s hosted payment page. The extension does not receive payment card details.
The license form runs on an extension-owned page, so websites you capture do not receive the key typed into it. No screenshots or page content are sent to the billing service or Lemon Squeezy. During the product review, the extension’s payment integration is in test mode; this website does not offer a test checkout.
Contact
For privacy questions, email gojo.seinsi@gmail.com.