imvoriAn online editor can do its work in different places. Most Imvori adjustments run in a browser worker on your device, while a smaller set of operations uses the site’s server CPU. The privacy consequences depend on the tool you choose. This guide explains the current workflow; the Privacy Policy gives the broader description of data handling and contact requests.
Open Remove metadataLocal tools work on your device
Compression, color and lighting adjustments, local filters, masking, document cleanup, product templates, screenshot merging and PDF conversions are browser operations. Choosing a local file makes it available to the editor on your device; these operations do not send the image or PDF bytes to our image-processing API. Tool code, PDF libraries and related static assets may still be downloaded from the site. A network request for a library is different from uploading your photograph.
Server tools upload the selected version
Background removal, old-photo repair, colorization, face restoration, the original Enhance operation, resize, grayscale, upscaling and selected watermark-region removal use the server pipeline. The current selected studio image is uploaded for that operation, not necessarily the first file you opened. The server stores the upload, a job record and its result so the browser can poll progress and download the output. Models run on the server CPU; their weights are not downloaded to the visitor’s device.
The session is not a permanent gallery
The version strip lets you choose which image the next operation should use. Undo follows the parent of the selected edit, and you can branch by choosing an older version. Local files and object URLs are temporary browser-session data. Reloading or closing the page discards this history. There is no public gallery where Imvori deliberately lists your uploaded pictures, but a server-generated result URL should still be treated as a private link. Anyone who has that URL may be able to fetch the file while it exists.
Understand server retention
Server images and completed or failed job records become eligible for cleanup after 24 hours from upload. The cleanup task runs periodically, so deletion is not a guarantee at the exact second the 24-hour period ends. Pending and processing jobs are excluded while active. Download before expiry and do not use a temporary result URL as a permanent image-hosting address. Ordinary web-server logs and messages sent through Contact are separate data categories described in the Privacy Policy.
Decide what to share
Use only images you are entitled to process and avoid sending material that does not need to leave your device. If local edits are sufficient, stay with those tools. Before selecting a server operation, review its description and the upload notice. Remove metadata changes embedded data, while visible personal information needs an image edit such as a solid redaction. For a privacy question, use the contact form and describe the request without unnecessarily including another sensitive image.
Need help with this workflow? Report a problem without sending the private image itself.
Try the tool Explore all tools