Result labels
How we label results.
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.
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.
Unsafe? Call or text 988 Report a threat: tips.fbi.gov (opens in a new tab) Under 18: Take It Down (opens in a new tab)
On this page
Publication rules
Publication rules
These are rules we follow, not results.
Record
A claim needs a real record behind it.
Any public statement about results has to be backed by a dated record. The record itself is never published.
Label
Result labels stay separate.
Request submitted, source removed, search delisted, and unresolved are never merged into one success word.
Numbers
No numbers without dated support.
This page publishes no success rates, client counts, or removal times.
Privacy
Real case details stay with the client.
A client's written report goes to that client only. The case-style examples on this site are hypothetical.
Evidence
Private
Evidence stays in your private case file and is never published.
Acting for you
Authorized
We act for you only with your written authorization.
Result labels
Separate
Request submitted, source removed, search delisted, and unresolved stay separate.
Scope before payment
Written
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.
Public and private
The rules are public. Case details are not.
Read this section: The rules are public. Case details are not.
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.
Claims
Public statements
- On this site
- Only general rules and result labels.
- In a client’s case file
- Each item's status, the client's report, and the closing note.
Scope
Written scope
- On this site
- That a written scope comes before any paid work.
- In a client’s case file
- The private review, limits, emails, and what is included.
Label
Result label
- On this site
- Request submitted, source removed, search delisted, and unresolved stay separate.
- In a client’s case file
- Why that label applies to that item.
Private
Private details
- On this site
- How we work — not how a specific case was handled.
- In a client’s case file
- Team notes, emails, pricing terms, and the client's facts stay private.
Public rules. Private details.
You can check our rules without anyone's private case being published.
- Our answer to you
- Your written scope
- Our emails with you
- Your closing report
- Each item's final label
- 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
Four example situations.
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.
Example: each item labeled on its own
- Several related sites
Hypothetical: leaked intimate images and AI-generated fakes appear on several related sites. In a case like this, evidence stays private, the written plan lists what is included, and each item is labeled separately: removed at the source, removed from search only, or unresolved.
Example step — evidence kept private
No client data — hypothetical example
Example: original and copies tracked apart
- 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.
Example step — limits written before payment
No client data — hypothetical example
Example: limits written first
- 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.
Example step — search-only results labeled separately
No client data — hypothetical example
Example: follow-up only if agreed
- 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.
Example step — follow-up only if agreed in writing
No client data — hypothetical example
What a case file holds
A result needs a record, not a status word.
Read this section: A result needs a record, not a status word.
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
What was reviewed
Each item is logged on its own, with its own record. The details stay in the client's case file.
Scope
What was included
The written scope and our private answer stay in the case file. Public pages show only a result label.
Private
What stays private
Review notes, emails, and limits stay in the case file.
Status
How it ended
Source removed, search delisted, unresolved, declined with a reason, a refund where the terms apply, or a referral to an official channel.
Source removed
- Kept in the case file
- The item, its link, and the date it was checked.
- How it is labeled
- Source removed — not a vague success badge.
Search delisted
- Kept in the case file
- The result, why it is limited, and the decision note.
- How it is labeled
- Search delisted — kept separate from a removal.
Follow-up
- Kept in the case file
- Match notes, only if follow-up is in the written agreement.
- How it is labeled
- Follow-up as agreed — not a promise to stop every repost.
Declined or referred
- Kept in the case file
- Why the matter does not fit our work, and the official option that remains.
- How it is labeled
- Said plainly, before any paid work.
What the client gets that this page does not.
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 item on its own.
Each link, search result, or post keeps its own record.
Label
Labels kept separate.
Request submitted, source removed, search delisted, and unresolved never merge into one result word.
Private
Details stay private.
This site shows the rules. The files, emails, and our private answer stay in the case file.
Close
A written close.
The case file shows what is done, what remains, and what we advise against paying for.
Before anything is published
What has to be true before we publish.
Read this section: What has to be true before we publish.
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.
Save
What can be saved without sharing the content again?
- Kept private
- A private record for each item. The details stay in the client's case file.
- What can be said publicly
- Kept private. Examples on this site are hypothetical, not edited client files.
Check
Can it be checked again later?
- Kept private
- A private decision note that can be checked again inside the case file.
- What can be said publicly
- Request submitted, source removed, search delisted, unresolved, or declined.
Label
Which label is accurate?
- Kept private
- A private note recording which label was chosen and why.
- What can be said publicly
- One of the result labels — never upgraded to a stronger one.
Publish
What is safe to say publicly?
- Kept private
- Written client consent, identifying details removed, and a review date wherever a number appears.
- What can be said publicly
- General rules first. A client's facts stay private unless every check is met.
Publication states
Public rules
Public definitions, result labels, clearly marked hypothetical examples, and privacy-safe claim language.
Private case file
Receipts, screenshots, correspondence, and identifying facts stay in the confidential case file.
Limited result
Search-only work stays labeled as search-only.
Never published
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.
Labeling standard
How results get labeled.
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.
What a public claim needs.
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.
Why case details stay private.
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.
The public standard, unpacked.
Record
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
Evidence stays private inside the case file. Nothing on this site links to a real file.
Scope
What is included is written into each client's scope. How a specific case was handled is never published.
48h
Under the TAKE IT DOWN Act, a covered platform must remove qualifying non-consensual intimate imagery within 48 hours after a valid request from the person shown or someone authorized to act for them. That is the platform's legal duty, not an AboutUs turnaround.
The labeling rule.
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.
Labeling rule · format — not client data
Source
Source removed
- What must be true
- The item is gone from the page where it was posted, and the link was checked.
- How it is reported
- Counted only as source removed — never merged with search results.
Search
Search delisted
- What must be true
- The page may still exist, but a search engine no longer shows it for the request.
- How it is reported
- Labeled search delisted, never as a removal.
Request
Request submitted
- What must be true
- A request was sent to the host, platform, or search engine.
- How it is reported
- Activity, not a result.
Open
Unresolved
- What must be true
- No change yet, or the request was refused.
- How it is reported
- Labeled unresolved — not hidden or left out.
Decline
Declined
- What must be true
- We say why, and point to a safer option or an official channel.
- How it is reported
- Not sold as paid work.
Counts
Operating counts
- What must be true
- Owner-maintained counts with a review date.
- How it is reported
- 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.
What we will never show you.
- Fake testimonials. We publish no client quotes or testimonials on this site.
- 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.
Outcomes vary. Third parties make the final decision, and your written scope defines what counts as done and how refunds work.
The client’s written report.
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.
| Item | Label |
|---|---|
| ITEM-01 | Source removed · example |
| ITEM-02 | Request submitted · example |
| ITEM-03 | Search delisted · example |
| ITEM-04 | Unresolved · example |
| FOLLOW-UP | Only if in written agreement |
Re-upload follow-up
If it comes back, the case does not start from zero.
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.
- Fingerprint. 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.
- Watch list. Public names, handles, and links the client authorizes stay on the written monitoring scope. Possible matches stay internal until a person checks them.
- Follow-up. 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