Privacy
Privacy Policy
Last updated: September 2026
Short version
Page to Image captures and edits webpages entirely on your device. Your screenshots, page contents, annotations, and exported files are not uploaded, stored remotely, sold, or shared.
Captures are processed locally
All capture and review work, including scrolling, stitching image segments, cropping, annotating, and encoding PNG, JPEG, or PDF files, happens inside your browser using your device’s resources. The extension has no backend servers for capture data.
Billing and licence requests
Page contents and captured images are not sent to Page to Image servers. To provide the free allowance and paid-access features, the extension creates a pseudonymous Installation ID and credential, stores them in the browser, and sends them to the Page to Image entitlement service for installation registration and access checks. Offer requests use the browser language and coarse country information available with the request to format prices. When you start checkout, the extension creates and checks a purchase claim; when you choose Manage billing, it requests a billing-management link. If you use a support-issued access transfer, the extension sends its one-time token to the service only after you select Activate. The API stores the Installation ID, a hash of its credential, and purchase, entitlement, and transfer records needed to provide those features. It does not receive the page URL, title, filename, screenshot, image bytes, annotations, or capture history.
The API is hosted on Cloudflare, which provides its network and hosting layer. It receives network request information; the Page to Image service uses the request IP for registration and transfer rate limiting. This is separate from page content, which the extension does not send.
Paddle, our payment provider and merchant of record, processes checkout and billing information. Page to Image stores payment-provider customer, transaction, subscription, product, and price references needed to verify access, but does not store customer email addresses in its entitlement database.
How extension data is used
Page content and captures are used only to provide the capture, review, copy, and export features that you request, and remain on your device. Installation and access data is used only to provide the free allowance and paid-access features and to protect those services. Page to Image does not sell extension data or use it for advertising. Paddle processes checkout and billing information as described above. Support, security, or legal work does not provide access to local page content or capture images because those are not sent to Page to Image servers. Authorized personnel may access installation, entitlement, or support records only when needed to provide requested support, protect the service, or meet legal obligations.
Preferences are stored locally
Your capture preferences, free allowance, pseudonymous Installation ID and credential, cached offers, pending purchase reference, and signed access record are saved on your device. Capture artifacts and editing state are also kept in local browser storage while you work. Clearing extension storage or reinstalling resets local free state; paid-access recovery is support-assisted.
No tracking
The extension contains no analytics, customer accounts, or advertising. It does not collect browsing history or capture content.
Website analytics
This website uses PostHog, hosted in the EU, to measure page visits and interactions such as Chrome Web Store link clicks and FAQ opens, diagnose errors, and review session recordings. PostHog may store analytics identifiers in your browser and receive technical information such as the page URL, browser and device details, approximate location, and interaction events. Website analytics never receive page contents or images captured by the extension.
Contact
Page to Image is operated under the Page to Image brand. Questions about this policy? Reach us at support@pagetoimage.app.