How to correct or remove information from DeepSearch
Quick answer
Report a wrong or mismatched result to DeepSearch support with the exact result URL, field, and source. Use Remove my info to suppress a public person or phone page, choosing full removal or search deindexing. Use Delete account for your login, history, saved profiles, and settings. Correct a third-party source and clear stale search-engine copies separately because DeepSearch cannot alter those systems.
- Correction, public-page removal, deindexing, third-party source deletion, and customer-account deletion affect different layers.
- An exact DeepSearch page link or phone number can be routed immediately; a shared name needs human matching.
- Provide only the result URL, disputed field, source, problem type, and a current authoritative correction when available.
Topics: DeepSearch corrections · Content removal · Deindexing · Account deletion
Use DeepSearch's correction or removal path according to what is wrong. Report a misstated or mismatched result to support with the exact result URL, field, and source. To remove a matched record from search results or stop publishing a public person or phone page, use Remove my info. To erase your DeepSearch account and product history, use Delete account. These actions affect different
data and do not erase a third-party source or a search engine's cached copy.
Choose the outcome you need
Scroll horizontally to compare all columns
One request cannot do all of these jobs because the publisher, index, public page, and customer account are different systems.
Report an incorrect result
Use DeepSearch support and include the minimum evidence needed to locate and check the problem:
- the exact DeepSearch result or public page URL
- the field or sentence that is wrong
- the source link shown for that field
- whether the problem is factual error, stale information, a namesake mix-up, missing context, or a source that no longer supports the summary
- a current authoritative source, when one exists
Do not email passwords, identity documents, full payment-card details, or a large dossier of unrelated personal information. If a sensitive document is truly necessary, first ask support for the appropriate secure route.
Correct the upstream source too when it is wrong. Otherwise the same statement can return in a later search or continue appearing elsewhere on the web.
Remove a public DeepSearch page
The Remove my info page has two separate forms. Neither requires a paid account.
For search-results removal, enter your name and an email address you control, then enter the six-digit verification code sent to that address. Nothing is withheld until verification succeeds. DeepSearch uses the confirmed address to match the provider record and withhold its associated identifiers from results on the website, apps, and API. This does not delete an upstream provider's own copy.
For public-page removal, use the form accepting a phone number, a person's name, or the exact DeepSearch subject-page URL:
- A phone number or exact page link can be routed to one subject and is suppressed immediately when the request succeeds.
- A name alone can refer to several people, so it is recorded for human matching rather than removing a possibly unrelated page automatically.
- The confirmation states whether DeepSearch interpreted the request as a phone number or a person. Check that message before leaving the page.
The form offers two scopes:
- Remove the page entirely: the DeepSearch page stops resolving.
- Keep the page, remove it from search: the link can continue working, but the page is excluded from search indexing.
Save the confirmation and the URL you submitted. If the form interpreted the subject incorrectly, resubmit the exact page link or contact support.
Understand the limit of a DeepSearch removal
A DeepSearch delisting controls DeepSearch's own public page and future publication rules. It does not:
- edit or delete the original publisher's page
- remove a government or court record
- opt you out of an unrelated data broker
- instantly clear a search engine's cached copy
- delete your DeepSearch customer account
Use the personal-information search-removal workflow for source and search-engine layers, and the broker opt-out directory for broker listings.
California residents can use the state's Delete Request and Opt-out Platform (DROP) to send a single deletion request to over 600 registered data brokers. DROP launched January 1, 2026; data brokers must process requests starting August 1, 2026, and have up to 90 days to report initial status. DROP deletion applies to personal information collected from third parties, with exemptions for public records such as
vehicle or real estate ownership, voting records, and information protected by federal privacy laws including FCRA credit information and HIPAA health information. DROP is a California state tool for data brokers generally and is separate from DeepSearch's own removal process described above.
Delete your customer account separately
Account deletion concerns the data connected to your use of DeepSearch: saved searches, history, saved profiles, settings, and related product data. The Delete account page explains the in-product route and the email route when you cannot sign in. Limited billing, fraud-prevention, security, tax, or dispute records may be retained where required.
Deleting an account does not automatically identify and delist every public page that might be about the account holder. Submit the public-page removal as a separate request when needed.
Verify the outcome at each layer
After a correction or removal:
- open the exact DeepSearch URL in a fresh session
- confirm the page is corrected, unavailable, or marked not for indexing, according to the requested scope
- check the original source separately
- check major search engines after their normal refresh interval
- retain the request date, confirmation, URLs, and any response
If a removed record later reappears, compare the URL and identifiers with the original request. It may be a new upstream record, another namesake, or a stale search copy rather than the same page being restored. Use the reappearance guide to classify it before submitting another request.
Sources and references
Getting Started
Reviewed by DeepSearch Research and Safety Team on October 23, 2026. Re-check trigger: Any removal-form, suppression timing, deindexing, correction, support, account-deletion, or retention change
DeepSearch
Accepted subjects, no-account workflow, immediate versus reviewed requests, confirmation, scope choices, and limits
DeepSearch
In-product and email account-deletion routes, covered product data, timing, and limited retention categories
DeepSearch
The current support and privacy-concern contact route
What we do - and don't do - with public data
DeepSearch
The source-link commitment, correction expectation, removal route, and source-versus-summary distinction
Google Search Help
Refreshing Google results after a source page or image is removed or materially changed
Delete Request and Opt-out Platform (DROP)
California Privacy Protection Agency
California residents can use the state's Delete Request and Opt-out Platform (DROP) to send a single deletion request to over 600 registered data brokers. DROP launched January 1, 2026; data brokers must process requests starting August 1, 2026, and have up to 90 days to report initial status. DROP deletion applies to personal information collected from third parties, with exemptions for public records such as
vehicle or real estate ownership, voting records, and information protected by federal privacy laws including FCRA credit information and HIPAA health information. DROP is a California state tool for data brokers generally and is separate from DeepSearch's own removal process described above.