PageStitch privacy policy
PageStitch captures a web page selected by the user and converts it into a PNG image. All capture processing happens locally in Google Chrome on the user's device.
Data PageStitch handles
When the user starts a capture, PageStitch temporarily handles the selected page's visual content, layout measurements, and URL. The URL is used only to confirm that the page is supported and remains the active source during capture.
Collection and sharing
PageStitch does not transmit page content, screenshots, URLs, or usage information to the developer or any third party. It has no analytics, advertising, tracking, account system, or remote service. PageStitch does not sell or share user data.
Limited use
PageStitch uses page content, screenshots, layout measurements, and the selected page URL only to provide its disclosed single purpose: creating the user-requested PNG capture. This use complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Local storage and deletion
The completed PNG is temporarily stored in extension-owned IndexedDB so the local result page can display it. It is normally deleted as soon as the result page reads it. If a result cannot be opened, the capture is deleted immediately. Records left by a browser or extension crash are deleted after 24 hours when PageStitch next starts or saves a capture.
Permissions
- activeTab: temporarily accesses only the page on which the user starts a capture.
- scripting: runs the packaged helper that measures, scrolls, captures, and restores the selected page.
- offscreen: stitches viewport images locally using a hidden canvas.
PageStitch does not request the clipboardWrite permission. The local result page calls the browser Clipboard API only after the user selects Copy image; Chrome or operating-system policy can still refuse the request.
User choices
PageStitch runs only after the user clicks its toolbar button. Users can choose not to copy or download a result, close the result page, disable the extension, or uninstall it through Chrome.
Remote code
PageStitch packages all executable code in the extension and does not download or execute remote code. In the Chrome Web Store Privacy practices dashboard, the publisher must declare: Remote code: No, I am not using remote code.
Changes
If PageStitch's data practices change, this policy and the Chrome Web Store privacy disclosures will be updated before the changed version is published.
Contact
Privacy and support questions can be sent through the contact and support channels displayed on PageStitch's Chrome Web Store listing.