HIP FULLPAGE / PRIVACY
Local first.
In the current Free release, Hip FullPage does not upload screenshots or product data to a remote server.
← Hip FullPageWhat is processed?
When you explicitly start a capture, the extension may process visible pixels of the active tab, page dimensions and scroll position required for full-page capture, and the page title and hostname used to label the capture in Preview and Library.
Where is data stored?
Captures are stored locally in the browser using IndexedDB. Settings and storage preferences are kept locally in Chrome extension storage.
The current Free release does not upload screenshots, page content, browsing history, titles, URLs, annotations or Library data to a remote server.
Permissions
- activeTab — temporary access only after an explicit user action.
- scripting — to inject the local capture helper into the active page.
- downloads — to save files only when the user chooses to export.
- storage — to store local extension preferences.
- contextMenus — for secondary capture modes and Library access.
The extension does not request persistent <all_urls> host access.
Exports and clipboard
PNG, JPEG, WebP and PDF files are created locally. Files leave the browser only when you explicitly export them. Copy places the rendered image on your local clipboard after an explicit action.
Issue reporting
The support page may prepare diagnostic text locally in your browser. When you submit the form, your email address, message and visible diagnostics are sent to our support team and email delivery provider. Page host, title and screenshots are sent only when you explicitly include them.
Accounts and network features
- No account required.
- No cloud sync.
- No analytics SDK.
- No advertising SDK.
- No remote screenshot processing.
- No AI processing.
Last updated: September 24, 2026