Google AI Search Privacy: Better Alternatives to Protect Your Searches

Part of AI Tools + Private AI Hub

Last updated: May 20, 2026

August 2026 check: the alternatives below still hold, and the chat-control fight moved to the EU back-door story this month.

Google Search is changing from a list of websites into an answer machine. That sounds convenient until you look at what it means for privacy, publishers, and user choice.

AI Overviews can summarize information before you ever click a source. Google says this helps people ask more complex questions and find information faster. The problem is that users, publishers, and independent website owners are being pushed into a new bargain they did not clearly choose: Google gets the query, Google gets the answer box, Google keeps the user, and the open web gets whatever clicks are left over.

What Google AI Search Changes

Google introduced AI Overviews to generate answers at the top of many search results. In May 2024, Google said AI Overviews would roll out to everyone in the United States and that it expected to bring the feature to more than a billion people by the end of that year.

Google describes this as a way to let Search do more work for users. The company says AI Overviews help people ask more complex questions, get quick summaries, and discover a greater diversity of websites.

That is the friendly framing. The more serious version is this: Google is moving from being a gateway to websites to being the place where more answers are consumed directly.

That matters because search queries are not random. They reveal health fears, legal problems, political curiosity, financial stress, relationship issues, business plans, and private intent. AI search encourages longer, more conversational, more revealing queries. Instead of typing a few keywords, people ask full personal questions.

That makes search privacy more important, not less.

Why People Are Angry About AI Overviews

The frustration is not just that Google added AI. The frustration is that Google placed AI summaries into a product people already depend on, then made the classic list of links feel secondary.

For many users, search is supposed to do one simple thing: show the best places to go next. AI Overviews change the experience into something closer to a platform-controlled summary.

That creates four problems:

1. User agency drops. You see Google’s synthesized answer before choosing your own sources.
2. Publisher traffic can fall. If the answer is already on Google, fewer people click through.
3. Source context gets flattened. A cited source is not the same as a visited source.
4. Search privacy gets more sensitive. AI prompts can reveal more than normal keywords.

The Click Problem: Sources Get Cited, But Do They Get Traffic?

Pew Research Center analyzed browsing data from 900 U.S. adults who agreed to share online activity. Pew found that users clicked traditional search results on 8% of Google search visits when an AI summary appeared, compared with 15% of visits when no AI summary appeared. Pew also found that users clicked a source link inside an AI summary only 1% of the time.

That is the key issue. A website can be credited and still lose the visit, the ad impression, the newsletter signup, the donation, the affiliate click, or the reader relationship.

Ahrefs also analyzed 300,000 keywords and reported that AI Overviews correlated with a 34.5% lower average click-through rate for the top-ranking page compared with similar informational keywords without an AI Overview. That is not a randomized experiment, so treat it as directional, not absolute. Still, it lines up with the common publisher fear: AI answer boxes can absorb the value of informational searches.

Google disputes the doom narrative. It says links in AI Overviews can get more clicks than if the page appeared as a traditional listing for that query. The problem is transparency. Publishers still need clean reporting that separates AI Overview impressions, AI Overview citations, AI Overview clicks, and standard organic search data.

What This Means For The Internet

The old web bargain was simple:

1. People publish useful pages.
2. Search engines index those pages.
3. Users click through to the source.
4. Publishers earn traffic, trust, revenue, or audience.

AI search risks changing that bargain:

1. People publish useful pages.
2. Search engines ingest and summarize those pages.
3. Users stay on the search engine.
4. Publishers get fewer direct relationships with readers.

If that becomes the default, the open web gets weaker. Small sites are hit hardest because they often depend on search discovery. Big brands can survive through apps, subscriptions, direct traffic, newsletters, and legal pressure. Smaller writers, hobby sites, local guides, independent reviewers, forums, and niche experts have fewer escape routes.

That is why this is not just a search feature. It is an internet infrastructure issue.

Why You Should Care Even If You Like AI

You can like AI tools and still reject forced AI layers in search.

