CLAIMGATED
Public claim
Public pageThe page can show a scrubbed proof standard and a safe label.
Client recordThe client record carries the item status, client receipt, and closeout note.
SECTION 04 — FINDINGS & PROOF
Findings — verification room & claim discipline
Public proof. Client record sealed.
Anyone can publish a flattering number. This room shows the verification standard instead: what can be said publicly, what stays sealed, and which claim AboutUs refuses to inflate.
Aggregate outcomes across eligible cases; individual results vary per your written service agreement.
Verification facts, not inflated result claims.
Publication rules
PROOF
Public proof needs a sealed record.
A public line has to trace to a client-only receipt. The artifact itself never becomes page content.
LABEL
Outcome labels stay plain.
Resolved, fallback, referred, and declined items are not collapsed into one success word.
CLAIMS
Claims need dated support.
Every performance claim needs dated substantiation before it reaches the page. Verification standards carry the proof here.
CLOSE
Every file closes with a receipt.
The client receives the record. The public page gets only a scrubbed label if it clears review.
Table 04-A — Verification evidenceBasis — verifiable facts, not promises
04-A-01
Proof
private record
public claims require a private receipt, dated review, and safe label
04-A-02
Agent
written authority
we record the boundary without publishing case-specific handling
04-A-03
Seal
public-safe labels
resolved, fallback, referred, and declined outcomes stay separate
04-A-04
Written
service agreement
eligible results-based work gets a written boundary before anything begins
[1]No outcome percentage or speed claim is shown here. Dated operational counts can appear only through the verified track record block.
[2]Aggregate outcomes across eligible cases; individual results vary per your written service agreement.
04-P - CLAIM CONTROL LEDGER
Public proof / sealed value
The page proves the gate. The record carries the answer.
Findings should make AboutUs inspectable without turning the site into a client record. Public proof shows the claim gate; the client record carries the answer, boundary, correspondence, and closeout receipt.
BASISGATED
Written boundary
Public pageThe page can prove a review gate exists.
Client recordThe client record carries the private review, limits, correspondence, and boundary.
LABELGATED
Outcome label
Public pageResolved, fallback, referred, declined, and withheld stay separated.
Client recordThe client record explains why that label applies to the reviewed item.
SEALGATED
Sealed value
Public pageThe public visitor sees discipline, not the sealed handling record.
Client recordSpecialist notes, client correspondence, commercial terms, and client facts stay sealed.
What stays off the page
Public standard. Sealed handling.
A serious proof page lets a client trust the controls without publishing the client record.
SEALED
Private answer
SEALED
Written boundary
SEALED
Working correspondence
SEALED
Closeout receipt
SEALED
Closeout label
SEALED
Client terms
The file drawer — cases 04-C-01 … 04-C-04
Four files. Closed.
Each one opens as it reaches you, and each one closed the same way. The names stay sealed because the client record stays closed.
REPRESENTATIVE SCENARIO — composite of typical engagements, anonymized. Individual results vary; eligibility and any results-based terms are defined in your written service agreement.
04-C-01NCII / DEEPFAKE
Private cluster
resolved label
Leaked intimate images and AI deepfakes spread across a grouped locator set. Reviewed under eSafety and provider standards; continuity support stayed tied to the client record.
- Client
- Identifiers
CUSTODY — OPENED · PUBLIC RESULT VERIFIEDClosed
04-C-02DEFAMATION
Mirror network
boundary set
A defamatory article was copied into a wider cluster. The client record separated direct review, related-copy notes, and fallback limits instead of blending them into one promise.
- Client
- Identifiers
CUSTODY — OPENED · LEGAL WINDOW REVIEWEDClosed
04-C-03EXECUTIVE CRISIS
Search exposure
limited label
Coordinated attack pages targeted a founder ahead of a raise. The client record kept proof and limit language together; the public page shows the standard, not case instructions.
- Client
- Identifiers
CUSTODY — OPENED · FALLBACK LABELEDClosed
04-C-04CONTINUITY DEFENSE
Continuity record
term attached
Ongoing continuity review kept match context and the client-only receipt ready inside the written agreement, without turning the file into public operating detail.
- Client
- Identifiers
CUSTODY — CONTINUITY READYClosed
04-D - EVIDENCE PACKET
Before a claim becomes public
The proof object is the packet.
The work is not finished by a nice status word. A serious file leaves behind enough client-record evidence to verify the outcome, while the public page sees only the scrubbed public-safe label.
ITEM
What was reviewed
Each reviewed item is logged as a visible surface with its own client-only receipt. Item-level specifics stay in the client record.
BOUNDARY
What boundary applied
The private answer stays in the client record. Public copy shows only a safe outcome label or referral boundary.
SEAL
What stays sealed
Review notes, working correspondence, and limits stay in the client record.
STATUS
How it closed
Client receipt, public response if any, fallback label, declined record, refund path, or official-channel referral.
Label
Label
Resolved item
Sealed record
Item context, boundary label, receipt, and final check.
Public label
A public-safe resolved label, not a vague success badge.
Label
Fallback item
Sealed record
Result context, limitation note, and decision record.
Public label
A fallback label kept separate from a stronger result claim.
Label
Continuity item
Sealed record
Match note and continuity context.
Public label
A continuity line tied to the agreement, not whole-internet prevention.
Label
Decline or referral
Sealed record
Why the matter does not belong in AboutUs work and the remaining official boundary.
Public label
A boundary note before AboutUs work, not a dressed-up weak path.
Client-record proof receipt
What the client gets that the page does not.
The public page proves the standard. The client record carries the receipts, safe labels, and closeout notes needed to verify the work without exposing the case.
ITEM
Item-level proof.
Each locator, result, post, or cluster keeps its own client-only receipt.
LANE
Label kept separate.
Resolved, fallback, continuity, referral, and declined files never collapse into one result word.
SAFE
Public copy stays scrubbed.
The site can show the standard. The artifact, correspondence, and private answer stay sealed.
NEXT
Closeout written.
The client record shows what is done, what remains, and what should not be sold.
04-E - VERIFICATION ROOM
After the packet closes
Findings pass through a verification room.
Public proof is not the raw file. Each item is checked against its private artifact, safe label, and privacy boundary before anything becomes a public claim or track-record line.
Publication standard
If a sentence cannot point back to a private artifact and a safe public label, it stays off the site.
Gate
Verification check
Sealed artifact
Public-safe label
CAPTURE
Verification check
What can be inspected without re-exposure?
Sealed artifact
A sealed item record for each visible surface; item-level specifics stay in the client record.
Public-safe label
Sealed artifact unless it can be scrubbed into a representative example.
VERIFY
Verification check
Can another human check the record?
Sealed artifact
A client receipt and private decision note that another reviewer can check inside the file.
Public-safe label
Resolved, fallback, referral, declined, or withheld.
SEPARATE
Verification check
Which public-safe label is allowed?
Sealed artifact
A private decision note recording which label was chosen, kept inside the file.
Public-safe label
Resolved item, fallback limit, continuity match, official referral, or declined boundary — never promoted into a stronger claim.
PUBLISH
Verification check
What is safe to say publicly?
Sealed artifact
Client consent, privacy scrub, proof notes, boundary note, and review date where a number appears.
Public-safe label
Standard language first; client facts stay sealed unless the file clears the gate.
Publication states
Public standard
Public definitions, boundary labels, representative scenarios, and privacy-safe claim language.
Sealed client record
Receipts, screenshots, correspondence, hashes, and identifying facts stay in the confidential file.
Limited label
Fallback work remains a fallback in the public record.
Withhold
Minor-involved content, unsafe intake, or unsubstantiated claims do not become public proof.
Hard locks
No named client proof without consent.
No sensitive file displayed as public evidence.
No fallback work described as a stronger result.
No aggregate rate without dated substantiation.
Table 04-B — Verification standard
How proof gets labeled.
A proof page is only as honest as its boundaries. These are ours: client-record backed, documented, explicit about limits, and careful about what stays out of public view.
04-B-01
What counts as public proof.
Public proof means a scrubbed line can trace back to a client-only verification report without exposing the person, artifact, or sealed answer. The page can show the standard. The client file carries the specific record.
04-B-02
Why sealed handling matters.
The public site should not expose case-specific handling. Inside a client file, every item gets sealed context, limits, and a receipt. Outside the file, you see the standard, not the client-record detail.
04-B-03
The public standard, unpacked.
Client record
Every public proof line has a private artifact behind it. The client record is specific; the public label is scrubbed.
Evidence
Evidence lives as private artifacts inside the file. Nothing on the site points at a raw file.
Boundary
Reviewed items can move inside a written client record, but the full handling record stays sealed.
24h
The statutory removal window for non-consensual intimate imagery — 24-hour removal-notice window, eSafety-enforced. We label it as the law's clock, not our outcome promise.
04-B-04
The claim gate.
A public claim does not get published because it sounds persuasive. It needs a file-backed evidence threshold first. This is the gate between sealed record notes and anything a client, reviewer, or public visitor can read on the site.
Gate
RESOLVED
Claim
Resolved label
Sealed check
A client-only item record and receipt that clears the final check.
Public label
Counts only when the public-safe record supports it.
FALLBACK
Claim
Fallback label
Sealed check
Result record, limitation note, and decision record.
Public label
Labeled as fallback work, never as a stronger result.
CONTINUE
Claim
Continuity coverage
Sealed check
Match note, private context, and written term.
Public label
Described as continuity coverage, not whole-internet prevention.
DECLINE
Claim
Outside boundary
Sealed check
Reason for refusal, safer path, or legal/official-channel referral.
Public label
Kept out of paid case language when the file should not be commercial.
PUBLIC
Claim
Track record
Sealed check
Dated owner-maintained counts with boundary notes and review date.
Public label
Shown only in the verified track record block, never as borrowed benchmarks.
This ledger is a publishing rule, not an outcome promise. It keeps resolved, fallback, continuity, referral, and declined files in separate categories.
04-B-05
What we will never show you.
Fake testimonials.
If a quote can't be verified without exposing a client, it doesn't get published. None are.
Named clients.
Confidentiality is part of the service. No logos, no first names, no “as seen on.”
Blanket promises.
Eligibility and any results-based terms are defined in your written service agreement — and some cases we decline rather than overpromise.
Aggregate outcomes across eligible cases; individual results vary per your written service agreement.
04-B-06
The sealed client report.
Every client engagement closes with a client-only document: item label, outcome label, dated record, and any continuity term that follows. The site can show a format specimen, but the real report stays with the client.
ITEM-01#a3f9c1RESOLVED · CLIENT VERIFIED
ITEM-02#7c12deRESOLVED · CLIENT VERIFIED
ITEM-03#de40b8FALLBACK · LABELED
ITEM-04#9f0274RESOLVED · CLIENT VERIFIED
CONTINUE--CONTINUITY TERM · AGREEMENT
Re-upload defense — standing order
If it comes back, the case does not start from zero.
Every closed case keeps its evidence record, match note, and continuity context attached. If a copy resurfaces, the next action starts from a complete record instead of panic.
01
FINGERPRINT
When a client chooses local fingerprinting, the browser can send a mathematical reference without uploading the image or video. That reference is a case aid, not an all-web scanner.
02
CONTINUITY
Authorized public names, handles, and URLs stay attached to the written monitoring scope. Search candidates remain internal until a person verifies them.
03
CONTINUITY
A verified public re-upload re-enters the same case ledger, where the source, request route, and next follow-up are recorded under the written agreement.
Continuity term - defined in your written service agreement
Record review — confidential intake
Open a sealed proof file.
The record review is confidential and file-light. You get a written boundary on what can be named publicly, what stays sealed, and whether AboutUs should open the client record.
Request record reviewDiscreet · private summary first · written boundary before work
Next in file
05 — Safety PacketAUSTRALIA · CONFIDENTIAL CLIENT RECORD