HTML TO FRAMES · BY EUREKA!

Privacy policy

Last updated 14 October 2026

In short: we only handle what is needed to turn a page into Figma layers. Captured pages are delivered to you once and not kept. The Chrome extension sends nothing to our servers unless you connect it to your plugin and click “Send to Figma”; that capture is held in memory until your plugin takes it, then deleted. We don’t sell data, show ads or use trackers.

This policy covers the HTML to Frames Figma plugin, its capture service (capture.89.116.236.13.sslip.io), the HTML to Frames Chrome extension and its connection for AI tools (MCP). They are made by EUREKA! (“we”).

1. Figma plugin and capture service

When you import a link, the plugin sends our service the page address, the screens and options you picked, and an account identifier. The identifier is derived from your Figma user id (or a random id); we do not receive your name or email address. If you use a license key or bought Pro in Figma, the key or a short-lived Figma purchase token is sent so we can apply your plan.

Our service opens the page in an isolated browser, reads its layout, text and images and sends the result to your plugin. The result can be downloaded once, is then deleted from memory, and is never written to disk. The import itself is forgotten after 15 minutes.

Local files and pasted code: files you upload are kept in memory only while their pages are captured and deleted right after the last one (or after 2 minutes if the import is abandoned). They are never published at a public address.

2. Chrome extension

The extension runs in your browser. When you click “Capture this page”, it reads the current tab — layout, text, styles and images — and puts the result on your clipboard (or in a file on your computer). It has no account, contains no analytics and does not load remote code. Its saved options stay in your browser.

Send to Figma (optional). If you connect the extension to your Figma plugin with a one-time code, the extension keeps a connection token in your browser (we store only a hash of it, with the time it was last used, until you disconnect). When you then click “Send to Figma”, the capture of that tab is uploaded over HTTPS to our service and held in memory only until your open plugin downloads it — it is deleted at that moment, and after 30 minutes in any case. Nothing is sent unless you click it; without a connection the extension sends no page content to us or anyone else.

When you paste a capture into the Figma plugin, the plugin tells our service the page address and width so the import can be counted against your plan. The page content itself is not uploaded.

Permissions: it can read the tab you capture and download that page’s images from the sites they are hosted on (images often live on other domains), which is why it asks for access to all sites. It only does this when you click capture.

The use of information received from the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

3. AI tools (MCP)

If you connect an AI tool from the plugin’s AI tab, we create a connection token and store only a hash of it, with the time it was last used, until you disconnect. Pages your AI tool sends (a link or HTML it wrote) wait in memory until your open plugin picks them up — HTML is deleted at that moment — and are discarded after 30 minutes in any case. Each one is then imported like a normal import.

4. What we keep, and for how long

5. Sharing

We don’t sell or rent data and don’t use it for advertising. Data is processed on servers we rent from our hosting provider. Figma receives a check of your purchase token when you pay through Figma. We disclose data only if required by law.

6. Cookies

The plugin, the extension and this website use no cookies, analytics or tracking pixels.

7. Your choices

8. Changes

If this policy changes, the date above changes with it.

Pricing