AI Risk Wire

Cases › leaked private data › LR-2026-0322

ChatGPT conversation logs exposed in Google Search Console

Preliminary Why: 1 report: Ars Technica · subject to change · 1 independent report

Status: no action reported

Severity moderate
Reported 7 Nov 2025

No source states: loss or records, developer and model, agent tool, could do, deployer, industry.

Severity moderate: test: data of others touched with a bounded scope stated (OpenAI says a small number of search queries were affected).

ChatGPT is OpenAI's chatbot, and in this incident user conversations appeared in Google Search Console, a tool site managers use to monitor search traffic. Some leaked entries exceeded 300 characters and read like private chats about relationship or business problems. Analytics consultant Jason Packer flagged the issue in a blog post, and he and Slobodan Manić ran tests they said suggested OpenAI scrapes Google Search with user prompts. OpenAI declined to confirm that theory but said it was aware of the issue and had resolved a glitch that temporarily affected how a small number of search queries were routed. Packer welcomed the quick fix but said OpenAI's response did not confirm whether it was scraping Google, leaving doubt that the issue was fully resolved.

What happened

No source tells the story step by step yet.

What was done

No source states an action or fix.

Risks

Read from the sources; not yet reviewed by a person.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Network egress control

Application

Sensitive-data checks on outbound data · Output filtering and redaction · Human approval for high-impact actions · Data minimisation · Least-privilege access for the agent · Activity logs

Evidence

No source states: a step-by-step account, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.

Show every field, with its source and grade

What happened

Earliest source we hold
2025-11-07
D inferred by us from the described behaviour, reason shown
Who caught it
an independent researcher or journalist
C one secondary source states it
What went wrong
leaked private data
C one secondary source states it
primary risk
RK04
D inferred by us from the described behaviour, reason shown
secondary risks
RK15
D inferred by us from the described behaviour, reason shown

Impact

Severity
moderate
D inferred by us from the described behaviour, reason shown
Kind of harm
privacy
C one secondary source states it
Why this severity
test: data of others touched with a bounded scope stated (OpenAI says a small number of search queries were affected).
D inferred by us from the described behaviour, reason shown

Notes on gaps

The OpenAI fix is not tied to any listed control, so remediations are empty. Scraping of Google by OpenAI was a theory from Packer and Manić and was not confirmed. Record counts and loss amounts are not stated.

LR-2026-0322 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON