Isolation
Accounts, projects and workspaces are isolated. Inside an organization, visibility rules are enforced in SQL.
On this page you will learn:
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.
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.Authorization header, never in the request URL.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:
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.
After a password change or reset:
Memory Guard checks every record before it is stored:
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.
| Log | Contains | Does not contain |
|---|---|---|
| MCP operations | Time, tool, call outcome | Record text |
Integration calls (gateway_call) | Time, tool, outcome, latency | Arguments and integration responses |
| Organization audit log | Offboarding, reads of handed-over knowledge, visibility and term changes | Record text |
| Key security journal | Key issue, reveal, rotation and revocation: time, who, organization and role, IP, browser, where; a copy in your memory | The keys themselves |
| Account actions | IP address, browser, time and type of request, email at sign-up and sign-in; kept 3 years | Passwords, keys, memory content |
| Web server logs | Requests to the site; kept 1 year | Passwords, 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.