Metadata: The Hidden Information Most File-Sharing Tools Leak
Metadata is a simple idea with a slightly intimidating name: it just means "data about the data." A filename, a file's size and type, sometimes a creation date or, for a photo, the location it was taken — none of that is the file's actual content, but it travels alongside it, and it's worth knowing where it ends up.
Where metadata normally goes
With a cloud-upload style sharing tool, that metadata is visible to — and often logged by — the service itself, simply because the file has to pass through its servers to reach the recipient. Filename and size routinely end up in server logs, sometimes retained well after the file itself is gone.
What changes on a direct transfer
On a direct, device-to-device transfer, that same metadata — filename, size, type — is only ever visible to the two devices actually involved. There's no third server in the data path to see it or log it, for the same underlying reason the file's contents aren't stored anywhere in between.
The metadata your files carry regardless of how you send them
This is worth being upfront about: none of this touches metadata embedded inside the file itself — EXIF location data baked into a photo, an author field in a document. That travels with the file no matter which transfer method carries it, and removing it, if it matters, is a separate step the sender has to take before sending.
A simple habit worth building
If you're sending something sensitive, it's worth checking a file's own embedded metadata — most operating systems let you strip photo location data or document author fields in a couple of clicks — regardless of which tool you use to send it. The transfer method and the file's own metadata are two separate things to think about.
Related reading
Private Sharing Secure Transfer What "No Account Required" Actually Means for Your Privacy A Beginner's Guide to End-to-End Encrypted File Sharing