Photos carry more than pixels
Every phone photo can embed EXIF data: GPS coordinates, timestamps, device model. Uploading such a photo to a server hands all of that to whoever runs the site — plus the image itself, which may show your home, family, or documents.
This is not paranoia; it is the default. Most people never strip EXIF, so the privacy question for any image tool is really: where does my file go?
Local processing keeps files on your device
The CubTools compressor runs entirely in your browser: your photos are read from disk, processed in memory, and the results are offered as downloads. At no point is a byte uploaded to a server — there is simply no server step in the pipeline.
That architectural fact beats any privacy policy. A promise can be broken or quietly changed; 'your file never left your device' is verifiable in your browser's network tab.
How to vet any image tool
Check for an upload step: if the tool shows upload progress or requires waiting on a server, your file is traveling. Check the privacy policy for retention language — 'deleted after X hours' still means stored for X hours.
Prefer tools that work offline after loading: if airplane mode does not break the compression step, nothing is being sent. And be wary of tools demanding accounts for a task this simple — accounts exist to track.
Good habits regardless of tool
Even with local processing, strip EXIF from photos you will publish — social platforms and blogs do not need your GPS coordinates. Keep originals archived separately from compressed sharing copies.
And remember the destination matters too: a privately compressed photo can still be screenshotted or re-shared after you send it. Compression privacy covers the tool step; sharing judgment covers the rest.
What compression does and does not do to metadata
One nuance worth knowing: browser-based compression produces a brand-new image file, and whether EXIF metadata survives depends on the implementation — some pipelines preserve it, others drop it. Never assume compression stripped your GPS coordinates; check with an EXIF viewer when location privacy matters for a particular image.
The privacy win of local processing is separate and absolute: regardless of metadata handling, your file never traveled to anyone's server. For maximum safety when publishing, strip metadata from public copies with a dedicated tool first, then compress. Two simple steps, each doing exactly one job well.
Teach this two-step habit to anyone who handles photos for your site or store: strip metadata first, then compress locally. It takes seconds and closes the two most common image-privacy gaps in a single pass.
Frequently asked questions
Do my photos get uploaded when I compress them here?
No. Compression runs entirely in your browser — your images never leave your device, and nothing is stored on any server.
What is EXIF data and should I worry about it?
EXIF is metadata embedded in photos (GPS location, timestamps, device info). Strip it from images you publish, regardless of which tool you use.
How can I tell if another tool uploads my photos?
Look for upload progress bars or server waiting times, read the retention policy, and test with airplane mode — if compression still works offline, nothing is uploaded.
Is anything stored after I close the tab?
No. There is no account and no server copy — closing the tab ends the session completely.