How PicShift Handles Privacy and Local Processing

What happens to your files

• Selected images are read by your browser and processed in local browser memory.
• Converted files are generated locally and returned to you as downloadable files.
• PicShift does not require registration or sign-in to use the tools.

What does not leave your device

• Original image content is not uploaded to PicShift servers for processing.
• Converted image files are not uploaded or stored on PicShift servers.
• No cloud storage account is required to use PicShift.

Local settings and analytics

• Small interface preferences such as theme, language, and default quality may be stored in browser localStorage.
• PicShift also sees ordinary website traffic records such as page URL, referrer, approximate country, browser type, and whether a button or internal link was clicked.
• Analytics reporting availability and retention follow each provider’s current policy and the active PicShift account configuration; PicShift does not publish a fixed deletion period here.

Security and trust model

PicShift keeps the privacy model simple on purpose: image processing stays on the device, no account is needed, and analytics stay at the ordinary website-traffic level. If you want the full policy language, see the Privacy Policy.

How to verify this yourself

Use a non-sensitive test image and keep browser DevTools Network open:

1. While online, open the exact tool and complete one conversion and download. This loads that route, workflow code, and codec.
2. In DevTools Network, enable Preserve log, clear the request list, and repeat the conversion. Ordinary page or analytics requests may appear; the source image should not be sent as a request payload.
3. Set Network to Offline (or disable Wi-Fi), reload the same tool page, and repeat the same input-to-output workflow.
4. If a new format or workflow fails offline, reconnect, complete that exact workflow once online, and then repeat the offline test.

Scope and boundaries

• An offline result applies only to the browser profile, device, route, workflow resources, and codec that were successfully loaded and cached.
• Passing this test shows that the observed workflow did not require an image upload; it is not a third-party security audit and does not cover browser extensions or other software.
• Batch conversion supports up to 200 files per run for stable performance.

Technical evidence references

• Privacy policy for legal terms and commitments. /privacy
• Format compatibility guide for supported input/output formats. /docs/format-compatibility
• Quality guide for practical compression and quality behavior. /docs/image-quality-vs-file-size

FAQ

Further reading

• What is EXIF data and why you should remove it — what's actually inside your photos and the privacy risk it carries.
• Does Instagram, WhatsApp, or Discord remove EXIF data? — platform-by-platform behaviour, and why stripping locally before sharing is safer.