How ImageToolkit handles information

Information we handle

Images and files

When you use an image tool, you may submit an image or other file for processing. Normal image processing is primarily handled in application memory: the server receives and validates the upload, processes it, and returns the result. Upload handles are closed after they are read.

No permanent application image archive, gallery, or application database/object storage for processed images was found in the current implementation. The Image Downloader is different and may create temporary files during a processing session; see the dedicated section below.

User-provided URLs

URL-based tools handle URLs that you provide. After validation and security checks, the backend may make requests to public destinations to retrieve or extract image content.

Technical information

The application may process the client IP address for request rate limiting and abuse protection. Application logs also contain operational, error, and rate-limit information where applicable. The inspected application code did not confirm collection of user-agent data, device fingerprints, location information, or analytics profiles.

Normal image processing

The normal lifecycle is: you upload an image, the server receives and validates it, processing happens, and the result is returned to your browser. Image bytes are handled in memory during this workflow, and no permanent application image archive was found.

Browser previews and downloads may use temporary blob: object URLs. These are client-side browser references, not permanent server storage. The application code does not establish a specific operating-system memory deletion time, and this policy does not make infrastructure-level storage or deletion claims.

Image Downloader

The Image Downloader accepts user-provided URLs, validates them, and may fetch public external content. Requests use protections for private and internal destinations, DNS/IP validation, redirect validation, and proxy bypass protection. The feature does not bypass login or private content.

Extracted files may be stored temporarily in a session directory so they can be previewed and selected. Preview access is temporary and session-controlled. Downloader sessions expire after 15 minutes, and temporary files are cleaned up after a successful download and through failure, cancellation, disconnect, timeout, periodic cleanup, and shutdown paths.

The downloader also applies limits to submitted URLs, extracted files, individual file sizes, and total session storage. Permanently retained downloaded files were not found in the application code.

IP addresses and rate limiting

The application may use your client IP address to enforce request rate limits and reduce abuse. Rate-limiting state is held in application memory, and stale entries are periodically cleaned. The repository does not establish a permanent application IP database.

This is separate from hosting or reverse-proxy logs. Their collection and retention periods cannot be determined from the application code.

Browser local storage

The website uses browser localStorage, which is different from cookies, for local preferences and statistics. The confirmed keys are:

• squeeze-theme for the selected theme.
• squeeze_images_compressed for a local compression statistic.
• squeeze_compressed_today_date and squeeze_compressed_today_count for daily local metrics.
• squeeze_reduction_sum and squeeze_reduction_samples for local reduction metrics.

According to the inspected application code, these browser-side values are not sent to the backend.

Cookies

No application-created cookies were found. This describes the current application code; hosting infrastructure, third-party services, or future integrations may have their own behavior outside that code. Full details are on the Cookie Policy page.

Analytics and advertising

The current application does not contain Google Analytics, Google Tag Manager, AdSense, advertising scripts, or an application analytics provider. No advertising cookies created by the application were found. No advertising or consent-management system is currently implemented.

Third-party services and external websites

gallery-dl

Supported Image Downloader workflows use gallery-dl as part of public-media extraction. The application may also contact external websites specified through URL features.

External websites are outside ImageToolkit's control. Their privacy practices and retention policies are governed by those services. ImageToolkit does not describe or guarantee how an external website stores or processes information.

Security

The application uses reasonable technical measures implemented within the application to reduce common security and abuse risks. These include upload limits, image and dimension validation, decompression protections, URL and DNS/IP checks, redirect validation, proxy bypass protection, temporary session expiry and cleanup, rate limiting, and security headers.

These measures are not a guarantee that any service is completely secure. No claim of zero risk or guaranteed protection is made.

Changes to this policy

This policy may be updated when application functionality, data handling, third-party services, or security and privacy practices change. The date at the top indicates the latest update shown on this page.

Contact

Questions about this policy or how the current application handles information can be sent to sahilaliyan265@gmail.com. You can also use the Contact page.