Step 01
Load the app shell
HTML, JavaScript, CSS, and other interface assets are fetched so the site can run.
Security
Security follows the same rule as privacy: the image work should stay in the browser.
This page explains the technical boundary around Image Tools. The product still needs network access to load its interface, but the image processing workflow is designed so the selected files stay on the device rather than moving through a remote image service.
HTTPSBrowser APIsNo server processingLocal export
FLOW
Security model
Step 02
Process the image locally
Selected files stay in browser memory and are handled through local browser APIs.
Step 03
Export back to the device
The output is generated locally and downloaded or saved through the browser.
Pillars
The model is intentionally simple.
Last updated March 30, 2026.
Browser-only execution
Image processing is designed to run locally with browser APIs rather than on a server-side image pipeline.
A narrow network boundary
The app still downloads code and static assets so the interface can load, but it is not built to transmit the selected image file itself.
Practical safety still matters
Keeping files local is a strong default, but users should still use HTTPS, updated browsers, and sensible handling for sensitive content.
SAFE
Best practices
Local-first is strong, but safe handling still depends on the environment around the browser.
01
Access the product over HTTPS and keep the browser up to date.
02
If a file is particularly sensitive, consider loading the page and then working offline for the edit session.
03
Treat exported files with the same care as the originals because the tool does not manage post-export sharing or storage.
LINK
Related pages
Security explains the architecture, not the full policy set.
Read privacy for data handling, and read terms for the usage boundaries and liability language around the service.