What Eve stores
Last updated: 25 September 2026.
The short version
Eve remembers things for you so your assistant does not start from nothing every time. To do that we store what you tell it, on our servers, in a database that is yours alone. You can see every memory, change it, delete it, or take it with you.
What we keep
Memories. Facts, people, projects, events, beliefs, questions. Each one shows you its text, its date, and where it came from. Nothing is hidden from you that we can see ourselves.
Your conversations with Eve on this website. If you chat with Eve here, we keep that conversation. Conversations you have inside Claude or ChatGPT stay there. We only ever see the specific requests your assistant makes to Eve.
Your email and name, from Google sign-in. That is all we ask Google for when you log in.
Your settings and your usage totals, so we can show you your plan and stop you going over your spend cap.
Files you hand us. If you import a chat history, we hold the file while the import runs and delete it when it finishes, or after seven days if you never finish.
Where it lives
On our servers, in San Jose, California, run by Fly.io.
Your memories live in their own database directory, not as rows in a shared table with a filter on them. Another person's question cannot reach your data even in principle.
The disk is encrypted under a key we hold. If that encrypted disk does not mount and check out, Eve refuses to start, rather than quietly writing your memories in plaintext.
Who can read a memory
You. Always.
Your assistant, when you connect it. The connector can only ever reach the memories of the account that authorised it.
People you invite to a shared space, and only in that space. Your personal memories stay personal. Everyone can see who added what.
Us, operationally. We run the servers, so we can reach the data. We are not going to pretend otherwise. Two things keep that honest. Every time anyone who is not you touches your memories, it goes in a log, and you can read that log yourself. An empty log is the normal answer.
Not our host, except structurally. Fly runs the machine, so Fly has the access any host has to its own hardware, and that includes the key that unlocks our encryption, because Eve has to restart on its own at 3am. Eve is not end to end encrypted and we will not describe it that way.
Who else sees your words
Two companies, briefly, while a memory is being made.
If you add files from Google Drive or upload files, Eve sends their text to the same model providers when it reads or indexes them.
Fireworks AI runs the model that turns what you said into a memory. Their terms say they do not train on it and do not keep it once they have answered. They do reserve the right to run safety checks over it, and to hold it if we ask them for support on a problem.
OpenAI turns memory text into the numbers that make it searchable. Their API does not train on data submitted through their API. It may keep that data for up to 30 days to check for abuse, then deletes it. We want to move this onto the same model provider so there is one company instead of two.
Stripe handles payment. We never see your card.
Nobody else. We do not sell your data. We do not share it for advertising. No third-party analytics or session-recording tools run here. The usage events described in the privacy policy stay on our own server. We do not train models on your data and never have.
Deleting
Delete a memory and Eve stops recalling it straight away. It sits in your trash so you can change your mind. That trash is yours. Eve does not read it.
Empty the trash and the content is gone. What remains is a note that something was forgotten, not the thing itself.
Ask Eve to forget a fact and it goes further. Eve removes it from every memory built on top of it, and from the three quiet places it could crawl back from: your trash, the undo copy a tidy-up pass leaves behind, and the queue of saves waiting to retry. If that takes something unrelated with it, we tell you what and why.
And restoring a backup does not bring it back. We keep a record of what was erased, stored outside the backup so a restore cannot delete the record along with the erasure, and we replay it. That record holds ids and a one-way hash, not the thing you asked us to forget.
Delete your whole account by emailing alexa@evecortex.com. There is no button for it yet, so we do it by hand, within 30 days. That means everything: your memories, your trash, your conversations with Eve, your settings, your usage records, your access log and your sign-in. You get a confirmation when it is done. Export first if you want a copy.
Taking it with you
Export everything as JSON and Markdown from the account menu, any time, free, including after your trial ends. That export is your memory graph. It does not yet include your chat transcript with Eve, your attachments, or your access log. Ask and we will send those.
What we do not have
No SOC 2. No ISO certification. We are a very small team and we have not been through an audit. What is above is the strongest posture we can honestly claim before one, and when the people relying on us need the audit, we will start it.
No BAA, so please do not put health records in Eve.
Google Drive and Calendar
Both optional, both separate from signing in.
Drive: Eve can see files it made and files you hand it through Google's file picker. That is all Google's drive.file permission allows, and we dropped the broader one on purpose.
Calendar: read your calendar and write events, if you connect it.
Disconnect either one whenever you like.
Questions
alexa@evecortex.com. You reach the founder, not a queue.