PUBLICLOCK
The public page proves the controls.
It shows safe intake, boundary separation, written terms, and verification without publishing client-only work.
SECTION 01 — CLIENT CASE ROOM
Public receipt. Client record sealed.
This is the kind of record AboutUs opens after safe intake and a written boundary. It shows what is safe to inspect: evidence discipline, terms before authorization, custody, and verification. The private answer, correspondence, and receipt trail stay inside the client record.
Adult intimate-image cases start with private case review. Files held back. Gated checkout only.
BOUNDARY — WRITTENRECORD — SEALED
- MATTER
- adult sensitive matter
- ENTRY
- private case review · files held back
- REVIEW
- written boundary · terms first
- RECEIPT
- client-only receipt · sealed record
REPRESENTATIVE SCENARIO — composite of typical engagements, anonymized. Individual results vary; eligibility and any results-based terms are defined in your written service agreement.
01A - CLIENT CASE ROOM
Client case room
This is not the client record.
A serious case page should make the agency feel inspectable without publishing the client record. The public receipt shows discipline; the client record carries the work.
CLIENTLOCK
The client record carries the work.
Private answer, written boundary, correspondence, and limits stay inside the client record.
SAFETYLOCK
Sensitive facts stay out of forms.
Adult intimate-image, AI-nude, and sextortion matters start in private case review from a minimal private summary. Sensitive files stay out; minor-involved content is referred out.
AUTHLOCK
Authorization waits for a written boundary.
AboutUs work begins only after the reviewed item, limits, and refund posture are separated from public checkout.
Why the record carries value
Public proof. Sealed value.
The public page earns trust; the client record carries the valuable answer, boundary, correspondence, and closeout proof.
ANSWERSEALED
Private answer
Public caseThe public case shows the control room.
Client recordThe client record says what AboutUs will review, stop, refer, or decline.
BASISSEALED
Written boundary
Public caseThe page proves a boundary exists.
Client recordThe record carries item limits, authorization posture, and refund labels.
TRAILSEALED
Working trail
Public caseThe page shows how a file stays orderly.
Client recordThe record ties client messages, private context, response states, and receipt states together.
CLOSESEALED
Closeout proof
Public caseThe page shows representative outcomes.
Client recordThe record labels removed, visibility-limited, referred, declined, and outside-record items.
SEALED
Specialist notes
SEALED
Written boundary
SEALED
Working correspondence
SEALED
Closeout receipt
SEALED
Proof notes
SEALED
Client terms
01B - BOUNDARY REVIEW
Before the documents move
The file gets a boundary review first.
The representative film below is not a promise of what happens next. A serious case opens with a client-record boundary check: what can be written, what must move to safety or referral, and when no AboutUs offer belongs.
What is safe to share publicly?
What belongs in the client record?
What can be priced only after review?
What proof can be shared safely?
Gate
Public receipt
Client record
Written boundary
ENTRY
Public receipt
Sensitive files held back.
Client record
Minimal private summary, visible-surface label, prior response state, and safety context held inside the client record.
Written boundary
Live-help boundary, client-record review, official referral, or no-commercial-work label.
BASIS
Public receipt
Visible surface logged without exposing the path.
Client record
Visible item, account or result, and client-only boundary note.
Written boundary
Primary record, search fallback, referral, or closed status stays separately labeled.
FILE
Public receipt
Scope written before authorization.
Client record
Reviewed private boundary, limits, and receipt standard.
Written boundary
Boundary, outcome label, limits, and refund posture written before work.
VERIFY
Public receipt
The result has a checkable receipt.
Client record
Submission receipt, public response if any, outcome label, and client receipt.
Written boundary
Verified receipt, client note, referral, or closed record.
Client-record receipt
What the client record should carry.
The public film proves control. The client-only record carries the private answer: written boundary, authorization posture, client correspondence, and proof record that stay off the public page.
CHECK
Reviewable or declined.
The first answer names whether the matter belongs in AboutUs work, private case review, official referral, legal referral, or no-commercial-work status.
BASIS
Written boundary before work.
The reviewed item and limits are written before AboutUs work begins.
AUTH
No silent acceptance.
Authorization is not treated as an AboutUs service until the boundary and refund posture are written.
PROOF
Record another human can inspect.
Receipts, outcome labels, correspondence, and closeout notes stay in the client record.
Sensitive channel
Adult intimate-image, AI nude, or sextortion facts start in private case review before files, email attachments, or public checkout.
Boundary split
Removal work, search limits, referral, and stopped items never share the same status label.
Acceptance gate
The boundary, limits, and refund posture are written before AboutUs work begins.
Publication gate
Any public case language stays representative, privacy-scrubbed, and tied to a checkable record.
The case, document by document
DOCS 01–05
The problem, described once.
CLIENT: MATTER: NCII / DEEPFAKE — ADULT (18+)
“I found them three days ago, on one site. I keep finding new ones — I’ve stopped counting.”
REPORTED BY CLIENT — INITIAL URLS
- surface-a.example/g/redacted#a3f9c1REPORTED
- video-surface.example/v/redacted#7c12deREPORTED
- thread-space.example/t/redacted#1b8e22REPORTED
CLIENT BOUNDARY RECORD:client-reported URLsrelated copies checkeddetail stays inside the file
RECEIVED — CASE OPEN
Captured once. Never viewed again.
Every asset is preserved in a timestamped evidence log and sealed client record that helps check mirrors or re-uploads without asking anyone to look at your content again.
ASSETMATCH IDCAPTURESEV
surface-a#a3f9c1full-page archiveS2
video-surface#7c12destream manifestS1
mirror-01#de40b8snapshot + headersS2
thread-space#1b8e22thread archiveS3
index-copy#9f0274index captureS2
SEALED CLIENT RECORD · TIMESTAMPED · LOGGEDLOGGED — EVIDENCE
Boundary detail stays inside the client record.
The public scenario shows the control system, not the sealed client record. It confirms a written boundary exists while the private answer and handling detail stay sealed. Primary items and fallback layers stay labeled separately.
WRITTEN — ACCEPTED CASE BOUNDARY
- VISIBLE ITEM CHECKTO: PUBLIC SURFACE
- PLATFORM POLICY BASISTO: PLATFORM TRUST & SAFETY
- SEALED DETAIL CHECKTO: DETAIL SEALED
- SEARCH BOUNDARYTO: SEARCH LIMITS
- CLIENT RECEIPTTO: CLIENT RECORD
CASE ITEMS — PUBLICLY SCRUBBED
- surface-aLIVEREMOVED
- video-surfaceLIVEREMOVED
- mirror-classLIVEREMOVED
- index-copyLIVEREMOVED
- search-indexINDEXEDDELISTED†
† Delisting is a fallback to removal, never a substitute — primary records are verified separately, not buried.
Every receipt, on the record.
- P-01CASE OPENEDIntake received; priority items recorded
- P-02EVIDENCE CAPTUREDAssets archived; client record opened
- P-03BOUNDARY RECORDEDWritten boundary recorded
- P-04PUBLIC RESULT CHECKEDPublic outcomes checked and logged
- P-05CONTINUITY CHECK READYContinuity receipt tied to the client record
- P-06CLIENT RECORD VERIFIEDVerification report delivered; client receipt ready
CHAIN OF CUSTODY — CAPTURED · RECORDED · FILED · VERIFIED
Verified means documented.
CLEARRESULT CHECKED
- PRIMARYPRIMARY RECORDprimary item checked before fallback layer
- CHECKCONTINUITY READYcontinuity receipt tied to the client record
- REPORTREPORT READYverification receipt delivered
“Removed” means resolved where it lived, verified in the public record and paired with fallback layers. Not pushed to page two.
REPORT DELIVERED TO CLIENT · CLIENT RECEIPT READYVERIFIED — CLIENT RECORD
EXIT — YOUR FILE
Your case starts the same way.
The first document in your file is a confidential boundary review, not a public template. Share a minimal private summary and a small case team gives you a straight answer: what can be written in the client record, what needs referral support, and what we’d decline rather than overpromise.
Case receipt ledger
What a serious receipt should preserve.
The case film is representative, but the control points are the same: safe intake, written boundaries, terms-before-work, and a client record another human can inspect.
What is being asked for?
What proof can be preserved privately?
What outcome can be written?
What stays outside the written boundary?
Client record first.
Enters the fileMinimal private summary, visible-surface label, prior response state, and a private boundary note.
Stays outIntimate files, minor-involved content, panic uploads, and card-before-review flows.
Boundaries stay separate.
Enters the filePrimary record, fallback-labeled search work, official referral, legal referral, or declined status.
Stays outBlended promises that make de-listing, suppression, or monitoring sound like deletion.
The boundary is written before work.
Enters the fileReviewed private boundary, intended outcome, limits if any, and refund posture.
Stays outA card authorization treated as acceptance before review. 48-hour review first — if we can't accept it, you're refunded before any work begins.
Verification has a paper trail.
Enters the fileFinal check, response state, and client receipt.
Stays outOutcome claims without a record another human can inspect.
Aggregate outcomes across eligible cases; individual results vary per your written service agreement.
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.
Next in file
02 — ExhibitsUNITED KINGDOM · CONFIDENTIAL CLIENT RECORD