MnemoverseDocs

Appearance

Terms of Service ​

Last updated: October 13, 2026

Mnemoverse is operated by UINSIDE Inc., a Delaware corporation. Its registered office in Delaware is at 251 Little Falls Drive, Wilmington, DE 19808, USA, with Corporation Service Company as its registered agent.

In these Terms, "UINSIDE", "we", "us", and "our" refer to UINSIDE Inc.

These Terms of Service ("Terms") govern your use of the Mnemoverse service described in section 2 and of our website at https://mnemoverse.com.

Effective date: October 10, 2026

1. Acceptance of these Terms ​

  • By creating an account, or by accessing or using the service or the website, you accept these Terms. The sign-up page at console.mnemoverse.com says so: "By creating an account, you agree to our Terms of Service and Privacy Policy." If you disagree with any part of these Terms, do not use the service or the website.
  • If you use the service for a company or other organization, you accept these Terms for it and confirm you are authorized to do so.
  • The service is not directed at children, as section 8 of the Privacy Policy says.

2. The service ​

Mnemoverse is a hosted persistent-memory service for AI agents. You and the agents you connect can store memories, retrieve them in later sessions and from other tools, rate whether a recalled memory helped, export the memories in your account, and delete memories from your private account (section 7).

You reach the service through:

  • the Memory API, a REST API at https://core.mnemoverse.com/api/v1, authenticated with an API key (API reference);
  • the MCP server package @mnemoverse/mcp-memory-server, run locally with an API key (MCP server);
  • the hosted MCP connector at https://mcp.mnemoverse.com/mcp, authenticated by signing in through OAuth (Remote MCP connector);
  • the Python SDK, the mnemoverse package (Python SDK);
  • the console at console.mnemoverse.com, where you manage your account, API keys, plan and billing.

The service also includes:

  • Shared Rooms (Beta), memory spaces shared between accounts (section 8);
  • Sigma (closed beta), a reviewer for GitHub pull requests at sigma.mnemoverse.com, with the additional terms in section 19;
  • the Vault, which stores secrets under an alias. Stored values are sealed, and no listing returns them;
  • per-customer isolation for products that serve their own customers, using a separate memory domain for each customer (Platform).

Features marked Beta are still developing. Their behavior may change, and the page that documents each one says what works today.

When you connect through a third-party client, such as Claude, ChatGPT, Cursor or VS Code, that client's provider processes what passes through it under its own terms and privacy policy. Those terms govern your use of that client; these Terms govern the Mnemoverse service it connects to.

Some of the client software we publish is open source: the MCP server package is MIT licensed, and the Python SDK is open source. That software is governed by its own license; these Terms govern the hosted service it talks to.

3. Your account and API keys ​

  • Signing in. You sign in with the email and password of your Mnemoverse account, or with an identity provider where one is enabled on your account.
  • API keys. You create API keys in the console, or, on its default local connection, the Mnemoverse Agent Memory editor extension creates one for you when you sign in through it and keeps it in your operating system's keychain (VS Code). A key you create in the console starts with mk_live_ and is shown exactly once, when it is created. We store a hash of each key, never the plaintext key (API security). While the editor extension signs in, its new key is also held in encrypted form until the extension collects it, which it must do within 10 minutes. If you lose a key, revoke it and create a new one.
  • Keep keys secret. Do not share a key outside the people and systems you trust with your account. The memory rules in section 6 recommend keeping keys out of memory content. All API keys of an organization share that organization's limits.
  • Connectors. When you connect a client through OAuth, the consent screen lists the scopes the client requests. You can approve or deny them, and an approved token is limited to the scopes shown. How to disconnect a connector, and what then happens to the tokens issued to it, is in the Privacy Policy (section 11.3).
  • Your responsibility. You are responsible for activity under your account and API keys, including activity by the agents and clients you connect, until you revoke a key you know has been exposed.
  • Security reports. Report a vulnerability to security@mnemoverse.com.

4. Plans, limits and fees ​

The Pricing page is the authoritative statement of plans, limits and prices. The current plans are:

PlanPriceQueries per dayStored atomsRate limit
Free$01,00010,00060 req/min
Pro$29/mo50,000500,000600 req/min
Team$149/mo500,0005,000,0003,000 req/min
Enterprisecontact salesCustomCustomCustom
  • Free needs no credit card. Section 5 and the Free Tier & Startup Program Terms cover how it may be used.
  • Enterprise plans are priced by contact with sales, as the Pricing page says. Self-hosting is available on Enterprise plans by agreement, when security or compliance requirements call for it. By default we run the engine for you, and that is what we recommend.
  • Limits are enforced by the service. A request over a limit is refused with HTTP 429, as the API reference describes; the Pricing page says how usage is counted. Usage in a shared room is billed to the member who makes the call, never to the room's owner.
  • Payment. Paid plans are billed in advance for each billing period through our payment processor, Stripe, and continue until you cancel.
  • Plan changes, cancellation, refunds and failed payments follow the Refund & Cancellation Policy, including its 14-day money-back guarantee on a first paid subscription.

