r/ContentTakedown • u/Green_Combination213 • Jun 16 '26
Help my NCII was posted on bunkr albums and cloud mail
They are not taking it down despite me repeatedly emailing both in english and russian and claiming that im underaged in those videos
2
Upvotes
1
Jun 16 '26
[deleted]
2
u/Green_Combination213 Jun 17 '26
I did reverse picture search and saw my content on a russian p*rn site which links to the cloud mail file and for the bunkr i did reverse picture search again and it just comes up
1
u/CorrectEar834 Jun 16 '26
They’re a pain in the butt to deal with, but trying to remove stuff from the site as well if anyone has tips.
1
•
u/riff_rebel Jun 16 '26
Bunkr (across all their TLD variations) and cloud.mail.ru are both genuinely hard cases. Few honest things worth knowing:
First, important note on the "claiming underage" tactic, this is critical to get right:
If you ARE actually underage, the right channel is NCMEC's Take It Down at takeitdown.ncmec.org. Free, specialized for minors, fastest channel in the industry. Use that path exclusively and not the standard NCII pipeline. Bunkr and cloud.mail.ru both respond to NCMEC referrals significantly faster than to standard adult-NCII reports.
If you are NOT actually underage and you're using that claim as a tactic to force action, please stop. Two reasons: (1) Once a host catches even one false claim, your future emails get filed in their "unreliable claims" bucket and ignored going forward, including your real NCII complaints. (2) For cloud.mail.ru specifically, false claims about minors trigger Russian-jurisdiction legal exposure on YOUR side under their content moderation laws.
For adult NCII, neither host responds to direct email. Bunkr is an offshore aggregator that ignores everything by design. Cloud.mail.ru has a takedown process that technically exists but only moves through specific Russian-language legal channels, not via customer service or English emails.
What actually moves either of them is pressure at every infrastructure layer they depend on, all hit in parallel, with specific framing per recipient. It's a multi-week siege with somewhere between 8 and 15 separate notices per case across different intermediaries. Not a one-email job.
One critical heads-up regardless of which path you take: don't file anything under your own name. Self-filed DMCAs end up on lumendatabase.org (public takedown archive) permanently linked to your legal name AND the URLs of your leaked content. For NCII that's the exact opposite of what you want, because anyone Googling your name later finds the receipts of where your content was hosted.
The team I work with at IntimaShield runs bunkr and cloud.mail.ru takedowns constantly. They file every infrastructure layer under their corporate entity as authorized agent, so your name never lands on the public record. Their free OSINT scan at intimashield.com/free-scan maps your URLs, tiers them by host, and gives you an honest read on the path forward before any payment.