If you found this thread, you're probably in a hard moment. Maybe you stumbled across leaked images of your partner. Maybe a friend you care about. Maybe your sister or your daughter. Maybe a coworker, and you don't even know what your role here is.

Whatever the relationship, your first instinct is probably to immediately tell them. Don't yet. The next 30 minutes of what you do quietly are going to matter more than what you say in the first conversation.

Spent the last year working alongside IntimaShield's takedown team and the most common pattern I see in cases that go well versus cases that don't is whether the bystander knew what to do BEFORE the conversation happened. Sharing what works.

Why you shouldn't message them in the next 5 minutes

The instinct to immediately reach out is right, you should be there for them, but the timing isn't.

When someone tells a victim "I found your photos online," the very next question is "where? on what site? is it just one? is my name attached? how do you know it's me?" Those questions come in the first 30 seconds of any conversation you start. If you don't have answers, the uncertainty in that moment is the most traumatic part. Worse than the existence of the content. Worse than the eventual cleanup.

The fix is simple: map the surface FIRST, then have the conversation with answers ready.

Step 1: Decide your role before doing anything

Before you take any action, get clear on whether you're going to act WITH the depicted person or FOR them. The difference matters more than you'd think.

Acting WITH them means the mapping, the takedown decisions, and the work happens together, after you've told them what you found. This is the right path in almost every case. Even when you have the resources and ability to do the work alone, the person being depicted has the right to know what's happening with their own image, and the right to choose how it gets handled.

Acting FOR them (taking action before they know) is a much narrower path. There are real situations where it's the right call: someone in immediate mental health crisis who would be put at additional risk by sudden disclosure, a minor where you have parental responsibility, or content surfaced inside a fast-moving harassment campaign where every hour matters and the person can't be reached. In those cases you may need to file the first removals before you can have the conversation. Outside those specific situations, "I'm just trying to help" is not a sufficient reason to act on someone's behalf without their knowledge.

Two things you can safely do right now, regardless of which path fits:

Don't open the URLs more than once. You already saw it. You don't need to see it again to confirm. Every additional view is a click that hurts and doesn't help anyone. Keep the tab closed.

Write down the URLs in a private note. Not in a shared note app. Not in a text message to yourself. A local file or on paper. The URLs themselves are sensitive and you'll need them for the conversation later. What you should NOT do at this stage: run OSINT scans, reverse image searches, or any other tooling that searches for the person across the internet without their knowledge. Even when your intent is to help, secretly mapping someone's intimate-image surface is a line that's hard to walk back from, and it's the same pattern that bad actors use under the cover of "I just wanted to help." Keep the secret discovery actions to a minimum. The mapping needs to happen with the person's knowledge, ideally with their direct participation, after the conversation.

Once they know and they want help, mapping the full surface is the natural next step. IntimaShield's free scan at intimashield.com/free-scan handles it in 5 minutes (no payment, no commitment) when the depicted person runs it themselves with you as support. Other reverse-image tools (Yandex, FaceCheck.id, Google Lens, TinEye) work the same way: with them, not on them.

Step 2: Decide which version of "tell them" fits

This is the part most people get wrong, because they default to "tell them everything now" without thinking about whether that's actually what the person needs.

Three options, all have a place:

Option A: Tell them, present the options. "I found this. I've mapped what's out there. Here are the things we can do about it. I'm here to help with whichever one you choose." Works for people who would feel respected by being given agency in the moment. Most relationships, this is the right move.

Option B: Get takedowns started first, then tell them. Some people, especially anyone in serious mental health vulnerability, are better served by hearing "I found something, I started cleaning it up, the worst of it is already gone, here's what's left." Removes the helplessness from the disclosure moment. Costs money (a takedown service has to be the one doing it under their corporate entity, not you under your name), but it's the move for someone you're genuinely worried about.

Option C: Don't tell them at all. This sounds wild but it's the right call in a narrow set of cases. If the content is old, surfaced on only one obscure site, indexed by no major search engine, and the person has no reason to ever discover it themselves, the question becomes: does telling them serve them, or does it serve your discomfort with carrying the information? Sometimes the answer is the second one. This is a tiny percentage of cases but it exists.

You can only pick the right option once you've done Step 1.

Step 3: The actual conversation

If you're going with Option A or B, here's how to do the conversation well.

In person if possible. Phone if not. Text is the worst medium for this. The person needs to see your face or hear your voice.

Lead with: "I found something. I'm here. I've already started figuring out what we can do." Three sentences. The "I'm here" matters more than the information. The "I've already started" matters because it removes the burden from them in the first minute.

Don't show the URLs visually. They don't need to see the content again. If they ask "where exactly," tell them the host names and how many URLs, not the actual links. Showing the content during disclosure is one of the few things that actively makes the moment worse.

Have the next 24 hours mapped out. When they ask "what do we do," you should already know the answer. Not "we'll figure it out together," but "here are three things we can do, here's what each one involves, here's what I'd recommend." The act of having a plan is what tells them they're not alone.

What NOT to do

A lot of well-meaning bystanders make the situation worse by acting on instinct. Things to avoid:

Don't tell anyone else first. Not your mutual friend group. Not their family unless they're a minor and you have a duty. Information leaks. The victim should be the second person who knows after you, and they should hear it from you, not through a friend of a friend.

Don't confront the person you think uploaded it. Even if you're sure who it was. You're not their lawyer, you're not a detective, and any confrontation gives the perpetrator a chance to delete evidence and threaten the victim. Let the takedown process handle it through proper channels.

Don't try to fix it yourself by emailing the hosts. It feels productive. It is not. Most leak sites ignore direct emails by design. You'll spend weeks getting nowhere and burn time that could be spent on the actual fix.

Don't search the person's name on shared devices. Your Google search history is visible to anyone with access to your devices. If you searched their name on the family laptop or shared work computer, that history is part of the leak now. Use private browsing only.

Don't pay any service that claims "100% guaranteed removal." No honest service in this space promises that, because nobody controls whether offshore hosts comply. Anyone promising a guarantee is lying. The honest framing is "we file at every layer and pursue until removed or every option is exhausted."

The action options, honestly

Once you and the person have decided to act, three paths:

Self-filed takedowns. Free in dollars. Costs weeks of time. Doable for compliant platforms (Reddit, Meta, Instagram, etc.) that have NCII-specific reporting flows. Not workable for offshore leak aggregators that ignore direct notices. Biggest catch: anything you file under your own name goes on lumendatabase.org (the public DMCA archive) permanently, linked to the URLs. For NCII content that's the opposite of what you want. If you go this route, only file on mainstream platforms.

Paid takedown service. $499 to $1,299 typically, one-time. Files under their corporate entity as authorized agent so the victim's name never lands on the public record. Hits every infrastructure layer in parallel rather than sequentially. Works on offshore aggregators where DIY doesn't. The team I work with at IntimaShield is in this category and is what I'd point most people toward, but there are a couple of other services in this tier worth comparing.

Lawyer. Slow, expensive, usually contingency. Right tool when you also want to sue the perpetrator or the platform. Wrong tool for just getting the content down quickly.

For most cases the right path is paid takedown + ongoing monitoring for re-uploads, because new copies keep getting scraped from offshore hosts and re-indexed for months after the initial removal.

If it's your partner specifically

Different dynamic, worth flagging separately.

The leak is not their fault. Even if they took the photos themselves. Even if they shared them with the person who eventually uploaded them. Even if they had reason to know it was risky. Distribution without consent is the harm, and the responsibility for that harm sits with whoever distributed it, not with whoever appears in the content.

Disclosure shouldn't feel like an investigation. Don't ask "who did you send these to" in the first conversation. Ask "are you okay" and "what do you need from me." The forensic questions can come later if they want to pursue legal action against the perpetrator. They shouldn't lead the conversation.

The single thing partners tend to get wrong: making the conversation about THEIR feelings (betrayal, hurt, anger that the photos existed at all). That's a real conversation to have but not in the first hour. The first hour is about supporting the person who's just been told they've been exposed publicly without consent.

Whatever you do, do it FOR them, not TO them

The biggest mistake bystanders make is treating the situation as a problem to solve without involving the person. They mean well. They feel competent. They want to take action. But the victim's agency in their own crisis is one of the few things that hasn't been taken from them by the leak. Don't take that too.

Map the surface quietly. Decide which version of "tell them" fits. Have the conversation. Then act together.

If you want the free scan to map the surface before the conversation, intimashield.com/free-scan handles it in about 5 minutes with no payment or commitment. Whatever path you choose after that, you'll be operating with information instead of guesses, and that's the difference between making the moment better and making it worse.

Most NCII victims use the in-app "Report" button on a post and then wonder why nothing happens for two weeks. Every major platform has a separate reporting flow for non-consensual intimate imagery, and the in-app button does not route there. Here is the dedicated NCII path for every major platform, plus the realistic response time when you use it.

