Local-file distribution · Updated 6 September 2026
H2F Capture helps you capture a page or selected region into a local .h2f file for import with the separate H2F Figma plugin. This policy applies to the local-file Chrome extension distribution, which has no extension account or cloud transfer feature.
When you start a capture using the popup or a keyboard shortcut, the extension reads the selected page and permitted embedded frames. It can process page text, images, font information, URLs, element structure, styles, dimensions and capture diagnostics. A capture may include personal or sensitive information that is displayed in the page you choose. Capture only content you are entitled and willing to save.
Chrome's debugger access is used for layout, frames, resource content and image fallback. The extension does not use the debugger to bypass a site's sign-in or payment requirements. Some browser-internal pages, protected content and embedded frames cannot be captured.
The capture is processed in the browser and saved through Chrome's download mechanism. This distribution does not upload captures to our servers. Direct cloud transfer and extension sign-in are unavailable. No analytics SDK, advertising script or remote executable configuration is included.
While reading a page's assets, the extension may request image, stylesheet or font resources from the page's original resource providers, including Google Fonts when referenced by the capture. Those providers receive the network information normally associated with such requests, including your IP address. Loading and operating the source website is also subject to that site's own privacy practices.
Viewport, theme and export preferences are stored in Chrome extension storage. The local-file build does not create an extension account or a tracking user ID. A temporary capture identifier and progress record let you reopen the popup and check the active task. Temporary capture data is used for the active task. Downloaded .h2f files remain on your computer until you delete them; uninstalling the extension does not remove downloaded files. The file format's compression and byte encoding are not encryption.
You can remove extension preferences and permissions through Chrome's extension settings or by uninstalling the extension. Remove downloaded captures through your file manager.
Captured information is used to provide the capture-and-export workflow. It is not sold, used for personalized advertising, or used to determine creditworthiness. Our use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.
Importing a saved file into Figma is an action you take separately. Figma's processing of the design and the H2F plugin's account, access and payment features follow their own applicable policies and terms. The Chrome extension does not process payment-card details.
Contact sutalxy11@gmail.com. If you send a capture to support, send only the information needed to explain the problem. Your support message and any attachment you choose to provide will be used to respond to that request.