Effective 15 August 2026. Last updated 15 August 2026.
This policy explains how Unit Network Limited ("we", "us") handles personal data in Mnemos. Mnemos is deliberately built so that the person using it holds their own data, and that shapes everything below.
Mnemos is self-hosted software. Who controls your data depends on who runs the server, so read whichever case applies to you.
If you install and operate Mnemos yourself, your data stays on infrastructure you control. We do not receive it, cannot access it, and hold no copy of it. You are the controller of that data, and the third parties described in section 4 are ones you configure and contract with directly. In that case this policy describes how the software behaves rather than anything we do with your information.
During the current private beta we operate an instance for a small number of invited users. When you use that instance, we act as the controller of the data described below, and the rest of this policy applies to us directly.
Mnemos exists to remember things on your behalf, so it stores materially more than a typical app. Everything below is stored on the server running your installation.
| Category | What it includes |
|---|---|
| Account | Your user record, passkey credentials (public keys and identifiers — never a password), sessions, invitations, and your role. |
| Content you add | Documents, notes, files, images, and other material you ingest, together with the search index and text chunks derived from it. |
| Conversations | Your questions, the answers produced, the citations behind them, and attachments you send. |
| Memory and records | Facts, events, corrections, and structured records extracted from your material so it can be recalled later. |
| Health data | If you enable it, Apple Health measurements: active and dietary energy, dietary protein, body weight, body fat, and sleep. See section 3. |
| Financial data | If you link an institution through Plaid: the institution, accounts, and transaction records you import, plus a sealed access token. |
| Settings and automations | Your preferences, model and spending limits, dashboards, scheduled automations, and their run history. |
| Devices | Push notification tokens for devices where you enabled notifications, and delivery attempts. |
| Diagnostics | Metadata about model calls and failures — durations, token counts, error categories, and cost. These records exclude prompt and response text, tool arguments and outputs, and conversation content. |
We do not use any of this for advertising, and we do not sell personal data or share it with data brokers.
Health data receives specific protections, and we hold ourselves to them explicitly:
Mnemos is not a medical device and does not provide medical advice. Health and financial entries are treated as material you reported, not as clinical or professional records.
Mnemos performs remote inference. Answering a question requires sending relevant parts of your material to a language model provider, and there is no way to use the generative features without that.
| Service | What it receives, and why |
|---|---|
| Language model provider | By default OpenRouter, which routes to the model chosen for the request. It receives your question and the excerpts of your material needed to answer it. An operator may configure a different provider, including one they run themselves. |
| Plaid | Only if you link a financial institution. Plaid handles the connection to your bank and returns account and transaction data. Your banking credentials are entered with Plaid and are never seen or stored by Mnemos. |
| Expo and Apple | Only if you enable notifications. The notification text and a device token pass through Expo's push service and Apple Push Notification service to reach your device. |
| Microsoft Azure | Hosting for the beta instance we operate, located in the United States. Azure stores the data at rest on our behalf but does not use it. |
| Mailgun | Email sent to and from our contact address. |
Each provider handles data under its own terms. Because the language model provider and the models behind it are the most consequential of these, review the provider's policy before adding sensitive material to Mnemos.
We are based in Hong Kong, the beta instance is hosted in the United States, and language model providers may process requests in other countries. Using Mnemos involves transferring your data across borders.
Mnemos is a memory system, so content is kept until you delete it or ask us to delete your account. Backups of the beta instance are retained for up to 90 days, after which deleted material also disappears from them. Diagnostic metadata is retained while the account exists.
You can view, correct, and delete individual documents, conversations, records, and dashboards from within Mnemos, and you can export your data.
Mnemos does not yet offer self-service account deletion. Until it does, email contact@unitnetwork.io from the address associated with your account and we will delete your account, vault, and records within 30 days, and confirm when it is done.
Under Hong Kong's Personal Data (Privacy) Ordinance you may request access to and correction of your personal data. If you are in the European Economic Area or the United Kingdom, you may also request erasure, restriction, portability, or object to processing, and you may complain to your local supervisory authority. We do not charge for these requests.
Access is passkey-only: there are no passwords to steal or reuse. Traffic is encrypted with TLS. Each user's data is isolated at the database level, so users sharing an installation cannot reach each other's material, and administrators can manage invitations and quotas without gaining access to other users' private data.
Two limitations we would rather state than obscure. Mnemos does not apply application-level encryption to its database or vault, so protection at rest depends on the server's own disk encryption and access controls. And because sign-in is passkey-only, losing every registered authenticator means losing access to the account — there is no recovery path today, by design of the authentication model rather than by oversight.
Mnemos is not directed to children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided data to an instance we operate, contact us and we will delete it.
If we change this policy we will update the date above, and for material changes we will notify users of instances we operate by email.
Unit Network Limited
contact@unitnetwork.io