One address handles everything: [email protected].
What follows is what to include for each kind of message, so a reply is useful rather than a request for more detail. Many support questions are already answered in the guides — those pointers are at the bottom.
If you hold rights to content and believe this service is being used to infringe them, write to [email protected] with the subject line Copyright.
Include, per the process in the copyright policy: identification of the copyrighted work, the exact URL or location involved, your contact details, a statement of good-faith belief that the use is not authorised, a statement that the information is accurate, and your physical or electronic signature.
Worth being clear about scope: this site hosts no media. It resolves public links and streams the result through to the person who pasted it, storing nothing. Notices about specific files we hold cannot be actioned, because there are none. Notices about the service, its behaviour, or a specific tool are actionable and taken seriously.
Subject line Privacy. Say what you are asking for — access, deletion, or a question about what is collected.
Worth reading first: the About page sets out exactly what is and is not collected, and the Privacy Policy is the authoritative version.
Identification is the awkward part of any access or deletion request here. With no accounts there is no username to look up, so include what you can — approximate dates, the browser and device you used, and whether your question is about analytics or advertising cookies specifically. Consent for those is denied until you accept the banner, so if you never did, there is unlikely to be anything to find.
If you are acting on somebody else's behalf, say so and say in what capacity. Requests that arrive without it tend to stall on a follow-up question.
Subject line Bug. These are the details that make a report actionable rather than a guess:
The exact link you were trying, or one that reproduces it. Without this, most reports cannot be investigated at all.
Which tool page you used, and which button you pressed.
Your device and browser — iPhone with Safari behaves differently from Android with Chrome, particularly around where files are saved.
What happened, including any error message shown on the page.
Before writing: try the link in a private browsing window. If the content does not load there either, it is not public — that is expected behaviour rather than a bug, and the triage guide explains why.
General questions, corrections, and press or partnership enquiries go to the same address. Plain subject lines get read faster than clever ones.
Messages are read in English and Arabic. Write in whichever you prefer.
One honest caveat: this is a small operation, and replies are not instant. Copyright and privacy messages are prioritised over everything else.
Most incoming questions already have written answers, and reading one is faster than waiting for a reply.
A link will not download → the triage guide — the private-window test resolves the large majority of cases.
The file downloaded but you cannot find it → iPhone or Android. On iPhone, Safari saves to the Files app rather than Photos, which accounts for most "the download failed" reports.
The video has no sound → choosing a resolution. Many sites store video and audio separately.
The watermark is still there → the watermark guide, which is honest about when removal is impossible.
The full set is in the guides index.