Remove my info

This stops DeepSearch showing your record to anyone who searches for you, whether they search by your name, your email address or your phone number. Give us your name and an email address you can open. We email you a code, and the removal takes effect when you enter it.

We use the email address to find the record our data providers hold about you, then withhold every identifier on it: the address itself, the other emails and phone numbers on the record, and the provider's own record ID. That is why the removal keeps working when a provider refreshes its data, which is how people usually reappear on other sites.

The code stops someone else removing you. Anyone can type a name, so a name alone can't prove the request is yours.

DeepSearch also publishes some public pages: phone-number pages under /who-called-me and profile pages about public figures under /people. Enter the phone number, person's name, or page URL you want us to review. A phone number or direct page link identifies one record and can normally be suppressed automatically. A name can refer to several people and may require manual matching.

The form is free and does not require an account. Keep the confirmation so you can identify the request if you contact support. Submitting more copies of the same request does not make processing faster.

A search-results removal stops DeepSearch returning the record tied to your confirmed email address in any search, report, or answer, on the website, the apps and the API. A page takedown stops DeepSearch serving one public page built around a phone number or a public figure. They are separate because they remove different things, and you can use both.

A suppression is not an admission that the information was unlawful, inaccurate, private, or owned by the requester. It is a product and privacy safeguard that limits DeepSearch publication and access. It does not transfer ownership of a source record or change another person's rights.

A valid phone number or direct DeepSearch URL is normally suppressed as soon as the form succeeds. The page stops being served and the normalized subject is placed on a suppression list designed to prevent automatic republication. A name alone is recorded for review because an automatic name-wide block could remove a different person's page.

We may review a completed request afterward for fraud, abuse, ambiguity, duplicate identities, legal obligations, and documented public-interest context. Examples include a request targeting a public business line, a record needed to protect someone from fraud, or an attempt to suppress another person. If we reinstate or narrow a suppression, we record the reason and provide a review path when we have a way to contact the requester.

Names are not unique. Two people can share a legal name, professional name, city, employer, photograph, or username. Removing every result that matches a short name could suppress information about people who did not request removal and make it easier to misuse this process.

When you submit a name, include a DeepSearch URL or enough non-sensitive context to distinguish the correct page, such as a general location or public profile link. Do not send government identification, passwords, full payment-card details, or unrelated private records. If the confirmation shows the wrong interpretation, submit the direct URL or contact support.

Requiring a new copy of an identity document can create more privacy and security risk than the public page itself. For a readily reversible DeepSearch suppression, we default toward removal rather than collecting high-risk proof. A direct URL or phone number also gives us a precise technical target without proving who owns every underlying fact.

We may request proportionate verification for a formal access request, an account request, an authorized agent, an appeal, a contested record, or a situation where disclosure to the wrong person would create harm. Verification is limited to what is reasonably necessary for the request and does not require you to create a paid account.

If you prefer correction rather than suppression, email the page URL, the specific field, why it is wrong, and a reliable public source supporting the correction. Because DeepSearch can combine several sources, correcting one source may not resolve another. We may update, remove, label, or disconnect a candidate match depending on the evidence and the product.

We will not ask you to prove that every true public fact should remain accessible. A removal request and an accuracy dispute are separate safeguards: you may request suppression even if you do not want to litigate accuracy, and you may challenge an incorrect association without asking us to remove all references to you.

We may retain a normalized phone number, page identifier, name and matching context, one-way hashes of the email addresses, phone numbers and provider record ID that a search-results removal withholds, the email address you confirmed, request timestamp, status, source route, audit notes, and limited technical security data. This record is used to honor the request, prevent the same page from being rebuilt, deduplicate submissions, investigate abuse, demonstrate compliance, and resolve an appeal.

Keeping a suppression key is different from continuing to publish the page. We restrict access to the record and do not use it to create a new people-search result, advertise to you, or sell the removal request. We retain it for as long as reasonably needed to keep the suppression effective and meet legal, security, and dispute obligations.

We may deny, narrow, or reverse a request where we reasonably determine that it targets the wrong person, is fraudulent or manifestly abusive, conflicts with a legal duty or court order, would defeat security or fraud prevention, or materially interferes with another person's rights. We consider the nature and sensitivity of the information, the requester's safety, public role, source, accuracy, age, context, and likely harm.

An exception is applied narrowly. Public availability alone does not make every use fair, and a public role does not eliminate privacy rights. Conversely, this form is not a tool to rewrite an independent public record, hide a business from documented consumer complaints, suppress journalism at its source, or interfere with lawful proceedings.

We can stop serving our own page or result. We cannot use this form to delete a court, government, news, social-media, business-directory, data-broker, telecom, or other independent source record. Contact the source if you want its original record corrected or removed.

Search engines and archives may keep a cached copy for a period after our page is suppressed. Their refresh schedules and expedited-removal tools are outside our control. A shared screenshot, export, or copy made by another user before suppression also cannot be recalled automatically.

A public result about a person and a customer account are separate records. This form suppresses the identified public output; it does not cancel a subscription, close a login, erase billing history, delete searches, or remove uploaded files from an account.

To close your account, use the process on Delete Account. If both actions are relevant, submit both. Cancel an Apple or Google subscription in the applicable store even if you also delete the DeepSearch account.

Remove my info is a free request directed at DeepSearch output. Data Cleanup is a separate paid, authorized campaign that submits requests to participating third-party data brokers using identity details you provide. Buying Data Cleanup is not required to suppress a DeepSearch page.

A DeepSearch suppression does not start a broader broker-removal campaign, and a Data Cleanup order does not guarantee removal from DeepSearch unless the relevant DeepSearch page is also identified or matched. See the Terms of Service for campaign limits.

An authorized agent may submit a request, but we may ask for proof of authority and direct confirmation from the person where appropriate. A parent or legal guardian may request suppression for a minor or protected adult. Do not upload a child's identity document unless we specifically request a secure form of verification.

If a page creates an urgent safety risk, such as exposing a protected address, facilitating stalking, or identifying a minor, state "Urgent safety" in an email to support@deepsearch.app, include the exact URL, and explain the risk without sending unnecessary sensitive details. This channel is not an emergency service; contact local emergency services when immediate physical safety is at risk.

A direct number or URL is normally suppressed immediately after a successful automated submission. We aim to review an ambiguous name-only request or support escalation within 30 days, and we follow a shorter or longer period when applicable law requires it or permits a justified extension. We will explain an extension or request missing information.

If you believe we matched the wrong page, failed to suppress the result, reinstated it incorrectly, or denied a right, email the confirmation and URL with the subject "Removal appeal." A different reviewer will consider the new context when practical. You may also complain to a competent privacy or consumer authority.

This streamlined suppression path does not limit a right to access, know, correct, delete, restrict, object, opt out of covered sale or sharing, or obtain a portable copy under applicable law. Those broader requests may require verification and may be subject to legal exceptions. See the Privacy Policy for the categories, purposes, and regional disclosures.

For a formal request or a situation the form does not cover, email support@deepsearch.app. General help is available at support@deepsearch.app. We do not charge for an ordinary request or provide unlawfully different service because someone exercised a privacy right.

DeepSearch is operated by RELOAD TECHNOLOGIES - FZCO.