Trust and transparency

How your images and account are handled

The editing workspaces use browser APIs so selected image data can be processed on your device. The website also handles account, support and payment information where those features are used.

Image processing

The core tools read files selected in your browser and create a local download. There is no server upload endpoint for the image workspaces. Some specialized formats use third-party JavaScript libraries loaded from a CDN, so review your browser extensions and network settings if you handle sensitive material.

Browser and file limits

Processing speed and size limits depend on device memory and the individual tool. Canvas output can change color profiles, remove metadata, flatten animation and re-encode pixels. Keep a copy of your source, then inspect the actual downloaded file before sharing it.

Accounts and sessions

Laravel stores account details and protected sessions in the application database. Passwords are hashed. Forms use CSRF protection, authentication routes have rate limits and administrator pages require a verified admin account. Google sign-in appears only after its OAuth credentials are configured.

Optional payments

Checkout is disabled until the site owner configures the payment gateway. A payment order is created on the server, and access is granted only after signature and gateway status checks. The site stores an order and receipt reference, not payment card numbers. Do not send card details via the contact form.

What you can do

  1. Use the exact tool page for your source format and check its limitations.
  2. Back up originals and use a separate metadata viewer if privacy is critical.
  3. Crop or cover sensitive visual information; blur and pixelation are not reliable redaction.
  4. Use HTTPS, keep your browser updated and review extensions with access to pages.

Read our Privacy Policy for details about account and contact data, cookies and retention. Contact us about a security concern.