PageGrab — Chrome Extension

Privacy Policy

Effective date: March 2026 · Developer: Daiki Soga

The short version: PageGrab processes everything locally inside your browser. No data — not your page content, not your screenshots, not any personal information — ever leaves your device. There are no servers, no analytics, and no accounts.

1. Information Collection

PageGrab does not collect, record, or store any personal information. The extension operates entirely within your local browser environment.

When you use PageGrab, it may access the following types of data on your active tab — solely to perform the function you requested:

Page text and HTML structure (for content extraction and layout analysis)
CSS styles and computed layout values (for design system reverse-engineering)
Visual rendering of the active tab (for visible viewport and full-page screenshots)

This data is processed in memory and, if you choose to export it, saved directly to your local filesystem via the browser's native download mechanism. Nothing is transmitted to any external server. PageGrab has no backend.

2. Data Usage

Data accessed by PageGrab is used exclusively to:

Extract and format text content from the current page
Analyze page layout and component structure
Identify design tokens (colors, typography, spacing)
Capture visible viewport and full-page screenshots from the active tab

No data is retained between sessions. When you close the extension popup or navigate away, any in-memory data is discarded. PageGrab does not write to chrome.storage, localStorage, IndexedDB, or any other persistent storage mechanism.

3. Third-Party Services

PageGrab does not integrate with any third-party services. There are no analytics SDKs, no crash-reporting libraries, no advertising networks, and no external API calls of any kind. No data is shared with any third party.

4. Permissions Explained

PageGrab requests the following Chrome extension permissions. Each permission is used strictly for the stated purpose and nothing else.

Permission	Why it is needed
`activeTab`	Grants temporary access to the tab you are currently viewing, only while the extension popup is open. Required to read page content for extraction and analysis.
`scripting`	Allows PageGrab to inject content scripts into the active tab in order to traverse the DOM, read computed styles, and identify layout components.
`downloads`	Used to save extracted text, JSON output, or screenshot image files directly to your local filesystem. No file data passes through any server.
`debugger`	Required only for full-page screenshots that capture content beyond the visible viewport. PageGrab attaches to the active tab during capture and detaches immediately after the screenshot is saved or the capture fails.

No permissions beyond those listed above are requested. PageGrab does not request access to browsing history, bookmarks, cookies, or any other sensitive browser data.

5. Children's Privacy

PageGrab is a developer tool and is not directed at children under the age of 13. Because the extension collects no personal information from any user, no special provisions for children's data are necessary.

6. Changes to This Policy

If PageGrab's data practices change in the future (for example, if a cloud feature is added), this privacy policy will be updated before that version is released to the Chrome Web Store. The effective date at the top of this page will reflect the date of the most recent revision.

Continued use of the extension after a policy update constitutes acceptance of the revised terms. Users are encouraged to review this page periodically.

7. Contact

If you have any questions or concerns about this privacy policy or PageGrab's behavior, please contact the developer:

Daiki Soga
ijinvlogs@gmail.com