Public statements
On this siteOnly general rules and result labels.
In a client's case fileEach item's status, the client's report, and the closing note.
Findings — how results are labeled
This page explains how AboutUs labels each result: removed at the source, removed from search only, request sent, or unresolved. It does not show client cases.
Illustrative examples only — the case-style files on this page are hypothetical. No client data, testimonials, or outcome numbers are published here.
Outcomes vary. Third parties make the final decision, and your written scope defines what counts as done and how refunds work.
Verification facts, not inflated result claims.
Publication rules
Any public statement about results has to be backed by a dated record. The record itself is never published.
Request submitted, source removed, search delisted, and unresolved are never merged into one success word.
This page publishes no success rates, client counts, or removal times.
A client's written report goes to that client only. The case-style examples on this site are hypothetical.
evidence stays in your private case file and is never published
we act for you only with your written authorization
request submitted, source removed, search delisted, and unresolved stay separate
what is included, the price, and the limits are written before paid work starts
[1]No outcome percentage or speed claim is shown on this page. Any dated counts shown are totals from our own records, not results.
[2]Outcomes vary. Third parties make the final decision, and your written scope defines what counts as done and how refunds work.
What is public / what stays private
This page lets you check how we work without publishing anyone's case. The rules and labels are public. Each client's answer, scope, emails, and closing report stay in their private case file.
On this siteOnly general rules and result labels.
In a client's case fileEach item's status, the client's report, and the closing note.
On this siteThat a written scope comes before any paid work.
In a client's case fileThe private review, limits, emails, and what is included.
On this siteRequest submitted, source removed, search delisted, and unresolved stay separate.
In a client's case fileWhy that label applies to that item.
On this siteHow we work — not how a specific case was handled.
In a client's case fileTeam notes, emails, pricing terms, and the client's facts stay private.
What stays off this site
You can check our rules without anyone's private case being published.
PRIVATE
Our answer to you
PRIVATE
Your written scope
PRIVATE
Our emails with you
PRIVATE
Your closing report
PRIVATE
Each item's final label
PRIVATE
Your price and terms
ILLUSTRATIVE EXAMPLE — a hypothetical situation written to explain how we work. It is not a client case and does not describe a real result. Outcomes vary; eligibility and any results-based terms are set in your written service agreement.
Illustrative examples — not client cases
These are made-up situations that show how we would organize a case and label each result. No client, name, or real outcome is behind any of them.
Several related sites
Hypothetical: leaked intimate images and AI-generated fakes appear on several related sites. In a case like this, requests are reviewed under eSafety rules and platform policies, and any follow-up stays tied to the private case file.
No client data — hypothetical example
Copied article
Hypothetical: a defamatory article is copied onto other sites. In a case like this, the original, each copy, and any search-only result are tracked separately, so one result is never reported as another.
No client data — hypothetical example
Search exposure
Hypothetical: attack pages target a founder before a fundraise. In a case like this, what can be requested and what is out of reach are written down before any paid work starts.
No client data — hypothetical example
Re-upload check
Hypothetical: an item that came down is posted again. In a case like this, follow-up checks happen only if they are included in the written service agreement, and no one can promise every repost will be stopped.
No client data — hypothetical example
What a case file holds
A case is not finished because a status word looks good. A real case file keeps enough evidence to check each result. This page shows only the rules.
ITEM
Each item is logged on its own, with its own record. The details stay in the client's case file.
SCOPE
The written scope and our private answer stay in the case file. Public pages show only a result label.
PRIVATE
Review notes, emails, and limits stay in the case file.
STATUS
Source removed, search delisted, unresolved, declined with a reason, a refund where the terms apply, or a referral to an official channel.
The item, its link, and the date it was checked.
Source removed — not a vague success badge.
The result, why it is limited, and the decision note.
Search delisted — kept separate from a removal.
Match notes, only if follow-up is in the written agreement.
Follow-up as agreed — not a promise to stop every repost.
Why the matter does not fit our work, and the official option that remains.
Said plainly, before any paid work.
The client's report
This page shows the rules. A client's case file holds the records, labels, and closing notes needed to check the work without exposing the case.
ITEM
Each link, search result, or post keeps its own record.
LABEL
Request submitted, source removed, search delisted, and unresolved never merge into one result word.
PRIVATE
This site shows the rules. The files, emails, and our private answer stay in the case file.
CLOSE
The case file shows what is done, what remains, and what we advise against paying for.
Before anything is published
A public statement is never the raw file. Each item is checked against its private record, its result label, and the person's privacy before anything becomes a public claim.
Publication rule
If a sentence cannot point back to a private record and an accurate label, it stays off the site.
What can be saved without sharing the content again?
A private record for each item. The details stay in the client's case file.
Kept private. Examples on this site are hypothetical, not edited client files.
Can it be checked again later?
A private decision note that can be checked again inside the case file.
Request submitted, source removed, search delisted, unresolved, or declined.
Which label is accurate?
A private note recording which label was chosen and why.
One of the result labels — never upgraded to a stronger one.
What is safe to say publicly?
Written client consent, identifying details removed, and a review date wherever a number appears.
General rules first. A client's facts stay private unless every check is met.
Publication states
Public definitions, result labels, clearly marked hypothetical examples, and privacy-safe claim language.
Receipts, screenshots, correspondence, and identifying facts stay in the confidential case file.
Search-only work stays labeled as search-only.
Anything involving minors, unsafe submissions, or unsupported claims.
Fixed rules
No client named without written consent.
No sensitive file shown on this site.
No search-only result described as a removal.
No outcome percentages or totals without dated support.
Table 04-B — Labeling standard
A results page is only as honest as its labels. These are ours: backed by a private record, explicit about limits, and careful about what stays out of public view.
A public statement about results must trace back to a private, dated record, without exposing the person or the content. This page shows the rule. A real case file holds the details, and only the client sees it.
Publishing how a specific case was handled can expose the person involved. Inside a case file, each item has its own notes, limits, and status. On this site you see the standard, not a client's details.
Any public statement about results needs a private, dated record behind it. The record stays in the client's case file; this page shows only the rule.
Evidence stays private inside the case file. Nothing on this site links to a real file.
What is included is written into each client's scope. How a specific case was handled is never published.
The statutory removal window for non-consensual intimate imagery — 24-hour removal-notice window, eSafety-enforced. It is the law's deadline for the platform, not an AboutUs turnaround.
A result is not labeled by how good it sounds. Each label has a condition that must be true first. This is the rule between a private case file and anything published on this site.
Source removed
The item is gone from the page where it was posted, and the link was checked.
Counted only as source removed — never merged with search results.
Search delisted
The page may still exist, but a search engine no longer shows it for the request.
Labeled search delisted, never as a removal.
Request submitted
A request was sent to the host, platform, or search engine.
Activity, not a result.
Unresolved
No change yet, or the request was refused.
Labeled unresolved — not hidden or left out.
Declined
We say why, and point to a safer option or an official channel.
Not sold as paid work.
Operating counts
Owner-maintained counts with a review date.
Published only with an as-of date, never as borrowed benchmarks.
This table is a labeling rule, not an outcome promise. Request submitted, source removed, search delisted, and unresolved always stay in separate categories.
We publish no client quotes or testimonials on this site.
Confidentiality is part of the service. No logos, no first names, no “as seen on.”
Eligibility and any results-based terms are defined in your written service agreement — and some cases we decline rather than overpromise.
Outcomes vary. Third parties make the final decision, and your written scope defines what counts as done and how refunds work.
When a case closes, the client gets a written report: each item, its result label, the date it was checked, and any follow-up that was agreed. Below is the format, filled with example data. A real report goes only to the client.
Re-upload follow-up — if included in your agreement
When a case closes, its evidence record and notes stay attached. If a copy comes back and follow-up is included in your written agreement, the next step starts from that record instead of from zero.
If a client chooses it, their browser can create a mathematical fingerprint of an image or video without uploading the file. The fingerprint helps with the case; it does not scan the whole web.
Public names, handles, and links the client authorizes stay on the written monitoring scope. Possible matches stay internal until a person checks them.
A confirmed re-upload goes back into the same case file, where the source, the reporting path, and the next step are recorded under the written agreement.
Follow-up — only if included in your written service agreement
Ask about your case
AboutUs is a paid service. Describe the situation briefly — do not send images, videos, or passwords. Replies come by email. Some first replies are written and sent automatically. If paid work fits, you get a written plan with scope, total price, limits, and refund terms before you pay.
Next in file
05 — Safety PacketAUSTRALIA · ILLUSTRATIVE EXAMPLES ONLY