Privacy Policy

Last updated: March 2025

TL;DR — The Short Version

  • Your images are processed entirely in your browser. They never leave your device.
  • We do not upload, store, or have access to any files you process with PixelZip.
  • We may use analytics (Google Analytics) to improve the product — this can be opted out.
  • We do not sell your data. Period.

1. Introduction

PixelZip ("we", "our", or "the Service") is committed to protecting your privacy. This Privacy Policy explains how we handle information when you use our image compression tools at pixelzip.app.

PixelZip is a browser-based image optimization tool. Our core principle is privacy by design: all image processing is performed locally in your browser using WebAssembly, and no image data ever leaves your device.

2. Image Processing — No File Uploads

PixelZip never uploads your images to any server.

When you use the Compress Image tool (or any other image tool on PixelZip), your files are processed entirely within your web browser using WebAssembly — a low-level binary instruction format that runs at near-native speed without requiring a server connection.

This means:

  • Your images are never transmitted over the network.
  • We have no access to the content of your images.
  • No image data is stored on our servers (because we receive none).
  • PixelZip can function entirely offline once the page has loaded.

3. Information We May Collect

3a. Analytics Data (Optional)

We may use Google Analytics to understand how visitors use PixelZip (e.g. which tools are most popular, how long sessions last, geographic distribution of users). This data is anonymised and aggregated — it does not identify you personally.

Analytics are currently not yet active. When activated, we will update this policy and add a cookie consent banner.

3b. Log Data

Like most websites, our hosting provider (Cloudflare Pages) may automatically collect standard log data such as your IP address, browser type, and the pages you request. This data is used solely for security and operational purposes and is not linked to your image processing activity.

3c. No Image Storage

We collect zero bytes of image data. We have no capability to access your images — by architectural design, not merely policy.

4. Cookies

PixelZip currently uses no cookies.

When Google Analytics is activated in a future release, it will use cookies to distinguish users. At that point, we will implement a GDPR-compliant cookie consent mechanism.

5. Third-Party Services

PixelZip is hosted on Cloudflare Pages. Cloudflare may collect standard traffic data as per their own privacy policy.

Future integrations (Google Analytics, Google Search Console, Google AdSense) are currently disabled. This policy will be updated before any third-party scripts are activated.

6. Data Retention

Since we do not collect image data, there is nothing to retain or delete regarding your files.

Any server log data collected by our hosting provider is subject to their retention policies (typically 30 days).

7. Your Rights (GDPR / CCPA)

If you are a resident of the European Economic Area (EEA) or California, you have the following rights regarding personal data:

  • Right to access the personal data we hold about you.
  • Right to rectification of inaccurate data.
  • Right to erasure ("right to be forgotten").
  • Right to restriction of processing.
  • Right to data portability.
  • Right to object to processing.

Since we hold no image data about you, exercising most of these rights has no practical effect on image processing. For any other data concerns, contact us at the address below.

8. Children's Privacy

PixelZip is not directed at children under 13. We do not knowingly collect personal information from children.

9. Changes to This Policy

We may update this Privacy Policy occasionally. When we make material changes, we will update the "Last Updated" date at the top of this page. Continued use of PixelZip after changes constitutes acceptance of the updated policy.

10. Contact

For privacy questions or requests, please open an issue on our public repository or reach out via the contact method listed on our About page.