V

Are you 18 or older?

Velvary contains adult content. You must be 18+ to enter.

Leave
Guides

AI chat privacy: who can actually see your messages

Max Korolev · · 11 min read

AI application developer working with language models since 2022. Built several chatbots with memory and personality.

“Only your companion sees your messages” is the promise almost every AI companion service makes, and technically it is true in exactly one sense: other users cannot see your conversation. Beyond that, no. The text you send passes through the service's server, lands in a database, goes to a third-party model provider, and stays in technical logs. That is not malice; it is how any cloud-based generation works. To reply, the model has to read the message.

The difference between services is not whether they read your conversation — in one form or another, they all do — but what they store, whom they pass it to, how long they keep it, and whether you can delete it. I build one of these services, so I know where this topic usually gets vague. Below: the three levels of privacy people keep confusing, six questions worth asking before you pay, and a straight answer about our side, limits included.

“Private from others” is not “private from the company”

Marketing glues these two into one phrase, though they are different promises with different costs.

  • Private from other users. Your conversation is not public, not shown in a feed, not indexed by search. That is the baseline for a closed account, and every decent service meets it.
  • Private from the operator. The company running the service technically has access to the message database. Not because it is curious, but because it has to answer support requests, delete data, and comply with the law. “We never read your messages” can only mean that employees have no routine access — not that access is impossible in principle.
  • Private from third parties. The model that writes the reply does not run on your device: the text goes to an inference provider. That provider sees the message at generation time — otherwise there is no reply. This is the most important level, and the one service descriptions usually skip.

A note on “anonymous”. A demo without registration does exist and is useful, but calling it anonymous is wrong: the server still sees your IP address, browser type, and request time. Anonymity on the web is not the absence of an account; it is the inability to link actions to a person, and most services do not provide that.

What happens to a message after you hit send

To keep this concrete, here is the path of an ordinary message in a service with memory — roughly the same everywhere:

  1. The server receives the text and saves it in the database together with the conversation history. Without that there is no chat on your next visit and no memory.
  2. The scaffolding assembles context. It pulls in the latest turns, a rolling summary, and the facts about you that look relevant to the current topic. This is covered in detail in the piece on character memory.
  3. The request goes to the model provider. It contains your message, fragments of the earlier conversation, and the character's system instruction. The provider returns the reply; with most commercial APIs, requests are retained for some period for debugging and abuse prevention.
  4. The reply is saved and shown to you. Meanwhile, technical logs record metadata: who, when, from which address, how many tokens. Those logs usually do not contain the conversation itself, but they do contain the user-time-action link.

Two conclusions follow, and both are better accepted before payment than after. First, there is no end-to-end encryption in these services, and there cannot be: the model must read the text to answer, so decryption happens on the service side. Second, privacy here is not “nobody sees it” but “a limited circle sees it, under clear rules and time limits”. The only question is how narrow that circle is and whether the rules are followed.

What a service actually stores: a five-point checklist

When you read a privacy policy, look for these five categories. If one is missing, it does not mean the data is not collected; it means nobody wrote it down, which is a bad sign on its own.

  • Account. Email and password (only a hash in a decent service), or Telegram ID, username, and name if you sign in through the bot.
  • Conversation content. The messages themselves. With memory features, also the derivatives: a short conversation summary and individual facts about you.
  • Technical data. IP, browser, device, request times, session cookie. It is needed to run the service and stop abuse — and it is the most underrated part of your footprint.
  • Payment data. The good answer is “we never receive card details; payment goes through a provider”. The bad answer is silence.
  • Age and consent. An 18+ service should at least declare an age requirement and describe how to delete an account. Missing both is a reason not to pay.

Two cases that show the cost of getting this wrong

Privacy in this niche is not abstract. Two public cases show what happens when both the service and the user underestimate it.

Muah.AI, autumn 2024. A breach exposed 1,910,261 accounts: email addresses, image- and chat-generation prompts, and the sexual preferences written into them. The breach is dated September 17, 2024; it became public on October 8. Passwords were not exposed — and that did not help, because the prompts were tied to emails with real names, and extortion attempts using the data were later reported. The lesson is simple: the most sensitive text in these services is not your password, but what you choose to write.

Replika and the Italian regulator. On April 10, 2025, the Garante fined developer Luka Inc. €5 million (announced in May). The complaints were not about model quality but about data processing: no valid legal basis, an inadequate privacy policy, and ineffective age verification. In other words, the regulator punished exactly the three things a user cannot verify and has to take on trust.

Both cases share one thing: the risk comes not from storing conversations as such, but from the gap between what a service promises and how it actually works. That is why verifiable facts — jurisdiction, retention periods, deletion — beat promises.

Six questions to ask before you pay

This is not legal advice; it is a practical filter. The first three answers are usually in the privacy policy. If they are not, ask support and see whether you get a substantive reply.

  1. Who processes messages besides the service itself? The model provider, hosting, payment infrastructure. A good answer names the processor categories and the jurisdiction instead of hiding behind “we share with no one”.
  2. Is the whole conversation stored, and for how long? “While your account is active” is a normal answer. “Forever” with no explanation is a red flag.
  3. What is stored beyond messages? Summaries, memory facts, embeddings, logs. These are derived data, and they are personal data too.
  4. How do I delete my account, and how long does it take? Look for specifics: a button or an email, a stated period such as “within 30 days”, and a note about accounting records. “Contact us” with no deadline is weak.
  5. Is there age verification? For an 18+ service this is not a formality: its absence is what earned Replika a fine.
  6. Which jurisdiction and laws apply? GDPR gives you rights to erasure and access; other regimes may offer less. It is not a quality guarantee, but it is a clear starting point.

