Add to Chrome
Add to Edge
Quick answer: GrabAll is designed around a local browser workflow: it scans pages selected by the user, stores settings and working data in extension storage, and sends selected files to the browser download system. Support submissions and license validation are separate network actions initiated for those features.
Why the extension needs browser permissions
Page scanning requires access to the active tab or selected pages so GrabAll can identify exposed links and media. Download permission allows the extension to ask the browser to save files chosen by the user. Storage permission supports settings, saved items, scan history, usage counters, and interface preferences.
Permission names can sound broad because browsers define reusable technical capabilities. The meaningful question is how and when the product uses them.
- Scripting or active-tab access for selected page scans
- Tabs access for open-tab workflows
- Downloads access for user-selected files
- Storage for settings, history, saved items, and license state
What local processing means
Local processing means the extension interface can inspect the selected browser context and organize results without uploading the entire page to a remote GrabAll server. Filters, selections, previews, and working lists can be handled in the browser.
The files themselves are normally requested from their original website and saved through the browser. GrabAll does not become the publisher or owner of those third-party resources.
Data stored in the browser profile
Settings, visual preferences, saved results, recent scans, counters, and similar extension state may be kept in browser extension storage. Clearing browser data, removing the extension, or changing profiles can remove locally stored information.
Avoid treating extension history as the only copy of critical project records. Export or preserve important links separately.
When a network request may occur
License activation or validation can require communication with a backend service. A support message sends the information the user enters when they choose to submit it. Analytics or website measurement may also operate on the public website according to the privacy policy.
These actions are different from uploading every scanned page. Review the current Privacy Policy for the authoritative description of services and data handling.
- Premium license activation and validation
- Support forms submitted by the user
- Requests for files from their original host websites
- Public website analytics described by the site policy
A privacy checklist for users
Install extensions only from official browser stores, review requested permissions, keep the browser updated, and scan only pages appropriate for the work. Do not collect private, personal, or confidential files without authorization.
For organizational use, confirm that the workflow matches company security rules, data-retention policies, and contractual obligations.
Frequently asked questions
Does GrabAll upload every scanned webpage?
GrabAll is designed around local browser scanning. Separate services such as support submission or license validation may send the information required for those actions.
Why does it need downloads permission?
The permission allows GrabAll to request browser downloads for files the user selects.
Where are settings and scan history stored?
They may be stored in the browser's extension storage for the current profile.
Can removing the extension delete local data?
Yes. Removing the extension or clearing browser data can remove extension storage, so export important project information separately.
Use GrabAll for files you are allowed to access and download. The extension helps discover and organize exposed webpage assets; it does not bypass authentication, paywalls, DRM, private content, copyright, or website rules.