Privacy Policy

When you submit an image, the application reads the upload for the selected workflow. The current Favicon and App Icon workflows do not save a separate copy of the original file in the application's uploads directory. The web request layer may use operating-system temporary buffering while receiving the file; that buffer is managed by the request framework rather than kept as a workflow asset.

Generated image files are written temporarily while the package is built. The individual files are deleted after they are added to the ZIP, and the local ZIP is queued for deletion after the download response finishes. A scheduled cleanup also removes output files older than about 2 hours if the normal post-response deletion did not complete.

When optional diagnostic object storage is enabled, the generated ZIP may be copied to an operator-controlled quality archive before the local ZIP is deleted. That archive does not affect the user download. Its retention is controlled outside this application; the application's local cleanup task does not delete object-storage copies.

The service records technical processing metrics such as a random task ID, workflow name, input format and dimensions, byte counts, processing time and status. These metrics do not contain the original filename or image bytes. The application does not currently define an automatic expiration period for the metrics database.

No account is required to use the current workflows. Do not upload an image unless you have the right to process it and are comfortable with the data handling described above.