SnapPDF Privacy Policy

Last updated: 2026-08-23

SnapPDF turns the current page into a PDF when you click its toolbar icon. This page explains, in plain language, what that involves.

What SnapPDF reads

Only the page you're looking at, and only at the moment you click the icon. SnapPDF has no background scanning, no content script running on every page you visit — it injects its capture code into a tab exactly once, right when you click, renders that page to an image, and is done. It also fetches the byte data of images already present on that same page (so they render correctly in the PDF instead of blank) — those requests go straight from your browser to the image's own server, not through anything SnapPDF operates.

What SnapPDF never does

• No browsing history access, no reading of tabs you haven't clicked the icon on.
• No analytics, no tracking, no sending page content or captured images to any server SnapPDF operates — there isn't one. The PDF is built entirely inside your browser and saved straight to your Downloads folder.
• No account or sign-up required to use the free tier.

Where your data lives

Two small things are stored locally in your browser via Chrome's storage API, never transmitted anywhere on their own:

• How many PDFs you've saved this calendar month, used only to enforce the free-tier limit and show it on the toolbar badge.
• Your Pro status and license key, if you've activated one.

Uninstalling SnapPDF removes this data along with everything else Chrome stores for the extension.

SnapPDF Pro & license validation

Purchases are handled entirely by Dodo Payments, a third-party payment processor — SnapPDF never sees or stores your card details. When you activate a license key, SnapPDF sends that key directly to Dodo's own license-validation server to confirm it's real; SnapPDF has no payment or license backend of its own that sees or stores it. Dodo's handling of your payment information is covered by Dodo's own privacy policy, not this one.

Permissions this extension requests, and why

• downloads — to save the finished PDF to your Downloads folder.
• activeTab / scripting — to render the current page into an image, only when you click the icon.
• offscreen — to assemble the PDF; this runs entirely inside your own browser.
• notifications — to tell you when a save succeeded or failed.
• storage — for the two local-only items described above.
• Optional host permission (all sites) — requested only the first time you click the icon, needed so cross-origin images on the page you're capturing render correctly instead of blank. You can revoke it any time from chrome://extensions.

Changes to this policy

If this policy changes, the "last updated" date above will change with it.

Contact

Questions about this policy: fieldworklabs.support@gmail.com