Does Erome Know When You Download?

This question comes up constantly and usually gets answered with a confident yes or no. The accurate answer depends on how the tool you used is built, and the difference is easy to explain.

What a server sees when you request a file

Any time your browser fetches something, the machine serving it learns a few things by necessity: your network address, roughly what browser you are using, and which page sent you if that was included. It needs your address to send bytes back. That is not tracking, that is how a transfer works.

So the real question is not whether some server sees you. It is which server.

Direct links: the source sees you

Some tools inspect a page and then hand your browser the original file addresses. You click, your browser connects straight to the source host, and the transfer happens between you and them.

That is simple and costs the tool nothing, which is exactly why it is common. The consequence is that the source host sees your address, your browser signature, and that the request arrived from a downloader page rather than from its own site.

Proxied: the source sees the server

Here the file is fetched by the server and streamed onward to you. Your browser only ever talks to this site. The source host receives a request from the server and has no way to know who the bytes were ultimately for.

On this site that is not a privacy feature bolted on afterwards. It is the only arrangement that works at all: the video host rejects requests that do not appear to come from its own pages, so a direct link would simply fail. The privacy consequence is a side effect of the necessary design, which is the most reliable kind there is.

Thumbnails are handled the same way, and that part was a choice. Preview images load from a host without that restriction, so they could have been loaded directly. Browsing here would then announce itself to the source with every thumbnail on screen.

Requests also carry no referrer, so nothing about the page you came from travels outward.

What this does not protect you from

This is where most answers stop being honest, so to be explicit:

• This site sees your request. It has to. Ordinary web server logs exist here as they do everywhere.
• The network in front of this site sees the traffic. Like most sites, this one sits behind a content delivery network, and that provider handles requests on the way through.
• Your internet provider sees that you connected here. Encryption hides what you did, not where you went.
• Your device keeps the file. Which is usually the part that actually matters, and the part people forget.

Proxying moves what the source can learn. It is not anonymity, and anyone selling it as anonymity is selling something else. What this site keeps, and for how long, is written out on the privacy page.

If it matters to you

1. Mind the device. Downloads land in a folder and often appear in a gallery app afterwards. That is the most likely way a file is seen by someone else.
2. Use a tool that does not hand out direct links. You can check this: if downloading sends you to a different domain, the transfer is between you and that domain.
3. Use a VPN if the concern is your provider or your network. That is the specific problem a VPN solves, and it changes nothing about the source host.

The uploader does not get told

Worth saying plainly, because it is the version of the question most people actually mean: the person who uploaded an album does not receive a notification when someone saves it. Platforms of this kind expose view counts on a page, not per-viewer identity, and a download made through a server is not distinguishable to them from any other request that server made.

Questions about this

Open the downloader