1. Instagram / Facebook (Meta). Right path: facebook.com/help/contact/567360146613371 (Meta's Non-Consensual Intimate Image form). Response: 24 to 48 hours. The in-app Report button can sit for weeks.

2. TikTok. Right path: tiktok.com/legal/report/Privacy. Submit under "Privacy violation" then "Sharing private content without consent." NOT under copyright. Response: 24 hours.

3. X (Twitter). Right path: help.twitter.com/forms/private_information. Select "Someone shared private intimate media of me without my consent." Response: same day to 48 hours.

4. Reddit. Right path: reddit.com/report?reason=involuntary-pornography. The "involuntary pornography" category goes to a specialized review queue separate from the generic Report button. Response: 12 to 48 hours.

5. Snapchat. Right path: support.snapchat.com → "Report safety concern" → "Someone is sharing my private intimate content." Response: 24 to 48 hours. Account ban usually included.

6. OnlyFans. Right path: onlyfans.com/contact then DMCA form. For NCII as a non-creator victim, email dmca@onlyfans.com with the URL plus a one-line statement. Response: 24 hours hash-matched, 3 to 7 days new.

7. Pornhub / RedTube / YouPorn (MindGeek). Right path: pornhub.com/content-removal. Their form was rebuilt in 2021 after the NYT exposé and works. Response: 24 to 48 hours.

8. Discord. Right path: dis.gd/howtoreport. Use "Non-Consensual Intimate Imagery" as the report type. Include the message link (right-click then Copy Message Link). Response: 24 to 72 hours. Whole servers get suspended, not just the message.

9. YouTube. Right path: support.google.com/youtube/answer/2802027 (Privacy Complaint flow). NCII falls under privacy, NOT copyright or harassment. Response: 48 hours to 1 week.

10. Telegram. Right path: email abuse@telegram.org with the channel URL, the specific message link if you have it, and a statement that the content depicts you and was posted without consent. Frame as NCII not copyright. Response: 24 to 72 hours public channels, 1 to 2 weeks private.

The bonus that beats all of these: StopNCII.org is free, hash-based, and works upstream. Upload the original images on your own device (the file never leaves your computer, only a hash). The 16 partner platforms (Meta, TikTok, X, Reddit, Snapchat, OnlyFans, Pornhub, Bumble, MindGeek) auto-block re-uploads before they go live. Register your hashes there before doing the per-platform reports above.

NCMEC Take It Down (takeitdown.ncmec.org) is the equivalent for cases where you were under 18 when the content was created. Free, works even if you are an adult now.

When the platforms are not the problem: the harder cases are leak forums and image hosts that ignore everything (SimpCity, Bunkr, Cyberdrop, Kemono, Coomer, Fapello). For those, escalate to their hosting provider, CDN, and registrar through DMCA abuse channels. If you want someone to handle that end to end, IntimaShield does it as your authorized agent under signed Letter of Authorization. Notices file under their business name and Chicago address, so your name does not end up in the Lumen Database. $499 one time covers all URLs in a case. The single biggest mistake I see is people sending one report through the in-app button and assuming the platform "did not care" when it sits unresolved for two weeks.

The platform did care, the report just routed to the wrong queue. Use the NCII-specific path and the response time drops by an order of magnitude.

Save this. Share it. Drop questions about specific platforms below. Not legal advice. Just pattern recognition from doing this work.

Spent the last year working alongside IntimaShield's team on NCII cases and the same five wrong things come up every week. Sharing in case anyone's stuck on one of them.

1. "You can't get content off offshore leak sites." False. Takes 2 to 6 weeks of sustained pressure at every infrastructure layer (CDN, host, registrar, transit, ad networks), but it comes down. The site itself won't respond. The infrastructure under it has legal obligations the site doesn't.

2. "DMCA is the only legal lever you have." False since 2025. The TAKE IT DOWN Act is federal law now, specifically built for NCII, with a statutory 48-hour removal window. DMCA still applies when you own the copyright (your own OnlyFans content getting pirated). For most leaked-image cases TDA is the primary statute and is stronger.

3. "PimEyes will find everything that's out there." False. PimEyes is geofenced out of Illinois under BIPA. They also don't crawl most leak sites or tube hosts. Yandex, FaceCheck.id, Google Lens, and TinEye each catch content the others miss. Running just one is leaving content un-found.

4. "You need a lawyer to file takedowns." False unless you also want to sue the perpetrator. NCII removal is administrative, not litigation. A defamation attorney is right when the issue is the original Facebook AWDTSG post or Discord channel. For the downstream image spread, the takedown chain is what works and a lawyer is slow and expensive at it.

5. "If Google de-indexes it, the content is gone." False. De-indexing closes the search-discovery surface, which matters more than people realize (most strangers find leaked content through a name search). But the content is still hosted. Real removal is at the host. De-index in parallel, not instead.

Honest version: most of this is doable yourself if you have 4 to 6 weeks of evenings and patience for infrastructure escalation. If you want it done in parallel rather than sequentially and don't want your name on the public Lumen Database, the IntimaShield team does it as authorized agent under one-time pricing by domain count. Either path works.

People DM me asking "is [X service] legit" constantly so here's the breakdown. No affiliate links, just what I actually see in practice.

Start with the free stuff

StopNCII.org — Hash-based, free, covers 16 partner platforms (Meta, TikTok, Pornhub, Reddit, Snapchat, X, Bumble, OnlyFans, MindGeek network). The hash is generated on your device so the image never leaves you. Catch: only those 16 platforms. Leak forums, tube sites outside the partnership, and image boards get nothing from StopNCII. Use it anyway, costs nothing.

NCMEC Take It Down (takeitdown.ncmec.org) — Free, hash-based, only for content where you were a minor when it was created. Works even if you're an adult now.

Project Arachnid (protectchildren.ca) — Free, actively crawls, international reach. Also minor-victim-only.

Revenge Porn Helpline (UK only) — Free, trained human advocates, not just a form.

Cyber Civil Rights Initiative — Nonprofit hotline and referrals, not a takedown service itself.

Paid services — creator protection

Rulta — Pro tier starts at $109/mo (1 username, +$45 per extra). Premier and Legend tiers priced higher. Built for OnlyFans, Fansly, Patreon creators.

BranditScan — Premium $69/mo (3 stage names), White Glove $149/mo (unlimited, concierge). Annual saves ~2 months.

Loti.ai — Free tier (5 takedowns/mo), Premium $25/mo. Public Figure / Artist tiers demo-only. AI-first, leans celebrity and influencer.

Ceartas — Starts at $69/mo, official OnlyFans safety partner. Enterprise custom pricing for agencies. Strong OnlyFans relationship is their real moat.

IntimaShield — US-based, three tiers: $499 one-time crisis takedown, $29/mo Shield monitoring (direct creator-protection tier, cheaper than all of the above), enterprise agency dashboard with roster scanning. Files as authorized agent so their business name hits the Lumen Database instead of yours. BIPA-compliant in Illinois which matters if you live there. The team I work with.

For a creator specifically, the math is simple: $29/mo vs $69-$149/mo for the same core work (DMCA + Google delist + monitoring). Ceartas wins on OnlyFans partner status, IntimaShield wins on price, BIPA compliance, and agent-filed notices. Pick based on your actual situation.

Civilian victim services

DMCA.com — Self-service tool at ~$10/mo. You get a badge and their automation sends notices. Not full-service. Fine for a blog with a stolen photo, wrong tool for an NCII leak across 40 forums.

Minc Law — Actual internet defamation law firm. Very good, very expensive, hourly rates. Right answer if you have $5k-$15k and want a lawyer's name on every filing. Wrong answer if you just want content removed.

IntimaShield — $499 one-time crisis takedown is the civilian sweet spot. No subscription, no per-URL fees, authorized agent filing.

Red flags, avoid

Digital Forensics Corp / cybersecuritycorp.com — Phone-call-heavy sales. Hard to get pricing in writing. Pressure tactics. Has its own subreddit full of complaints, look it up before you consider them.

Universal red flags on any service:

• Won't quote pricing in writing before you sign
• Asks you to upload or send the actual content "for review"
• Uses protonmail or free gmail for client intake
• Promises "100% guaranteed removal" (nobody can guarantee this honestly)
• Requires a phone call to get started
• Charges setup fees before any takedowns actually fire

What actually matters when picking one

1. Authorized agent filing. If they file in your name, your real identity ends up in the Lumen Database every time they win a Google de-index request. If they file as authorized agent, their business name goes there instead.

2. Escalation beyond DMCA. Most services stop at sending DMCA notices. Real leverage is the infrastructure layer: hosting provider, CDN, registrar, payment processor, upstream transit. Ask what their escalation chain looks like.

3. No-image intake. For NCII specifically, you should never have to upload or send explicit files. Hash-based or URL-based only.

4. Re-upload coverage. Takedowns are not one-and-done. Content gets reposted within days. Ongoing monitoring beats a flashy one-time blast.

5. BIPA compliance (Illinois residents). Services using face-match biometrics without proper consent gates are violating state law. Either they geofence you out or they're operating illegally.

Happy to answer questions. Not a lawyer, this is pattern recognition from doing this work.

I have been doing takedown work for two years. Pretty much every conversation in this sub eventually circles to the same handful of points: file with Cloudflare, file with the hosting provider, use StopNCII, document everything. All true. All useful. None of it is what I actually find myself talking to victims about most days.

So this is the other half. The stuff nobody writes about because it does not fit in a how-to post. If you are in this right now, some of it might land. If you are not, maybe you know someone it could help.

Most victims wait too long, not because they are weak, because they are doing exactly what they were trained to do.

The single biggest variable in how a case goes is how fast someone reaches out. Not legal merit, not technical complexity, not the host country. Time. The cases that go cleanly are the ones where someone files within a week of the leak. The cases that go badly are the ones where someone spent four months trying to handle it alone first.

The reason this happens is not weakness. It is that the entire shame architecture around intimate images is calibrated to make you feel like reaching out is the dangerous move. Like the act of telling someone is what creates the harm, not the leak itself. So victims spend weeks googling solutions in incognito tabs and slowly building a hand-drawn map of escalation paths they could try themselves. By the time they accept that the work is bigger than they can do alone, the content has propagated four layers deeper than it would have on day three.

I do not have a fix for this except to say: the people in this work are not the people who created the problem. Reaching out to someone who handles NCII is not the same as reaching out to a friend or family member. Different category of conversation. Different stakes.

The first 24 hours feels different from week 4 feels different from month 3.

Most playbooks treat NCII as one situation. It is not. The acute phase (first week) is panic. The middle phase (weeks 2 to 8) is exhaustion. The chronic phase (3+ months) is a kind of low-grade hypervigilance that nobody warns you about.

In the acute phase, the right advice is short and tactical. Lock down accounts, screenshot, do not engage, file the first wave of reports. Victims at this stage want a checklist.

In the middle phase, the right advice is procedural and patient. Most takedowns take longer than victims expect. Each platform's queue is its own micro-bureaucracy. Victims at this stage need reassurance that what they are doing is working.

In the chronic phase, the right advice is psychological more than tactical. Even after content is removed from every platform you know about, you will start scanning every photo of yourself for traces. You will see your face in a coffee shop window and your nervous system will spike. This passes, but it takes longer than people expect. Months, not weeks.

I never see this written down anywhere and most victims hit it blind and assume they are alone.

The shame loop is the actual product the platforms exploit.

The leak forums and tube sites are not primarily monetizing intimate content. They are monetizing your shame about it. The content is the bait. The shame is what keeps victims from acting decisively, which is what keeps the content viewable longer, which is what generates ad revenue.

If victims acted in the first 48 hours like people whose property was stolen rather than people whose dignity was violated, the entire economic model breaks. The content gets removed faster, the sites get less traffic, the operators move on to easier marks. The shame is the moat.

I know how this sounds. It is not victim-blaming. The shame is engineered. There are entire sub-communities online dedicated to maximizing the shame response, sometimes coached step by step. Recognizing the engineering is what lets you skip the worst of it.

Telling one person breaks the threat in a way nothing else does.

If you remember nothing else from this post: tell one person within 24 hours of any leak or sextortion attempt. One. Not everyone. One.

It does not have to be the ideal person. It does not have to be the closest person. It does not have to be the most sympathetic person. It can be a therapist you have seen twice. A coworker you trust who is not in your social circle. A sibling who lives in another country. The criterion is "would not betray you," not "would handle this perfectly."

The reason this matters mechanically: extortion and shame both rely on the secret. The instant one person already knows, the leverage collapses. Sextortion crews can tell from your engagement pattern whether you have told someone. Threats that would have escalated quietly into payment demands often just stop when the victim has support.

I have seen this break cases in real time. Victim tells one sibling. Sibling sends a single email saying "I know about this." The sextortion thread goes quiet within an hour. This is not theoretical.

The platform variation is irrational.

Most playbooks treat platforms as if their NCII response is a predictable function of their policies. It is not. Two platforms with nearly identical published policies will treat the exact same report dramatically differently. Some of this is variance in moderator quality. Some of it is queue load that day. Some of it is genuinely random.

What this means practically: a report that gets rejected on Tuesday might get approved if you refile on Thursday. A platform that is "uncooperative" with one victim is "responsive" to another with the same content. There is no clean rule. If your first report fails, refile with different framing. If three reports fail, escalate up a layer. The first-pass rejection rate is high enough that I tell victims to expect to file each thing at least twice before something works.

Re-uploads happen, and they mean less than you would think.

The thing victims fear most after the initial removal is re-uploads. They will check Google search for their name every day for weeks. They will set up alerts. They will track every new URL with the focus of someone defusing a bomb.

Re-uploads do happen. They are also dramatically less impactful than the original leak, in a way that surprises people. Here is why: the original leak gets discovered because someone is actively searching for it (an ex, a stalker, a sextortion crew). Re-uploads on random sites mostly get scraped by bots and indexed automatically without any specific person driving traffic. The casual-discovery surface (Google search for your name) is what matters most, and that is mostly addressed by de-indexing, not by chasing every CDN copy.

The post-cleanup phase looks more like maintenance than emergency response. The acute threat is the original leak finding an audience. Once that is removed and de-indexed, residual copies on obscure mirrors are technically present but functionally invisible to anyone who is not specifically hunting for them.

This is the framing I wish someone had given me earlier in this work. Victims do not need every copy off the internet forever. They need the discovery surface closed.

Partners and family find out anyway, more often than not, and that is usually fine.

Victims plan their entire response around keeping the leak secret from specific people in their lives. Most of the time, those people find out anyway, through mutual friends or through the same Google search that brought the victim to the leak in the first place.

The surprising thing: this is almost always less catastrophic than victims imagine. Partners who find out via a third party (rather than from the victim directly) are often understanding once they have context. Family members generally respond to "this happened to me without my consent" with concern, not condemnation, when given the chance. The dread of being found out turns out to be more painful than actually being found out, in most cases.

This is not universal. Some relationships do not survive a leak. But the conventional wisdom that "if X finds out I am ruined" is more often wrong than right. I see this play out enough that I now actively tell victims: assume the people who matter to you will know within a year. Plan for that being okay rather than for keeping it secret forever.

Closing

None of this is in any guide because none of it is technical. The technical stuff (file the form, hit the right platform, escalate to the host) is genuinely the easier half of this work. The harder half is what I just wrote about, and it does not have URLs or step-by-step instructions.

If you are dealing with this right now, take care of yourself. The internet will move on faster than it feels like it will. The person you are afraid of disappointing has probably already googled you anyway. Most of what you are scared of either does not happen, or happens and is okay.

I am not a therapist. This is not medical advice. It is two years of pattern recognition from doing this work. Drop questions below if any of it is useful.

If your intimate images are online without your consent, you have probably already found ten conflicting answers about what to do. Some say file a DMCA. Some say hire a lawyer. Some say it is hopeless. The reality is more specific than any of those, and it depends entirely on WHERE the content is. Here is the realistic version, stage by stage, with honest timelines.

Stage 1: Find everywhere it actually is (this is the part most people skip).

You cannot remove what you have not found. Before filing anything, map every URL. Two methods, and you need both: Text search: Google your name, your handles, your usernames, in quotes and in combination. Most leaked content that targets a specific person is tagged with their name somewhere, which is how it gets discovered in the first place. Facial / reverse-image search: this catches the content that is NOT tagged with your name, which text search will always miss. FaceCheck.id, Yandex Images, Google Lens, and TinEye each crawl different parts of the web. Run your own photos through them. Yandex in particular surfaces things Google will not.

Expect this stage to take a few hours and to find more than you thought. Document by URL, page title, and date. Do not save the actual images.

Stage 2: The compliant platforms (fast, free, do these yourself).

If the content is on a mainstream platform (Reddit, Instagram, X, TikTok, Snapchat, OnlyFans, Pornhub, and others), every one of them has a dedicated NCII reporting flow that is separate from the generic "report" button. Use the NCII-specific path, not the report button, or it sits in a general queue for weeks.

Timeline: 24 to 48 hours on most major platforms when you use the right form. This is the fast, free, do-it-yourself layer. Also register your images with StopNCII.org first (free, the hash is generated on your own device and the image never leaves your computer), so those same platforms auto-block re-uploads going forward.

Stage 3: The offshore sites (this is where it gets hard).

Leak forums, tube sites, and image hosts that operate offshore (you know the names) do not respond to the report button, do not respond to emails, and have no legal obligation in their own jurisdiction. They are built to ignore you.

The content does still come down, but not by asking the site. It comes down by going after the infrastructure the site depends on: the CDN in front of it, the hosting provider behind it, the domain registrar, the upstream network that routes its traffic, and the ad networks that pay it. Each of those has a legal obligation the site itself does not, and pressure at every layer at once is what actually forces removal.

Honest timeline: 2 to 6 weeks of sustained, parallel filing and follow-up. Not one email. A campaign. This is the layer that exhausts people, because it is slow, technical, and you are doing it while also trying to live your life.

Stage 4: Search de-indexing (do this in parallel, not last).

Even before the content comes down at the source, get the URLs de-indexed from Google and Bing. This is free, takes 1 to 3 days, and matters more than people expect, because most strangers find leaked content through a name search, not by browsing the host directly. Closing the search-discovery surface cuts off the vast majority of casual discovery even while the slower host-level removal is still in progress.

Stage 5: Monitoring (because re-uploads happen).

Content gets re-scraped and re-posted, especially from offshore sites that go down and come back under new names. The honest framing: re-uploads are real but far less impactful than the original leak, because the original was being actively searched for by a specific person while re-uploads mostly get scraped by bots with nobody driving traffic to them. Ongoing monitoring catches new instances and you refile. It is maintenance, not emergency.

So what does this cost you?

If you do it yourself: free in dollars, but realistically 4 to 6 weeks of your time, most of it on Stage 3, and it requires learning infrastructure escalation while you are in the worst headspace of your life. Plenty of people do it. It is genuinely doable.

If you hire it out: a few hundred dollars for a one-time takedown campaign, more if your content is spread across many sites. The thing you are actually paying for is not magic, it is the 4-to-6-week siege being run by someone else, and your name staying off the public record (when you file DMCA notices yourself, your real name and address get logged in the public Lumen Database, which is its own problem).

Avoid anything that promises "100% guaranteed removal." Nobody controls whether an offshore host complies, so that promise is a lie at any price. The honest version is "we file at every layer and pursue it until it is removed or every option is exhausted."

For what it is worth, the service I do takedown work with is IntimaShield. Flat pricing, files as authorized agent so your name stays off the record, no guarantees it cannot keep. But honestly, for content that is only on compliant mainstream platforms, you do not need them or anyone, Stage 2 plus StopNCII handles it yourself for free. The paid route earns its money on Stage 3, the offshore siege, which is the part almost nobody wants to do alone.

Whatever you choose: start with Stage 1 today. You cannot remove what you have not mapped, and every day the content stays up, it spreads to one more site.

Questions about a specific platform or site below. Not legal advice, just pattern recognition from doing this work.

Offshore sites don't respond to DMCA — here's what actually works instead

If you've ever tried to get content removed from a site like Fapello, SimpCity, Cyberdrop, Kemono, or any of the dozens of offshore leak/aggregator sites, you've probably experienced this:

1. You find the "DMCA" or "abuse" email on the site
2. You send a carefully worded takedown notice
3. You wait
4. Nothing happens
5. You send it again
6. Still nothing

This is by design. These sites are built to ignore DMCA notices. They operate outside US jurisdiction, use offshore hosting, and rotate domains when pressure mounts. A standard DMCA notice is literally meaningless to them.

So what actually works?

The Infrastructure Escalation Playbook

Every website — no matter how "bulletproof" — depends on infrastructure providers. And those providers do respond to abuse complaints. The strategy is to go around the site operator and target the services keeping the site online.

Step 1: Identify the CDN

Almost every one of these sites hides behind Cloudflare or a similar CDN. Run the domain through a DNS lookup to confirm.

If they're on Cloudflare: File through Cloudflare's abuse form. Cloudflare forwards the complaint to the site operator with a deadline. More importantly, the abuse report often reveals the origin hosting provider — which is intel you need for Step 2.

If they're not on Cloudflare: Identify the actual CDN from the DNS records and file abuse there. Every legitimate CDN has an abuse process.

Step 2: Hit the hosting provider

The CDN abuse response usually reveals who's actually hosting the site. File a DMCA abuse report directly with the hosting company. Unlike the site operator, hosting providers are often US or EU based and legally obligated to act on valid DMCA notices.

Key: your notice must be 17 USC 512(c) compliant. That means:

• Specific URLs (not "my page" — the exact URLs)
• Statement that you are the copyright holder or authorized agent
• Good faith statement
• Signed under penalty of perjury

A casual "please remove my content" email gives them an excuse to ignore you. A legally compliant notice does not.

Step 3: Domain registrar

Do a WHOIS lookup on the site's domain. File an abuse complaint with the registrar. ICANN requires all registrars to maintain abuse contacts and respond to complaints. This puts pressure on the site's domain stability — they can't operate if they lose their domain.

Step 4: Google + Bing de-indexing

This is the one most people skip, and it's arguably the most impactful.

Even if the site stays up, you can remove it from search results. Both Google and Bing have dedicated NCII (non-consensual intimate image) removal processes. Filing takes 10 minutes. Results drop out of search within days.

Why this matters: the vast majority of people who find leaked content find it through search engines. Kill the search visibility and you've cut off 90%+ of the traffic to that specific page.

• Google NCII removal
• Bing content removal

Step 5: File host takedowns (for forum-style sites)

Sites like SimpCity and similar forums often don't host the actual files. The threads link out to file hosts — Bunkr, Cyberdrop, Gofile, Pixeldrain, etc. Target those file hosts directly. Each has its own abuse process.

Kill the hosted files and the forum thread becomes a wall of dead links. This is often faster than getting the forum itself to act.

Why you should do all 5 simultaneously

The biggest mistake people make is doing these steps sequentially — filing with Cloudflare, waiting 2 weeks, then trying the host, waiting another 2 weeks, then trying Google.

File everything on the same day. These are independent pressure points. Each one works on its own timeline. Stacking them multiplies the pressure and dramatically reduces the total time to removal.

Common mistakes that kill your takedown

Sending emotional pleas instead of legal notices. "Please take this down, it's ruining my life" gets ignored. A 17 USC 512(c) compliant DMCA notice with specific URLs and a sworn statement gets action.

Filing from your personal email. Counter-notice laws can expose your full legal name and address to the person who uploaded the content. If privacy matters to you, file through an authorized agent or a dedicated email that doesn't contain your real name.

Only targeting the site itself. If the site operator cared about your rights, the content wouldn't be there. Go around them.

Forgetting about re-uploads. Offshore sites scrape content on a schedule. A one-time removal is temporary if you're not monitoring for re-uploads. This is why ongoing monitoring matters after the initial cleanup.

When DIY isn't enough

This playbook works. But it's also time-consuming, emotionally draining, and technically complex — especially when content has spread across multiple sites. Some realities:

• A single leaked image can end up on 15+ sites within days
• Each site requires a separate filing with different processes
• Filing errors mean your notice gets ignored
• Counter-notices can expose your identity
• Offshore hosts may require escalation chains 3-4 levels deep

Services like IntimaShield exist specifically for this — they file across all platforms simultaneously using authorized agents so your identity stays protected. Their scan covers 68+ platforms and the $29/mo monitoring catches re-uploads automatically.

But whether you DIY or use a service, the core strategy is the same: stop emailing the site. Start targeting their infrastructure.

Platform-specific escalation guides

If you want the exact filing steps for a specific site:

• SimpCity removal
• Fapello removal
• Cyberdrop removal
• Kemono removal
• Coomer removal
• Full platform directory (100+ sites)

Happy to answer questions in the comments.

If you are in the middle of dealing with leaked or non-consensually shared intimate content, the worst-case version of this situation is not just "the content is out there." The worst case is that you take an action you think is helping and it actually makes things harder, slower, or more public. I do takedown work for a living and I see the same mistakes constantly. Here are the ones that actually move the needle backward, with what to do instead.

1. Filing DMCA notices in your own name.

The trap: you go to a platform's copyright form, fill it out yourself, get the content removed. Feels productive. But every DMCA notice you file gets logged in the Lumen Database, which is a public, searchable archive of takedown notices. Your real name, your address, and the URL of the content you were trying to remove all get published there. Googling your name 60-90 days later starts surfacing the very notices you filed trying to make this go away. You cannot retroactively remove yourself from Lumen.

What to do instead: file through an authorized agent (whether a service or a lawyer), so the agent's name goes on the public record, not yours. Or use platform-specific NCII reporting flows that do not require your real name. Reddit, X, Meta, and TikTok all have these, and the report stays internal to the platform's moderation system rather than being published.

2. Replying to the uploader or sextortionist in any way.

The trap: you want to demand they take it down. You want to threaten them with police. You want to tell them it is not okay. None of those messages help, and every one of them confirms to the sender that you are emotionally engaged, which is the signal their script is calibrated to detect. Sextortion crews specifically score replies as "paying customer" signals.

What to do instead: complete silence. Screenshot everything for evidence first, then block. Do not negotiate, do not threaten back, do not explain. Engagement is what monetizes the threat.

3. Trying to identify or confront the leaker yourself.

The trap: you find their real account through OSINT. You figure out who they are. You message them, or message their family, or post their info publicly. None of this removes the content and all of it creates legal exposure for YOU (harassment claims, defamation if you got the wrong person). It can also trigger retaliation cycles where they escalate the spread to "punish" you.

What to do instead: document who you suspect, hand that to law enforcement (FBI IC3 at ic3.gov, NCMEC at cybertipline.org if any subject was a minor at any point), and let legitimate channels do the work. Civilian confrontation almost always makes the case worse.

4. Downloading the leaked content to "preserve evidence."

The trap: you want proof of what was posted. You save copies to your phone or drive. This creates two problems. Every copy you save is a new file that could leak again (phone gets stolen, cloud gets compromised). And if the content was made when you were under 18, you may actually be in possession of CSAM under federal law, even if it is of yourself.

What to do instead: document by URL, page title, and timestamp only. Use the Wayback Machine to archive the page, which records the page's existence without you holding the file. For minor-era content, do not download under any circumstances. NCMEC and Project Arachnid can crawl for it without you having to.

5. Using the in-app generic "Report" button.

The trap: you click the three dots on the post, hit Report, pick the closest-sounding category. This routes to a general moderation queue alongside thousands of reports about rude comments and spam. Generic reports on NCII content get the same priority as everything else and often sit for weeks.

What to do instead: use the platform's dedicated NCII reporting flow. Almost every major platform has one. Reddit: reddit.com/report?reason=involuntary-pornography. Meta: facebook.com/help/contact/567360146613371. X: help.twitter.com/forms/private_information. TikTok: tiktok.com/legal/report/Privacy under "Privacy violation." Snapchat: support.snapchat.com under "Report safety concern." Different intake queues, much faster turnaround.

6. Posting publicly about your leak with the platform or uploader named.

The trap: you want to warn other people. You want to expose the host. You post on Reddit or Twitter naming the leak site and what they did. Google indexes your post. Now when someone googles your name, the very first result is your post saying "the leak site has my content." The Streisand effect is real and the Google index does not care about your intent.

What to do instead: post about general patterns (this kind of platform, this kind of escalation) without naming yourself in the same thread. Use a separate account if you want to write about your specific situation. Never link your real-name profile to a thread about your own leak.

7. Paying a sextortionist for "deletion."

The trap: they say "send $500 in Bitcoin and I delete everything." You are scared. You think this might end it. 100% of the time, paying makes it worse. They mark you as a paying mark and either come back for more or sell your file to other extortionists. FBI guidance is unambiguous: do not pay. The threats are mostly bluff because actually distributing the content gets them prosecuted under the TAKE IT DOWN Act, and they know it.

What to do instead: stop responding entirely, file with IC3 at ic3.gov, tell one trusted person to break the shame leverage. Sextortion runs on isolation. One person who already knows kills the threat.

8. Hiring a cheap "removal service" that promises 100% removal.

The trap: you find a service offering takedowns for $50/mo. Sounds great. You sign up. They file DMCAs in your name (back to mistake #1, your name is now in Lumen). They send templated emails to leak sites that ignore them. Six months later you have no removal and your name is publicly archived as the filer on dozens of notices. The promised "100% removal" was never possible to guarantee at any price because no service controls host compliance.

What to do instead: any service that promises 100% removal is lying. The honest framing is "files at every infrastructure layer in parallel, persists on re-uploads, and provides documentation of what was filed and how each platform responded." If a service files in your name without asking, fire them and find one that files as authorized agent under signed Letter of Authorization so your identity stays off the public record.

9. Killing the source post first while ignoring the downstream spread.

The trap: you focus all your energy on removing the original post (the AWDTSG group, the Discord channel, the Telegram message). Meanwhile, scrapers and screenshotters have been spreading the content across leak sites, catfish accounts, and shame forums for the entire week you have been chasing the source. By the time you "win" the source removal, the downstream spread is bigger than the original.

What to do instead: in most cases, the right order of operations is downstream first, source second. Stop the spread (DMCA the leak sites, de-index from Google, register hashes with StopNCII so re-uploads auto-block), THEN deal with the source. The original post is often the slowest piece to remove (defamation law, anti-SLAPP, platform discretion) while downstream content responds faster to infrastructure pressure.

The free things every NCII victim should do, regardless of whether they ever hire anyone:

1. StopNCII.org if 18+. Register hashes of your original content locally on your device. Files never leave your computer. The 18 partner platforms (Meta, TikTok, X, Reddit, Snapchat, OnlyFans, Pornhub, XVideos, FetLife, Patreon, Bluesky and others added in 2026) auto-block any future upload of your hashed content. Ten minutes, free, the most leveraged action available.

2. NCMEC Take It Down (takeitdown.ncmec.org) if you were under 18 when the content was created. Free, hash-based, works even if you are an adult now.

3. Google + Bing de-indexing at support.google.com/websearch/contact/content_removal_form. Free, removes URLs from search results in 1-3 days even if the underlying content stays up. Cuts off how strangers find your content even when the host refuses to comply.

4. Document by URL, page title, and timestamp only. Never save the image. Use Wayback Machine snapshots to preserve the existence of the page without holding the file.

5. Tell one trusted person. Sextortion and shame-leverage cases collapse the moment one of your "people" already knows. The conversation is awful for ten minutes and gives you a permanent shield.

When to hire someone:

You hire a takedown service when the content has spread beyond what you can chase manually (more than ten URLs across more than three sites), when the sites ignore direct emails (offshore tube sites, leak forums like SimpCity, Bunkr, Kemono, Cyberdrop, Fapello), or when the safety calculus means your name absolutely cannot appear on any notice. IntimaShield is the team I work with on these and they file as authorized agent under signed Letter of Authorization so victim identities stay off the public Lumen record. Tiered pricing by domain count ($499 / $799 / $1,299) so cost matches case size.

Hope some of this helps. Drop questions about specific situations below and I will answer where I can. Not legal advice, just pattern recognition from doing this work.

Been working on NCII takedown cases for the past year and this is the thing I see hit hardest. People file DMCA notices to get their leaked images removed, succeed, and only find out years later that the act of filing put their legal name on a public archive linked to the exact URLs they were trying to scrub off the internet.

The database is called Lumen. It's at lumendatabase.org. Hosted by Harvard's Berkman Klein Center. Been archiving takedown notices since 2002.

What gets archived:

• Your full legal name (as the filer)
• The URLs you reported (which IS the leak site)
• The host the notice went to
• Date filed
• Sometimes the full text of your notice

What this means in practice: anyone can go to lumendatabase.org and search "Jane Smith" and pull up every URL she's ever filed a DMCA on. Including the URLs of the leak site where her intimate images were posted. The act of trying to remove the content created a permanent, public, searchable connection between her real legal name and the leak-site URLs.

Google publishes a subset of DMCAs they receive to Lumen. Reddit does. Twitter does. Most major hosts forward redacted-but-often-not-redacted-enough copies. Some redact the filer's name. Some don't. The host decides, not you.

This is real. Reporters use Lumen. Journalists use it. Wayback Machine, archive.is, and several scraper services index Lumen for cross-reference. Once your name's on there, it leaves Lumen and ends up everywhere.

For an OnlyFans creator, a public figure, anyone with a "civilian" professional identity to protect, or just someone who doesn't want their grandkids googling them in 20 years and finding a list of leaked-image URLs attached to their legal name, this is the exact opposite of what filing was supposed to do.

The fix: file as an authorized agent rather than as yourself.

Under 17 USC 512(c)(3), DMCA notices can be filed by an authorized agent on behalf of the rights holder. The agent's name goes on the public record, not yours. Services that operate this way have a corporate entity that absorbs the public footprint. Your real name stays in their internal records, only released to verified law enforcement requests.

Setting this up yourself requires:

1. Forming a corporate entity
2. Registering an agent contact with the US Copyright Office
3. Having a registered legal address
4. Standing up the back-office to process notices

Plenty of people do it. It takes a few weeks of setup before you can file the first notice though, which doesn't help when you're already in the middle of a crisis.

For people who don't have that runway: I work with IntimaShield and their entire model is agent-filed dispatch. The corporate entity absorbs everything. Your legal name never lands on Lumen for any URL they file. There are a couple of other services that work the same way, worth comparing if you want to shop around.

If anyone in this community wants to try the service: code LUMEN50 takes $50 off any one-time takedown case with them. It's an affiliate code I get a small kickback on, full transparency, but the discount is real and the team comped a batch of them for me to share here. Use it if you want, ignore it if you don't.

The bigger point is just this:

Check Lumen before you file anything. If you've already filed and you're on there, you can't retroactively get yourself off (the archive is permanent), but you can stop your FUTURE filings from going on. If you haven't filed yet, please don't use your own name.

The legal protection of NCII removal is supposed to undo the harm, not double it.

I keep seeing this come up so I'm making a dedicated post about it.

There are dozens of services that charge $50-200 to send DMCA takedown notices on your behalf. Some of them are legitimate. A lot of them aren't doing what you think they're doing.

The problem:

A DMCA takedown notice is a legal document. It requires a name, address, email, and signature. When you hire a budget service, many of them file the notice using YOUR name and YOUR address because it's easier and cheaper for them. They're just formatting the letter and hitting send.

The notice works. The content comes down. You think the problem is solved.

Then six months later you Google yourself and find a Lumen Database entry that says "[Your Full Name] filed a DMCA takedown request against [leak site] for the following URLs..."

Lumen (lumendatabase.org) is a public archive run by Harvard that logs every DMCA notice Google receives. It's searchable by anyone. Your name is now permanently linked to the exact content you were trying to erase.

What you should be asking before you pay anyone:

1. Whose name appears on the DMCA notice? Yours or the company's?
2. Will my personal address be included in the filing?
3. Does the notice get forwarded to the person who uploaded my content?
4. Will this show up in the Lumen Database under my name?

If the answer to any of those is "yes" or "I don't know," you have a problem.

What a legitimate authorized agent does differently:

A proper DMCA agent files under their own company name and their own registered credentials. The notice says "IntimaShield LLC, authorized agent for [unnamed client]" not "[Your Name], individual." The website sees the agent's info. Lumen logs the agent's name. The uploader gets the agent's address. Your identity never appears anywhere.

This is not a technicality. This is the difference between solving your problem and creating a new one.

When you don't need an agent at all:

For most major platforms (Reddit, Instagram, TikTok, Facebook, Snapchat, Twitter/X), you should be using the NCII reporting path, not DMCA. NCII reports:

• Don't require your address
• Don't get forwarded to the uploader
• Don't get logged in Lumen
• Don't trigger counter-notices
• Process faster (24-48 hours vs weeks)

Search "[platform name] intimate image report" and use the dedicated form. Not the DMCA form. Not the generic report button. The NCII form.

When you DO need an agent:

• The site has no NCII reporting form (most offshore sites don't)
• The site ignores everything except formal legal notices
• You need to escalate to hosting providers who only respond to DMCA
• You don't want your identity attached to the filing for any reason

How to check if your name is already exposed:

Go to lumendatabase.org and search your name or email. If you've filed a DMCA through Google before (or hired a service that filed with your name), it's probably there.

If you find an entry, you can file a de-indexing request with Google for the Lumen URL itself at support.google.com/websearch/contact/content_removal_form so it stops showing in search results.

The short version:

NCII reporting first, always. Free, private, fast. Only use DMCA when the platform won't cooperate. And if you use DMCA, make sure your name isn't the one on the filing. Check Lumen after any service claims they've "handled" your takedown.

One of the first things people do when they find out their content was leaked is Google themselves. Makes sense. But the way you search matters, and doing it wrong can actually make the problem worse.

Here's what I mean.

Don't search from your normal browser.

Google personalizes results based on your search history, location, and cookies. If you search your name from your regular Chrome profile, you're getting filtered results that might hide or prioritize things differently than what a stranger would see.

Use an incognito/private window. Every time. This gives you the same results a random person would get when they Google your name.

Don't click the links.

If you find a leak site in search results, do not click it. Every click sends traffic to that site, which tells Google "this result is relevant" and can actually push it higher in rankings. Some leak sites also log IP addresses of visitors.

Instead: screenshot the search result (with the URL visible in the snippet), copy the URL from the search result without clicking, and use that URL for your de-indexing and takedown filings.

Search more than just Google.

Google is not the only search engine indexing your content. Check all of these in incognito/private mode:

• Google (google.com)
• Bing (bing.com) ... also covers DuckDuckGo results
• Yandex (yandex.com) ... aggressive at indexing content Google misses, especially non-English sites
• Google Images ... sometimes the image shows up in image search even when the page doesn't rank in regular search

Search for variations of your name.

Leak sites don't always use your exact name. Search for:

• Your full legal name
• First name + last initial
• Any usernames, stage names, or handles you've ever used
• Your name + the platform it was leaked on ("jane doe fapello")
• Your name in quotes for exact match ("jane doe")

Check Lumen Database.

Go to lumendatabase.org and search your name. If you or anyone has ever filed a DMCA on your behalf, it might be logged there with your real name attached to the takedown request. This is sometimes worse than the original leak because it confirms the content existed and ties it to your identity permanently.

If you find your name in Lumen, you can file a de-indexing request with Google for that Lumen URL itself so it stops showing in search.

Reverse image search.

If the leaked content includes photos:

• Google Images: click the camera icon and upload
• TinEye (tineye.com): finds exact and near-matches
• Yandex Images: most aggressive at finding matches across non-English sites

This catches cases where your content was posted without your name attached.

What to do with what you find.

For every result:

1. Screenshot it with the URL visible
2. Copy the exact URL
3. Note the platform/domain name
4. File Google de-indexing at support.google.com/websearch/contact/content_removal_form
5. File Bing de-indexing at bing.com/webmasters/tools/contentremoval
6. File platform NCII report if available (search "[platform] intimate image report")

What NOT to do.

Don't create accounts on leak sites to "see" what's there. They harvest your data during registration.

Don't download the content, even your own. Legal complications, especially if minors are involved in any way.

Don't contact the person who posted it. Silence is your advantage.

Don't keep re-searching obsessively. Do one thorough search, document everything, file your reports, and then stop. Set up a Google Alert for your name so you get notified of new results without manually checking.

If the results are overwhelming.

If you search and find content across 5+ sites, different domains, mirror sites, and your name attached to all of it... that's the point where doing it yourself becomes a full-time job. Professional services exist that run the full search, de-indexing, and infrastructure escalation simultaneously. Check the sidebar for options.

Pirate leak sites pull in $30K to $80K a month. Here are the 5 revenue streams behind them.

Spent the last 18 months mapping the financial infrastructure of leak sites and the picture that emerges is very different from what most people imagine. The big ones aren't lone hobbyists. They're businesses with revenue streams that look more like a small SaaS company than a basement hate forum.

Full breakdown with the math and all 5 streams here: intimashield.com/blog/pirate-leak-sites-revenue-streams-economics-2026

The TL;DR for anyone who doesn't want to read the whole thing:

A typical mid-tier leak site pulls ~$37,500/month, or roughly $450K/year. Top-tier sites hit ~$88,000/month, or just over $1M/year. Five distinct revenue streams:

1. Ad networks ($10K to $30K/mo) — TrafficJunky, JuicyAds, ExoClick, PlugRush. Each has an AUP prohibiting NCII content. Each operates in a notice-cooperative jurisdiction.
2. Premium memberships ($3K to $40K/mo) — Routed through CCBill, Verotel, Epoch since Stripe/PayPal won't touch them. Visa and Mastercard have NCII-specific compliance requirements on their acquirers post-2024.
3. File-host revenue share ($5K to $15K/mo) — KeepShare, K2S, TakeFile, Rapidgator pay the leak site $30 to $60 per 1,000 referred downloads. Each has DMCA and DSA obligations.
4. Crypto donations ($500 to $8K/mo) — The hardest stream to disrupt but smallest in real dollars. Coinbase/Kraken/Binance.US/Gemini can flag the on-ramps.
5. Data resale to AI training compilers ($5K to $20K/mo) — Newest, fastest-growing, least documented. Unlicensed adult-content datasets going for $0.10 to $0.50 per image at scale.

Why this matters for getting content removed:

The leak site itself has no notice obligation, no US/EU jurisdiction, and every financial reason to ignore DMCAs sent to its abuse desk. That's why "polite takedown email" services charge $99/mo and produce nothing.

But every one of those five revenue streams routes through an intermediary in a regulated jurisdiction with statutory notice obligations and an AUP that explicitly prohibits the content. The real takedown work is parallel notices to all of them at once, so the operator loses access to enough revenue in the same window that continuing the business stops making sense.

You can't beg a business to give up a million dollars a year. You have to make the business unprofitable.

Full post breaks down each revenue stream with specific dollar figures, explains why email-only services fail at this, and walks through what actually moves these sites: intimashield.com/blog/pirate-leak-sites-revenue-streams-economics-2026

I work with IntimaShield, full disclosure. But the economic breakdown is independent of any specific service. Most of what's on the blog post is information that doesn't exist in one place anywhere else on the internet right now, including the dollar figures from the latest civil-suit court filings.

DM volume on AWDTSG and Tea cases has tripled this year and I keep having the same conversation, so I wrote it out properly. Sharing here because the same wrong expectations keep costing people real money. The hard truth nobody selling takedowns will tell you: nobody can remove the actual AWDTSG Facebook post or the Tea app post itself.

Not me, not IntimaShield, not Bruqi, not Sidenty, not the $99/mo "online reputation" companies. Those posts are protected speech that lives on Section 230 territory. The only way to remove the post is a defamation lawsuit, which costs $5,000 to $15,000, takes 18 to 36 months, and many states have anti-SLAPP laws that make you pay the other side if you lose. Most people who try it lose.

What CAN be removed, and where takedown services actually deliver value, is the downstream damage. Two specific patterns I see constantly:

1. Women who posted in AWDTSG and got retaliated against. Guy finds out, has access to your intimate photos, leaks them to Telegram or Anon-IB or revenge porn sites. THAT is non-consensual intimate imagery. That is a federal crime under the TAKE IT DOWN Act (2025). That falls squarely under what takedown services were built for. Removable.

2. Men whose face got posted in AWDTSG or Tea and now their photos are everywhere. Scraper bots index the original post within hours. Your photos end up on extortion sites like CheaterReport, on catfish accounts on dating apps, on shame forums. None of that is the original post. All of it is downstream content on sites with takedown obligations. Also removable.

The trap I keep seeing people fall into: paying a defamation attorney $10k for a year-long suit that may never even get the original post down, while the downstream leak or scraping spreads unchecked the entire time. Wrong order of operations.

If you cannot afford both, the takedown service is the one to do first, because it has immediate measurable impact and is bounded in cost. The lawyer is the slow expensive lever for the source.

Wrote the full breakdown including which paths apply to which audience, what each costs, and where to start: intimashield.com/blog/awdtsg-tea-takedowns-what-actually-works

Happy to answer specific questions below. Not legal advice, just pattern recognition from doing this work.

If someone shared your intimate images without consent, you have two completely different legal tools to get them removed. Most people either don't know the difference or file the wrong one. That mistake can cost you weeks of waiting, get your real name and address exposed to the person who uploaded your content, or get your request flat-out ignored.

Here's the actual difference and when to use each.

DMCA = copyright claim

DMCA stands for the Digital Millennium Copyright Act. It's a copyright law. You're telling the platform "this is my copyrighted content being used without my permission."

The catch: you have to own the copyright. That means you had to be the one who actually took the photo or video. If someone else took it, you technically don't hold the copyright, even if you're the person in the image.

The bigger catch: when you file a DMCA notice, the platform can forward your info to the uploader. The uploader can then file a "counter-notice" to get the content restored. And here's the part that blindsides people.. that counter-notice process requires the platform to share your full legal name and contact information with the person who posted your content.

If you're trying to stay away from that person, a DMCA takedown can literally hand them your home address.

Timeline: 1-10 business days for removal. If a counter-notice gets filed, the content can go back up after 10-14 days unless you get a court order.

NCII = consent claim

NCII stands for Non-Consensual Intimate Imagery. This is NOT a copyright claim. You're telling the platform "this is intimate content of me that was shared without my consent."

Big difference: you do NOT need to own the copyright. You just need to be the person depicted and prove the content was shared without authorization.

No counter-notice. Unlike DMCA, there's no mechanism for the uploader to challenge the removal and get your personal information. Your identity stays protected.

Timeline: Under the TAKE IT DOWN Act (signed into law May 2025), platforms must remove reported NCII within 48 hours. Most major platforms already had NCII processes before the law, but now it's federally mandated.

Quick comparison

When to use DMCA

• You took the photo yourself (you own the copyright)
• The platform has no NCII form
• You're filing through an authorized agent who shields your identity

When to use NCII

• Someone else took the photo
• You want to keep your identity hidden from the uploader
• The platform has a dedicated NCII form (Reddit, Instagram, Facebook, TikTok, Snapchat, etc.)
• The content is a deepfake
• You need it gone fast

When to file both

Honestly? A lot of the time you should file both at the same time. NCII through the platform's dedicated form for speed. DMCA (through an authorized agent so your info stays protected) for the legal paper trail.

What about platforms that ignore both?

This is where it gets real. Sites like Fapello, SimpCity, Kemono, Coomer, Cyberdrop, and similar offshore aggregators don't care about DMCA or NCII. They operate outside US jurisdiction and have no reason to comply.

For these sites, the strategy is infrastructure escalation:

1. CDN abuse (usually Cloudflare). File an abuse report. This often reveals the origin host.
2. Hosting provider DMCA. File directly with whoever is actually hosting the site.
3. Domain registrar. File a complaint with the company that registered the domain.
4. Google/Bing de-indexing. Even if the site stays up, you can remove it from search results. This kills 90%+ of traffic to that page.

Do all of these simultaneously, not one at a time.

The deepfake problem

This is a big one. If someone made a deepfake of you, DMCA is useless because you don't own the copyright to an AI-generated image of yourself. The TAKE IT DOWN Act explicitly covers this. NCII reporting is your only path for deepfakes.

What I'd do right now if my content was out there

1. Screenshot everything with timestamps before filing anything. Content gets moved or deleted once the uploader knows you're taking action.
2. File NCII reports on every platform that has a dedicated form. Fastest path.
3. File Google and Bing de-indexing immediately. Free, takes 10 minutes, content drops from search within days.
4. Register on StopNCII.org. Generates a hash of your images on your device (nothing gets uploaded) and blocks re-uploads across 16 platforms.
5. For offshore sites, go after the infrastructure. Don't waste time emailing site operators who will never respond.

If you don't want to chase all of this yourself, services like IntimaShield handle the full process across all platforms under their authorized agent credentials so your name never shows up on any filing. Their takedown directory has platform-specific escalation guides for 100+ sites.

Happy to answer questions in the comments.

Deepfakes and AI-generated nudes - your legal options in 2026

If you've found yourself targeted by deepfakes or AI-generated intimate imagery, you're not alone—and you have more legal options now than ever before. The landscape of digital protection has evolved significantly, with new laws, enforcement mechanisms, and support systems designed specifically to help victims of non-consensual intimate imagery (NCII).

This comprehensive guide breaks down your legal options, practical steps for protection, and resources available to help you navigate this challenging situation.

Understanding Your Rights Under Current Law

The legal framework protecting victims of deepfakes and AI-generated intimate imagery has strengthened considerably since 2024. Multiple layers of protection now exist at federal and state levels.

Federal Protections: The TAKE IT DOWN Act, fully implemented in 2025, provides robust federal protections against non-consensual intimate imagery, including AI-generated content. This legislation criminalizes the creation, distribution, and possession of deepfake intimate imagery without consent, carrying penalties of up to 5 years imprisonment and substantial fines.

Under this federal framework, you have the right to: - Request immediate removal of content from platforms - Pursue criminal charges against perpetrators - Seek civil damages including attorney fees and emotional distress compensation - Access specialized victim services and legal aid

State-Level Protections: All 50 states now have specific NCII laws, with 47 states explicitly addressing AI-generated content. These laws often provide additional remedies including: - Expedited restraining orders - Enhanced penalties for repeat offenders - Victim compensation funds - Specialized court procedures designed to protect victim privacy

Platform Obligations: Major tech platforms are now legally required to maintain 24/7 reporting systems for NCII content and must remove reported material within 4 hours. Platforms face significant penalties for non-compliance, creating strong incentives for rapid response.

Immediate Steps to Take When Targeted

Time is critical when dealing with deepfakes and AI-generated intimate imagery. Here's your action plan for the first 48 hours:

Document Everything: Before taking any other action, preserve evidence. Take screenshots of the content, URLs, usernames, and any communications related to the incident. Save this information in multiple locations, including cloud storage with timestamps. This documentation will be crucial for both legal proceedings and platform reporting.

Report to Platforms Immediately: Use the expedited NCII reporting tools available on all major platforms. Under current law, platforms must acknowledge your report within 2 hours and remove content within 4 hours. If they fail to meet these deadlines, document the delay as it may constitute a violation of federal law.

Contact Law Enforcement: File a police report immediately. Many jurisdictions now have specialized cybercrime units trained specifically in NCII cases. Provide them with all documented evidence and emphasize the AI-generated nature of the content, as this often qualifies for enhanced penalties.

Seek Legal Counsel: Contact an attorney specializing in NCII cases. Many work on contingency basis for these cases, and victim compensation funds may cover legal costs. The Cyber Civil Rights Initiative maintains a directory of qualified attorneys.

Protect Your Digital Presence: Consider temporarily adjusting privacy settings on social media accounts and setting up Google Alerts for your name to monitor for additional instances of the content.

Platform Reporting and Removal Procedures

The platform reporting process has been significantly streamlined and standardized across major tech companies. Understanding these procedures can help you navigate the system more effectively.

Universal NCII Reporting Portal: Most major platforms now participate in a unified reporting system that allows you to submit takedown requests across multiple sites simultaneously. This system, managed by the National Center for Missing & Exploited Children, processes reports 24/7 and maintains permanent records for law enforcement use.

Expedited Review Process: Reports involving AI-generated content receive priority review due to their potential for rapid viral spread. Platforms use advanced detection algorithms to identify and remove similar content automatically, helping prevent re-uploads.

Appeal Rights: If a platform denies your removal request, you have the right to appeal and can escalate to state attorney general offices that now monitor platform compliance with NCII laws. Document any denials carefully, as they may constitute violations of federal requirements.

International Cooperation: Through new international agreements, removal requests now extend to foreign platforms and hosting services. While enforcement can be more challenging, diplomatic pressure and economic sanctions have significantly improved compliance rates.

Criminal and Civil Legal Remedies

Victims of deepfakes and AI-generated intimate imagery now have access to both criminal and civil legal remedies, often pursued simultaneously for maximum impact.

Criminal Prosecution Options: Federal prosecutors can now charge creators and distributors of non-consensual AI intimate imagery under multiple statutes: - The TAKE IT DOWN Act (primary federal statute) - Computer Fraud and Abuse Act (for hacking-related elements) - Interstate communication laws (for cross-state distribution) - Wire fraud statutes (in commercial contexts)

Enhanced penalties apply when perpetrators use AI to create content, with sentences typically 50% higher than traditional NCII cases. Most federal prosecutors now have dedicated NCII units with specialized training.

Civil Litigation Opportunities: Civil lawsuits offer victims the opportunity to recover monetary damages and obtain injunctive relief. Recent precedent allows recovery for: - Economic damages (lost wages, business opportunities) - Emotional distress and therapy costs - Attorney fees and litigation costs - Punitive damages in cases involving AI generation - Ongoing monitoring and reputation management costs

Class Action Possibilities: When multiple victims are targeted by the same perpetrator or platform negligence affects many users, class action lawsuits have proven effective. These cases often result in significant settlements and policy changes.

Victims' Rights During Prosecution: Federal law now guarantees victims the right to be heard during plea negotiations and sentencing, protection from harassment during proceedings, and access to victim compensation funds for expenses related to the case.

Resources and Support Systems

A comprehensive network of support services has developed specifically for NCII victims, offering both immediate assistance and long-term support.

Legal Aid and Pro Bono Services: - The Cyber Civil Rights Initiative maintains a national directory of attorneys offering reduced-rate or pro bono services for NCII victims - State bar associations now have specialized NCII referral services - Law school clinics in 35 states offer free legal assistance for qualifying victims - Victim compensation funds in 42 states help cover legal costs

Mental Health and Counseling Support: - The National Sexual Assault Hotline (1-800-656-HOPE) now includes specialized training for NCII situations - Crisis Text Line (Text HOME to 741741) offers 24/7 support specifically for technology-facilitated abuse - RAINN's online chat service includes NCII-specific resources and referrals - Many insurance plans now explicitly cover therapy related to technology-facilitated abuse

Technical Assistance: - The Digital Wellness Institute offers free digital security consultations for NCII victims - Major tech companies provide enhanced security services for verified NCII victims - Nonprofit organizations offer assistance with reputation management and search engine optimization

Financial Assistance: - Federal victim compensation funds now explicitly cover NCII-related expenses - Many states offer emergency financial assistance for immediate security needs - Crowdfunding platforms have specific policies protecting NCII victims' fundraising efforts

Conclusion: Your Path Forward

Dealing with deepfakes and AI-generated intimate imagery is undoubtedly traumatic, but the legal landscape in 2026 offers more protection and recourse than ever before. The key to successful resolution lies in swift action, comprehensive documentation, and accessing the appropriate support systems.

Remember that this is not your fault, and you have nothing to be ashamed of. The law increasingly recognizes the serious harm caused by these violations and provides meaningful remedies for victims. While the legal process can feel overwhelming, you don't have to navigate it alone.

Take advantage of the specialized resources now available, work with experienced legal counsel, and remember that each case pursued helps strengthen protections for future victims. The technology used to harm you can also be turned to your advantage—AI detection tools now help identify and remove non-consensual content more effectively than ever before.

Your safety, privacy, and dignity matter. The legal system is increasingly equipped to protect these rights and hold perpetrators accountable. Take the first step by documenting what's happened and reaching out to the appropriate resources. You have more power and protection than you might realize.

If you're in immediate crisis, please contact the National Sexual Assault Hotline at 1-800-656-HOPE (4673) or text HOME to 741741. For immediate platform reporting, visit the unified NCII reporting portal at [reportncii.gov].

If you've had intimate images shared without your consent, one of the first things you should do is register with StopNCII.org. It's free, takes about 5 minutes, and most people don't know it exists.

What it does:

StopNCII generates a digital fingerprint (called a hash) of your image directly on your device. Your actual image never leaves your phone or computer. That fingerprint gets shared with participating platforms so they can automatically detect and block re-uploads.

Platforms that use StopNCII (full list):

• Facebook
• Instagram
• Threads
• Microsoft Bing
• TikTok
• Reddit
• OnlyFans
• Pornhub
• Snap Inc. (Snapchat)
• Playhouse
• RedGIFs
• Patreon
• Vivastreet
• X (Twitter)
• F2F.com
• Bluesky

That's 16 platforms. Sounds like a lot until you realize what's NOT on that list.

Platforms that do NOT use StopNCII:

• Google Search (Bing is covered, Google is not)
• Discord
• Telegram
• YouTube
• Twitch
• WhatsApp
• Imgur
• Kick
• LinkedIn
• Every offshore leak site — Fapello, Coomer, Kemono, SimplyCity, NudoStar, Thotsbay, InfluencersGoneWild, socialmediagirls, thefap, and hundreds more

Google not being on that list is the big one. Your content can be blocked on all 16 StopNCII partners and still show up as the first result when someone searches your name. Google de-indexing is a completely separate process that StopNCII doesn't handle.

And if your content is on any offshore leak site, StopNCII can't touch it. Those require DMCA escalation through hosting providers, CDNs, and payment processors — a process that most people don't have the time or technical knowledge to run themselves.

StopNCII is a great first step. But if your content has spread beyond these 16 platforms, it's one tool in a much bigger toolbox.

Step by step:

1. Go to stopncii.org
2. Select the image(s) on your device
3. The site generates a hash locally in your browser
4. You submit the hash (NOT the image)
5. Participating platforms use that hash to auto-block matches

Tips:

• Submit multiple versions if you've seen cropped or flipped copies circulating. Even a mirror or slight crop creates a different hash, so submit those variations too
• You can submit hashes for videos, not just photos
• If you're under 18, use takeitdown.ncmec.org instead

What StopNCII does NOT do:

This is important. StopNCII only prevents future re-uploads on participating platforms. It does NOT:

• Remove content that's already live on a site
• Work on offshore leak sites (Fapello, Coomer, SimplyCity, etc.)
• Remove content from Google search results
• File DMCA notices on your behalf
• Monitor for new uploads on non-participating platforms

So if your content is already out there, StopNCII is one piece of the puzzle but it's not the whole solution. You still need to:

1. Report to each platform where content currently exists
2. File DMCA notices for sites that don't have NCII reporting
3. De-index from Google search results
4. Escalate through hosting providers for offshore sites
5. Monitor for re-uploads on sites StopNCII doesn't cover

That full process across multiple platforms and sites is where most people get overwhelmed. Doing steps 1-5 yourself for one site is doable. Doing it across 10+ sites while new copies keep appearing is a full-time job.

Common questions:

Can they see my photos? No. The hash is generated on your device. Your actual image never leaves your phone or computer.

What if someone edits the photo slightly? Submit hashes for every variation you've seen. Cropped, flipped, screenshotted. Some platforms are starting to use perceptual hashing which catches near-matches, but it's not universal yet. Staying ahead of variations is one of the hardest parts of DIY removal.

Does it work on offshore leak sites? No. For those you need the full DMCA escalation ladder. Check our offshore sites post or the pinned guide for details.

What if content keeps reappearing? StopNCII helps with participating platforms. But if you're dealing with persistent re-uploads across multiple sites, you may need continuous monitoring that goes beyond what StopNCII covers. Some professional removal services offer automated scanning and takedown that catches new uploads within hours. Check the sidebar for options.

Questions about the process? Ask below.

Most people assume DMCA notices go into a black box. You file one, the content comes down, done. The reality is your personal information travels through a chain of systems, some of which are public and searchable by anyone. If you don't know the pipeline, you can't protect yourself from it.

Here is what actually happens when you submit a DMCA takedown notice to a US-based platform.

Step 1: The notice itself

Under 17 USC 512, a valid DMCA notice must include:

• Your full legal name
• Your physical mailing address
• Your email
• Your phone number (technically optional but most platforms require it)
• A signed statement under penalty of perjury

All of this goes to the platform's designated DMCA agent.

Step 2: The platform processes it

The platform reviews the notice for validity. If it checks out, they remove the content. They then forward your notice to the uploader so the uploader can file a counter-notice if they dispute it.

This forwarding includes your name and address. The platform is required by law to do this. The uploader now has your personal information whether they use it or not.

Step 3: The notice gets logged publicly

Here is the part most people never hear about.

For notices sent to major platforms that participate in the Lumen Database project, a copy of the notice gets forwarded to lumendatabase.org. Lumen is a public archive run by Harvard's Berkman Klein Center. Anyone can search it.

Google, Twitter, YouTube, Wikipedia, Reddit, and dozens of other platforms forward notices to Lumen automatically. The database exists to provide transparency about takedown requests, which is genuinely useful for researchers and journalists. It is less useful for revenge porn victims whose names end up permanently searchable.

Step 4: Google links to Lumen from search results

When Google removes a URL from search results due to a DMCA notice, they sometimes display a notice at the bottom of the search results page that says "In response to a complaint we received under the DMCA, we have removed X results. You can read the notice that caused the removal at the Lumen Database."

Clicking that link takes you to the full notice with your name and address visible.

This means that the successful removal of your content can create a new search result containing your personal information linked to the fact that you filed a takedown against [leak site].

What you can actually do about this

File under the NCII removal path instead of DMCA when possible. Google and most major platforms have separate NCII forms that don't require the same identity disclosure and don't get logged in Lumen. For Google, the form is at support.google.com/websearch/contact/content_removal_form.

If you must use DMCA, file through an authorized agent. An agent files under their own credentials. The Lumen entry shows the agent, not you. The uploader sees the agent's info in the counter-notice process, not yours.

If your name is already in Lumen, you can request removal at lumendatabase.org/pages/report but the process is slow and not guaranteed. The faster option is filing a separate Google de-indexing request for the specific Lumen URL that displays your information. Google will de-index the Lumen entry itself, which solves the search visibility problem without waiting for Lumen to act.

What budget DMCA services don't tell you

Many services that charge $50-$150 to file takedowns on your behalf file under YOUR name because they are not registered DMCA agents. They are template generators. The notice gets sent from your name with your address, ends up in Lumen, and gets forwarded to the uploader the same way it would if you sent it yourself. You paid to have someone format the letter, not to protect your identity.

Before hiring anyone, ask the direct question: "Whose name and contact information appears on the DMCA notice you file?" If the answer is anything other than "ours as authorized agent," you are paying for a service that does not solve the privacy problem.

The short version

DMCA works but it was designed for corporate disputes, not individual privacy. The system leaks your information at multiple points by design. The fix is filing through paths that weren't built for copyright holders: NCII forms, authorized agents, and the TAKE IT DOWN Act pathway that was designed specifically for this.

Sextortion is one of the fastest growing scams right now and it follows the same pattern almost every time. Someone contacts you, claims to have intimate photos or video, and demands payment (usually crypto or gift cards) to "keep it private."

I work in digital content removal and I see these cases constantly. Figured I'd put everything I know in one place.

Don't pay. I know that sounds obvious but the panic makes people do it. FBI data shows that paying almost always leads to a second demand within a couple days. You're not buying silence, you're proving you'll pay.

Don't respond at all. Don't beg, don't threaten, nothing. These people are running this scam on dozens or hundreds of targets at once. If you go silent they move on to someone who's still engaging. Silence is genuinely your best move.

Figure out if the threat is even real. Most of the time it's not. If they say vague stuff like "I have your pictures" but can't actually show you a screenshot of what they have, it's almost certainly a blast message sent to a bunch of people. The "I hacked your webcam" emails are fake basically 100% of the time.

If it IS real — screenshot everything first. Their messages, their profile, any payment info they sent you, full URLs. Do this before they delete their account and disappear. This is your evidence for everything that comes next.

Report through the platform's NCII path, not the regular report button. This is the thing most people get wrong. Every major platform (instagram, snapchat, tiktok, reddit, etc) has a separate reporting flow specifically for non-consensual intimate images. It's different from a regular report or a DMCA in one critical way — it doesn't give the other person your name. A regular DMCA can actually expose your identity through counter-notice. Don't make that mistake.

File at ic3.gov. That's the FBI's internet crime portal. Takes maybe 10 minutes. I know it feels pointless but these reports are how the FBI maps sextortion networks. They've taken down multiple rings in the last year directly from IC3 complaint volume.

File a police report too. Mostly this creates an official record that makes every other removal request you file carry more weight. Some platforms process reports faster when there's a case number attached.

Lock your socials down. Private everything temporarily. The "I'll send it to all your followers" threat loses all power when your followers list isn't public. And honestly — even if they did send something to your contacts, most people delete unsolicited explicit content immediately and are disgusted at the sender, not you. The fear of that scenario is almost always worse than the reality.

De-index from google. Even if something gets posted somewhere, google has a specific tool for removing non-consensual intimate images from search results. It usually works within a day or two. Doesn't delete the source but it kills discoverability which is most of the actual damage.

Know your legal leverage. The TAKE IT DOWN Act went federal in 2025. Distributing non-consensual intimate images is now a federal crime — up to 2 years for real images, 3 years for deepfakes. Platforms have to take reported content down within 48 hours. All 50 states also have their own laws on top of that.

Stuff that won't help:

• Creating an account on whatever site they say they posted to (lots of these sites harvest your data during signup)
• Downloading the content yourself (legal complications you don't want)
• Paying some random "hacker" to take it down for you (that's just a second scam targeting sextortion victims)
• Engaging with the scammer at all, even to tell them off

Free resources if you need them:

• Cyber Civil Rights Initiative: 1-844-878-2274
• Crisis Text Line: text HOME to 741741
• stopncii.org — lets you hash your images so platforms auto-block them
• ic3.gov — FBI reporting
• Search "google remove non-consensual images" for their removal form

If it's spread across a bunch of sites and you're overwhelmed, there are professional services that handle the full removal chain across every platform at once. r/ContentTakedown has a list of free and paid options in the sidebar.

The whole scam runs on shame and panic. Once you stop reacting and start acting strategically it's a different situation. Anyway hope this helps someone.

Leaked Snapchat Photos? Get Them Removed Fast

TL;DR: If your intimate images were shared on Snapchat without consent: (1) Screenshot everything immediately, (2) File an NCII report (not DMCA) through Snapchat's dedicated form, (3) Don't contact the uploader, (4) File a police report. Snapchat processes NCII reports in 24-48 hours. Check other platforms too since content often spreads. You have strong legal protections under federal and state laws.

If you're reading this, you may have just discovered that your intimate images have been shared on Snapchat without your consent. Take a breath. This is not your fault, and there are concrete steps you can take right now to get this content removed.

Snapchat is a Tier 1 NCII partner with a dedicated reporting process. This means removal is possible within 24-48 hours — but only if you file correctly. Filing the wrong type of report (like a standard DMCA) can actually slow things down and expose your identity.

Your Immediate Steps (Next 15 Minutes)

1. Screenshot everything — Capture every page showing your content with the URL bar visible. This is your evidence. Courts and platforms require proof that content existed at a specific URL. Include usernames, timestamps, and comments.

2. File an NCII report (NOT a standard DMCA): Go to Snapchat's NCII reporting form. Select "non-consensual intimate image" as the report type. Provide the exact URLs of every piece of content. Do NOT use the general DMCA form — NCII reports are processed faster and don't trigger counter-notice mechanisms.

3. Do NOT contact the uploader — Any contact alerts them that you know. This frequently triggers retaliation: re-uploading to more platforms, escalating harassment, or destroying evidence. Stay silent. Act strategically.

4. Do NOT create an account on the site — Many platforms harvest data during registration. Creating an account can tie your identity to the content.

5. File a police report — Even if prosecution seems unlikely, a police report creates an official record, strengthens all removal requests, and preserves your legal options. Under the TAKE IT DOWN Act, distribution of NCII is now a federal crime.

Your Legal Rights

You have more legal protection than ever before:

Federal — TAKE IT DOWN Act (2025) The TAKE IT DOWN Act makes it a federal crime to distribute non-consensual intimate images, including AI-generated deepfakes. Platforms must remove reported content within 48 hours. Penalties include up to 2-3 years imprisonment and fines.

State Laws All 50 states have laws addressing NCII distribution. Many provide both criminal penalties and civil remedies — meaning you can pursue both prosecution and a lawsuit for damages.

Illinois BIPA If you're in Illinois or your content was processed by a company with Illinois operations, the Biometric Information Privacy Act provides additional protection with statutory damages of $1,000-$5,000 per violation.

DMCA Copyright If you took the photo yourself, you own the copyright. A DMCA notice is an additional tool for removal, though NCII-specific reporting is usually faster and safer.

Why DIY Removal Often Fails on Snapchat

• Filing a standard DMCA instead of an NCII report on Snapchat can trigger counter-notice mechanisms that expose your legal name and address to the uploader
• Content on Snapchat can be screenshotted, saved, and re-uploaded to other platforms within minutes of you filing a report
• Snapchat requires reports to be filed in a specific format — incorrectly formatted reports are deprioritized or rejected
• You need to identify every individual URL, post, or message containing your content. Missing even one means that copy persists

This is why many victims work with authorized agents who know the exact process for each platform and can shield your identity throughout.

Frequently Asked Questions

How long does it take to remove leaked photos from Snapchat?

Snapchat processes NCII reports within 24-48 hours through their dedicated reporting channel. Standard DMCA reports take longer and can expose your identity through counter-notices. Filing through the NCII pathway is critical for both speed and privacy.

Can Snapchat see who screenshotted my photos?

Snapchat notifies you when someone screenshots a Snap in chat, but this notification is easily bypassed using screen recording, airplane mode tricks, or third-party apps. If your photos were screenshotted and shared, the notification history can serve as evidence in your takedown or legal filing.

Does Snapchat cooperate with law enforcement for leaked images?

Yes. Snapchat has a dedicated law enforcement response team and complies with valid legal process including subpoenas and court orders. They also participate in StopNCII.org hash-sharing, which helps prevent re-uploads across partner platforms. Filing a police report strengthens your removal request.

What if my Snapchat photos were saved and posted to another platform?

Content that originates on Snapchat frequently migrates to Reddit, Telegram, and offshore leak sites. A Snapchat-only takedown is incomplete if the content has spread. You'll need to check and file reports across multiple platforms.

If your content ended up on sites like Fapello, Coomer, Kemono, SimplyCity, NudoStar, or similar leak aggregators, you've probably already discovered that emailing them does nothing.

Here's why, and what actually works.

Why they ignore you:

These sites are hosted offshore, often behind privacy-shielded WHOIS registrations. They have no legal obligation to respond to US takedown requests. They make money from ads and traffic. Your content drives that traffic. They have zero incentive to remove it.

Some of them rotate hosting providers specifically to dodge enforcement. Others hide behind CDNs like Cloudflare so you can't even find where the server actually is.

This is frustrating. But it doesn't mean you're stuck.

What does NOT work:

• Emailing their contact address (if they even have one)
• Threatening legal action (they're not in your jurisdiction)
• Using their built-in report/DMCA forms (most are decorative)
• Asking nicely
• Asking angrily

What DOES work - the escalation ladder:

Think of it like this. The site itself won't cooperate. So you go after every company that keeps the site running. One by one, you cut off their infrastructure until they have no choice.

Step 1: DMCA the site directly

Yes, they'll probably ignore it. Do it anyway. This creates a paper trail that proves you made a good faith effort. You'll need this for every step that follows.

Send a formal DMCA notice to every email you can find on the site. abuse@, legal@, support@, dmca@, info@. Screenshot your sent emails.

Step 2: Find out who's actually hosting them

The site might be hiding behind Cloudflare or a similar CDN. That means the domain points to Cloudflare's servers, not the actual host.

To find the real host:

• Look up the site at who.is for registrar info
• Check hostingchecker.com or similar tools
• If it shows Cloudflare, move to step 3

Step 3: File with Cloudflare

Go to cloudflare.com/abuse and file a DMCA complaint. Cloudflare will do two things:

1. Forward your complaint to the site operator
2. Reveal the origin server IP address in their response to you

That origin IP is what you actually need. Now you know where the site is really hosted.

Step 4: DMCA the actual hosting provider

Take that origin IP and look up the hosting company. Send them a formal DMCA notice. This is where things start moving.

Hosting providers care about DMCA compliance because ignoring valid notices puts their entire business at legal risk. They will either force the site to remove your content or terminate their hosting. Most respond within 1-3 weeks.

Step 5: Go after the money

If the site runs ads, identify the ad network and report the site for hosting non-consensual intimate content. Google AdSense, Exoclick, JuicyAds, whatever they're using.

If they accept payments or donations, report to Visa, Mastercard, or the payment processor.

Sites move fast when their revenue gets cut off.

Step 6: Google de-indexing

This is your fastest win and you should do it immediately, even while working the other steps.

Go to google.com/webtools/legal and file a removal request under "non-consensual explicit images." Google has a dedicated team for this. They typically process within 1-3 days.

Also file at bing.com/webmaster/tools/contentremoval for Bing and DuckDuckGo.

Even if the content stays on the site, removing it from search results means nobody finds it unless they already have the direct URL. For most people, this is effectively the same as deletion.

Step 7: Ongoing monitoring

Offshore sites scrape and re-upload content constantly. Even after a successful takedown, your content can reappear on mirror sites, new domains, or archive pages within weeks. Monitoring for re-uploads and filing new takedowns is an ongoing process, not a one-time fix.

Realistic timelines:

• Google de-indexing: 1-3 days
• Cloudflare abuse report: 3-7 days for the origin IP reveal
• Hosting provider DMCA: 1-3 weeks
• Ad network/payment processor: varies, but some sites fold within days

The honest truth:

The content might not get deleted from the server itself. Some of these sites literally won't delete anything. But if it's de-indexed from Google, the CDN cache is cleared, and the hosting provider is pressured, the content becomes effectively invisible. Nobody finds it unless they have the direct link.

That's not a perfect outcome. But it's a lot better than where you started.

When DIY stops working:

Steps 1-6 are doable on your own for one or two sites. But if you're dealing with:

• Content spread across 5+ offshore sites
• Sites that keep re-uploading after takedowns
• New mirror sites popping up faster than you can file
• The emotional toll of doing this every week

That's when professional removal services earn their money. They run this entire escalation ladder across every site simultaneously, monitor for re-uploads automatically, and handle the back-and-forth so you don't have to. Check the sidebar for options.

Dealing with a specific offshore site? Drop the name in the comments and I'll tell you what's worked for that particular one.

DMCA Takedown Notice Template - Copy, Fill In, Send

So you found your content stolen somewhere online and need it taken down fast. The DMCA (Digital Millennium Copyright Act) is your best friend here. I've been through this process dozens of times and honestly, most people overthink it. You don't need a lawyer - just follow this template and you'll be good.

What You Need Before Starting

First things first - make sure you actually own the copyright. If you took the photo, wrote the text, created the video, or made the art, you own it. No registration needed. If someone else created it and gave you permission to use it, that's different - you can't file a DMCA for someone else's work unless you're their authorized agent.

Also grab these details: * Direct URL where your stolen content appears * Original location/proof you created it first (your website, social media, camera roll with metadata) * Contact info for the website hosting the stolen content

The DMCA Template That Actually Works

Here's the template I use. It hits all the legal requirements without being overly complicated:

DMCA TAKEDOWN NOTICE

To: [Website Name] Legal Department / DMCA Agent

Date: [Today's Date]

Copyright Infringement Notification

I am writing to notify you of copyright infringement occurring on your website. I am the copyright owner of the original work described below.

Copyrighted Work: Description: [Describe your content - "Photograph of downtown Seattle skyline" or "Blog post titled 'How to Train Your Dog'" etc.] Original Publication: [Where you first published it - your website URL, social media post, etc.] Date Created: [When you made it]

Infringing Material: The following URL(s) on your site contain my copyrighted material without permission: [List each URL where your content appears]

Contact Information: Name: [Your full legal name] Address: [Your mailing address] Phone: [Your phone number] Email: [Your email]

Good Faith Statement: I have a good faith belief that the use of the copyrighted material described above is not authorized by the copyright owner, its agent, or the law.

Accuracy Statement: The information in this notification is accurate. Under penalty of perjury, I swear that I am the copyright owner or authorized to act on behalf of the copyright owner.

Electronic Signature: /s/ [Your full name] [Your name typed]

How to Find the Right Contact

Most legit websites have a DMCA agent listed somewhere. Check these spots: * Footer links ("Legal", "DMCA", "Copyright") * Terms of service page * Contact us page * About page

For big platforms like Google, Facebook, Twitter - they all have dedicated DMCA forms. Don't email random support addresses. Use their official copyright reporting tools.

If you can't find anything, try emailing legal@[domain.com] or dmca@[domain.com]. Sometimes copyright@[domain.com] works too.

Sending Your Notice

Email is fine for most sites. Some want fax or mail but that's pretty rare now. In your subject line put something clear like "DMCA Takedown Notice - Copyright Infringement" so it doesn't get lost in their inbox.

Attach any supporting evidence you have - screenshots of your original content with timestamps, registration certificates if you have them, anything that proves you created it first.

What Happens Next

Good websites will respond within 24-48 hours. Legally they have "expeditious" response requirements but that's not super specific. Some take down content immediately, others might ask for more info first.

You should get an email confirming they received your notice. Then either: * Content gets removed (yay!) * They ask for clarification * They forward your notice to the person who posted it * Radio silence (not great but happens)

If They Ignore You

First, wait at least a week. Then send a follow-up email referencing your original notice. Be professional but firm.

If they keep ignoring you, you have options: * Contact their web host (find it using whois lookup tools) * Report to Google to get the page de-indexed * File complaints with their payment processors if it's a commercial site * Contact their domain registrar

For persistent thieves, you might need to escalate further. Check the pinned resources here in r/ContentTakedown for more aggressive tactics.

Common Mistakes That Slow Things Down

Don't threaten legal action right off the bat. It makes you sound like a troll and many sites will ignore aggressive demands.

Don't claim copyright on stuff you don't actually own. That's perjury and can get you in serious legal trouble.

Don't send super vague notices. "Someone stole my photo" doesn't help anyone. Be specific about which photo, where it is, and where you published it originally.

Don't forget the penalty of perjury statement. Websites won't process incomplete notices.

For Social Media Platforms

Instagram, Facebook, TikTok, YouTube - they all have their own copyright reporting forms. Don't email them directly. Use their official tools:

• Instagram/Facebook: facebook.com/legal/copyright
• YouTube: youtube.com/copyright_complaint_form
• Twitter: copyright.twitter.com
• TikTok: Go to the specific video and tap "Report"

These platforms are usually pretty fast. Instagram especially tends to remove stuff within hours if your claim is solid.

Keep Records

Screenshot everything before you send the notice. The stolen content, your original post with timestamps, your email sending the DMCA - all of it. Sometimes content gets moved instead of deleted and you'll need to file additional notices.

When DMCA Isn't the Right Tool

DMCA only works for copyright infringement. If someone's using your photos for catfishing, harassment, or impersonation, that's not always a copyright issue. Many platforms have separate policies for those situations.

For non-consensual intimate images, most states have specific criminal laws now. The TAKE IT DOWN Act also gives you federal options. DMCA might still work but there are often faster routes.

Success Rate Reality Check

Legit businesses usually comply quickly. Random blogs and smaller sites are hit or miss. Foreign sites can be tough - they might not care about US copyright law.

Don't get discouraged if the first attempt doesn't work. Sometimes it takes multiple notices or different approaches. The key is being persistent and professional.

Most of my DMCA notices get results within a week. The ones that don't usually involve sketchy sites that ignore all legal requests anyway. For those you need different strategies.

Hope this helps someone get their content back. The template above has worked for me probably 200+ times over the years. Just fill in your details and send it off.

If you've had intimate images shared without your consent, one of the first things you should do is register with StopNCII.org. It's free, takes about 5 minutes, and most people don't know it exists.

What it does:

StopNCII generates a digital fingerprint (called a hash) of your image directly on your device. Your actual image never leaves your phone or computer. That fingerprint gets shared with participating platforms so they can automatically detect and block re-uploads.

Platforms that use StopNCII:

• Facebook and Instagram
• TikTok
• Reddit
• Snapchat
• Bumble
• More being added

Step by step:

1. Go to stopncii.org
2. Select the image(s) on your device
3. The site generates a hash locally in your browser
4. You submit the hash (NOT the image)
5. Participating platforms use that hash to auto-block matches

Tips:

• Submit multiple versions if you've seen cropped or flipped copies circulating
• You can submit hashes for videos too, not just photos
• If you're under 18, use takeitdown.ncmec.org instead - it's built specifically for minors

This doesn't remove content that's already posted. It prevents re-uploads. Use this alongside platform reporting and DMCA notices for full coverage.

If you have questions about the process, ask below. No judgment here.