Privacy Policy

1. Scope and operator

This policy applies to PixelSaaz’s converter, compression, resizing and informational pages. It describes the current website, not unrelated services reached through external links. Contact details for support and privacy requests appear below and on our Contact page.

2. 100% in-browser image processing; zero image uploads

Image decoding, conversion, compression, resizing, previews and ZIP creation execute client-side in your browser. Our converter does not upload image bytes, filenames, previews or converted output to an image-processing server. HEIC and AVIF processing libraries and WebAssembly codecs run on your device; codec downloads fetch program files, not your photos. Selecting an image gives this page access to that selected file, not the rest of your device.

The queue uses temporary browser memory and local object URLs. Removing files, clearing the queue or closing the page releases application references; browser memory management controls final reclamation. We do not keep a server-side photo archive or offer recovery after the session. Downloads remain on your device under your browser’s download settings. Keep original masters yourself.

3. Local storage and essential preferences

The appearance picker saves your white or black appearance choice in localStorage so it can persist on the same browser and origin. It stores a theme value, not image data. Other tabs on the same origin may receive a storage-change notification. You can remove this preference through your browser’s site-data settings; doing so resets the saved appearance. The current converter does not use an account, persistent image history or image-tracking cookies.

4. Website delivery and technical requests

Zero image uploads does not mean zero network requests. Loading pages, fonts, JavaScript and codecs contacts the website host. Hosting or security providers may process IP addresses, requested URLs, browser information and request timestamps to deliver resources, diagnose failures and prevent abuse. These infrastructure records are separate from image contents. Their retention and availability depend on the chosen deployment provider; we do not claim that local photo processing eliminates hosting logs. Do not place private filenames or personal information in page URLs.

5. Google AdSense and advertising disclosures

The current application does not load Google AdSense ad scripts or serve live Google ads. Reserved placement previews are layout demonstrations only. If advertising is enabled, this policy and the site’s consent controls must be updated to reflect the actual providers and settings before ad requests begin.

When Google ads are served, third-party vendors, including Google, may use cookies and other identifiers to serve ads based on previous visits to this website or other websites. Google advertising cookies can enable Google and its partners to personalize ads. Ad serving may involve IP addresses, page URLs, device information, cookies or web beacons. These advertising interactions do not authorize the converter to upload your images. See how Google uses information from partner sites and Google’s advertising choices. Other active ad networks and their choices must be disclosed if introduced.

6. Google Analytics and measurement

Google Analytics is not installed or loaded by the current application. If introduced, it may use cookies or identifiers to measure visits, page interactions and device or browser characteristics according to the deployed configuration. We would disclose that configuration and provide consent or opt-out controls where required. Image contents, filenames and private user inputs must not be sent as analytics events. Google provides an Analytics browser opt-out add-on and explains its practices in the Google Privacy Policy.

7. Consent, choices and external links

Before personalized advertising is served in the EEA, UK or Switzerland, an appropriate Google-certified consent platform must be configured. Other regional consent or opt-out requirements depend on deployment and visitors. A written policy or an ad placeholder is not a consent implementation. Browser controls can clear local site data and restrict cookies, although some third-party functions may then be unavailable. External documentation, partner or support links have their own privacy practices.

8. Support messages, rights and changes

If you contact us, the details you choose to send, including your email address and message, are processed through the email providers involved to answer the inquiry. Do not send private photographs, passwords or confidential documents. Use a non-sensitive sample only when necessary. Ask through the contact channel about access, correction or deletion of correspondence or other rights available where you live. We cannot retrieve or delete image files that were never uploaded to us, or erase downloads from your device.

We do not ask children to submit personal information, and the converter does not require registration. If you believe a child has sent personal information through support, contact us. Material changes to processing or third-party integrations will be reflected here with an updated date. Review this policy when you return.