JumWeb is local-first. Your screenshots and their metadata are stored on your own device and are never uploaded to us or anyone else.
1. Who this applies to
This policy covers the JumWeb browser extension. It does not cover third-party websites you capture, or the payment/licensing provider (see §6).
2. What JumWeb stores, and where
| Data | Where it is stored | Leaves your device? |
|---|---|---|
| Screenshot images and thumbnails | Local IndexedDB (in your browser) | No |
| Metadata: title, source URL, hostname, capture date, dimensions, size | Local IndexedDB | No |
| Organization: tags, folders, favorites | Local IndexedDB | No |
| Preferences (filename template, default export format) | chrome.storage.local |
No |
| License key + entitlement cache (only if you enter a Pro key) | chrome.storage.local |
Only during license activation/validation — see §6 |
We do not operate a server that receives your screenshots or browsing data. There is no JumWeb account and no sign-in.
3. What JumWeb does not do
- It does not upload your screenshot images or thumbnails.
- It does not send webpage content, HTML/DOM, or page text.
- It does not collect or transmit your browsing history.
- It does not use analytics, advertising, tracking, or fingerprinting.
- It does not sell or share personal data with third parties.
- It does not load or run remotely-hosted code, and never uses
eval.
4. Permissions and why they are used
| Permission | Why it is needed |
|---|---|
activeTab |
Access the current tab only after you click the JumWeb icon or a shortcut, to capture it and inject the temporary scroll/measure helper. No standing access to your pages. |
scripting |
Inject the capture helper on demand only — never a persistent content script. |
storage |
Save preferences and the license cache locally (never images). |
downloads |
Save and re-download the screenshot files you export. |
contextMenus |
Add a right-click entry to start a capture or open the library. |
JumWeb does not request broad host access on install. Restricted pages (chrome://, the Chrome Web Store, and other extensions) cannot be captured.
5. How captured pages are handled
During a full-page capture, JumWeb temporarily scrolls the page and may briefly hide sticky/fixed elements (headers, cookie banners, chat widgets) so they are not duplicated in the stitched image. All temporary changes are reverted on success, failure, or cancellation. This processing happens entirely within your browser.
6. Licensing (only if you buy Pro)
If you enter a Pro license key, JumWeb sends only the information required to activate or validate that key — the license key and a per-installation instance identifier — to the configured license provider. No screenshots, URLs, page contents, or browsing data are included. Your payment is processed by that provider under their own privacy policy; JumWeb never sees or stores your payment card details.
7. Data retention and deletion
- You can delete any screenshot at any time from the Library.
- Because all data is stored locally, uninstalling the extension may remove your locally stored screenshots and settings. Export a backup first if you want to keep them.
- We hold no server-side copy of your data, so there is nothing for us to delete.
8. Children
JumWeb is a general-purpose productivity tool and is not directed at children.
9. Future cloud sync
Cloud sync is not implemented in the current version. If optional cloud backup or cross-device sync is added in the future, it will be strictly opt-in, and this policy will be updated to describe exactly what is synced and how to disable it.
10. Changes to this policy
If this policy changes materially, we will update the effective date above and note it in the extension's release notes.
11. Contact
Questions about this policy or your data: support@yusoft.app