Privacy Policy — Page to PDF

This Privacy Policy describes how the Chrome extension "Page to PDF" ("the Extension", "we") handles data. The Extension is available on the Chrome Web Store. It runs entirely on the user's machine and has no server-side component.

1. Our principles

We designed this policy — and the Extension itself — around three rules:

• Privacy policies should be human-readable. No legal cosplay, no template boilerplate describing things we don't do.
• The simplest data practice is no data practice. The less we collect, store, or transmit, the less can leak, get subpoenaed, or be misused. So we collect nothing.
• Match the reasonable expectation of the user. You installed an extension that turns a webpage into a PDF. It does exactly that and nothing else.

2. What data we process

2.1 Stored locally on your device

• User preferences — stored in chrome.storage.sync, which means Chrome synchronizes them across other browsers signed into the same Google account. The synced preferences include:
  • Theme (light or dark)
  • Default export mode and paper size
  • Whether to pre-scroll for lazy loading
  • Whether to reload the page after export
  • Whether to add date/time to the filename
  • Other UI toggles described in the Settings page
• PDF cache — stored in IndexedDB on your device so the built-in viewer can reopen recent exports without re-rendering the page. Cache entries stay on your machine and are cleared when you uninstall the Extension or clear browser storage.

We do not store your browsing history, page content, URLs you visit, or any personal identifiers.

2.2 Data sent to our servers

None. The Extension does not have a backend. The PDF is generated using Chrome's native rendering APIs inside your own browser. No URL, no HTML, no page content, no metadata about the pages you save is transmitted to us or to any third party.

2.3 Third parties

The Extension does not include any third-party analytics, tracking SDKs, advertising networks, or telemetry services. There are no requests to external servers triggered by normal use.

2.4 Welcome and support pages

The Extension may open a welcome page on first install and a support page if you click "Help" from the popup. These are static pages on pagetopdf.app. Our web server logs the visit (IP address, user-agent, timestamp) in standard web-server logs, retained for operational diagnostics only. These visits are caused by you opening the page in your browser, not by the Extension reporting on your activity.

3. What we do NOT collect

• Names, email addresses, phone numbers, postal addresses
• Account credentials, passwords, authentication tokens
• Payment or financial information
• Health or biometric data
• The URL, HTML, or content of any page you save as a PDF
• Your browsing history
• Keystrokes, mouse movements, or screen recordings
• Usage analytics or telemetry
• Data from children under 13

4. Permissions we request and why

• activeTab — to access the current tab when you click the Extension icon, so the page can be rendered to PDF
• scripting — to inject the page-preparation script (pre-scroll, hide fixed elements, run the element picker, run the article reader) into the active tab
• storage — to save your preferences locally and cache recent PDFs in IndexedDB
• downloads — to save the resulting PDF file to your downloads folder
• tabs — to open the built-in viewer in a new tab
• debugger (only when you trigger an export) — to call Chrome DevTools Protocol's Page.printToPDF, which is what produces the actual vector PDF. Permission is requested per-tab, used for the duration of the export, and released immediately afterwards

All permissions are used only for the purposes described above and only when you actively trigger an export.

5. Data retention

• Local preferences — stay on your device until you uninstall the Extension or clear Chrome's extension storage
• Local PDF cache — stays on your device until you clear it from the viewer's history, uninstall the Extension, or clear browser storage
• Web-server logs for the welcome/support pages — rotated automatically according to standard log-retention policy (typically a few weeks)

6. Data sharing and selling

We do not sell, rent, or trade any data. We do not share data with advertisers or anyone else. There is no data to share — the Extension does not collect any.

7. Your rights

Because we do not collect personal data, there is nothing tied to "you" that we could look up, export, or delete on our side. You can:

• Delete your local data by uninstalling the Extension or clearing extension storage in Chrome's settings
• Clear cached PDFs from the built-in viewer's history at any time
• Contact us at pagetopdf@gmail.com with any questions or concerns

If you are located in the EEA, UK, or California, you have rights under GDPR / UK GDPR / CCPA including access, rectification, erasure, and objection. Contact us at the email above to exercise these rights.

8. International data transfers

The web-server hosting pagetopdf.app (and its welcome/support pages) is a VPS in the European Union. The Extension itself does not transfer any data internationally because it does not transmit any data at all.

9. Security

Web traffic to pagetopdf.app is protected by HTTPS/TLS. The Extension does not handle any user secrets, tokens, or credentials, and does not store anything sensitive in extension storage.

10. Children

The Extension is not directed at children under 13. We do not knowingly collect data from children. If you believe a child has used the Extension, contact us and we will take appropriate action.

11. Changes to this policy

If we change this policy, we will update the "Last updated" date at the top. Material changes will be communicated via the Chrome Web Store listing and/or our website.

12. Contact

Questions, requests, or privacy concerns:
pagetopdf@gmail.com