Why Online Image Tools Upload Your Photos (and Why Vizua Doesn't)

Most online image tools upload your photos to remote servers, process them there, and send the result back. Your files travel across the internet, sit on hardware you don't control, and may be stored for hours or days. Vizua works differently — every operation runs locally in your browser, and your images never leave your device.

What Happens When You Use a Typical Image Tool

When you drag a photo into most online compressors, resizers, or background removers, here is the actual sequence of events:

1. Your browser uploads the full image file to the service's server (often hosted on AWS, Google Cloud, or similar infrastructure).
2. The server receives your file, processes it (compression, resizing, format conversion), and stores the result.
3. You download the processed file from their server.
4. The original and processed files remain on the server until they are deleted — which could be minutes, hours, or days later.

During this process, your image — along with its EXIF metadata (GPS location, device model, timestamps) — passes through networks and infrastructure you have no visibility into. For a vacation photo, that might feel harmless. For a medical document, a private family photo, or a business-sensitive image, the calculus changes.

How Long Do Services Keep Your Files?

The answer varies, and it is not always easy to find. Here is what the privacy policies of some popular tools actually say:

• TinyPNG/TinyJPG — uploaded images are "temporarily stored, optimized and deleted within 48 hours." Request logs (including IP address, browser type, and file fingerprint) are kept for 31 days.
• iLoveIMG — processed files are "automatically and permanently deleted within 2 hours." Uploads use HTTPS encryption.
• Canva — uploaded media is stored as part of your account. Canva's privacy policy (updated October 2025) states the company may "analyze your activity, content, media uploads and related data" and use this data to "train algorithms, models and AI products." Users can opt out in settings, but the default is opt-in.

Even services with good deletion practices still hold your files temporarily. And "deleted" on a server does not always mean "irrecoverably gone" — data may persist in backups, CDN caches, or logging systems.

Why Most Tools Need a Server in the First Place

There are legitimate technical reasons why image tools have historically relied on server-side processing:

• Computational cost — advanced image processing (especially AI-based tasks like background removal) requires significant CPU or GPU power. Five years ago, running these algorithms in a browser was either impossible or impractically slow.
• Codec availability — specialized image encoders (for formats like JPEG, WebP, or AVIF) were traditionally compiled for servers, not browsers.
• Business model — server-side processing lets companies meter usage, enforce limits, and require accounts. It also gives them data they can use for analytics or model training.
• Legacy architecture — many popular tools were built years ago when browser capabilities were far more limited. Rewriting them for client-side processing would mean rebuilding from scratch.

These reasons made sense in 2015. Browser technology has advanced dramatically since then.

How Vizua Processes Everything Locally

Vizua takes a fundamentally different approach. Every tool — from JPEG compression to background removal to text extraction (OCR) — runs entirely in your browser using modern technologies:

• Optimized algorithms compiled for browsers — the same compression engines used by professional software, adapted to run locally on your device.
• AI models that run on your hardware — background removal and text recognition use machine learning models that execute on your device's CPU, not a remote server.
• No upload, no download — your files are read from disk, processed in memory, and saved back to disk. At no point do they leave your device.

You can verify this yourself: open your browser's Network tab (F12 > Network) and compress a JPEG. You will see zero outbound image data. The processing happens right where your files already are.

What You Actually Risk by Uploading

For many users, uploading a photo to a compression service feels inconsequential. But the risks are real and cumulative:

• Data breaches — in July 2025, the Tea app suffered a breach that exposed 72,000 images including 13,000 photo IDs and 59,000 selfies from an unsecured database. Any service that stores your files is a potential breach target.
• Metadata exposure — your photos carry EXIF data including GPS coordinates, camera model, and timestamps. When you upload to a server, that metadata travels with the file.
• AI training — some services use uploaded images to train their AI models. Canva's privacy policy explicitly mentions this practice.
• Compliance violations — if you handle images subject to GDPR, HIPAA, or similar regulations, uploading them to a third-party server may create legal liability.

These risks apply even to services with solid reputations. The issue is structural: any architecture that involves uploading your files introduces risks that a local-processing architecture avoids entirely.

A Practical Privacy Checklist for Image Tools

Before using any online image tool, run through these checks:

1. Check the privacy policy — look for language about "temporary storage," "server processing," or "data analysis." If the policy mentions retention periods, the tool uploads your files.
2. Inspect network traffic — open Developer Tools (F12), switch to the Network tab, and process an image. If large POST requests appear, your files are being uploaded.
3. Look for offline capability — tools that work without an internet connection are processing locally by definition.
4. Check for account requirements — tools that require sign-up or login are more likely to store data server-side.
5. Read the terms on AI training — if the service uses AI features, check whether your uploads contribute to model training.

Frequently Asked Questions