Infohash removal
We respect all valid removal requests.
Any spam will be rejected by our automated system and will be considered hacking.
A valid request includes a text document of a copyright certificate, HTML is fine. Once our AI has validated the request it is removed and 0 bytes are returned to any client requesting its swarm info.
There are cases where content cannot be removed for technical reasons, explained in the Process below.
All requests are published online for transparency.
Process
To prevent abuse we validate both ends of a request: the copyright certificate must match the content being removed.
Because trackers have no knowledge of what's being shared, the infohash must first be resolved to get its metadata (title, file list). Once this happens, the copyright certificate is checked to see if they match.
Resolving an infohash is expensive and can take anywhere from minutes to hours, and sometimes it never resolves.
Why might an infohash not resolve? If the swarm is dead (no seeders) and it isn't cached anywhere, the metadata can't be fetched and the request can't proceed because it could not be validated.
Step by step
- Pass the anti-spam check
- Verify your e-mail address
- Enter the infohash; we resolve it and show you the metadata. If it doesn't resolve straight away it will be put into a queue.
- Attach the copyright certificate and submit
- If the certificate and metadata match, the infohash is added to the blacklist table
Transparency Log
No removals have been published yet.