Privacy

Meww answers a question by searching your connected systems at the moment you ask, and it does not keep a copy of what it finds. This page says what it does keep, and who else sees your question.

What we hold

• If you ask for access: the email address, company name and note you typed into the form, the time you sent it, and for a self-host request where you plan to run it. It is saved on our server and emailed to us so we can reply. It is not used for anything else.
• If you have an account: your email address and your password. The password is stored only as an argon2id hash, never as text. A sign-in session is a random token; we keep only its SHA-256 hash, so a copy of our database contains no usable session.
• Your connections: the credential each system gave Meww when you connected it, such as an access token or an API token. They are encrypted before they are stored, they belong to your account alone, and they are never sent to the model or written to logs.

Your systems’ data

Meww has no index, no crawl and no stored copy of the content in your connected systems. When you ask a question it searches those systems then, with your own account, so it can read only what that account can already open.

Your questions and answers live in the server’s memory for the length of the conversation. They are not written to the database. A conversation ends after a quiet spell (two hours by default) or when the server restarts, and you can delete it sooner. Our logs record that a question was asked and how many sources it used, not what it said.

The model that writes the answer

To write an answer, Meww sends your question and what it retrieved for it, such as the text of messages, tickets, deal records and email threads, to a language model. By default that is a model served by Amazon Bedrock; whoever runs the service can choose another provider. That provider processes the request to answer it. Meww never sends the model a credential.

In your browser

• One cookie keeps you signed in. It is marked HttpOnly, so scripts on the page cannot read it, and it ends when your session does. While you connect a system through its own sign-in page, a second short-lived cookie guards the redirect back to Meww.
• The home page remembers in your browser tab, not on our server, that its opening animation has played.
• There are no analytics, advertising or tracking scripts. The logos of connected systems are loaded from cdn.simpleicons.org, which sees your IP address when they are.

Your choices

• Disconnect a system in Connections and Meww deletes its copy of that credential. It does not revoke the access at the system itself; to end it there, remove Meww in that system’s own settings.
• Delete a conversation to remove it from memory straight away.
• To close your account or have what we hold about you removed, ask us through the request-access form and say that is what you are asking. Deleting an account deletes its sessions and connections with it.

If you run Meww on your own servers, none of this goes to us: see self-hosting.