Skip to content
MMW Docs

On this page you will learn:

  1. how MMW keeps your memory apart from everyone else’s;
  2. how keys are stored and what protects records from secrets;
  3. what goes into logs and backups.

Isolation

Accounts, projects and workspaces are isolated. Inside an organization, visibility rules are enforced in SQL.

Hash-based key checks

A key is shown once; the server stores a PBKDF2 hash and an index.

Memory Guard

Secrets are removed before storage; dangerous records are rejected.

Logs without content

The MCP log and the organization audit log never contain record text.

Every request to MMW runs on behalf of a key, and a key belongs to one space — personal or an organization — and, if bound, one project. The server searches and writes only within that space and project.

Inside an organization, visibility rules apply as well: the access condition is built into the SQL query itself on every read path — search, validation, deletion, graph relations, the account (including AI-processing reads). A record you are not allowed to see appears neither in results nor in counts.

The server is stateless: every request is checked on its own, from scratch.

  • An mmw_… key is shown once. For checking it the server keeps only a PBKDF2 hash and a lookup index; the key cannot be recovered from the hash. The key itself is held only until its first display in the account, for at most 7 days, and the regular backup excludes the temporary reveal secret; the separate full release snapshot preserves all data under encryption. A key created by “Rotate” is not stored at all: it is shown in the response.
  • Revoking a key takes effect immediately.
  • The key travels in the Authorization header, never in the request URL.
  • claude.ai and ChatGPT connect over OAuth and get their own 30-day token — your key is not shared with them. A token obtained with an API key ends together with that key; a token obtained with the password ends when the password changes. See API keys and OAuth.
  • After 10 wrong passwords in a row on the claude.ai and ChatGPT consent page, sign-in for that email is closed for 15 minutes.
  • In an organization, the admin sees and revokes members’ keys but can never reveal or reissue them.

Every time an API key is issued, revealed, rotated or revoked, the event is recorded and a copy goes straight into your own MMW memory. Search for “MMW security” in your account or ask your agent.

Each entry has:

  • when it happened, to the second (UTC);
  • who: the email, plus the organization name and the member’s role inside an organization; when an MMW operator issued or revoked the key, the entry says so;
  • the IP address and the proxy chain;
  • the browser or device;
  • where: personal account, organization account, MMW admin console, or an OAuth connection (claude.ai, ChatGPT);
  • the key’s name and the first 8 characters of its id.

The key itself is never in the journal.

If the event cannot be recorded, the key is not shown, and a freshly issued key is revoked at once. If the copy cannot reach your memory (for example, the record quota is full), the server keeps the entry and retries until it gets through.

If the journal shows an action you did not take, rotate the key, change your password and contact support.

  • Change the password. In the account, open “Clients & key”, the “Change password” block. Enter the current password and a new one of at least 8 characters.
  • Forgot the password. On the login page click “Forgot password?” and enter your email. You get an email with a link. The link is valid for 1 hour and works once. The page answers the same way whether or not such an account exists.

After a password change or reset:

  • your other sign-ins to the account end (a reset ends all of them, a change keeps only the one you changed it from);
  • claude.ai and ChatGPT connections you approved with the password are disconnected: connect them again;
  • API keys and the connections approved with a key keep working. If a key may have leaked, rotate it separately.

Memory Guard checks every record before it is stored:

  • API keys, tokens and passwords are removed from the record;
  • a record that looks like an attempt to plant instructions in the agent’s memory (“memory poisoning”) is rejected with Memory rejected by Security Guard: ….

Session history, if you turned it on, is cleaned of secrets twice: on your computer before upload and again on the server. Model reasoning, system prompts, file snapshots and paths are not sent.

All MMW addresses — the account and the memory server https://mcp.mmwhub.tech/mcp — use HTTPS.

The MMW AI Archivist automatically processes eligible new records through an external model provider. Get AI Assistance sends eligible record texts when you request help. Access restrictions and privacy withdrawals apply; experimental model query expansion and outbound gateway execution remain disabled. Your connected assistant receives the authorized records you request and processes them under its own terms. MMW cannot recall data already received by a client.

LogContainsDoes not contain
MCP operationsTime, tool, call outcomeRecord text
Integration calls (gateway_call)Time, tool, outcome, latencyArguments and integration responses
Organization audit logOffboarding, reads of handed-over knowledge, visibility and term changesRecord text
Key security journalKey issue, reveal, rotation and revocation: time, who, organization and role, IP, browser, where; a copy in your memoryThe keys themselves
Account actionsIP address, browser, time and type of request, email at sign-up and sign-in; kept 3 yearsPasswords, keys, memory content
Web server logsRequests to the site; kept 1 yearPasswords, keys, memory content

The regular backup includes system data on all plans. Its script includes memory and session content only for paid customers and organizations; Free content is excluded. The Core release does not change this policy.

The current job configuration retains one copy. Do not rely on the former seven-day or off-server-copy promise. Confirm restoration terms with support; no new SLA, RPO or RTO is promised without an agreement.

A separate full encrypted release snapshot was created on November 7, 2026, covering all customers including Free, and restored in isolation. This is a one-time release snapshot, not a new recurring backup policy. An additional disk on the same VM is not an independent off-host copy. Keep your own export of important notes using the available account tools.

The full release snapshot is retained for 30 calendar days from creation, until December 7, 2026, 12:08:02.420159569 UTC. Removal requires a new full backup, a verified restore and a separately defined retention period for the replacement. Without a verified replacement, removal of the sole full copy is blocked and escalated to the service owner; the reason and decision are logged without resetting the original deadline. This is an exceptional hold, not a new retention period. For erasure requests affecting existing archives, contact support@mmwhub.tech from your account email address, without passwords or keys. Support records the request and explains the applicable retention and outcome; selective erasure from encrypted archives is not promised. Requests must be considered before preparing a replacement and restoring data. See the Privacy Policy.

  • Keep your key in a password manager, not in chats, tickets, Git or screenshots.
  • In an organization, issue a separate key per device (for example “work laptop”) so a leaked key can be revoked without stopping the others.
  • Bind keys to projects so an agent sees only the memory it needs.
  • In an organization, give every person their own key: a shared key breaks record authorship and knowledge handover.