📸

FigSnap
Privacy Policy

Last updated: November 30, 2025

FigSnap ("we," "us") is a Chrome extension and Figma plugin that captures webpage screenshots and delivers them directly to your Figma or FigJam boards. We designed FigSnap to operate entirely on your device and through services you control. This policy explains what we store, what we send, and how your data is handled.

1. Data We Store Locally

FigSnap saves only the configuration values you provide in the Chrome Extension Options page and/or Figma plugin:

  1. Figma Personal Access Token (PAT)
  2. Figma File Key
  3. ImgBB API key

These values are stored locally in chrome.storage.local (Chrome extension) and Figma's client storage API (Figma plugin). They never leave your device unless you are syncing extensions through your Google account (in which case they sync only through Chrome's standard mechanism).

2. Data We Transmit

When you capture a screenshot:

  1. FigSnap captures the visible portion of the active browser tab and converts it to a PNG image.
  2. The screenshot is resized (1024–1280px wide) and uploaded to ImgBB using the API key you provided. The image is stored under your ImgBB account.
  3. FigSnap posts a comment to your Figma file using the Figma API and your Personal Access Token. The comment includes:
    1. The public image URL returned by ImgBB
    2. The page URL where the screenshot was captured
    3. A timestamp
  4. The Figma plugin detects the new comment via the Figma API and automatically places the screenshot on your active board.

No other services receive this data. We do not log or relay it to any FigSnap-controlled server.

3. Data We Do Not Collect

  1. No personally identifiable information
  2. No browsing history or page content beyond the screenshot you explicitly capture
  3. No analytics, tracking pixels, or telemetry
  4. No cookies or advertising identifiers

4. Third-Party Services

FigSnap relies on:

  1. Figma: You provide the Personal Access Token and File Key. Figma's handling of API requests, comments, and file data is governed by their own terms and privacy policy.
  2. ImgBB: Screenshots are uploaded via the API key you supply. ImgBB's storage and retention policies are governed by their service terms.

You control both endpoints. Removing or rotating your Figma PAT or ImgBB API key revokes FigSnap's access.

5. Security

  1. All network requests use HTTPS.
  2. We recommend using dedicated Figma Personal Access Tokens with only the required scopes (file_comments:read and file_comments:write) that you can revoke if necessary.
  3. If your device has multiple users, consider clearing the FigSnap options or removing the extension to prevent access to your stored credentials.

6. Your Choices

  1. You can remove or update your Figma PAT, File Key, or ImgBB API key at any time through the FigSnap Extension Options page or Figma plugin settings.
  2. Uninstalling the Chrome extension removes all locally stored data from your browser.
  3. Removing the Figma plugin deletes all locally stored data from Figma.
  4. To delete images stored at ImgBB, sign in to your ImgBB account and remove the files there.
  5. To remove screenshots from Figma, delete them directly in your Figma file (FigSnap does not have the ability to delete content once placed).

7. Contact

If you have questions or need to report a privacy concern, contact:

Email: jesse@emptycan.com

By using FigSnap you acknowledge that the extension and plugin operate solely on your device, transmit data only to the Figma and ImgBB endpoints you configure, and do not otherwise collect or sell your information.