Privacy Policy

Last updated:2026-10-23

The short version

Your images never leave your device. We don’t have a server to receive them, so we have no way to see them.

How your images are actually processed

This site is a set of image-processing tools that run entirely in your browser. When you upload a photo to compress it, add a watermark, resize it, crop it, or convert its format, all of that happens on your own computer or phone, using your browser’s own image-processing capabilities.

We didn’t skip the “upload to a server” step because we chose not to look — the code simply doesn’t have that capability. You can open your browser’s developer tools, switch to the Network tab, and confirm this yourself: while an image is being processed, nothing gets sent out.

That also means we don’t know what images you’ve processed or what’s in them, and we do not store their contents on our servers.

What we collect

We collect almost no personal data. It breaks down into two things:

1. Page-view analytics

To understand which tool pages people actually use and which content is useful, we count visits and a handful of anonymous feature-usage signals ourselves (like “how many times the watermark feature was used this month” — not “who used it”). We don’t use any third-party analytics service. Instead, the page sends a tiny request to this site’s own server carrying only: which page you’re on, what happened (page opened / file picker opened or cancelled / images imported / processing started or ended, including cancellation or error / result exported), a rough count range of imported images (e.g. “2-5”), whether the imported files opened successfully (count ranges only; for a file that fails to open, just its extension such as “pdf” and a rough reason such as “password-protected”, never the file name), whether you’re on a phone or a computer, and which site you came from (the domain only, never the full link).

To diagnose PDF to Images failures, we also record fixed processing-stage and reason codes, known exception types, coarse ranges for page position, page count, file size and canvas pixels, and the selected output format and DPI. These diagnostics do not include raw error messages, stacks, filenames, document contents or passwords.

Like almost every website, our server keeps standard access logs, which include IP addresses and browser type. Our reports are aggregate numbers computed from those logs; we don’t analyze individual visitors. Beyond that:

• No cookies, and nothing stored in your browser to identify you
• No tracking of your activity on other websites
• No profile of you as an individual
• Never the content or filenames of the images you process — the images themselves never leave your device

2. Data you save locally

If you use the “save watermark template” feature, your watermark settings (text, logo, position) are stored in your own browser’s local storage. They’re never synced to us, because we don’t have a server to sync them to.

When browser storage is available, PDF to Images keeps tasks for that tool locally: the source PDFs, page selection, export settings, generated images and progress. This supports automatic download parts and recovery after an interruption. These files stay in the current browser on this site and are never uploaded. Recovery is available for 24 hours after the last checkpoint; expired records are removed when you next open the tool. You can delete them immediately with “Clear this tool’s local tasks and results”. If storage is full, denied or cleared, recovery may be unavailable; the tool tells you to download the current results before continuing.

If you clear your browser data, those templates disappear with it. We recommend using the “export template” feature to keep a backup file of your own.

What we don’t do

• No ads, no third-party ad networks
• No cookies used for tracking
• We don’t sell or share your information with anyone (we don’t have anything to share in the first place)
• No account or email required to use any tool
• Every feature is free — there’s no payment involved, so there’s naturally no payment information of yours for us to handle

A technical note on local storage

Your browser’s local storage (used to save watermark templates) isn’t technically a cookie, but some privacy regulations covering “storing or reading information on a device” apply more broadly than cookies do. We consider this storage “strictly necessary” for a feature you explicitly asked for, and don’t think it needs a separate consent prompt — but if you’re in a jurisdiction with stricter requirements, let us know via the contact details below.

Changes to this policy

If this policy changes in any meaningful way, we’ll update the date at the top of this page. Continuing to use the site after that means you accept the updated version.

Contact us

Questions about this policy? Reach us at yiketob@gmail.com.

This page is written in plain language for clarity, and while we’ve tried to keep it accurate, it isn’t formal legal drafting. If your jurisdiction has specific requirements for privacy disclosures, please consult professional legal advice.