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.
• Under the current setup, both Umami and Cloudflare Web Analytics retain analytics data for 6 months.

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 this test to verify local-only processing:

1. Disconnect network (airplane mode or Wi-Fi off).
2. Select an image, then convert and download successfully.

Scope and boundaries

• First page load needs network to fetch static assets and WebAssembly codecs.
• After assets are cached, conversion workflows can continue offline.
• 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