Skip to content
CLIENT RECORD PRECHECK - SEALED VALUE
FILE US-NCR/2026CLIENT RECORD PRECHECKCLASSIFICATION: CLIENT-CONFIDENTIALSEALED CLIENT RECORDSENSITIVE FILE STAYS OUT

Managed boundary precheck

Get the public boundary. Keep the real answer in the record.

This page tells you enough to stop unsafe moves: what not to send, what record to keep, and when a managed AboutUs record may begin. No images, no exposed process, no guesswork.

Built for the decision moment

18+ onlyUnder-18 material goes to NCMEC, local law enforcement, and no commercial path.
Private summary firstPublic boundaries stay visible. The real answer stays in the client record.
Human handoffIntimate-image and sextortion cases move to live help, not payment-first paths.

Plan preflight

Confidential check before authorization.

The tool does not scan the internet, quote a case, or ask for sensitive files. It checks the safety boundary, names keep-out rules, and points to the client record when a real answer is needed.

AGESET

18+ safety gate

Under-18 material goes to child-safety authorities and never becomes commercial work.

TYPESET

Situation before advice

The public answer changes for posted NCII, sextortion, doxxing, defamation, or a general reputation problem.

BOUNDARYSET

Record before fee

Official reporting, evidence safety, and stop lines stay visible before any client record.

HANDOFFSET

Live help when sensitive

Intimate-image and sextortion cases move to live help with a minimal private summary.

Managed plan room

This is a precheck, not the client file.

The tool gets you oriented without making the real work public. It creates the first safe record, then the client record carries the private answer.

Open client record
PUBLICLAYER

The public check names the safety line.

It labels what to keep out and what kind of record to save. It is not the client file.

FILELAYER

The client record carries the work.

Private answer, correspondence, limits, and proof boundaries belong in the client record.

GATELAYER

Authorization waits for a written boundary.

AboutUs waits until safety lines, refund posture, and reviewed items are separated.

LIVELAYER

Sensitive matters leave the tool.

Adult intimate-image, AI-nude, sextortion, and urgent threat facts move to human help instead of payment-first paths.

Commercial discipline

Three records. No card-first spillover.

Safety record

Situation, keep-out rules, official boundary, and unresolved gap.

WHAT MOVES INTO THE CLIENT RECORD

Client-record boundary

Reviewed item list, outside-boundary status, and proof standard.

Client record

Saved records, response state, correspondence state, and closeout proof.

Why AboutUs belongs after the precheck

The plan is public. The value is the record.

The public precheck can orient you. The client-record work is the disciplined record: private answer, correspondence, and closeout proof without publishing the method.

GATECLIENT

Written boundary

Public precheckThe plan names the safe door.

Client recordThe client record gives the written boundary: live help, written review, a fixed quote, or a stop.

BASISCLIENT

Private answer

Public precheckThe page keeps the categories broad.

Client recordThe client record carries private answer, legal-referral boundaries, and what AboutUs will not take.

FOLLOWCLIENT

Client correspondence

Public precheckThe public site says correspondence is tracked.

Client recordThe client record tracks replies, stalls, client receipt, and what remains unresolved.

PROOFCLIENT

Closeout proof

Public precheckThe site explains original-page versus visibility honesty.

Client recordThe closeout receipt labels original-page, visibility-limited, declined, official-boundary, and outside-record items.

Commercial discipline

What stays sealed.

Keep ownership context inside the record.

Keep client-specific next moves inside the record.

Keep the private answer inside the record.

Keep safety resources useful without making them the full plan.

Public boundary packet

Open enough to stay safe.

This panel gives the buyer enough to stop unsafe moves, preserve the right signals, and move hard answers into the client record.

Client-record review
HOLDGATE

Stop the public spiral.

No public posting, forwarding, bargaining, or payment. The open page only marks the hold line.

The client record keeps the private threat and surface summary together.

SAFETYGATE

Lock the safety line before forms.

Adult intimate-image and sextortion facts move to live help; minor-involved facts stay official-only.

Use a minimal private summary. Keep the file itself out.

OUTSIDEGATE

Save only the outside record.

Public guidance names the official boundary without publishing client-record detail.

Bring the official receipt into review. What each receipt means is a private decision inside the client record.

REVIEWGATE

Move the hard answer private.

Review status, limits, and decline reasons belong in the client record.

Bring one clean boundary packet forward instead of repeating the whole story publicly.

Locator set

Minimal private summary of the visible surface and what changed.

Hold back

Intimate files, passwords, full ID or card numbers, and anything involving someone under 18.

Only if asked

Identity proof, registrations, court records, or non-intimate screenshots that support the review.

NEXT

Check the safety line below, then complete the short client-record check. The result should be a boundary packet, not public work detail.

Client record handoff

The public page stops here.

This page gives the safety line, not the method. The client record carries the written boundary, the answer, and the client receipt.

Situation

Physical danger, self-harm risk, or panic is present.

Public boundary

Emergency help and 988 come before removal paperwork.

Client-record note

Return to a private boundary check only after the person is safe enough to decide.

Situation

Everyone was 18+ when the image was made and is 18+ now.

Public boundary

Confirm adult NCII safety boundaries and platform receipts before AboutUs work is accepted.

Client-record note

Bring a minimal private summary and the official boundary. Keep the sensitive file out.

Situation

Anyone was under 18 when the image or video was created.

Public boundary

Use NCMEC CyberTipline and NCMEC Take It Down. This is never AboutUs commercial work.

Client-record note

Do not send the content to us or any commercial service.

Situation

A person is threatening to post, send, or keep spreading the material.

Public boundary

Stop replying, preserve the messages, and use the appropriate official report.

Client-record note

Keep the threat record private and intact. Do not pay.

Situation

The urgent exposure is a Google result or exposed personal contact information.

Public boundary

Treat search as a visibility layer. Do not confuse a hidden result with the original-page question.

Client-record note

Keep the search boundary separate from the source-page question.

ABOUTUS RECORDAuthorization gate
Situation

The official boundary stalls, exposure returns, or the remaining issue needs a client record.

Public boundary

Move to live help for sensitive cases or client-record review for non-intimate cases.

Client-record note

Review the written boundary, safety lines, refund terms, and outcome limits before authorization.

01Age
02Situation
03Plan

First — is everyone involved 18 or older?

Including you, if you were under 18 when the content was made. If the image was made before 18, choose the under-18 answer even if you are an adult now.