Preserve, don't spread.
Keep a private record without forwarding or reposting intimate content itself.
Crisis boundary — start with a person
This was done to you. The next move should be confidential, calm, and held inside the right boundary: what to preserve, what to keep out of forms, when official boundaries apply, and when a human should open the client record.
Adults (18+) only — if this involves someone under 18, go straight to the referral box.
Sensitive boundary
Private case review, file-light.
Adult intimate-image, AI-nude, leaked-photo, and sextortion situations stay out of upload and checkout flows. A person can start from a minimal private summary.
Keep a private record without forwarding or reposting intimate content itself.
Adult intimate-image and sextortion cases stay in private case review, away from forms, uploads, and card-first flows.
A human confirms what belongs in a client record before AboutUs work begins.
Repeat exposure belongs inside the client record, not the public guide.
Safety confidence record
The premium part is accountability. It is turning a scattered trail into a written record, naming the limits, and keeping AboutUs work behind a written boundary.
The first read can start without publishing the operating detail or sending the intimate file.
Visible page, account, repost, receipt, and search result stay organized without reposting the file.
The written boundary, limits, and client terms stay in the client record.
Timing, platform response, source control, and re-upload risk stay visible instead of being sold as certainty.
Assessment decision packet
The first useful answer is not a sales pitch. It should separate route boundaries, source status, search exposure, excluded items, and anything that belongs with public authorities or outside help.
Official tools, platform reports, and safety referrals are named before AboutUs work when they fit the situation.
Items are sorted into written boundaries before a service agreement: what can be reviewed, what is excluded, and what needs a safer route.
The client record holds the private proof summary so the public page does not become the operating file.
Eligible AboutUs work gets written intended outcomes and refund terms. Sensitive matters do not start with upload or checkout.
For intimate-image, AI-nude, or sextortion matters, the safe path is live help first. Start with a minimal private summary; keep the sensitive file out of public and payment-first flows.
Trusting someone with intimate images was never permission to share them. When an ex or anyone else posts them to humiliate, control, or punish you, the crime is theirs — and most U.S. states, plus federal law, treat it that way. The shame belongs to the person who did this, not to you.
You don’t have to identify them, confront them, or prove your case to start a removal. A serious review acts on accountable surfaces and search exposure — not on you.
A public page should keep you safe and get you to the right door. It should not expose what belongs inside the confidential client record.
Don’t reply, beg, or threaten back. If there’s a demand for money, don’t pay — it confirms you’re reachable and the demands usually continue.
Keep a private surface summary. Don’t forward or repost the content itself; the operating detail belongs in the client record.
Start the private case online with one safe public pointer. Stripe opens a file-light case room and keeps AboutUs work behind a written boundary.
Before any form
Revenge-porn cases are rarely one clean report. The same situation can include a threat, a live post, a search result, a hacked account, and support needs. The first read gets cleaner when each surface has its own evidence line and boundary label.
The sensitive file itself is not needed for a first human read. A minimal private summary is enough.
If anyone was under 18 when the image was made, taken, or shared, this is not commercial work. Use NCMEC options.
Go to NCMEC referralUse private case review before any form, upload, or card authorization. A file-light read is enough to begin.
Official safety, child-protection, covered-service, regulator, law-enforcement, search, and support boundaries stay visible before AboutUs work.
Open verified logImage-based abuse can be destabilizing. Crisis, survivor, and confidential support options can run alongside takedown work.
Open support optionsR01
A minimal private summary of where the copy appears.
Do not reply, threaten back, forward the image, or upload the sensitive file into a commercial form.
Relevant policy or covered-service boundary first; the client record separates written scope, search exposure, support, and client updates.
R02
A private threat summary and any visible surface at a high level.
Do not pay, bargain, send another image, or move the conversation to a new private channel.
Private case start for the removal boundary, plus cybercrime reporting where coercion is involved.
R03
A private account/surface summary and any official result already created.
Do not delete the account or conversation before preserving the trail you may need for reports.
Account-security, policy, source, and search boundaries stay separated before any AboutUs scope is set.
R04
Search result, source locator, query context, screenshot of the result, and any search-engine receipt.
Do not confuse de-listing with deletion. Search removal can hide a result while the source copy remains live.
Google personal sexual content removal as a search fallback while source and policy options stay separately labeled.
R05
Known identical copies, surface labels, prior report receipts, and response states kept privately.
Do not collapse every surface into one generic abuse report or assume a search result means the source is gone.
Repeat exposure stays in the client record, with each live copy labeled separately.
R06
A short list of trusted contacts, any police report number if you choose to file, and support notes.
Do not carry the whole situation alone or let a commercial service replace crisis, survivor, or legal support when you need it.
CCRI, RAINN, 988, local victim services, or legal counsel can run alongside removal work without sending sensitive files to AboutUs.
Adult NCII and sextortion facts stay in private case review. The public page sets boundaries; case-specific handling stays in the client record. Minor-involved imagery moves to NCMEC and law enforcement, never commercial work.
Use safety checkpointCommercial discipline
NCII cases get messy fast: source, threat, search, repost, account security, official record, and support can all be true at once. The public page keeps the person safe; the client record keeps the work owned.
It shows the age stop, sensitive-file rule, official boundaries, support boundary, and search-versus-source limit without exposing what belongs behind authorization.
Reviewed surface, intended outcome, exclusions, client updates, support boundary, and receipt stay in the client record.
Adult NCII and sextortion facts move through private case review from a minimal private summary, not uploads or card-first flows.
Client-only record
Owner notes
Client-update terms
Search fallback posture
Support boundary
Client-only receipt
Non-consensual intimate images are covered by the federal TAKE IT DOWN Act, which sets a 48-hour removal obligation for covered platforms after a valid victim notice, and by non-consensual image laws in most states. Most people need the boundary, a clean evidence trail, and a human who can review the client record without pulling the sensitive file into commercial intake.
If the images keep reappearing, the next-step record belongs in the client record, not on the public page. Search de-listing is a fallback when content cannot yet be deleted at the source — never a substitute for taking it down.
That is the difference between this and a random leak, and it changes three things. It changes what evidence is worth keeping, because the account, the messages around the post, and the timing all matter later in a way they do not when the source is anonymous. It changes the reporting path, because most state non-consensual image statutes turn on whether the person knew the images were private — which is usually provable when it is an ex. And it changes what you should not do first, which is contact them.
Keep
Do not
Contacting the person who posted it is the one move that reliably makes the situation worse. It tells them the post is working, it gives them a reason to repost somewhere you have not found yet, and in a criminal matter it can be read as the two of you working it out privately. A platform report and a written record do the same job without handing them anything.
We do not contact the person who posted it either, and we do not offer to. Removal here is aimed at the platform’s own rules and at the legal boundary, not at the poster. If what you actually need is a protective order or a criminal report, that belongs with a lawyer or the police, and we will say so rather than sell around it — AboutUs is a removal agency, not a law firm, and this page is not legal advice.
Before AboutUs work
For intimate images posted to punish, threaten, or control you, start with safety, preservation, and official boundaries while the client-record detail stays sealed.
Official boundaries create the first safety record. AboutUs belongs only when the matter needs accountable client-record review after official or free lines are known. The public page names the boundary; the private decision stays inside the record.
Adults can use StopNCII for participating services. If anyone was under 18 when the image was taken, use NCMEC Take It Down and CyberTipline instead.
Check boundaryThe 48-hour federal removal window is a legal standard, not an AboutUs promise. The client record carries whether the standard fits the written boundary.
Check local standardOfficial outcomes can support the written record. What AboutUs owns stays inside the client record.
Check failure optionThe public page names official and free boundaries. The written boundary belongs inside the client record.
See boundary linesSafety record
Bring the boundary, not the content. A human can open the safety line from a minimal private summary.
We don’t make guarantees, and we won’t pretend a fallback is a removal. Our core work is results-based: for eligible cases we accept, the terms — including the written item, intended outcome, search-exposure limits if any, and refund term — are defined in your written service agreement. We tell you up front what’s realistically removable and what isn’t. We’re a removal agency, not a law firm; if your situation needs a lawyer, we’ll say so and coordinate or refer. The public page shows the boundary; the AboutUs client record contains the written boundary, client updates, and outcome labels.
REPRESENTATIVE SCENARIO — composite of typical engagements, anonymized. Individual results vary; eligibility and any results-based terms are defined in your written service agreement.
After a breakup, intimate images are posted to a forum under the victim’s name and spread through reposts. The source context, receipts, support needs, and search exposure are documented privately; the case record stays inside the client record, with source status and search fallback labeled plainly.
We work with adults (18+) only. If intimate images of someone under 18 are involved, report it immediately to the NCMEC CyberTipline at report.cybertip.org, use NCMEC's Take It Down at takeitdown.ncmec.org, and contact local law enforcement. Do not send the content to anyone — including us.
Common questions
Related: leaked photo removal · AI / deepfake nude removal
You do not have to handle this alone.
Confidential next step
Choose the situation, send one safe public pointer, and authorize a written scope online. Keep the sensitive file out of the case record.
Client record check · Confidential · Adults 18+ · Sensitive file stays out
Adult intimate-image, AI-nude, and sextortion situations stay in private case review. Start with a minimal private summary.
StopNCII, NCMEC, platform reports, FTC platform-failure reporting, and IC3 stay visible when they fit. The AboutUs client record adds coordination, persistence, follow-up, and documented handoff where those boundaries stop.
Open safety deskThe TAKE IT DOWN Act is a legal request path for valid notices to covered platforms, with FTC reporting when the platform process fails. It is not a blanket outcome promise.
Read the statute explainer