ResizeNestImage Editor
Resize ImagesCompress ImagesCrop ImagesImage Editor

Convert

Convert ImagesJPG to PNGPNG to JPGJPG to WebPWebP to JPGPNG to WebPWebP to PNGJPG to AVIFAVIF to JPGPNG to AVIFAVIF to PNGHEIC to JPGHEIC to PNGSVG to PNGPNG to ICOJPG to ICOImage to PDFPDF to Image

More tools

Rotate ImagesFlip ImagesImage EnlargerImage EditorAdd a Watermark to ImagesPick Colors from an ImageRemove Personal Metadata from Images

Document tools

Image to WordWord to Image

Privacy Policy · Updated September 24, 2026

Privacy Policy

This page explains the privacy model of the current ResizeNest website and tools. Most image processing remains on-device in your browser. Word to Image is explicitly different: it uses Secure cloud processing and uploads the selected DOCX only after you start conversion.

1. Images you choose

When you select a supported image for a current ResizeNest tool, the application reads that file in your browser so it can inspect, preview and process the requested operation. Supported processing is performed with browser code, Web Workers and self-hosted codec assets. The selected original image bytes are not intentionally transmitted to a ResizeNest application server as part of that image-processing workflow.

Some tools can work with several files in one browser session. Those files, previews, settings and current generated results are associated with the active page/workspace in your browser. Clearing the workspace, replacing a file, navigating away or closing the page releases app-managed references as the browser lifecycle allows.

2. Generated files and downloads

Processed outputs are generated in the browser and exposed to the page through temporary browser-managed object URLs until they are replaced, cleared or revoked. When you choose Download, the browser saves the resulting file to the location controlled by your browser and operating system.

3. Browser-local does not mean zero network activity

Loading any website requires normal network requests. Your browser must request ResizeNest pages and public runtime assets such as JavaScript, fonts, workers and codec files. Hosting, delivery and security infrastructure can therefore receive ordinary technical request information even though the selected image bytes are processed locally.

Ordinary request information can include an IP address, requested URL, timestamp, browser/user-agent information, protocol details and security-related request metadata.

4. Secure cloud processing for Word to Image

Word to Image is explicitly classified as Secure cloud processing. When you start conversion, your browser uploads the selected DOCX directly to the ResizeNest Cloud Gateway. The ResizeNest website VPS does not relay the document. Temporary input and generated result files are retained only for the job lifecycle and are deleted by explicit cleanup or the server janitor according to the published retention policy.

Cloud job logs are designed to record operational metadata such as job state, duration and stable error codes rather than document bytes, document text, raw capability tokens or unrestricted filenames. The temporary processing area is not a backup or cloud-drive service.

5. Cookies and persistent browser storage

The current image-processing code does not require a ResizeNest account and does not intentionally store selected image bytes in persistent browser storage such as localStorage or sessionStorage. The image workspace is designed around in-memory browser state and temporary object URLs.

6. Metadata inside image files

Some image files can contain EXIF or other metadata. Several ResizeNest workflows create a fresh encoded output and are designed to remove supported personal metadata rather than preserve arbitrary metadata from the source. Behavior can vary by tool and format, so review the tool interface and generated result before relying on metadata removal for a sensitive use case.

7. Sensitive files

Browser-local processing reduces the need to send image content to an application server. Secure cloud processing intentionally sends the selected Word document to temporary server-side processing. Decide whether your device, browser, network and the selected processing mode are appropriate for sensitive material, and review downloaded results before sharing.

8. Unsupported and future features

The current service is not presented as cloud storage, an account vault or a public server-processing API. Word to Image uses the disclosed temporary Secure cloud processing path. Any future feature with a materially different data path should disclose the change before use.

9. External destinations

If a ResizeNest page links to another website, that destination operates under its own privacy practices. This Privacy Policy describes ResizeNest and does not control unrelated external sites.

10. Changes to this policy

The policy may be updated as the site, infrastructure or feature set changes. The updated date at the top identifies the current published version.

11. Privacy questions

For a question about this policy or to report a privacy concern related to ResizeNest, email [email protected].