I built a free video downloader that keeps nothing about its visitors. No accounts, no sign-up, no database, no uploaded files sitting on my server. So when I sat down to write the privacy policy, my first thought was: what is there to write about?

Quite a lot, it turns out. "We store nothing" is a claim, and a claim has to be true in every part of the system, not just in the parts I feel proud of.

What actually happens when you paste a link

On ramrom.io, you paste a video link into a box and press a button. That is the whole interaction. Here is what happens behind it:

  1. The link goes to a small PHP endpoint, resolve.php, over HTTPS.
  2. That endpoint sends the link to a third-party provider API, which works out where the video file actually lives.
  3. The file is streamed back to your browser through a proxy script. It passes through my server, but it is never written to disk. Once the stream ends, it is gone.

Nothing is saved. There is no users table because there is no database at all. There is no folder of downloaded videos to clean up, because one never existed.

The honest exceptions

Here is where a lazy policy falls apart. If I wrote "we collect nothing" and stopped there, I would be wrong. A few things do happen, and the policy has to name them plainly:

  • Server logs. My host keeps the standard access logs every web host keeps: the time of the request, the page asked for, the browser type. I do not read them to track people, but they exist, and pretending otherwise would be dishonest.
  • Analytics. I use Google Analytics, which sets its own cookie and records anonymous, aggregate usage. I say so, and I say the visitor can block it.
  • The provider API. The link you paste is sent to a third-party service so it can resolve the video. That service sees the link. I cannot promise what it does with it, so the policy says exactly that.

None of this is scary. It is ordinary. But it is not "nothing", and the difference between "nothing" and "almost nothing, here is the list" is the difference between a policy people can trust and one that falls apart the moment anyone checks.

Writing it in plain words

Most privacy policies read like they were written by a lawyer who has never met a user. Mine is short, in plain English, and written in the first person. Each paragraph answers one question a real visitor might ask:

  • What do you keep about me? Nothing you typed, nothing you downloaded.
  • Do I need an account? No.
  • Who else sees my link? The provider that resolves it, and the analytics service, in aggregate.
  • Can I ask you to delete my data? There is nothing to delete, and I say so — with a contact address if you want to check.

I also wrote the things the site does not do, because for a tool like this the absences are the policy. No cookies set by the site itself. No tracking pixels of my own. No selling, sharing, or renting of anything, because there is nothing to sell.

The rule I keep

Every time I add a feature, I ask one question before it ships: does this change what the policy says? If the answer is yes, the policy gets updated in the same deploy, not next month. A privacy policy that lags behind the code is worse than no policy, because it is a promise the site has already broken.

Keeping nothing is easy on shared hosting — a flat-file project with no database makes it the default, not a feature. The hard part is saying so honestly, including the small exceptions, in words a non-technical visitor can actually read. That is what the policy is for.