Boundary proof
Official tools and hotlines stay visible as trust and safety boundaries.
Boundary first
If intimate images were shared without consent, you’re being sextorted, or you’re being harassed online, use this desk to identify the right safety line and preserve the boundary record. The page intentionally stops before the private decision, client notes, and client receipt; those belong inside the confidential client record when the official route cannot resolve the gap.
This page is education, not legal advice. We are a removal agency, not a law firm; for advice on your specific situation, consult an attorney — or start with the written boundary check and we'll tell you honestly what your case needs.
Boundary proof
Official tools and hotlines stay visible as trust and safety boundaries.
Boundary limits
The public page names ceilings without exposing the client-specific answer.
Safe handoff
Sensitive cases start with a minimal private summary and a human channel.
Situation triage
The right path depends on what happened, who is involved, and whether the urgent issue is safety, search exposure, or a live surface. Start here, then use the verified safety log only where it proves the boundary.
Source check: June 30, 2026. External programs can change; their official pages are the source of truth.
View safety recordVisible boundary, client record
Official boundaries stay visible so safety and trust are checkable. The client-work detail stays in the AboutUs client record once work is authorized.
This page names the official owners, safety exits, and hard limits a client should be able to check before handoff.
Client-record work, status, correspondence, and client receipt stay inside the AboutUs client record, not on a public resource page.
Clients get the record that matters: what was received, what remains visible, what is outside the boundary, and what needs an accountable owner.
Client record owner receipt
The public page can show the official boundary. The AboutUs client record carries the private decision, accountable owner, written terms, and client-only receipt.
ANSWER
Open, referred, held, or stopped is written before work starts.
OWNER
The client record turns a pile of tabs into one accountable workstream.
TERM
Reviewed item, intended outcome, refund posture, and exclusions are written down before authorization.
RECEIPT
The closeout label, remaining visibility, and next boundary stay inside the client record.
Boundary discipline
A resource hub should prove safety without becoming the operating manual. The visitor gets the official boundary. The client gets the private decision, written record, correspondence, and receipt.
It names the official owner, safety line, hard stop, and limit a client can verify before talking to us.
Reviewed surface, private decision, intended outcome, exclusions, correspondence, and receipt stay client-only.
Correspondence, client-only receipt detail, and client-specific notes are not published as public copy.
Client-only fields
If you’re in immediate danger, call 911. For crisis or emotional support:
BoundaryEmotional crisis, suicidal thoughts, or panic after a threat or leak.
CeilingIf anyone is physically unsafe right now, call 911 before using a hotline.
BoundarySexual-violence survivor support, safety planning, and local referrals.
CeilingSupport and referrals, not content-removal ownership.
If everyone involved was 18 or older when the image was taken and is 18+ now, these official adult boundaries help prove the safety boundary. They can help with blocking, support, and reporting; they cannot cover every source, copy, or client-record answer.
BoundaryAdults 18+ who still have the image or video and want participating services to block matching copies.
CeilingIt works by hash matching on participating companies; it is not an all-web resolution path.
BoundaryImage-based sexual abuse support, referrals, and practical next-step guidance.
CeilingA nonprofit support line; it does not replace emergency services or legal counsel.
The FTC record is for reporting a covered-service problem: no clear process, a broken process, or failure to reasonably act on a valid TAKE IT DOWN request. It is not a client-record owner, and it does not replace the required first notice.
BoundaryReporting a covered service that has no compliant process or did not reasonably act on a valid TAKE IT DOWN request.
CeilingThis reports the compliance problem to the FTC. It is not client-record ownership and it does not replace the required first notice.
If coverage or request validity is unclear, keep that question in the boundary record and review the TAKE IT DOWN Act explainer before moving into client-record review.
Paying the person threatening you confirms you’re reachable and the demands can continue. Stop responding, preserve the messages, and keep the law-enforcement record separate from any removal work.
BoundaryReporting cyber-enabled crime, including online extortion and sextortion.
CeilingA law-enforcement reporting channel. It does not remove source content by itself.
For a calmer first-hour decision path, see the safety packet.
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.
BoundaryReporting suspected online child sexual exploitation or sexualized images involving someone under 18.
CeilingThis is the official reporting channel. Keep sensitive files out of commercial services.
BoundaryNude, partially nude, or sexually explicit images taken when someone was under 18.
CeilingIt works through participating services. It is separate from law enforcement reporting.
Google can remove eligible results from Search, but the underlying page may still exist at the source. Treat these official paths as search-boundary proof, then keep the remaining issue as a separate client-record question.
BoundaryRequesting removal of eligible non-consensual explicit imagery from Google Search results.
CeilingGoogle can hide an eligible result from Search; it does not remove the image from the source page.
BoundaryDoxxing or exposed contact information that appears in Google results.
CeilingThis affects Google Search results. The source page may remain live and reachable directly.
BoundaryChecking and requesting removal of search results that expose your personal contact information.
CeilingAvailability and eligibility depend on Google account settings and Google's policies.
BoundaryCrime-victim support, rights information, and referrals across many crime types.
CeilingReferral support, not a client-record owner or emergency responder.
BoundaryReporting scams, impersonation, and fraud patterns to the FTC.
CeilingA report helps enforcement and tracking; it is not a client-record owner.
Evidence safety
A strong client review needs records and context, not a fresh copy of intimate content. Keep the evidence useful without sending sensitive images into another inbox or form.
Keep a private surface summary without forwarding intimate images or videos to anyone.
If someone is threatening you, stop replying and preserve the messages. Paying the person threatening you can confirm you are reachable.
A source page, account profile, search result, threat thread, and re-upload are different records. Keep them labeled before any client-record review.
Adult intimate-image, AI-nude, and sextortion matters should start with a human and a minimal private summary. The sensitive file itself stays out of forms and authorization paths.
Before a report or handoff
Most safety lines need a clean boundary record, not the sensitive file. Keep the public record light; the client-only review belongs inside the handoff.
POLICY
Boundary noteA specific post, profile, page, service, or accountable surface controls the copy.
A minimal private surface summary, plus any official result already created.
The intimate file itself, passwords, full ID numbers, payment details, and unrelated personal history.
SEARCH
Search boundaryThe urgent exposure is search visibility, while the source page may still remain live.
The search boundary, the source question, and any prior decision at a high level.
Do not describe search removal as removal of the original page. Keep the source page as its own surface.
EXTORTION
Extortion recordSomeone is threatening, demanding money, or using accounts to coerce you.
A private threat summary and any official record, without publishing the case file.
Do not negotiate, send new material, or move the threat to a new channel.
HUMAN
Sensitive checkpointAdult intimate images, AI nudes, or sextortion need a human client-record channel.
A minimal private summary and any official result already created.
The intimate file itself. If anyone was under 18 when it was made, use NCMEC instead.
Report capsule
Where
The place where the problem is visible, threatened, indexed, or controlled.
What
A plain description of the harm without resending the sensitive file.
Tried
The official boundary you already used and any receipt or reply.
Remaining
What is still live, still threatened, or still unresolved.
After the official boundary
The next step should be based on what reached the original page, what only reached search, and what belongs in a written client record.
Do not authorize payment until the public boundary is clear and the private answer is written in the client record.
Official and policy boundaries label the first move before AboutUs work begins.
Boundary deskKeep the sensitive file out; the private record carries what the public page does not.
Safety recordReviewed items, search boundaries, follow-up, referral, and exclusions stay labeled separately.
Compare outcomesTRUST GATE
The company, payment boundary, refund language, closeout label, and safety-first posture should all be visible before authorization.
Run authorization gateCommercial boundary, safety first
The same leak can create six different boundaries: crisis support, hash blocking, child-protection reporting, extortion reporting, search exposure, or an AboutUs client record. Confirm the owner first.
A good record protects the person, keeps sensitive files out, and leaves enough context for a human to review.
SAFETY
Crisis boundaryPhysical danger, self-harm risk, or panic after a threat.
Call 911 for immediate danger. Call, text, or chat 988 for crisis support.
Do not wait for a content-removal plan before getting crisis help.
Return to removal review only after the person is safe enough to decide.
ADULT NCII
Adult boundaryEveryone involved was 18+ when the image was taken and is 18+ now.
Confirm the adult safety boundary and keep its receipt separate before AboutUs review.
Do not upload or forward the sensitive file to commercial forms, email, or authorization paths.
If the copy stays live, move the remaining facts into a human client-record read.
MINOR
NCMEC referralAnyone involved was under 18 when the image was created.
Official child-safety channels own the boundary.
Do not send the content to anyone, including us. This is never a commercial case.
Use official child-protection channels and law enforcement where appropriate.
EXTORTION
IC3 recordA person is threatening to post, send, or keep spreading the material.
Stop replying, preserve messages, and keep a law-enforcement record separate from client-record work.
Do not pay the person threatening you or move the conversation to a new private channel.
If content is already live, keep the law-enforcement record separate from client-record review.
SEARCH
Search boundaryThe urgent exposure is a Google result, not a source page you control.
Confirm whether a Google path reaches only the search exposure.
Do not treat a search-result change as removing the original page.
Keep the source page separate if the remaining issue needs review.
ABOUTUS FIT
Where we fitThe official boundary stalls, the copy spreads, or the source needs client-record review.
Keep the safety boundary visible; the remaining facts belong in a private client-record read.
Do not pay until the public boundary, reviewed item, intended outcome, and exclusions are written down.
Use live help for sensitive cases; open a client record when the matter is eligible.
Verified safety lines
A serious resource page should show enough official proof to build trust. It should not publish the work path. The log below names the owner, the limit, and the official door.
Public proof stops at owner and ceiling. The work order, surface notes, and private decision stay inside the confidential client record.
Last checked: June 30, 2026. External programs can change; the linked official page controls.
988 Suicide & Crisis Lifeline
Public ceilingIf anyone is physically unsafe right now, call 911 first.
SWGfL / Revenge Porn Helpline
Public ceilingHash blocking does not delete a live source page or reach every service.
RAINN
Public ceilingSurvivor support and referrals; not removal work or a law-enforcement report.
Cyber Civil Rights Initiative
Public ceilingA nonprofit support line; not emergency response, legal counsel, or a client-record owner.
National Center for Missing & Exploited Children
Public ceilingCyberTipline reporting and Take It Down blocking serve different jobs; follow NCMEC's official instructions.
Federal Trade Commission
Public ceilingFTC reporting documents compliance failure; it is not a client-record owner.
FBI Internet Crime Complaint Center
Public ceilingA law-enforcement report is not the same as client-record handling.
National Center for Victims of Crime
Public ceilingReferral support; not emergency response, client-record ownership, or investigation.
Federal Trade Commission
Public ceilingA report helps enforcement and tracking; it is not a client-record owner.
Google Search
Public ceilingSearch removal can hide a result without removing the source page.
Google Search
Public ceilingEligibility depends on Google's policies and the specific result.
Official boundary controls
The linked official page is the source of truth if a program changes names, eligibility, forms, hours, or process.
Safety record before authorization
If the official boundary resolves the issue, keep the receipt as the record. AboutUs work belongs inside the client record after boundary and written terms.
Sensitive file stays out
Keep the public record light unless an official boundary instructs otherwise.
Before boundary is written
The safest first move is a boundary check, not a blind authorization. The boundary may be a crisis line, a hash-blocking tool, a compliance record, a search-result request, or a law-enforcement record.
If the official boundary resolves the issue, keep the receipt as the record. If it does not, bring the safety record, not the intimate file, to a human.
Physical danger, self-harm risk, or panic belongs with emergency and crisis support before any removal workflow.
For intimate images, AI nudes, and sextortion, start with a minimal private summary and keep the file out.
Official safety lines, child-protection channels, compliance reports, regulators, law enforcement, and search each reach a different part of the problem. Confirm the boundary before you repeat the story.
If the official boundary resolves the problem, the receipt becomes the record. If it stalls, spreads, or keeps returning, the next step should be bounded in writing.
Safety record
WHERE
The visible surface, search result, profile, source page, or inbox thread at a high level.
FILED
Which official, support, or reporting boundary you already used.
STATUS
Receipt, reply, deadline, denial, or silence after follow-up.
NEXT
Client-only review, written terms, support referral, or stop.
Boundary ledger
An official boundary, a public report, a search-result request, and client-record handling are not interchangeable. The honest question is what the boundary can reach, what it cannot, and who should own the next step.
ReachesParticipating services that can match a private fingerprint of the image.
CeilingIt does not delete a live source page or cover every service on the open web.
ReachesThe service or accountable surface that controls a specific copy.
CeilingIt depends on policy fit, evidence quality, and whether the service acts on the report.
ReachesThe federal regulator when a covered service lacks a compliant process or does not reasonably act on a valid TAKE IT DOWN request.
CeilingIt documents a compliance problem; it is not client-record ownership.
ReachesGoogle or another search index when the urgent harm is search visibility.
CeilingIt can hide an eligible result from search without deleting the source page.
ReachesA public reporting channel for extortion, exploitation, threats, or crime patterns.
CeilingIt creates a report; it is not the same as client-record handling.
ReachesEligible adult matters where a written client record can define the work and limits.
CeilingWe are not a law firm, and client-record outcomes are defined in writing before authorization.
Client-record boundary gate
The resource desk proves the official boundary. It should not expose the private decision, correspondence, or client receipt. AboutUs fits when the unresolved gap needs a written owner, not another link.
We are a removal agency, not a law firm. Eligible reviewed items are bounded in writing with the intended outcome, exclusions, and refund posture before authorization.
Public signalOfficial owner, safety boundary, ceiling, and receipt path are checkable.
Client roomThe client record states whether the unresolved gap belongs in an AboutUs record.
Public signalSearch, safety, threat, and unresolved-material boundaries stay labeled separately.
Client roomReviewed item, exclusions, intended outcome, and refund posture are written before money.
Public signalThe visitor can see enough to avoid panic buying or vague rescue language.
Client roomOne accountable owner tracks status, correspondence, and client receipt inside the record.
Public signalThe public page stops before the client-specific answer and notes.
Client roomThe client receives the closeout receipt, remaining visibility label, and stop boundary.
Commercial discipline
Visitors get enough proof to stay safe. Clients get the accountable record that decides what AboutUs owns next.
What stays public
Official routes, safety exits, limits, evidence safety, and the boundary needed for trust.
What the fee buys
Client-record judgment, written boundary, status discipline, and client-only receipt.
What stays sealed
Correspondence, client-only receipt detail, and client-specific notes.
Bring the official boundary and the unresolved gap at a high level. The public record proves the boundary; the client record names the client-record work.
When new surfaces appear, the work becomes ownership and status discipline, not another public link list.
We separate what can be reviewed, referred, held, or stopped before authorization.
The reviewed item, intended outcome, refund posture, and client-only receipt are written before AboutUs work starts.
Common questions