Content on the hosted instance...?

Even though Webtor doesn’t host or index any content itself, users can generate direct links like https://webtor.io/{infohash} to access specific torrents. Sometimes these links get shared publicly — on forums, blogs, or aggregators — and that’s usually how DMCA notices find their way to me.

When that happens, I remove access to that specific infohash from the hosted service. It’s not about removing stored files (since there’s no persistent storage), but about disabling further processing of that particular torrent.

There’s also the ability to revisit previously used content via direct links like https://webtor.io/{infohash} — this lets users bookmark a stream or return to it later. However, availability still depends on whether the content is cached or needs to be fetched again.

I actually experimented with making content indexable in the past, but many torrents turned out to be pirated — and eventually triggered DMCA notices. So I chose not to publicly expose anything on the hosted version.

Automation is possible: there’s a public API and a lightweight SDK for embedding content into external websites.