What Web2Fig Processes
Only when you explicitly activate Web2Fig, it processes the selected webpage’s DOM structure, displayed text, computed CSS styles, layout dimensions, and visible assets (images, SVGs, background styling). This processing is strictly necessary to assemble the Figma clipboard output you requested.
Where Processing Happens
100% of processing occurs locally within your Chrome browser. The extension keeps DOM structure in temporary memory only long enough to write the payload to your system clipboard, then discards it immediately. Web2Fig does not use browser sync, local storage persistence, cookies, or remote databases.
Images and Network Requests
To preserve visible cross-origin images or SVGs, Web2Fig may request the public asset URL directly from its original host server after you initiate a capture. This is a standard browser HTTP request directly to that host — not a transfer to Web2Fig or any third-party service. Web2Fig never uploads captured content to any external server.
System Clipboard
When capture completes, Web2Fig writes the Figma-compatible payload to your local system clipboard. Clipboard memory is governed by your operating system and the Figma app where you paste it. Web2Fig does not read back or retain clipboard data.
Permission Minimization
- activeTab: Allows Web2Fig to operate exclusively in the browser tab you explicitly trigger it on.
- scripting: Allows Web2Fig to inject its element-picker UI overlay into that active tab.
- Host Access (<all_urls>): Used solely to fetch cross-origin visual images/SVGs required for your active capture. It is never used for background tracking or browsing monitoring.
Policy Changes & Contact
If this privacy policy is updated, the revision date will be reflected at the top of this page. For any questions or privacy inquiries, please open an issue in the official Web2Fig GitHub Repository or contact Bukhtyar Haider Khan.