Why No Accounts

Where your data actually lives

Every companion, conversation, memory, and setting is written to storage on your own device — the browser's local database on web, and the equivalent on desktop and mobile. Messages go directly from your device to whichever model provider you configured (your own OpenRouter key, or a local Ollama model) — never through an Ensoul server in between.

What does leave your device

"Local" doesn't mean nothing ever moves, and it's worth being precise about the exceptions:

• Your messages go to the model provider you configured. When you send something, it's transmitted to OpenRouter — or to your own machine, if you're using a local model. That's how a reply gets generated at all. What that provider does with it is governed by their terms, not ours.
• Support emails are stored. If you write to support@ensoul.so, that message is kept in a mail system — the one piece of data that isn't on your device. The Privacy Policy says how long.
• Generated images are fetched from the provider. Images are served from the provider's temporary storage, which is why their links eventually expire.

There is no bundled key and no usage tracking tied to you, so nothing about your conversations is reported back here. What leaves is what you send to the provider you chose, and what you write to support.

The honest trade-off

No accounts means no automatic sync between devices — each one only knows what happened on it. If you lose a device without a backup, there's no password reset to recover your history, because there was never a server copy to recover from.

You are the backup. Use Full backup if your conversations matter to you, and export individual companions to carry a specific one to another device.

Why we chose this

Companion conversations get personal. An account system means somewhere holds a permanent record tied to a real identity, on a server that can be breached or subpoenaed. Removing the account removes the target — there's no central list of who talked to what, for anyone, including us, to hand over.

Your API key is stored locally on your device — in your operating system's own secure storage where that's available — not in a shared pool tied to an account.