Data broker opt-out not working? Find the failed step
An opt-out that appears not to work may be incomplete, apply to a different record, still be processing, or have succeeded at the source while a search result remains. Find the failed step before repeating the request.
Sources
- FTC: people-search source and recurrence limits
- California AG: rights, verification, and complaints
- FastBackgroundCheck: current documented flow
Sources accessed October 4, 2026. This is a public-documentation review; no requests were submitted or outcomes measured.
California complaint and DROP references checked October 5, 2026 (UTC); this does not re-verify every provider workflow.
Start with the exact record
Open the URL you requested and compare it with your saved record. A similar name, a second profile, a different search mode, or another provider can explain a result that looks unchanged. Confirm the listing belongs to you. If it mixes people, identify which fields are yours and use the provider's correction or privacy channel without claiming the whole record.
Locate the failure
| Observation | What to inspect | Next step |
|---|---|---|
| No acknowledgment | Did the form finish? Was there an error or CAPTCHA? | Save the error privately and check the official instructions. |
| No email link | The entered inbox, spam folder, filters, and the provider's stated delivery guidance. | Use its official support route if the message does not arrive. |
| Expired link | The expiry shown in that provider's message. | Request a fresh link through the official process. |
| Acknowledgment only | Whether another confirmation step or identity check remains. | Complete only the documented outstanding step. |
| Still visible during processing | The submission date, completion of verification, and that provider's current estimate. | Recheck after the applicable processing guidance, rather than sending blind duplicates. |
| Provider says complete but the page remains | Exact URL, fields, response scope, and whether a new record is involved. | Ask the provider to reconcile the visible record with its response. |
| Source changed but Google still shows it | Whether the result points to the same changed URL. | Follow the Google post-removal guide. |
| CAPTCHA, login wall, or loading failure | Whether you could actually inspect the target. | Record an inconclusive check, not success or failure. |
Keep the provider's clock separate from your notes
For example, FastBackgroundCheck's documented flow distinguishes the email-link deadline from its processing guidance. Those timings do not apply to another broker. A voluntary suppression process and a statutory deletion request can also have different requirements. Keep the request type, confirmation date, and any stated deadline together.
Do not start a new timer every time you check a page. Keep the original receipt, later responses, and dated observations in the private tracker. Exclude identity documents, full sensitive identifiers, confirmation links, and recovery codes from a shared log.
Ask support a precise question
Use the provider's current official privacy or support channel. Explain the requested action, submission date, reference number if appropriate, and the specific remaining URL. Ask whether another step is required and what the response covers. Supply personal data only through the verified channel and only as required. This privacy request kit helps prepare the record.
If identity verification is the obstacle, consult the verification guide. Do not assume that every provider accepts email in place of a document.
If information reappears
Preserve the earlier successful visibility observation. Record the new URL, date, and exposed fields as a new observation. A duplicate record, fresh source data, or another publisher may require a different request. Shared ownership does not prove shared suppression, and a new listing does not prove the original request was never processed.
Check the exact site's current procedure before requesting another removal. Investigate whether a lawful source record can be corrected or have public access limited through its own process. Do not assume a broker opt-out erases an original government record.
When a rights complaint may be appropriate
First distinguish the requested right from voluntary website suppression. Eligibility, the business, the data, and exceptions matter. For California requests, consult the CPPA’s CCPA guidance and current complaint instructions. Eligible California residents can also use DROP for registered data brokers. DROP and a direct website request are separate routes; neither establishes deletion of every record or source. A complaint is not a guarantee of individual removal or a substitute for completing verification. Other jurisdictions have their own rules; consult the applicable authority.
Frequently asked questions
How long should I wait before trying again?
Should I send the same request every day?
Does a provider confirmation prove removal?
More guides
Find out what data brokers know about you
Start with a free scan to review possible exposure. Review service scope and any required authorization separately.