Privacy Policy

1. Operator and contact

PixelConvert is operated by Prashantkumar Kishanrao Sundge. Contact support@pixelconvert.net for privacy questions or requests.

2. Client-side image preflight

The Upload-Ready Image Builder initially inspects the file in your browser. It reads the file signature, byte size, available dimensions and aspect ratio, transparency where the browser can decode it, and recognizable metadata categories such as EXIF, GPS, orientation, ICC, or XMP. This local inspection does not send the file to PixelConvert. The file is sent only when you choose conversion or preparation.

3. Conversion, preparation, and ZIP files

The backend reads uploaded images into memory, validates and decodes them, builds output in an in-memory buffer, and streams it back. Batch ZIP archives are also created in memory. PixelConvert does not provide accounts or a permanent user-file store and does not intentionally retain image contents after the request completes.

Upload-Ready outputs apply recorded EXIF orientation before resizing or cropping and are re-encoded without copying EXIF/GPS metadata. This does not remove sensitive information visible inside the image itself, and metadata removal is not a forensic anonymity guarantee.

4. Technical logs and security

Hosting, reverse-proxy, rate-limiting, and security systems may process IP address, user agent, request time, route, response status, and error details. These records support security, abuse prevention, and reliability. Do not put sensitive file names or personal information into support messages unnecessarily.

5. Analytics, consent, and advertising

PixelConvert uses Google Analytics 4 with Google Consent Mode v2 Advanced. The Google tag loads on public pages. Outside the EEA, United Kingdom, and Switzerland, analytics storage defaults to granted. In those regulated regions, analytics storage and all advertising-related consent states default to denied while Google’s certified consent message collects the visitor’s choice.

When analytics consent is denied, Google describes the Advanced Consent Mode behavior as sending consent status and cookieless measurement pings without writing Analytics cookies. Full Analytics storage is enabled only when the applicable consent signal permits it. Advertising storage, advertising user data, advertising personalization, Google Signals, and Analytics ad-personalization signals remain disabled by PixelConvert during the current recovery period.

PixelConvert sends only high-level events such as a tool page view, file selection count, conversion start or completion, and ZIP download count. Image contents, file names, user-entered colors, and file-level metadata values are not included in those events.

PixelConvert retains the Google AdSense verification script and Google-certified consent message, but ad units and Auto Ads remain disabled during the current quality review period. If advertising is enabled later, Google and its partners may use cookies or similar technologies according to the choices presented by the consent platform. Applicable visitors can revisit privacy choices through Google’s message and manage advertising preferences at Google My Ad Center.

6. Changes

This policy is updated when the product, providers, or applicable requirements change. The revision date above identifies the current version.