Privacy Policy

Last updated: September 10, 2026

Snapture is a Chrome extension ("Snapture") and a companion Figma plugin ("Snapture Import") that let you capture a web page and rebuild it as editable layers in Figma.

The short version

What the extension accesses, and why

• The page you choose to capture. When — and only when — you start a capture (by clicking a Snapture button or pressing a capture shortcut), Snapture reads the rendered content and computed styles of the current tab in order to reconstruct it. This data is written into a .figma.json file saved to your computer or copied to your clipboard. The extension does not upload the capture.
• Images on the page. To embed images into that file so they appear correctly in Figma, the extension's background process fetches the image bytes (including from other domains/CDNs). These bytes are embedded into your local file only. This happens only within a short window right after a capture you started, and only for the tab where the capture began.
• A screenshot of the visible tab, during your capture. Some content (WebGL canvases such as 3D viewers/charts/maps, and embedded iframes) cannot be read as layers. For those areas only, Snapture takes one screenshot of the visible tab, crops out just those rectangles, and embeds the crops into your local file. Like image fetching, this works only within the short window after a capture you started, and the extension does not upload the screenshot.
• A small helper on figma.com only. When you open Figma within 30 minutes of a capture, Snapture shows a small dismissible reminder that your capture is ready to paste. This helper reads nothing from the Figma page — it only renders that reminder and, when you click it, copies your own capture from local storage to your clipboard.
• Clipboard, only when you click "Copy for Figma". As an alternative to saving a file, you can copy the capture to your clipboard and paste it into the Figma plugin. Snapture writes to the clipboard only on that click and never reads your clipboard.

What the extension does NOT do

• It does not run on any page automatically — only when you trigger a capture. The one exception is the small figma.com reminder described above, which renders UI only and reads nothing from the page.
• It does not collect browsing history, form data, credentials, cookies, or personal information.
• It does not send page content, captures, or screenshots to the developer or anyone else — there is no server that could receive them.
• It contains no analytics, telemetry, tracking, or advertising.
• It loads no remote code; all code is contained in the published package.

Network requests

This is the complete list of requests the extension can make. Everything else happens offline.

• Images on the page you are capturing — described above. These go to whichever sites host the images (the page's own CDN), only within the short window after a capture you started, and only so the pictures appear in your file.
• One retry with a Referer header. Some image CDNs refuse requests that do not say which page they came from. If such a fetch is refused during your capture, Snapture retries that single image once, telling the CDN the origin (e.g. https://example.com/) of the page you are capturing. This uses Chrome's declarativeNetRequestWithHostAccess permission, which here only sets that one header on that one retry — it never blocks, redirects, or reads your other traffic.
• Pro license check. If you buy Snapture Pro and enter your license key, the extension sends that key (and a randomly generated activation name) to our payment provider, Lemon Squeezy (api.lemonsqueezy.com), to activate it, and re-checks it at most once a day afterwards to confirm the subscription is still valid. This request contains your license key only — never page content, browsing history, or personal information. If you never use Pro, this request never happens. Lemon Squeezy's own privacy policy governs the data you give them when purchasing.
• Batch capture page discovery (Pro). When you click "Load from sitemap" in the popup, the extension fetches /sitemap.xml and /robots.txt from the site you are currently on, to list that site's pages for you. It sends nothing but the request itself, and only on that click.

The Figma plugin (Snapture Import)

The plugin has no network access of its own (networkAccess.allowedDomains: ["none"]). It reads the capture you paste or open, or the bundled practice file, and builds layers in your Figma file. Figma itself stores and shares that file according to your Figma account and file settings.

The plugin remembers import options and review-prompt state using Figma's local clientStorage. Imported frames carry their source URL, capture identifier, time and viewport width as plugin data inside the Figma file, so you can compare or replace a previous import. This information travels with the Figma file; it is not sent to Snapture. The practice file contains invented example content and does not read a website or consume your capture allowance.

Permissions

• scripting — to inject the capture script into the active tab when you start a capture.
• storage — used in three scopes:
  • session — that you just started a capture on a tab (a tab id and an expiry timestamp), so the image/screenshot helpers keep working if the background process restarts mid-capture. Cleared when the browser closes.
  • local — your most recent capture, so the popup and the figma.com reminder can re-copy it without you capturing again. This does contain the captured page's data, it stays on your device, it is overwritten by your next capture, and removing the extension deletes it.
  • sync — your Pro license state (license key, activation id, plan) and your free-capture usage count and UTC calendar month, so Pro follows you across the Chrome profiles you are signed into. Chrome uploads this to your own Google account, the same way it syncs bookmarks; it is not sent to Snapture. Page content is never written to sync storage.
• declarativeNetRequestWithHostAccess — only for the single Referer retry described under Network requests. Snapture registers no blocking, redirecting, or tracking rules.
• host_permissions: <all_urls> — so capture works on whatever site you're viewing, and so image bytes can be fetched from any origin to embed into your file. This same permission allows the one-time visible-tab screenshot described above. No host is accessed and no screenshot is taken without a user-initiated capture.

This website

Everything above is about the extension and the plugin. The website you are reading is a separate thing, and it does collect one: Cloudflare Web Analytics counts page views, so we can tell which pages are actually useful to people.

It is the least invasive analytics available, and the specifics matter. It sets no cookies, writes nothing to your browser's storage, and does not fingerprint your device. It cannot follow you to other sites, and it gives us no way to identify you or single you out. What reaches us is aggregate: which page was viewed, roughly which country it came from, what linked to it, and what kind of device it was.

We use it to answer questions like "is anyone reading the cancellation guide", not to build a picture of you. Any content blocker stops it, and the site behaves exactly the same without it.

Data retention

Snapture does not retain your captures on a server. You control your downloaded files and imported Figma layers. The extension's latest capture stays in local storage until the next capture replaces it or you remove the extension. Chrome sync storage and the Figma plugin's local preferences and file metadata are described above. Purchase and license records are handled by our payment provider.

Changes

If this policy ever changes, the updated version will be posted at this URL with a new date above.

Contact

Questions about this policy: snapture26@gmail.com