5. Free tier and Startup Program ​

The Free Tier & Startup Program Terms supplement these Terms for the Free tier and for plan grants under the Startup Program. They cover what the Free tier is for, the fair-use process for unusual usage, Startup Program grants, and the rule that memory content is used for research only if you opt in. Where they address a Free-tier or grant matter, they apply together with these Terms; section 16 covers which document prevails in a conflict.

6. Acceptable use ​

The memory rules we recommend for every agent tell it not to store passwords, API keys, payment data, MFA codes, government IDs, or health records (Make your agent use memory). The Vault is the part of the service built to hold secrets (section 2).

You agree not to:

  • use the service or the website in any way that causes, or may cause, damage to it or impairment of its availability or accessibility;
  • store another person's personal data that you have no lawful basis to share (the Privacy Policy, section 3);
  • store content you have no right to store, or use the service for unlawful content or activity;
  • upload malware;
  • try to reach another account's private data or a room you are not a member of;
  • probe the service's security other than through a report to security@mnemoverse.com;
  • reverse engineer the hosted service.

Use of the Free tier also follows the fair-use section of the Free Tier & Startup Program Terms (their section 2).

Section 10 says what we do when use breaks these rules.

7. Your content ​

  • It stays yours. You own the memories and other content you store ("your content"). We claim no ownership of it.
  • Our role. UINSIDE Inc. stores and processes your content on your behalf and on your instructions, as a data processor. If you use the service for your own customers, you decide what is stored about them and why. Business customers can request a data-processing agreement (DPA) at support@mnemoverse.com.
  • What we do with it. We store and process your content to provide the service to you, using the sub-processors listed in the Privacy Policy (section 11.6). We do not train on your content. Research use of memory content is opt-in only, as the Free Tier & Startup Program Terms state. The content-free aggregate statistics we compute and may publish are described in the Privacy Policy (section 11.9).
  • Writes can be declined. A write may come back as not stored; when it does, the response says so (stored: false) instead of dropping it silently.
  • Export and deletion. You can export the memories stored in your account through the API (GET /memory/export). You delete single memories (DELETE /memory/atoms/{id}) or whole private domains (DELETE /memory/domain/{domain}) through the API, and your whole account by a request to support@mnemoverse.com. The Privacy Policy (sections 11.4 and 11.5) says what is deleted and when.
  • We do not delete your memories because your plan changes, a payment fails or your account is suspended. In each of those cases you keep read and export access to what you stored (Refund & Cancellation Policy, Free Tier & Startup Program Terms).
  • The license you grant us is limited to hosting, copying, processing and transmitting your content to provide the service to you, and it ends when the content is deleted.

8. Shared Rooms (Beta) ​

A room is a memory space shared between Mnemoverse accounts (Rooms). It is a separate memory bucket: content written to a room lives in the room, not in the writer's private account, and joining a room exposes nothing from your private memory. The Privacy Policy (section 11.8) describes rooms in full. In short:

  • Membership is required and checked on every request. A room's owner adds members with a share code or through the console. Anyone who holds a valid share code, or the invite link or message that carries it, can join with the scope it grants until it expires or reaches its use limit, so treat a share code like a key.
  • Members can read what is stored there. Current and future members whose scope permits it can retrieve content stored in a room, including content stored before they joined. Read-only members cannot write.
  • You cannot take back a contribution yourself. No control lets a member retract past contributions, and leaving or being removed does not withdraw them.
  • Removing a member is access control, not erasure. It stops future access at once, but it cannot make a member forget what they already received.
  • Usage is billed to the caller, never to the room's owner.
  • Deleting a room is support-assisted. Archiving a room disables ordinary access but does not erase its content. A room owner, or anyone exercising a data-protection right over personal data in a room, can send a verified request to support@mnemoverse.com.

9. Availability and changes to the service ​

The service is provided "as is" (section 14). We do not commit to a level of availability unless a separate written agreement states one: the Pricing page lists an SLA, an uptime guarantee with credits, as an Enterprise feature. If an outage significantly affects your usage, contact support; refund requests for outages are evaluated case by case under the Refund & Cancellation Policy.

We change the service as it develops, and the documentation states what works today, including features that are switched off on the hosted service. Material changes that reduce what the Free tier offers are announced before they take effect.

10. Suspension and termination ​

By you.

  • You can cancel a paid subscription at any time in the console under Settings → Manage subscription. It stays active until the end of the billing period you have paid for, then your account moves to the Free tier.
  • You can ask us to delete your account, as section 7 describes.

When a payment fails. The Refund & Cancellation Policy sets out the schedule and its 14-day grace period, during which the service continues at your paid plan and both reads and writes work.

