Published July 21, 2026 · Facts last verified July 21, 2026
Logging out feels like putting on a mask. No account, no email, no name — just a text box and a question. It is the most common privacy move people make with AI, and it is far weaker than it feels.
Identity on the web is not primarily a login. It is an accumulation of small signals, each harmless alone, that together single out one person. AI chat sites collect the same signals every other website does — and then add one nobody else has ever had at this quality: a long, unguarded sample of how you write and what you worry about. Here is what is actually being gathered when you are logged out, ranked roughly by how much it gives away.
1. The Network Layer: Your IP Address
Before a single line of JavaScript runs, your request arrives carrying an IP address. OpenAI's privacy policy is explicit that it automatically collects Log Data — "your Internet Protocol address, browser type and settings, the date and time of your request, and how you interact with" the service — and that this applies whether or not you are signed in. Every major provider collects the equivalent.
An IP address is not your name, but it is close enough to be useful: it pins you to a household, an office, or a coffee shop, and it is stable enough over hours or days to stitch separate visits together. A residential IP typically identifies a home; a corporate one identifies an employer. On its own it is a coarse signal — but it is the anchor the other signals attach to.
2. The Device Layer: Browser Fingerprinting
This is the one most people have heard of and few appreciate the scale of. Your browser volunteers a startling amount of configuration to any site that asks: user agent, operating system, screen resolution and colour depth, timezone, language list, installed fonts, the exact way your graphics stack renders a hidden canvas element, audio-processing quirks, hardware concurrency. None of these identify you. The combination frequently does.
How well? Honest research says: better than you would like, worse than the scare stories. The EFF's early Panopticlick study found about 83% of visitors had instantly recognisable fingerprints — but that sample was biased, because the people who visit a fingerprinting-demo site are unusual by definition. The rigorous follow-up, "Hiding in the Crowd" (2018), collected over two million fingerprints from an ordinary French news site and found 33.6% were unique. So roughly one visitor in three is individually identifiable from browser characteristics alone, and most of the rest sit in small groups — which, combined with an IP address, usually collapses to one person anyway.
Crucially, none of this requires a cookie, and clearing your cookies does not touch it. Fingerprinting is a measurement of your device, not a tag placed on it.
3. The Session Layer: Cookies, Storage, and Rate-Limit IDs
Logged-out does not mean stateless. Chat sites set cookies to remember preferences and monitor performance, and virtually all of them need some stable identifier to enforce free-tier limits — otherwise "10 free messages" would be meaningless. That identifier lives in a cookie or in browser storage and persists across visits until you clear it.
Then there are the third parties. As the November 2025 Mixpanel incident demonstrated, analytics vendors are wired into AI platforms like any other product, and the metadata they hold — account identifiers, approximate location, device and browser type — is real enough that its exposure warranted user notifications. Anything an analytics SDK sees, it can correlate.
4. The Content Layer: Your Writing Identifies You
Here is where AI chat departs from ordinary web tracking, and where the honest analysis gets uncomfortable.
Stylometry. Authorship attribution is a mature discipline: everyone develops unconscious linguistic habits — function-word frequencies, punctuation rhythms, sentence-construction preferences — that persist across topics and are hard to suppress deliberately. Academic work reports 85–95% attribution accuracy against a closed set of candidates given enough text, and Narayanan et al. demonstrated identification from a pool of 100,000 authors. The technique famously unmasked J.K. Rowling behind the pseudonym Robert Galbraith. A long chat session is a generous writing sample.
Direct inference by the model itself. This is the newer and sharper finding. In "Beyond Memorization: Violating Privacy via Inference with Large Language Models" (ETH Zurich, ICLR 2024), Staab and colleagues showed that today's LLMs can infer personal attributes — location, income, sex, age — straight from ordinary text, reaching up to 85% top-1 and 95% top-3 accuracy on real Reddit profiles. No tracking infrastructure is involved. The model simply reads what you wrote and deduces who you probably are, from the register you use, the idioms you reach for, and the incidental details you never thought of as identifying.
And you volunteer the rest. Every self-identifying detail typed into a "private" chat — your city, your employer, your diagnosis, your children's ages, the contract you are arguing about — is content no fingerprinting technique was needed to obtain. This is the layer no tool can protect you from, and the one users control completely.
5. The Correlation Layer: Where It Actually Gets Personal
Individually these signals are weak. Stacked, they converge fast — and the real risk is not identification in the abstract, it is linkage: the moment an anonymous session gets joined to a named one. If you browse logged out and later sign in from the same browser and IP, the two sessions share a device fingerprint and often a storage identifier. Nothing exotic is required to connect them; the join is trivial, and the anonymous history acquires a name retroactively.
This is why "I didn't log in" offers so much less protection than it seems. It removes the label at the top of the session, not the twenty other things that point back to you.
What Actually Helps
- Separate the network path. A VPN or Tor replaces the anchor signal. Useful, and not sufficient by itself — fingerprint and writing style survive it untouched.
- Reduce device uniqueness. The Tor Browser deliberately makes users look alike; Firefox and Brave ship fingerprinting resistance. Note the counter-intuitive trap: a heavily customised "privacy" setup with rare extensions and unusual fonts can make you more unique, not less. Blending in beats standing out.
- Never mix identities in one browser profile. If a browser has ever been signed in, treat it as named. Use a separate profile or container for anything you want kept apart.
- Redact before you send. Against stylometry and model inference there is no technical shield — only discipline about what goes into the box.
- Prefer a service that never receives the signals in the first place. Which is the structural version of all of the above.
How Secret Chat AI Fits — Including What We Do Collect
Secret Chat AI is built to break the correlation layer, and on a topic like this it would be hypocritical to describe only the good half. So here is both.
What the model providers receive. Your prompt reaches the LLM through our gateway, which means the provider sees the gateway's request — not your IP address, not your browser, not an account belonging to you. The signals in sections 1–3 above simply never arrive: there is no device fingerprint to compute, no cookie of yours to set, no login to correlate against. We build no profile of you, and no conversation is ever associated with you. Registration takes an email, but it is used only for account access and payment — never stored against your prompts. Retention may still apply at the provider, but your query arrives anonymized: you use the model as a stranger.
What we ourselves store — plainly. We are not a zero-data service, and claiming otherwise would fail this article's own test:
- An anonymous device token. Your browser holds a random token so free-tier limits can be enforced and so we can tell which marketing channel a visit came from. It is not a fingerprint — it is not derived from your hardware or browser characteristics, it is a random value you can clear at any time — but it is a stable identifier, and honesty requires calling it that. It is never sent to the model providers.
- Basic visit data against that token: the referring site, the landing page, UTM parameters, your browser's user-agent string, and a two-letter country code (never a stored IP address). This is ordinary marketing attribution, and it is separate from your conversations.
- Your chats stay on your device. Chat history, threads, and files live in your own browser's local storage (IndexedDB and OPFS). There is no chat archive on our servers to browse, breach, or subpoena. A prompt does pass through the gateway in order to be answered — that request record is deleted the moment your browser collects the reply, and an hourly sweep clears any that were orphaned by a closed tab, so nothing lingers.
What we cannot do. Secret Chat removes you from your queries — it does not remove the data from your messages. Your text reaches the provider verbatim, so sections 4's stylometry and model-inference risks are ours to warn about, not to solve: if you write in a distinctive voice about identifying circumstances, a sufficiently motivated analysis of that text is not something anonymized routing undoes. Redacting identifying details before sending remains your responsibility, as our Terms of Service and Disclaimers set out. What we do remove is everything in sections 1, 2, 3 and 5 — the machinery that turns a stranger's question into a named person's file.
Frequently Asked Questions
- Am I anonymous if I use a chatbot without logging in?
No. Your IP address, browser fingerprint, cookies or storage identifiers, and writing style are all still available, and if you ever sign in from the same browser the anonymous sessions can be linked to your account retroactively.
- How unique is my browser fingerprint?
The large-scale 2018 "Hiding in the Crowd" study found 33.6% of browsers were uniquely identifiable from fingerprint alone. Earlier figures above 80% came from self-selected privacy-enthusiast samples. Combined with an IP address, even a non-unique fingerprint usually narrows to one person.
- Can an AI identify me from my writing?
To a meaningful degree, yes. Stylometry reports 85–95% authorship accuracy against a closed candidate set, and ETH Zurich researchers showed LLMs inferring location, income, sex and age directly from ordinary text at up to 85% top-1 accuracy. No tracking is required — only the text itself.
- Does a VPN make me anonymous with AI chatbots?
It removes one signal, not all of them. Your device fingerprint, any storage identifiers, your account if you log in, and your writing style are unaffected by changing your IP address.
- Does Secret Chat AI fingerprint or track me?
We do not fingerprint your device and we build no profile of you. We do store a random anonymous device token (for free-tier limits and marketing attribution) plus the referrer, landing page, user-agent and country of a visit — never an IP address, never linked to your conversations, and never sent to the model providers. Your chats stay in your browser, and your queries reach the models with no identity attached.
Conclusion
Anonymity is not a checkbox you leave unticked; it is the absence of correlatable signals, and a logged-out browser emits plenty. IP addresses anchor you, fingerprints single you out, storage identifiers persist, analytics vendors correlate, and — uniquely with AI — the text itself can betray your location, age, and income to a model that was never asked to guess. The fix is not to hunt for a chatbot with a better privacy toggle. It is to stop emitting the signals: send your questions through something that never learns who is asking, keep your history on your own machine, and stay deliberate about what you type. The last part is still yours. Secret Chat AI handles the rest.
Related reading: how to use ChatGPT anonymously · the fine print on "temporary" chat modes · what happens when a provider is breached · the models available on Secret Chat
Sources
- OpenAI — Privacy policy (Technical Information and Log Data)
- Gómez-Boix et al. — Hiding in the Crowd: an Analysis of the Effectiveness of Browser Fingerprinting at Large Scale (WWW 2018)
- Staab et al. — Beyond Memorization: Violating Privacy via Inference with Large Language Models (ETH Zurich, ICLR 2024)
- EFF — Cover Your Tracks (browser fingerprinting test, successor to Panopticlick)
- OpenAI — What to know about the Mixpanel security incident