How it works on our side

Now specifics about Velvary, checked against our privacy policy. The full text is on the dedicated page.

  • The operator is a Maltese company; processing follows GDPR and the Maltese Data Protection Act. That means you have rights to access, rectification, erasure, and portability, and you can complain to the Maltese supervisory authority, the IDPC.
  • Account: email and a password stored as an irreversible bcrypt hash, or Telegram ID, username, and name when you sign in through the bot. We do not store passwords in plain text.
  • Content: messages, a short conversation summary, and memory facts. The last two are derived from the conversation and are required for the character to remember it. Without them, memory does not work.
  • Third parties: the AI inference provider, hosting, the email delivery service, and Telegram payment infrastructure. Each has a data processing agreement; transfers outside the EEA use the EU standard contractual clauses.
  • Payment: through Telegram Stars. We never receive or store bank card details.
  • Technical data: IP, browser and device, request times, session cookie, and language preference. No third-party ad tracking.
  • Retention: account data and conversations are kept while the account is active. After deletion, conversations and files are erased or anonymised within 30 days, except records we are legally required to keep — primarily accounting records.
  • Security: TLS for traffic, password hashing, and restricted employee access to data.

And the honest limits, without which this section would be an ad. There is no end-to-end encryption — the service's design does not allow it. The inference provider sees the request text at generation time; that is a condition of any cloud model. Support staff can access account data when handling a request — otherwise a complaint about a charge or a missing photo could not be checked. You are not anonymous to the operator: we have your email or Telegram ID. If it is critical that nobody, including the company, ever sees your conversation, a cloud AI companion is fundamentally the wrong tool.

What we can promise without caveats: we do not sell personal data, do not use conversations for advertising, and do not show them to other users. That is not “total privacy”, but they are verifiable commitments backed by a specific company in a specific jurisdiction.

What you can do on your side

You cannot erase every trace, but you can meaningfully narrow the risk — much as with any other service you trust with something personal.

  • Do not share what you would not want to see in a breach. Passport details, home address, employer, real people's names — none of that is needed for a good conversation, and all of it stays in the database.
  • Use a separate email for services like this. It is not anonymity, but a breach will no longer tie the conversation to your main inbox and real name.
  • Do not reuse a password. Hashing protects the database, but not you if the same password already leaked elsewhere.
  • Delete old data. If a conversation no longer matters, delete the account rather than leaving it “just in case”: data that does not exist cannot be lost.
  • Read the policy before paying, not after. Three points are enough: retention, deletion process, jurisdiction. That is two minutes that usually save more than comparing prices.

The short version

“Can anyone see my AI conversation?” has an honest answer: yes — the service and the model provider, to the extent needed to run it; other users — no. Everything else is in the details: what is stored, for how long, whom it is shared with, and whether it can be erased. A service that answers those questions with concrete periods and names its limits deserves more trust than one promising absolute secrecy.

If you want to see how the memory that makes conversation storage necessary actually works, there is a separate breakdown. If you are choosing between services on price rather than privacy, see the guide to plans and media. And if you are curious how the site differs from the bot, read the Telegram piece. You can try it without registration in the character catalog: the first messages need no account, and it is a good way to see how a service talks before trusting it with anything personal.

Frequently asked questions

Can anyone see my conversation with an AI companion? +

Other users cannot: the conversation is private and not published. But the service stores messages on its side, and the model provider sees the text at generation time. That is not malice; it is how cloud generation works — to answer, the model has to read the message.

Is the conversation stored forever? +

Ours is kept while the account is active. After account deletion, conversations and files are erased or anonymised within 30 days, except records the company must keep by law, such as accounting records. With other services, check the periods separately: “forever” with no explanation is a bad answer.

Can I use the service completely anonymously? +

There is a demo without registration, but calling it anonymous is wrong: the server sees your IP address, browser, and request time. After registration there is a link to an email or Telegram ID. Anonymity on the web means actions cannot be tied to a person, and an ordinary AI service does not provide that.

What exactly leaked in the Muah.AI breach? +

Public reporting says 1,910,261 accounts: email addresses, image- and chat-generation prompts, and the sexual preferences written into them. The breach is dated September 17, 2024; it became public on October 8. Passwords were not exposed, but prompts were tied to emails with real names, and extortion attempts using the data were later reported.

Why was Replika fined? +

Italy's Garante fined developer Luka Inc. €5 million; the decision was issued on April 10, 2025, and announced in May. The complaints were about data processing: no valid legal basis, an inadequate privacy policy, and ineffective age verification. Model quality was not part of the fine.

Is the conversation encrypted? +

Traffic between you and the server is encrypted with TLS, and database access is restricted. There is no end-to-end encryption, and there cannot be: the model must read the text to generate a reply, so decryption happens on the service side. An “end-to-end encryption” claim in this kind of product is marketing, not technical reality.

Read next

All guides

Try it instead of reading about it

Pick a companion and send the first message — free, no sign-up needed.

Choose a companion → See pricing → Create companion Contact support

Continue in Telegram

Chat right inside Telegram with @Velvarybot

Email

Enter your email and we'll send you a reset link.

💎

Need 💎 · you have 💎

Get a subscription

We use cookies to keep you logged in and improve the site.

V