“My home address and phone show up on Google and on people-search sites. Remove them. What is the price per year?”

The steps

1. 1

   Ask where the person lives, never the details

   A home address and a phone number are the situation contact-info. Where the person lives decides which Google features and laws apply, so without a region the checker returns 1 question. It never needs the address, the phone number, the name or a link.

   MCP tool call: find_removal_route

   Copy

   {
     "situation": "contact-info"
   }

   Same call over REST

   Copy

   curl -X POST https://essentras.com/api/agent/v1/check/removal-route \
     -H 'Content-Type: application/json' \
     -d '{"situation":"contact-info"}'

   Real response, trimmed. Captured 19 Oct 2026

   Copy

   {
     "status": "needs_answers",
     "summary": "Where do you live? This changes which laws and Google features apply to you.",
     "situation": {"id": "contact-info", "label": "My phone number, home address or email"},
     "needs": [
       {
         "field": "region",
         "options": [
           {"id": "us", "label": "United States"},
           {"id": "eu", "label": "EU, EEA or UK"},
           {"id": "other", "label": "Somewhere else"}
         ]
       }
     ]
   }

   What to read: status is needs_answers: the agent asks the question in needs, then calls again with the answer.

2. 2

   Google results: Results about you, then the removal form

   Contact details are on Google’s private info list, so the route is Google policy. Results about you finds results that show the details and lets the person request removal; the removal request form covers any URL it misses.

   MCP tool call: find_removal_route

   Copy

   {
     "situation": "contact-info",
     "region": "us"
   }

   Same call over REST

   Copy

   curl -X POST https://essentras.com/api/agent/v1/check/removal-route \
     -H 'Content-Type: application/json' \
     -d '{"situation":"contact-info","region":"us"}'

   Real response, trimmed. Captured 19 Oct 2026

   Copy

   {
     "summary": "Google policy: Results about you, then the removal form. Honest odds: Good fit.",
     "route": {
       "title": "Google policy: Results about you, then the removal form",
       "who_decides": "Google"
     },
     "do_it_yourself": {
       "steps": [
         "Search your name in a private window and list every result that shows your details, with its exact URL.",
         "If you can edit or delete it yourself, such as your own profile or blog, do that first. Google will not remove what you can remove yourself.",
         "Open Results about you, add the details you want Google to look for, and request removal of each matching result.",
         "For anything it does not catch, submit the URL through Google’s removal request form and say which detail it shows.",
         "Ask the site to delete your details too, so they are gone at the source and not only hidden in Google."
       ],
       "official_links": [
         {
           "label": "Results about you (Google)",
           "url": "https://myactivity.google.com/results-about-you"
         },
         {
           "label": "Google’s removal request form",
           "url": "https://support.google.com/websearch/contact/content_removal_form"
         },
         {
           "label": "Google’s private info policy",
           "url": "https://support.google.com/websearch/answer/9673730"
         }
       ]
     },
     "timeline": {
       "text": "Google says Results about you alerts arrive within a few hours of a match, and approved removals may not take effect immediately. It states no timeline for the removal form.",
       "label": "Official: stated by Google"
     },
     "fit": {"label": "Good fit"},
     "will_not_do": "It hides results in Google Search only. The page and your details stay online, and other search engines are not affected."
   }

   What to read: timeline.label is “Official: stated by Google”. will_not_do: the page and the details stay online and other search engines are not affected, so the last step asks the site to delete them too.

3. 3

   People-search sites: each broker’s own opt-out

   A people-search profile is the situation data-broker. The route is the source: each broker runs its own opt-out, and Google keeps showing a profile until it is gone and recrawled.

   MCP tool call: find_removal_route

   Copy

   {
     "situation": "data-broker",
     "region": "us"
   }

   Same call over REST

   Copy

   curl -X POST https://essentras.com/api/agent/v1/check/removal-route \
     -H 'Content-Type: application/json' \
     -d '{"situation":"data-broker","region":"us"}'

   Real response, trimmed. Captured 19 Oct 2026

   Copy

   {
     "summary": "Source: each broker’s own opt-out, then Google. Honest odds: Good fit.",
     "route": {"title": "Source: each broker’s own opt-out, then Google"},
     "do_it_yourself": {
       "steps": [
         "Search your name with your city and list every people-search profile that appears.",
         "Use each broker’s own opt-out page, often linked from its privacy policy, or send template 6.",
         "Add your contact details to Results about you so Google flags profiles that show them.",
         "Once a profile is gone, use Refresh Outdated Content if Google still shows it.",
         "Check again every few months: removed profiles can come back."
       ],
       "templates": [
         {"id": "t6", "title": "Template 6: Data broker opt-out request"},
         {"id": "t7", "title": "Template 7: Follow-up"},
         {"id": "t4", "title": "Template 4: Refresh Outdated Content checklist"}
       ]
     },
     "timeline": {"label": "No official timeline"},
     "fit": {
       "label": "Good fit",
       "why": "An opt-out removes the profile at the source, and Results about you covers contact details. Data-removal vendors say on their own pages that records tend to come back."
     },
     "will_not_do": "Opting out of 1 broker does not remove you from the others, and Google keeps showing a profile until it is gone and recrawled."
   }

   What to read: The last step says to check again every few months, because removed profiles can come back, and fit.why adds that data-removal vendors say records tend to come back. Template 6 is the opt-out request.

4. 4

   Price the service: per case, no yearly priceService step

   The buyer asked for a price per year. quote_service returns no amount and no subscription: the service starts with a free scan, start_url is null and terms is null.

   MCP tool call: quote_service

   Copy

   {
     "id": "remove-personal-information-internet"
   }

   Same call over REST

   Copy

   curl https://essentras.com/api/agent/v1/services/remove-personal-information-internet

   Real response, trimmed. Captured 19 Oct 2026

   Copy

   {
     "id": "remove-personal-information-internet",
     "name": "Remove personal information from the internet",
     "start_url": null,
     "price": {
       "amount": null,
       "label": "Free scan first, then a price for your case before you pay",
       "basis": "per_case"
     },
     "options": [],
     "terms": null,
     "decides": "Each site and Google decide.",
     "free_check": null,
     "how_to_buy": "This service starts with a free assessment: send the buyer to url. The agent never pays."
   }

   What to read: price.label: “Free scan first, then a price for your case before you pay” With no start_url, the handoff is url, where the free scan starts. decides: “Each site and Google decide.”