Field notes / 04 · Privacy in practice
Anonymous AI Chat: Separate Identity From Visibility
“No sign-up” describes an entry step. “Anonymous” is a claim about whether activity can be connected to you. Check the identity links and the people who can see your device separately.
Which link are you trying to reduce?
| Choice | Useful question | Limit |
|---|---|---|
| A nickname | Does the conversation need my real name? | A nickname does not change an account’s email, payment or device records. |
| No-sign-up access | Which identifiers are collected before registration? | The absence of a registration form is not evidence of absent logs. |
| Private browsing | What will remain on this shared device? | It does not make activity invisible to the visited service. |
| Separate account details | What can still connect this profile to other services? | Recovery, billing and sign-in providers require their own review. |
Private browsing is a local boundary
Chrome’s Incognito documentation explains that websites and organizations managing your network may still observe activity. Close all Incognito windows to end the session. Treat that as a browser behavior, not a statement about a companion service’s retention.
On a shared device, inspect notification previews, signed-in tabs, downloads and saved screenshots. Use a harmless message to see what a lock screen reveals. For a work or school device, consider that the organization manages the environment; changing a browser mode does not turn it into a personally controlled device.
Look beyond the name field
As a concrete example, Nomi’s privacy policy lists IP address and visit information among data learned even without creating an account. This illustrates why registration status alone cannot establish anonymity. It is not a claim that every provider collects the same fields.
Before subscribing, inspect what the payment flow asks for, which company processes it and where receipts go. If an age-checking service is involved, review that recipient’s documentation too. Do not assume an email alias changes information already given to a payment or verification provider, and do not falsify age or bypass an eligibility check.
Keep a recovery route you control
Less visible identity can come with a practical trade-off: losing access to an email or sign-in account can make recovery harder. Use account details you can maintain and protect. Keep recovery information private rather than pasting it into the companion conversation.
Reduce unnecessary identifying detail in the content itself. A combination of workplace, location and a distinctive event may be more revealing than a name. When asking a general question, use a fictional example instead of a real person’s identifying history. This reduces what you disclose; it does not certify anonymity.
Complete the downloadable identity checklist and mark unanswered fields explicitly. If the issue is who inside the service can access content, continue with the five-route access map.
Make it practical
Keep your own record
Download the blank worksheet and fill it in privately. No account or upload is needed; nothing you write in the downloaded file is sent to this site.
Download worksheet · TXTScope: editorial guidance and official documentation checked on September 18, 2026. No in-app deletion tests or infrastructure audit were performed. Illustrative scenarios are fictional. Evidence method · Website privacy