Scope and controller
This policy applies to the PageUnfold Chrome extension, the PageUnfold website, and account or quota services used by the extension. For privacy questions, access requests or deletion requests, contact [email protected].
Information processed on your device
- Selected webpage content. When you start a conversion, PageUnfold reads the selected page’s DOM, text, styles, links, images, fonts and layout information to reproduce it as a PDF.
- Local conversion history. Generated PDF files and related metadata—including page title, source URL, host, output mode, file size, page count, filename and creation time—are stored in the extension’s local IndexedDB history.
- Settings and templates. Conversion settings are stored with Chrome extension storage and may sync through your Chrome profile according to your Chrome settings. Custom template images remain in extension-local storage.
- Authentication state. Access tokens and a basic account cache are stored in extension-local storage so the extension can recognize the signed-in account.
Processing data locally still counts as handling user data. PageUnfold limits that processing to the webpage-to-PDF features you request.
Information sent to PageUnfold services
Account, entitlement, quota, security and diagnostic requests are sent over HTTPS to the PageUnfold SDK/API service at ext.pageunfold.com and may include:
- basic Google account information returned through sign-in, such as a user identifier, email address and display information;
- authentication tokens, account or subscription identifiers, and download quota requests;
- an anonymous installation identifier, acquisition source and browser/device fingerprint used for abuse prevention and request integrity;
- extension ID, extension and SDK versions, language, event names and limited diagnostic properties;
- standard server logs, including IP address, user agent, request time and response status.
When you click Download, PageUnfold sends a quota-consumption request before Chrome saves the locally generated file. The PDF itself is not included in that quota request.
Webpage access
PageUnfold requests access to HTTP and HTTPS webpages because users may convert a page on any domain, including lazy-loaded or authenticated content already visible in the selected tab. This access is used to read and render the page, operate the element or area picker, and retrieve page resources needed for the PDF. PageUnfold does not read passwords or use webpage access to build advertising profiles. Restricted pages such as chrome:// pages cannot be captured.
Optional document uploads
The current public workflow performs core conversion locally. Server-side PDF compression and email delivery are not exposed as available features in this release. If a future version offers either feature, PageUnfold will clearly disclose the upload before it happens, require an explicit user action, state the processing and retention terms, and update this policy before release.
How information is used
PageUnfold uses information only to:
- provide webpage conversion, preview, local history and download features;
- authenticate accounts and provide remotely configured plans and quotas;
- prevent fraud, abuse and duplicate quota consumption;
- maintain security, reliability and compatibility;
- measure aggregated product performance directly related to PageUnfold’s disclosed functionality;
- respond to support, privacy and legal requests.
Sharing and service providers
PageUnfold does not sell personal data. Information may be processed by service providers only when necessary to operate the extension, including Google for OAuth sign-in, hosting and infrastructure providers for PageUnfold APIs, and the payment provider displayed at checkout. PageUnfold does not store complete payment-card details in the extension.
Information may also be disclosed when required by law, to protect users or the service from security threats, or as part of a merger, acquisition or asset transfer subject to applicable protections. We do not transfer user data for personalized, retargeted or interest-based advertising.
Chrome Web Store Limited Use disclosure
PageUnfold’s use and transfer of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
- Chrome API data is used only to provide or improve PageUnfold’s single purpose and user-facing webpage-to-PDF features.
- Chrome API data is transferred only when necessary to provide or improve those features, for security, to comply with law, or as part of a qualifying business transfer.
- Chrome API data is not used or transferred for personalized advertising, creditworthiness, lending or unrelated profiling.
- Humans do not read private webpage content unless the user gives specific consent for support, access is required for security or legal reasons, or the data has been aggregated and anonymized for permitted internal operations.
Security
PageUnfold uses HTTPS for data sent to its services. Authentication tokens are stored in Chrome extension-local storage and are not intentionally exposed to webpages. The extension packages its executable code locally and does not execute remotely hosted code. No security measure is absolute, but access is limited to the data and systems needed to operate the service.
Retention
- Local PDF history follows the retention period selected in PageUnfold settings and can be deleted at any time.
- Settings remain until you reset them, disable the relevant Chrome sync behavior, or uninstall the extension.
- Local authentication data remains until logout, local deletion or uninstall.
- Account, entitlement and quota records are retained while needed to provide the account and to resolve security, billing or legal obligations.
- Raw operational and SDK diagnostic events currently do not all have an automatic deletion schedule. They are retained only for operation, reliability, security and aggregate measurement, and may be included in a verified deletion request where legally and technically applicable.
- Transaction records may be retained for the period required by tax, accounting, fraud-prevention or other applicable law.
Your controls and deletion requests
- Delete individual PDFs or reset local history from PageUnfold.
- Reset extension settings and remove locally stored template assets.
- Sign out to remove the active extension session.
- Uninstall PageUnfold to remove extension-local data from Chrome. Data synchronized by Chrome is also subject to your Chrome account settings.
- Request access to or deletion of server-side account data by emailing [email protected] from the account email. We may verify the request and retain limited records where required for security, billing or law.
Changes to this policy
Material changes will be dated on this page. If a change introduces a new collection or upload that requires consent, PageUnfold will provide an in-product disclosure before that processing begins.
Contact
Email [email protected] for privacy questions, account deletion, data access or support. Please do not email passwords, authentication tokens or private document contents.