Privacy Policy: Webpage to Figma
This policy explains what the Webpage to Figma browser extension can see, what it does with it, and where that information can end up. It is written to be read, not to be skimmed past.
What this covers. The Webpage to Figma browser extension, and the companion Webpage to Figma plugin that imports its export file inside Figma. Together these are called "the Extension" below. "We" means FS Cluster and Torus Founding Space, who publish it.
In short: the capture runs entirely in your browser, the result is saved as a file on your own device, and we do not receive it. We run no analytics, no trackers, no telemetry, and no server that your captures are sent to.
The one thing worth knowing is what happens next: if you import that file into Figma, the captured content goes to Figma. Section 5 explains this.
1. How the Extension is built
The Extension runs entirely on your machine. It has no backend. There is no account to create, nothing to log in to, and no server of ours that your captures, preferences, or usage are sent to. Parsing, document building, and file generation all happen inside your browser.
2. What the Extension accesses
To do its job, which is turning a page layout into an editable design file, the Extension reads the following, and only when you start a capture:
The active tab's Document Object Model, computed CSS styles, visible text, images, and SVG elements. If the page you capture shows personal or confidential information, that information is part of the capture, because the capture is a picture of the page as rendered. Only pages you explicitly capture are read.
Capture settings you choose are kept in your browser's local extension storage so they persist between sessions. They stay in your browser.
No names, email addresses, browsing history, keystrokes, IP addresses, payment details, or cookies. The Extension does not watch pages in the background and does not record where you go.
3. What happens to a capture
The captured content is parsed and compressed into a .kn file, which is downloaded to your device through your browser's normal download mechanism. It is saved wherever your browser saves downloads. That file is yours. It is not uploaded, mirrored, logged, or copied to us at any point.
4. What we do not do
We do not sell, rent, or trade your data.
We do not use your data or captured page content for advertising, profiling, or creditworthiness decisions.
We do not transfer your data to third parties, except as described in section 5, which you control.
We do not execute remote or dynamically fetched code at runtime.
5. Figma, and the one time data leaves your device
The Extension writes a file to your device and stops there. It does not send that file anywhere.
The file exists to be imported into the companion plugin inside Figma. When you choose to import it, the captured page content is read by that plugin and becomes part of your Figma document, which Figma stores on its servers under your Figma account. You start that transfer, not us, and once the content is in Figma it is governed by Figma's Privacy Policy and terms, not this one.
If you never import the file, the captured content never leaves your device. If you capture a page containing sensitive information, this is the step to think about before taking it.
6. Retention
We operate no server that receives your data, so there is nothing on our side to retain, and nothing for us to delete on request. Export files stay on your device until you delete them. Saved preferences stay in your browser until you clear them or uninstall the Extension, which removes them.
7. Permissions, and why each one is needed
The Extension requests the smallest set of permissions that lets a capture work:
| Permission | Why it is requested |
|---|---|
activeTab, scripting | To read and parse the visual structure of the page you are on, and only after you start a capture. |
downloads | To save the resulting .kn export file to your device. |
storage | To remember your capture preferences between sessions. |
<all_urls> | Broad by necessity, because a capture can be run on any site you choose, including localhost. It is also used to fetch images the page loads from another domain, which browser CORS rules otherwise block from being read into the export. It is not used to browse, monitor, or read sites in the background. |
8. Your rights
If you are in the EEA, the UK, California, or another place with data protection rights, those rights apply to any personal data we hold about you. In practice we hold none from your use of the Extension, because none reaches us. The only personal data we are ever likely to have is an email you send us. You can ask us to delete that at any time using the address below.
9. Children
The Extension is a tool for developers and designers. It is not directed at children, and we do not knowingly collect personal data from anyone, children included.
10. Changes to this policy
If this policy changes, the revised version is published at this same address and the "Last updated" date at the top changes with it. If a change materially affects how your data is handled, we will say so in the extension's store listing too. This page is the authoritative version.
11. Contact
Questions about this policy, or about anything the Extension does, can go to: