Save Image As Type
v2.0.0

Privacy Policy

Transparent, local-first image conversions. We believe your data and images are your own business—never ours.

Last Updated: July 21, 2026

1. Introduction

Welcome to Save Image As Type. We value your privacy and security above all else. This privacy policy describes how the browser extension handles your information when you convert and download images. Our core engineering principle is Local Isolation: all processes are completed locally on your machine, keeping your network footprints to an absolute minimum.

Privacy Commitment at a Glance

We do not collect, view, monitor, store, or transmit your images, URLs, browsing history, or personal identifiers. Zero data leaves your device. Everything runs inside your browser sandbox.

2. Offline Architecture

To deliver high conversion speeds and ensure complete privacy, our application runs locally without external APIs. Below is a simplified look at the localized image pipeline:

Secure Local Conversion Pipeline
1. URL Fetch

Image data fetched locally to bypass CORS limitations

2. Conversion

Client canvas API processes the image in memory

3. Download

Converted image written directly to your default directory

Because the image conversions occur inside an invisible HTML5 canvas element injected into your currently open browser tab, the original images and the final products are never uploaded to any remote server or stored persistently by the extension.

3. Data Collection

Save Image As Type adheres to strict zero-collection protocols:

  • No Personal Data: We do not ask for, collect, or store personal identifiers such as names, emails, IP addresses, or location data.
  • No Usage Metrics: The extension contains no telemetry, analytics scripts, trackers, or cookies. Your interactions remain entirely private.
  • No File Logging: We do not log filenames, file counts, sizes, format choices, or source websites.

4. Extension Permissions

To operate inside the Google Chrome environment, the extension requests certain browser permissions. We believe in absolute transparency. Click below to inspect exactly why each permission is required and how we ensure it remains safe.

Permission Checker

contextMenus
Security Verified

Allows the extension to add options directly to Chrome's right-click context menu when right-clicking on elements.

How we use it:

We use this permission to display the custom "Save Image As..." submenu (offering choices like PNG, JPEG, WebP, PDF) exclusively when you right-click on an image. It does not monitor other right-clicks.

downloads
Security Verified

Grants the ability to initiate and manage downloads using the browser's download manager.

How we use it:

Once our internal engine processes and converts your chosen image, the extension triggers Chrome's download API to write the final file directly into your local download directory. We do not access or read your existing download history.

activeTab
Security Verified

Gives the extension temporary access to the active browser tab when the user interacts with the extension.

How we use it:

This is standard practice for Chrome extension safety. It limits our scripting injections. We only gain access to script on the specific webpage where you choose to invoke our "Save Image As..." action. Other background tabs remain inaccessible.

scripting
Security Verified

Provides the ability to execute script files in the context of webpages.

How we use it:

We inject the image converter script (`imageConverter.js`) onto the active page. This script performs the technical tasks of drawing the target image to a hidden canvas, converting it to your requested configuration, and returning it. No scripts are executed persistently.

host_permissions (<all_urls>)
Security Verified

Permits the extension to request and manipulate pages matching the specified url pattern list.

How we use it:

To fetch images from websites that use strict CORS (Cross-Origin Resource Sharing) policies, our background worker must fetch the raw data stream from the image URL. The host permission allows our worker to safely fetch this data without blocks, keeping the process fast and private.

5. Third-Party Libraries

Our codebase is optimized to prevent reliance on bloated external resources. We incorporate only one open-source package:

jsPDF (v2.5.1)

We use a minified copy of the official, widely trusted jsPDF library stored locally inside our extension codebase at `lib/jspdf.min.js`. This script runs completely offline to bundle converted images into PDF formats. It does not contact any external domains, nor does it log usage.

6. Regulatory Compliance

Even though we collect zero user information, we actively support modern regulatory compliance standards:

Under the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA), individuals have rights regarding their personal data. Because we do not collect, capture, store, or transmit any of your personal data, our extension complies with these standards naturally. No personal logs exist that we could disclose, modify, or delete.
The Children's Online Privacy Protection Act (COPPA) protects the privacy of children under 13. Since Save Image As Type does not collect any data from any users, it poses no tracking risks to children and is completely compliant with COPPA requirements.
We strictly comply with the Chrome Web Store Developer Program Policies, including the User Data Policy's Limited Use requirements. All requested permissions are restricted to the absolute narrowest scope required to perform the offline conversions.

7. Support & Contact

If you have any questions, concerns, or suggestions regarding this privacy policy, the permissions requested, or the inner workings of the extension, please feel free to reach out:

  • Support Repository: Open an issue on our official repository.
  • Contact Email: developer@example.com (Please replace with your actual support email upon deployment)

We typically review and reply to inquiries within 48 business hours.