Privacy request kit: choose a route and track the outcome

Delist · Updated October 5, 2026 · Corrections

Choose the route for your problem

Check the exact source URL first. Similar-looking problems can need different requests. These routes are starting points; provider rules and eligibility still apply.

Prepare before submitting

1. Identify the target. Keep the exact URL, check date and matching details. A shared name alone is not enough.
2. Confirm the destination. Reach the process through the provider's current official site or help center. A forwarded address, old guide or working domain alone does not verify the recipient.
3. Check authority and requirements. Confirm eligibility and any required permission to act. Use only the personal data needed by that process.
4. Choose the action. Name the listing and the requested change. Suppression, deletion, correction and search-result removal have different scopes.
5. Keep a private record. Save receipts and responses securely. Use a reference in the tracker instead of passwords, full identity documents or sensitive account numbers.

A starting message for a verified request channel

Use the provider's required form where one exists. If its official process accepts a written request, adapt this starting message to that process. It does not establish a legal right, agent authority or a universal deadline.

I am requesting [the supported action] for the listing at [exact URL]. The listing concerns [me, or a person I am authorized to represent under your requirements]. Please tell me how to complete any required verification through your official process. Please confirm the action taken, its scope and any next step needed from me.

Remove any statement that is not true for you. Do not paste passwords, recovery codes or full government identifiers into this message. If you are acting for another person, check the provider's authorization process first.

Interpret the response before choosing a next step

• Received: save the acknowledgment. It establishes receipt, not completion.
• Needs verification: check the recipient and requirement through the official process before sharing additional personal data.
• Expired link: use the current official instructions for a replacement; preserve the earlier receipt.
• Denied or no match: read the stated reason and check the target, eligibility, scope and required evidence. Do not repeat an unchanged request without a supported next step.
• Action confirmed: record exactly what the provider says changed, then make a separate visibility observation where possible.
• Access blocked: a CAPTCHA, login requirement or unavailable page is an inconclusive check. It does not establish removal.

Use the tracker's separate evidence log for repeated checks. Record the actual date, URL, access context, source of the observation and next step. A single successful check does not establish permanent absence or deletion from every copy.

Keep outcomes within their scope

Suppression can limit display in a particular product without deleting underlying records. A search decision can remove a result fully or only for identifying queries while the source remains live. A broker opt-out does not remove the government record that supplied the data. Check each destination separately.

Five dated provider examples

The sample below was reviewed on October 1, 2026. It illustrates different requirements and retrieval limits; it is not a current Delist coverage roster or a tested workflow.

This is a dated reference, not a ranking of services. A working link alone does not establish that a removal process is usable or that a request succeeded.

Review a possible match before requesting removal

A shared name is a starting point. Compare the listing’s city, approximate age, current or past addresses, and contact details with information you recognize. Review the person’s own record, rather than borrowing details from relatives or other rows on a directory page. Missing or conflicting details leave the match uncertain.

A name and city match, shared address, or confidence label does not by itself authorize a removal request for another person. Only claim your own listing or act with the required authorization. Keep a possible match, identity review, permission to submit, request receipt, and removal result separate.

If a listing mixes your personal data with someone else’s, record the exact URL and which fields belong to you. Use the provider’s verified privacy or correction channel, and share only the information required for that process. Do not send full sensitive identifiers in ordinary email. An inaccurate employment background report needs the reporting company’s dispute process; a people-search opt-out does not correct that report. See the accuracy and correction guide and the FTC’s employment background-check guidance.

A record you can keep privately

1. Save the exact listing or account URL and the date you checked it. Record matching and conflicting details separately before choosing which record to request.
2. Confirm the request destination through the provider’s current website or help center.
3. Record the fields requested and how the provider verifies identity or authority.
4. Save the acknowledgment separately from the completed-removal evidence.
5. Check the original listing again after processing. Treat search-result updates, source removal, and model-training preferences as different outcomes.

Download the blank request tracker (CSV). Its column guide keeps the submission, provider response, listing checks and supported outcome apart.

Keep this record in your own notes. This page does not ask you to upload personal data or identity documents.

How we reviewed the sources

Delist editorial compared the five destinations’ public instructions on the date shown above. The sample was chosen to illustrate different request types: professional profiles, people-search listings, stale search results, and AI account controls. It is not a representative survey of all data brokers.

We inspected documentation and public status pages, not private accounts or completed workflows. Nuwber’s live form could not be retrieved, so its current fields and processing time remain unverified. A domain-transfer notice at Centeda is evidence about its public website, not proof of deletion from every database.

Provider forms and policies can change. Check the official source again before submitting. Delist sells a removal service; this reference also supports people handling requests themselves.

Detailed guides

SignalHire · Centeda status · Nuwber · Old addresses and Google · Claude