The issue is not whether AI summaries are sometimes useful. They are. The issue is whether one company should control the answer layer for the public web while also running the ad market, browser, mobile operating system, analytics stack, video platform, and search monopoly.

When a search engine becomes the answer engine, it gains more power over:

• Which sources are visible.
• Which claims are summarized.
• Which publishers survive.
• Which questions are considered answered.
• How much context users reveal in queries.

Convenience is real. So is centralization.

Best Privacy Search Alternatives

SearXNG

SearXNG is a free metasearch engine. It aggregates results from many search services and is designed to avoid tracking or profiling users. It can be used through public instances, but the strongest privacy benefit comes from running your own private instance.

Best for: people who want control, self-hosting, and a search engine they can configure.

Downside: you need a VPS or home server, Docker or another install method, and basic maintenance. Upstream engines may also rate-limit requests.

Brave Search

Brave Search is one of the easiest serious replacements because it has its own independent index and does not require you to self-host anything. It includes AI features, but it is not built on the same Google results dependency as many alternatives.

Best for: users who want a quick default search replacement.

Kagi

Kagi is paid search. That turns some people away, but it also fixes the incentive problem. If a search company is paid by users, it does not need to monetize attention the same way an ad-funded engine does.

Best for: people who would rather pay with money than with behavior data.

Startpage

Startpage is useful if you still want Google-like result quality but do not want to search directly through Google. It is not self-hosted, so you still trust Startpage as a middle layer.

DuckDuckGo

DuckDuckGo is the easiest mainstream privacy switch. It is not perfect, and it depends on partners for much of its search data, but it is still a practical step away from Google tracking for everyday users.

Mojeek and MetaGer

Mojeek matters because it runs its own crawler and index. MetaGer matters because it is a nonprofit metasearch option. Both are useful if you want to escape the Google and Bing monoculture.

How To Run SearXNG On A VPS

The cleanest setup is a small VPS with Docker Compose and a reverse proxy such as nginx or Caddy. Do not expose a personal SearXNG instance carelessly. If it is public, it can be abused. For personal use, put it behind a domain, private network, or access control.

1. Install Docker

sudo apt update
sudo apt install -y ca-certificates curl gnupg docker.io docker-compose-plugin
sudo systemctl enable --now docker
sudo usermod -aG docker "$USER"

Log out and back in so the Docker group change applies.

2. Create the SearXNG folder

mkdir -p ~/searxng/core-config
cd ~/searxng

3. Use the current official container template

curl -fsSLO https://raw.githubusercontent.com/searxng/searxng/master/container/docker-compose.yml
curl -fsSLO https://raw.githubusercontent.com/searxng/searxng/master/container/.env.example
cp -i.env.example.env

Edit the .env file. For a reverse proxy on the same server, binding to localhost is usually safest:

SEARXNG_HOST=127.0.0.1
SEARXNG_PORT=8080

4. Add basic settings

nano ~/searxng/core-config/settings.yml

Use this as a starting point:

use_default_settings: true

general:
  debug: false
  instance_name: "Private SearXNG"

search:
  safe_search: 0
  autocomplete: "duckduckgo"
  formats:
    - html

server:
  secret_key: "REPLACE_WITH_LONG_RANDOM_SECRET"
  base_url: "https://search.example.com/"
  limiter: true
  image_proxy: true
  public_instance: false
  method: "POST"

valkey:
  url: valkey://searxng-valkey:6379/0

Generate a real secret:

openssl rand -hex 32

5. Start it

docker compose up -d
docker compose ps

Test locally:

curl http://127.0.0.1:8080/

Reverse Proxy With Nginx

Point a subdomain such as search.example.com to your server, then add an nginx site:

