Privacy Policy

Figma Plugin (URL Import): When you import a page via URL, the target URL is sent to our cloud capture service at api.htmltofigma.com. The service renders the page in a headless browser and returns the extracted structure (DOM, computed styles, image URLs) to the plugin. This data is used solely to build your Figma design.

Browser Extension — Page-start canvas preparation: On matching pages and frames, the extension installs a lightweight script at document start that changes how newly created WebGL drawing buffers are preserved. This lets supported canvas content remain available if you later choose to capture the page. The script does not read or store page content, create a capture, contact HTMLtoFigma, or transmit data.

Browser Extension — User-initiated capture: Only after you choose Capture full page or Select an area, the extension may access the selected tab's DOM structure, visible text, computed CSS styles, images, fonts, SVGs, canvas output, other referenced assets, page title, sanitized source URL, viewport size, and scroll position. This information is used to create the capture you requested.

A page you choose to capture may contain personal, private, or sensitive information that is visible in that page. HTMLtoFigma does not receive or retain the extension capture. The extension does not access your browsing history outside the selected tab, collect your Figma account details, or intentionally collect authentication credentials, financial information, or precise location.

All data accessed by HTML to Figma is used exclusively for the single stated purpose: converting web page content into Figma designs.

URL Import: Page content is processed in memory during the capture session and is not stored after the import completes or is cancelled.

Extension capture: Captured page data is processed in extension memory and written through Chrome Downloads as a local .h2f file, or as readable JSON only when you explicitly enable the advanced debug-export option. HTMLtoFigma does not receive or store these files.

Settings and capture state: Viewport choices and short-lived capture status are stored in Chrome's extension session storage so the popup can recover its state. Capture payloads and full page URLs are not stored there. Exported source URLs remove credentials, query parameters, and fragments; local-file exports omit the original directory path.

To embed referenced assets in a local capture, the extension may request those assets directly from the website or CDN already hosting them. Same-origin asset requests may use the browser session already active for that page. Cross-origin asset requests omit credentials.

These requests go to the asset's existing host, not to an HTMLtoFigma capture server, and remain subject to that host's access rules and privacy practices.

We do not sell, rent, trade, or use captured content for advertising, creditworthiness, or unrelated purposes. The browser extension contains no advertising or analytics SDK and does not transfer captured page content to HTMLtoFigma or another third party.

A browser-extension capture reaches Figma only when you separately choose to import the downloaded file with the HTML to Figma plugin.

URL Import: Captured page data is held in memory only during the active import session. It is automatically deleted when the import completes, fails, or is cancelled. No data is persisted on our servers.

Browser Extension: Capture data is held in extension memory while the requested export is being created. The resulting .h2f or debug JSON file remains on your device until you move or delete it. HTMLtoFigma has no access to it unless you voluntarily send it to support.

All communication between the Figma plugin and our capture service uses HTTPS encryption. Browser-extension capture files are generated locally and are not uploaded to HTMLtoFigma. Referenced assets may be requested from their existing website or CDN hosts as described above.

URL Import uses our page capture API hosted at api.htmltofigma.com. During a browser-extension capture, referenced assets may be requested directly from the source website or its CDN. No third-party analytics, tracking, or advertising services are integrated into the browser extension.

Host access and scripting prepare supported WebGL canvases at page start and, after you initiate a capture, read the chosen page and request its referenced assets. The page-start preparation does not read or transmit page content.

activeTab and tabs identify the chosen tab, determine whether Chrome allows it to be captured, and read the viewport dimensions needed for the requested export.

debugger temporarily emulates responsive viewport widths and gathers browser-rendered page data for the capture, then disconnects after capture or cleanup. storage keeps viewport preferences and short-lived capture state in the browser session. downloads saves the generated .h2f or debug JSON file on your device.

If you choose Copy diagnostics, the copied text may contain the extension version, time, page origin, viewport, capture stage, and sanitized error details. Diagnostics are not sent anywhere automatically. HTMLtoFigma receives them only if you voluntarily send them to support.

HTML to Figma's use and transfer of information received from browser APIs adheres to the Chrome Web Store Developer Program Policies, including the Limited Use requirements. Browser data is used only to provide and improve the single user-facing capture function. It is not used or transferred for advertising, creditworthiness, lending, or unrelated purposes.

Human access does not occur unless you explicitly send diagnostics or a capture file to support, or access is required for a security investigation or legal obligation.

Since we do not collect or store personal data, there is no personal data to access, correct, or delete. If you have questions or concerns, you can contact us at any time.

HTML to Figma is not intended for use by children under the age required by applicable law. The website and products are not designed to knowingly collect personal information from children.

This Privacy Policy may be updated from time to time. Changes will be posted on this page with an updated "Last updated" date. Continued use of the plugin or extension after changes constitutes acceptance of the revised policy.

Questions about this Privacy Policy or data handling requests can be sent to [email protected].