Overview
PageBlueprint is designed to keep your data on your device. We capture semantic UI maps for AI training, but they never leave your machine unless you export them.
This policy describes what data PageBlueprint captures during a recording session, where that data is stored locally, and how it is managed. All extension functionality exists exclusively to serve the single purpose stated above.
Data Captured
Recording is always user-initiated. We only capture data from the tab you explicitly choose to record.
During an active recording session, PageBlueprint may capture:
- DOM snapshots — The structural content of the web page, including HTML, ARIA attributes, and element bounding boxes.
- Network requests — HTTP metadata (URLs, methods, status codes). Bodies may be captured if CDP interception is active.
- Console logs — JavaScript console output from the recorded page.
- User interaction events — Clicks, inputs, and navigation actions used to generate interaction narratives.
- Screenshots — Visual captures of the visible tab at snapshot time.
- Annotations — Freehand drawings, shapes, and text added by the user during a session.
PageBlueprint does not capture data from tabs that are not actively being recorded.
Data Storage & Retention
All captured data is stored locally on your device only. We have no servers to receive your captures.
Local Only
PageBlueprint does not transmit any captured data to external servers, third-party services, or GoManzanas infrastructure. Data is held in the browser's local IndexedDB storage and is accessible only within the extension context.
Exported Files
Exported .appspec files are saved directly to your local filesystem via the browser's downloads API. Once exported, the file is under your control entirely.
Retention
Recorded session data persists in local storage until you explicitly delete it within the extension. Clearing the extension's storage or uninstalling PageBlueprint will permanently remove all stored session data.
Permissions Explained
We request the minimum permissions required to enable deep UI capture and recording.
| Permission | Purpose |
|---|---|
debugger |
Required for Chrome DevTools Protocol (CDP) access to enable network request and console log capture during recording. |
downloads |
Used to save exported .appspec files to your local machine. |
storage |
Used to persist session state and temporary recording data locally. |
offscreen |
Required for heavy DOM-to-SVG processing without blocking the UI. |
scripting |
Required to inject the capture logic into tabs. |
tabs |
Required to query the active tab and capture visible screenshots. |
Debugger API Disclosure
PageBlueprint uses the debugger API to intercept network requests. When attached, Chrome displays a notification bar. This is a built-in behavior that cannot be suppressed. The debugger is only attached while a recording is active and detached immediately when paused or stopped.
Contact
Questions about this policy or our data practices?
Reach us directly at: extensions@GoManzanas.com
Last updated: 2026-04-28