Your memories never reach us. Your account details do.
Those are two different systems and most of the confusion about this product lives in the gap between them. This page keeps them apart.
Your memories are not here Everything Enovari remembers for you lives
in SQLite files on your own disk — a shared store plus a separate
mind.db for every persona. We do not hold them, cannot read them,
and cannot recover them if you lose them. Nothing on this page is about that
data, because we never receive it.
What an account stores Your name, your email address, an organisation name if you give one, and a one-way hash of your password. Never the password itself. Also: whether your email is verified, whether the account is active, and when it was created.
Your API key We store a hash of it, the first few characters, and the time it was created. The four characters are what lets the account page show you which key you are looking at — the rest genuinely cannot be recovered, which is why a key is shown to you exactly once.
Signing in Two cookies, set only when you log in.
sh_session carries the session itself and is marked HttpOnly,
Secure and SameSite=Lax, so scripts on the page cannot read it.
sh_logged_in is readable by the page and only says yes or no, so
the site can show the right header. Both expire after 24 hours and logging out
clears them.
When you write to us The support form keeps your name, your email address, your message and the time you sent it, in a database only we can reach. It is not sent to any third party. The phone box is optional: what you type there reaches our server with the rest of the form and is not kept, so if you want a call back, put the number in the message itself. There is no company field.
Your IP address We use it to rate-limit sign-in and administrative requests, which is what stops someone guessing at your password all night. It is also recorded in an internal audit log when an administrator changes an account. It is not used to profile you and it is not shared. How long each of these lives is the next section.
Companies we rely on Two of them, both named in full below. We send email through Resend, so your address and the contents of a verification or password-reset message pass through them. Payment, if and when there is any, would run through Stripe. Nothing is for sale yet, so nothing has been sent to them. If that changes, card details would go to Stripe directly and never to us, and we would hold only the identifiers Stripe gives us back.
What we do not do No third-party analytics. No trackers. No advertising network, no data broker, at any point. We do not sell your personal information and we do not share it for advertising. Every font and asset on this site is served from this site, so loading a page here reports nothing to anyone else — and nothing here needs to answer a Do Not Track signal, because there is nothing for one to switch off.
How this is kept safe Your password is stored as a one-way hash and your API key as a hash, so neither can be read back — not by you and not by us. This site is served over HTTPS, and sign-in and administrative requests are rate-limited by IP address. We do not claim more than that here, because more than that is not ours to certify.
Removal Ask through our support form and we will delete your message, or your account, and confirm it. Deleting your account does not touch the memories on your disk — those are yours and they stay where they are.
Changes When this policy changes, the date at the top of this page changes with it, and what changed is written down. Corrections dated, never silent.