What the company behind an AI can actually see
Every message reaches the provider in readable form, because a model has to read it to answer. Around that message travels metadata: address, browser, timing, and an account identifier if one exists. Which parts are kept, and for how long, is a decision each provider makes, and the account is the part you control.
It helps to separate what a provider necessarily receives from what a provider chooses to keep. The first list is fixed by how the technology works. The second list is a policy, and it differs sharply between services.
On this page
The message itself, always
A hosted model reads your text to answer it, so the text arrives readable at the provider. Encryption in transit protects the message from everyone in between and not from the destination. Any service promising that it cannot read your messages is either running the model on your own device or using words loosely.
The metadata around it
A request carries your network address, a browser signature, and a timestamp. Together these approximate location, device, and rhythm of use. This information arrives whether or not you have an account, because that is how the connection works. It stays thin only while nothing joins the separate requests together.
The identifier, if there is one
An account, a session cookie, or a browser fingerprint turns separate requests into a series. This is the piece that changes the picture: without it, a provider holds a heap of disconnected events; with it, a provider holds a history. It is also the piece most often under your control, because no account can be issued if none is required.
What a provider chooses
Whether the conversation is written to storage, whether it trains a future model, how long access logs live, and who else receives the data. None of these follow from the technology; each is a decision. Reading them takes longer than reading a headline on the front page and it is the only part that tells you what a service is.
Questions about private AI
Can a provider read my messages if the site uses HTTPS?
Yes. HTTPS protects the message from networks along the way. It ends at the provider, which has to read the text to produce a reply.
Is a provider allowed to hand over a conversation?
If it holds one, a lawful request can reach it. A provider that never stored the text has nothing to hand over, which is a stronger position than a policy of refusal.
Does an on-device model avoid all of this?
It avoids the provider entirely, because nothing leaves your machine. The trade is a smaller model and the hardware to run it.
Ask something here, knowing exactly which of these applies.
Open private chat