server {
    listen 80;
    server_name search.example.com;

    location / {
        proxy_pass http://127.0.0.1:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Then add HTTPS:

sudo apt install -y certbot python3-certbot-nginx
sudo certbot --nginx -d search.example.com

Caddy is simpler if you prefer automatic HTTPS:

search.example.com {
    reverse_proxy 127.0.0.1:8080
}

Can You Run SearXNG On Android With Termux?

Yes. It is possible, but it is not the path I would recommend for a public search instance. A properly secured VPS is more stable. A phone setup is best for personal experiments, travel, emergency use, or learning how the stack works.

Option A: Native Termux install from Git

This uses the same basic idea as the official non-Docker SearXNG install: clone the repository, create a Python environment, install dependencies, point SearXNG at a settings file, and run the web app locally.

pkg update && pkg upgrade
pkg install -y git python clang rust libxml2 libxslt openssl libffi

mkdir -p ~/apps
cd ~/apps
git clone https://github.com/searxng/searxng.git
cd searxng

python -m venv ~/searxng-venv
. ~/searxng-venv/bin/activate
pip install -U pip setuptools wheel
pip install -U pyyaml msgspec typing-extensions pybind11
pip install --use-pep517 --no-build-isolation -e.

mkdir -p ~/.config/searxng
cp utils/templates/etc/searxng/settings.yml ~/.config/searxng/settings.yml
openssl rand -hex 32

Edit ~/.config/searxng/settings.yml. At minimum, set a long random server.secret_key. For phone use, keep it local unless you know exactly what you are exposing.

export SEARXNG_SETTINGS_PATH="$HOME/.config/searxng/settings.yml"
cd ~/apps/searxng
python -m searx.webapp

Then open:

http://127.0.0.1:8888

Option B: Debian in Termux with proot-distro

If native Termux dependencies fight you, use a Debian userspace. This is heavier, but it behaves more like the official Linux install path.

pkg update
pkg install -y proot-distro
proot-distro install debian
proot-distro login debian

apt update
apt install -y git python3-dev python3-venv python-is-python3 build-essential libxslt-dev zlib1g-dev libffi-dev libssl-dev

useradd --shell /bin/bash --home-dir /usr/local/searxng --create-home searxng
su - searxng
git clone https://github.com/searxng/searxng /usr/local/searxng/searxng-src
python3 -m venv /usr/local/searxng/searx-pyenv
. /usr/local/searxng/searx-pyenv/bin/activate
pip install -U pip setuptools wheel pyyaml msgspec typing-extensions pybind11
cd /usr/local/searxng/searxng-src
pip install --use-pep517 --no-build-isolation -e.

From there, create a settings file and run python -m searx.webapp with SEARXNG_SETTINGS_PATH set, like the native option.

Keeping it alive on Android

Android may kill background work. The most stable workarounds are:

• Disable battery optimization for Termux.
• Install Termux:API and run termux-wake-lock.
• Run SearXNG inside tmux so the process survives disconnects.
• Keep the instance bound to 127.0.0.1 for local phone use.
• Use Tailscale or WireGuard if you need private access from other devices.

pkg install -y tmux termux-api
tmux new -s searxng
termux-wake-lock
export SEARXNG_SETTINGS_PATH="$HOME/.config/searxng/settings.yml"
cd ~/apps/searxng
. ~/searxng-venv/bin/activate
python -m searx.webapp

What about Docker on Android?

Docker on Android usually requires root, a custom kernel, or Linux container workarounds. If you already run a rooted Android/Linux environment, you can try it. For most people, native Termux or proot-distro is more realistic. For anything public or daily-use, a $5 VPS with nginx or Caddy is still the sane choice.

How To Make SearXNG Your Browser Search Engine

Firefox Desktop

1. Visit your SearXNG instance.
2. Open Firefox search settings.
3. Add the site as a search engine if Firefox detects it.
4. Set it as your default.

Chrome or Brave Desktop

Open:

chrome://settings/searchEngines

Add a site search engine:

Name: SearXNG
Shortcut: sx
URL: https://search.example.com/search?q=%s

Phone

Firefox Android is usually easier than Chrome or Brave for custom search. If your mobile browser fights custom defaults, add your SearXNG instance to your home screen and use it like an app.

Final Recommendation

If you want the easiest privacy upgrade, switch your default search to Brave Search, DuckDuckGo, Startpage, or Kagi.

If you want control, run SearXNG on a VPS and use it from every device.

If you care about the open web, do not let one company turn every website into raw material for its answer box. Search should help you find sources. It should not replace the habit of visiting them.

Try it here: Venice AI private chat. If you try Venice through this link, TheThriftyDev may earn a referral benefit.

FAQ

Is Google AI Search private?

It is still Google Search, which means your activity can be handled under Google’s privacy policy and account settings. AI search can also encourage more detailed queries, which may reveal more sensitive context.

Can I turn off AI Overviews?

Google does not offer a universal permanent switch that restores classic search for every user and query. Availability and workarounds can change by region, browser, account, and product updates.

What is the best private alternative to Google Search?

For most people, Brave Search, DuckDuckGo, Startpage, or Kagi are easiest. For self-hosting and control, SearXNG is the strongest option.

What is SearXNG?

SearXNG is a free metasearch engine that aggregates results from many search services. It is designed to avoid tracking and profiling users.

Should I use a public SearXNG instance?

Public instances are convenient, but you must trust the instance operator. A private instance gives you more control.

Citations and Further Reading

• Google: Generative AI in Search, May 2024
• Pew Research Center: Google users are less likely to click on links when an AI summary appears
• Ahrefs: AI Overviews Reduce Clicks by 34.5%
• SearXNG documentation
• Startpage privacy policy
• DuckDuckGo privacy policy
• Brave Search
• Kagi
• Mojeek
• MetaGer

Private Search Alternatives Comparison

Self-Host SearXNG in 10 Minutes

docker run -d --name searxng -p 8080:8080 searxng/searxng:latest

Related Posts

• Run Your Own AI: The Beginner’s Guide to Local LLMs in 2026
• Private AI Is Becoming the New Developer Edge: Why Venice AI Fits the 2026 Shift
• n8n AI Agents: Self-Hosted Automation Guide (2026)

Update: the 4 year retention problem hiding inside AI search

The short answer first. Switching off your search history no longer stops Google from training on your data. If Google’s systems already selected your media for training, that copy is disconnected from your account and kept for up to four years, and deleting the original activity does not pull it back. You have to stop it before it is selected, and you have to do it on more than one settings screen.

Google split Search history into two controls

If you last audited your settings when Web & App Activity was the only switch that mattered, your map is out of date. Google’s own help page states: “In the past, saving history and personalized recommendations were managed by Web & App Activity and Search Personalization settings. Going forward, you’ll be able to manage history and personalized recommendations independently through 2 new settings: Search Services History, Personalized Recommendations.”

Search Services History covers Search, Maps, Shopping, Flights, Hotels, Translate and News. Google is equally clear about what it does not cover: “services that save history under other settings, such as Chrome, Gemini Apps, Google Assistant, and YouTube.” Gemini keeps its own store and its own clock, so turning off one has no effect on the other.

The roll out is staged, and Google says so: “These are rolling out gradually over the next few months. If the settings in this article do not match what you see, history and personalized recommendations for Search services are still controlled by Web & App Activity.” If your settings screen still looks like 2025, you are not seeing a bug, you are seeing the old layout.

What gets stored is wider than a list of queries: your search queries, generative AI responses in AI Mode or Ask Maps, recordings and transcripts from Search Live and voice searches, images uploaded to Lens, AI Mode or the try on tool, Maps places, Flights and Hotels bookings, Translate audio, News articles, the ads you click, and metadata including location data drawn from “your device’s general area and IP address.”

Save Media is the switch that actually matters

Inside Search Services History sits a subsetting called Save Media. Google describes it as “your images, files, and audio and video recordings from your interactions with Search services,” including Lens images, recordings from Search Live or Translate speaking practice, content you upload, and voice searches. Two exclusions matter: “Saved media doesn’t include media that you generate or modify with AI. It also doesn’t include media you share publicly on Search services, like photos added to your reviews.”

Turning it off is narrower than it sounds. Google states: “If you stop saving media, your existing text-based history, transcripts, and generative AI media responses will continue to be saved to your Search Services History.” And: “If you turn this Save Media subsetting off, previously saved media isn’t deleted and may continue to be used to improve Google technologies unless you delete it from your account.”

The four year tail that survives deletion

Here is the sentence worth reading twice: “When saved media is used to train our AI models, it is disconnected from your Google Account and retained for up to 4 years.” Then the version with nothing left to interpret: “Saved media that has already been selected to train AI models is no longer connected to your account and is kept for up to 4 years, even if you delete the original activity.” The same figure appears on the Search Services History page itself: “Data used to train our AI models is disconnected from your Google Account and retained for up to 4 years.”

That is the whole argument in one line. Delete is not a privacy control any more. It is a cleanup control, and it operates on a copy that is no longer the one that matters.

The exact steps, in Google’s own order

1. Go to My Google Activity and sign in.
2. Select Search Services History.
3. Uncheck the Save Media subsetting.
4. To end the history itself, select Turn off, then choose Turn off and delete activity.

What that buys you, in Google’s words: new activity “won’t be saved to your Search Services History in your Google Account” and “used to train generative AI models, unless you provide feedback.” That last clause is load bearing. Feedback you submit can still be used.

Then handle the second clock. Gemini Apps Activity defaults to 18 months, and Google documents the alternatives: “You can change your auto-delete setting in Gemini Apps Activity from the default of 18 months to 3 months, 36 months, or indefinite.” Two catches sit on the same page. Chats that human reviewers looked at “are not deleted when you delete your activity. Instead, they are retained for up to three years.” And with Keep Activity off, Workspace documentation still has new chats “saved in user accounts for up to 72 hours.”

Bing and Copilot: Microsoft’s own documentation disagrees with itself

Bing first. Microsoft states: “After 18 months, we no longer use cookies and other identifiers that could be linked to a specific account or device to personalize your search experience. In the coming months, we will retain data from authenticated users for up to 5 years to help improve our products and services.” The same page warns that “some copies may be retained within Microsoft’s backup systems for a limited time,” and that searches made while signed out “will not be displayed on the privacy dashboard,” which means the dashboard is not a complete record of what exists.

Copilot is worse than unclear, it is contradictory, so here are both statements side by side. The older Copilot privacy FAQ says: “By default, we store conversation activity for 18 months,” and documents an opt out under your profile, then Privacy, then “Training on conversation activity.” That page now carries a notice saying it applies only to the version of the app before 18 August 2026. The newer activity history page states the reverse: “Prompts, responses, and your file contents when using the Microsoft Copilot app aren’t used to train foundation models.” Microsoft has not published a page reconciling the two. If Copilot is in your threat model, read the documentation for the app version you actually run rather than trusting either summary, including this one.

The rest of the field, retention by retention

• OpenAI: consumer plans have data sharing on by default. The opt out path is your profile, then Settings, then Data Controls, then Improve the model for everyone. API traffic is not used for training by default, abuse monitoring logs are retained for up to 30 days, and Zero Data Retention for frontier models was announced on 19 August 2026.
• Anthropic: the consumer policy in force from 8 July 2026 allows de-identified retention of “up to 5 years in our model training pipelines” where training use is permitted, against a 30 day window on standard API traffic.
• Gemini: 18 months by default, up to 3 years for chats a human reviewed, 72 hours in Workspace with Keep Activity off.
• xAI: 30 days under the policy effective 24 August 2026.

What to actually do

Work through this once, then set a reminder for twice a year, because every one of these documents changed at least once in 2026. Turn Save Media off. Turn Search Services History off and delete it. Change the Gemini auto delete to 3 months. Flip the training opt out on every assistant you use with a personal account. Stop submitting feedback on anything you would not want retained. And when a product tells you it deletes your data, find the sentence that says what happens to the copy that was already selected for training, because that is the sentence that decides whether deletion means anything.