If the payment is still unpaid when the grace period ends, we pause new writes and email you. The API refuses writes with HTTP 429 until you update your payment method and the payment goes through; then writes resume. Reads and export keep working within your plan's limits, and your memories are kept (section 7). We do not cancel your subscription, downgrade your plan or delete your content because a payment failed.

When an account holds more atoms than its plan allows. After a downgrade, an account that holds more atoms than its new plan allows has a 30-day grace period. Once it has passed, the API refuses new writes and keeps serving reads, as the API reference describes under "Subscription / atom limit". Deleting memories or upgrading lifts the block.

Free tier fair use. For usage that looks outside the Free tier's purpose, we follow the order in the Free Tier & Startup Program Terms: we ask first, may suggest a paid plan, may reduce performance, and only as a last resort decline service. Whatever happens, your memories are not deleted, and you keep read and export access to them.

Stopping abuse. To stop abuse, an administrator can stop an organization's writes. Writes and memory deletions are then refused for every API key of that organization, reads keep working, and the API returns this message: "This organization's writes and memory deletions have been disabled by an administrator. Reads continue to work. Contact support if you believe this is an error." To dispute it, use our contact page.

By us. We may suspend or terminate an account for a breach of section 6, for non-payment, or because the law requires it. We give notice before acting, except while abuse is ongoing.

11. Privacy and data protection ​

The Privacy Policy explains how we handle personal data. UINSIDE Inc. is the data controller for the account, billing and operational data we collect to run the service, and a data processor for the memory content you store. The Privacy Policy also lists our sub-processors and how international transfers are safeguarded. The Cookies Policy covers what the website stores in your browser.

12. Intellectual property ​

Unless otherwise stated, UINSIDE Inc. and its licensors own the intellectual property rights in the service, in its software, and in the material published on this website. Open-source software we publish is governed by its own license (section 2). Your content remains yours (section 7).

13. Use of the website ​

You agree not to use the website in any way that causes, or may cause, damage to the website or impairment of its availability or accessibility.

14. Disclaimer ​

The service and the materials on our website are provided "as is". We make no warranties, expressed or implied, and hereby disclaim all other warranties.

15. Limitation of liability ​

In no event shall UINSIDE Inc. be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption) arising out of the use or inability to use the service or the materials on our website.

16. General ​

  • Order of precedence. A signed agreement, such as an Enterprise agreement or a DPA, prevails over these Terms. The Free Tier & Startup Program Terms prevail for Free-tier and grant matters. The Refund & Cancellation Policy is part of these Terms.

17. Changes to these Terms ​

We may revise these Terms. The current version is always on this page, and the "Last updated" date reflects the latest revision. Revised Terms apply from the date of publication, except that a material change takes effect only after we notify you. Continued use after a change takes effect means you accept it.

18. Contact ​

19. Additional terms for Sigma (closed beta) ​

Sigma reviews GitHub pull requests and posts its reviews back to them. It is a closed beta at sigma.mnemoverse.com. This section applies when you request beta access, accept an invitation, install the Sigma Mnemoverse GitHub App or ask Sigma for a review. The rest of these Terms apply to Sigma too; where this section says something different about Sigma, this section applies.

  • Access is by invitation. A request for beta access does not grant access. An invitation is personal: it works for the GitHub account it names and expires after 7 days. Once you accept it, your access stays until it is revoked. We may revoke access or end the beta, and we will email you before anything about the beta changes for you.
  • Free during the closed beta. Reviews requested by invited accounts run on our model access at no charge to you, within a shared limit that we set. When a limit is reached, reviews wait or stop, and the check on the pull request says which.
  • Connect only what you may connect. Install the App and connect repositories only where you have the right to do so, as their owner or administrator or with the owner's permission. Anyone with write access to a connected repository can ask Sigma for a review there.
  • What Sigma does with your code. To review a pull request, Sigma reads its commits through the GitHub App, reviews them in a disposable container, sends source and review context to model providers, and publishes a review, comments and a check run on that pull request. It never pushes, fixes or merges code. The Privacy Policy (section 12) and What Sigma does with your code say what is processed, where, by whom, for how long, and how to have it deleted.
  • Your code stays yours. Section 7 applies to the code and pull requests Sigma reads: we use them only to review them for you, and we do not train models on them.
  • Reviews are information, not approval. AI models produce Sigma's findings and a second model checks them; they can still be wrong or incomplete. A review is not a security audit, a guarantee that code is correct, or an approval to merge. You decide what to merge. Sections 14 and 15 apply.
  • Reviews are published on GitHub. Reviews, comments and checks appear on your pull request under GitHub's terms and your repository's visibility: on a public repository they are public, including to people who watch it. Removing Sigma does not remove what it has already published.
  • Stopping. You can turn a reviewer off, disconnect a repository or uninstall the App at any time, as Beta access and removing Sigma describes.
  • Help. Reply to your invitation email or write to support@mnemoverse.com.