memU
Back to memU

Legal · Version 2026-09-20

memU Terms of Service

Effective date: September 20, 2026 (Singapore Time)

Last updated: September 20, 2026 (Singapore Time)

1. Agreement and scope

These Terms of Service (the “Terms”) govern your access to and use of memu.so, memu.pro, the hosted MemU Cloud memory service, Cloud APIs, management pages and dashboard, installation materials, command-line tools, SKILLs, host-Agent adapters, SDKs made available by memU, and related services, including future versions of those offerings unless separate terms are presented (collectively, the “Services”).

The Services are provided by NEVAMIND AI PTE. LTD., a company organized under the laws of Singapore (“memU,” “we,” “us,” or “our”).

Before completing registration, you must affirmatively agree to these Terms and the MemU Privacy Policy. You cannot complete registration if you do not agree. By completing registration and subsequently obtaining or using an API key, installing or directing an Agent to install a memU integration, submitting or retrieving Memory, using MemU Cloud, or otherwise using the Services, you confirm your continuing agreement to these Terms.

If you created your account before the registration acceptance control was introduced, you will not be required to complete a one-time re-acceptance step solely because this initial version is published. To the extent permitted by applicable law, your continued use of the Services on or after the Effective date means that you agree to these Terms. If you do not agree, you must stop using the Services and close your account.

The current public version of these Terms is available at memu.so/terms-of-service. Links to these Terms and the Privacy Policy are provided through the MemU homepage, login or registration flow, management interface, and applicable site footer or equivalent navigation.

Important data and security notices

Before using MemU Cloud, you should understand these material limitations:

  • No encryption at rest: Memory, Search History, update records, complete API-key copies, and related stored index data are currently stored without encryption at rest. Do not submit passwords, private keys, authentication tokens, or information that applicable law or another obligation requires to be encrypted at rest.
  • Plaintext API keys: Complete API keys are stored so that you can view them again through the management page. Anyone who obtains access to an active key may be able to read, search, submit, or alter Memory associated with your account. Protect your account and keys and promptly revoke any key that may be exposed.
  • No backup or export guarantee: The standard Service does not guarantee backup, bulk export, migration, restoration, or recovery. Keep independent copies of information you cannot afford to lose.
  • Agent privacy risk: A host Agent may read local conversations, messages, and tool activity to prepare Memory and may not reliably recognize personal, confidential, or sensitive information. Review Agent permissions and stored Memory and do not assume sensitive content will be filtered automatically.
  • External vectorization: Plaintext Memory segments and Agent-prepared retrieval requests are sent to Voyage AI or another external provider for vectorization. Provider retention, training use, and processing locations may not be fully known or controlled by memU.
  • Permanent deletion: Closing your account permanently deletes associated Cloud data through the process described in Section 8. Deletion may begin immediately, cannot be undone, and there may be no backup from which to restore the data.

If you use the Services for a company or another organization, you represent that you have authority to bind that organization. A separate written agreement expressly governing the same Services controls to the extent of any conflict.

These Terms apply to hosted Services. Open-source software remains subject to its applicable open-source licence. Self-hosted infrastructure and third-party services selected by you are not operated by memU unless we expressly agree otherwise in writing.

2. Eligibility

MemU does not impose a separate universal minimum age. Because MemU operates as infrastructure used through Agents and host platforms, you must satisfy the minimum-age, eligibility, parental-consent, supervision, and other user-protection requirements that apply to the Agent or host platform through which you access MemU, as well as the requirements of applicable law.

You may use the Services only if you are legally permitted to do so and, where required, have authorization from a parent, legal guardian, or organization with authority to accept these Terms for you. Nothing in these Terms overrides protections or restrictions that apply to children or minors under applicable law.

The Services are intended to be available globally. You may not use the Services, and memU may not provide them to you, where access or provision is prohibited by Singapore trade controls, sanctions, export restrictions, or other applicable laws or regulations.

3. Accounts, API keys, and security

You must provide accurate account information and safeguard access to your email account, API keys, local configuration, environment variables, access tokens, and other credentials. You are responsible for activity conducted through credentials associated with your account.

The standard Service currently supports email-based login and personal accounts only. It does not currently provide organization accounts, team administrators, or shared account-management controls. Teams and organizations with those requirements may contact support@nevamind.ai to discuss a separate cooperation arrangement.

All current CLI operations authenticate through an API key. An active API key authorizes the supported CLI to upload, modify, search, and read Memory associated with your account. Treat every API key with the same care as a password. A person or system that obtains it may be able to read, submit, search, or alter Memory as you and may cause corruption, unauthorized access, or disclosure of your data.

The CLI does not currently provide a direct command for deleting Memory. It may remove the substantive Memory content by overwriting a fact with empty content. Search history and update-activity records associated with that operation remain subject to the separate retention rules in Section 8. The CLI and API-key authorization do not currently provide access to your search-history page or account-level operations such as closing your account.

memU stores both an irreversible hash and a plaintext copy of each active API key. Routine API authentication and identity matching use the irreversible hash. The plaintext copy is retained so that you can view the complete key through the authenticated management page and so that memU can generate installation instructions containing it in real time. Because the plaintext copy is stored without encryption at rest, compromise of your management-page session, the relevant production system, or storage may expose usable API keys.

You may create and delete multiple API keys through your MemU management page. We recommend using a different key for each device, Agent, or usage context so that you can manage access more precisely. When you revoke or delete a key, memU immediately deletes both the stored plaintext copy and corresponding irreversible hash. The revoked key becomes invalid for subsequent authentication attempts, although an operation already accepted before revocation may still complete.

When creating a key, you may assign a name and choose an expiration time. A key does not expire by default unless you set an expiration time. The management page displays the key's complete plaintext value, name, creation time, last-use time, and expiration time.

There is currently no stated maximum number of active API keys per account. memU may introduce a reasonable limit in the future based on security, fairness, capacity, or operational needs. We will update the applicable documentation or these Terms and provide any notice required by law before or when such a limit takes effect.

Installation instructions containing an API key are rendered in real time and are not retained by memU after generation.

You must promptly notify us at support@nevamind.ai if you suspect unauthorized access, key disclosure, credential compromise, or another security incident involving your account or Memory.

You must not publish an API key in source code, logs, prompts, screenshots, repositories, or other locations accessible to unauthorized persons. You should promptly revoke and replace a key that may have been exposed.

API-key capabilities may change as CLI functionality develops. We will update the applicable documentation and, where required, these Terms before materially expanding the operations available through an API key.

If you lose the ability to log in through your email account, you may contact support@nevamind.ai. To protect Memory and API keys, memU will require satisfactory evidence that you control or own the applicable email account or other legally sufficient proof of identity before restoring or changing access. It may be difficult or impossible to establish ownership when you cannot access the email account, and memU does not guarantee that an account can be recovered.

Closing your account immediately invalidates every API key associated with it. The stored plaintext copies and hashes are then deleted through the asynchronous account-deletion process described in Section 8.

4. Description of memU

memU is an agent-driven memory system that enables supported Agents to share reusable Memory across sessions, Agents, and devices.

Depending on the configuration, the Services may:

  • install or provide a SKILL, local CLI or binary, host adapter, configuration, scheduled task, and host instruction;
  • read new local Agent session history through the host adapter;
  • process session information locally for an Agent to evaluate and distill;
  • allow the Agent to create, update, or leave unchanged reusable Markdown Memory or Skills;
  • submit the resulting Memory changes, but not the underlying raw session history, to the selected Memory backend;
  • create embeddings and indexes for relevant retrieval; and
  • return relevant Memory to a connected Agent for use in a later task.

The host Agent performs the judgment and synthesis involved in producing Memory. The memU MemoryService stores, embeds, indexes, and retrieves the Memory submitted to it. It does not itself use a generative chat model to make the Agent's judgment or synthesis, although Cloud vectorization uses an external model or embedding provider as described in Section 10.

MemU Cloud provides a hosted Memory backend. In local or self-hosted mode, you select and operate the storage, embedding provider, environment, credentials, and infrastructure unless a separate agreement states otherwise.

Support for particular Agents, operating systems, versions, models, or features may change as those hosts and integrations evolve.

5. Installation, local access, and host Agents

memU ordinarily provides installation instructions for you to give to a supported host Agent. The host Agent, rather than memU acting directly on your device, interprets and carries out those instructions within the permissions and authority you have granted to it. You are responsible for reviewing the instructions and the Agent's requested actions and for granting only the permissions you consider appropriate.

Depending on the host and configuration, installation may include:

  • installing packages or binaries;
  • installing or updating a SKILL or host adapter;
  • creating or updating ~/.memu/config.env or similar configuration;
  • reading supported Agent session logs;
  • creating a scheduled background or bridging task;
  • writing local job, cache, or Memory files;
  • updating a host instruction file such as AGENTS.md, CLAUDE.md, SOUL.md, or another detected instruction file; and
  • sending Memory to or retrieving Memory from the configured backend.

The exact files, settings, permissions, and actions depend on the host Agent, operating system, version, your instructions to the Agent, and the authority you have granted to it. memU does not independently control or guarantee how a host Agent interprets or executes the installation instructions. You are responsible for granting appropriate local permissions, protecting local credentials, maintaining backups of files you need, and determining whether the integration is appropriate for your device, organization, and data.

Codex, Claude Code, Cursor, OpenClaw, Hermes, WorkBuddy, Cola, pi, and other host Agents are independent third-party products. Their terms, privacy practices, model behavior, permissions, and security controls apply separately. memU does not control how a host Agent interprets a SKILL or instruction or what content that Agent chooses to submit.

A host Agent and the memU CLI may not reliably recognize passwords, API keys, personal information, confidential business information, or other sensitive content in your sessions. You must not assume that the integration will identify or exclude such content before an upload. You are responsible for deciding what information may lawfully and appropriately be processed through the Services and for reviewing and correcting stored Memory when necessary.

The CLI may process raw conversations, tool-call records, or other session information on your device when preparing Memory. Under the current Cloud design, that raw session information is not uploaded to MemU Cloud; only the Memory prepared by the Agent is submitted. This boundary may differ in local or self-hosted configurations selected by you.

memU does not currently use an automatic-update mechanism for the CLI, SKILLs, or local configuration. If we later introduce automatic updates, we will update the relevant documentation and, where necessary, these Terms to explain the update behavior before it applies.

Uninstallation is performed for a selected host Agent. It is intended to remove or revise that host's SKILL, Agent instructions or configuration, scheduled or background tasks, and other host-specific integration components so that the host no longer performs memU actions. Shared CLI or binary files, memU configuration, API keys, caches, local Memory or other local data, and components used by other host Agents may remain so that uninstalling one host does not disrupt another.

Uninstalling local tooling affects only the applicable local integration. It does not close your MemU Cloud account or delete Cloud Memory, search history, update records, or other Cloud data. To request deletion of all Cloud content associated with the account, you must close the account through the management page or another supported account-closure process described in Section 8.

6. User Memory and ownership

“Memory” means information, Markdown files, Skills, resources, summaries, workflows, preferences, instructions, metadata, and other content submitted to or stored in the selected memU Memory backend. “User Content” includes Memory, retrieval queries, SKILLs you create, and other content you submit through the Services.

As between you and memU, you retain ownership of your User Content. You represent that you have all rights, permissions, notices, consents, and lawful bases needed to allow the Agent, local tooling, and memU to read, transform, submit, store, index, and retrieve that content. Your ownership does not extend to memU or third-party materials that may be incorporated into or used with your content.

You grant memU a non-exclusive, worldwide, royalty-free, limited licence to host, reproduce, segment, process, embed, index, transmit, retrieve, display to you, and otherwise use User Content only as reasonably necessary to provide, secure, maintain, and support the Services, comply with law, and carry out another purpose that you separately authorize.

memU does not acquire ownership of your private User Content and will not sell or license private User Content to third parties for their independent use.

SKILLs, instructions, templates, code, documentation, and other materials preinstalled, distributed, or supplied by memU remain owned by memU or its licensors. Any applicable open-source or product licence grants you the rights stated in that licence but does not transfer ownership of those materials to you.

The hosted Service provides an online page through which you can review and edit Memory stored in your account. When corrective action is required, the Service also supports editing or deleting an individual Memory. This control helps you manage stored Memory after submission, but it does not guarantee that a host Agent or CLI identified sensitive content before uploading it.

Deleting an individual Memory immediately removes the current Memory record, its text segments, embeddings, and vector-index entries. This action does not rewrite Search History or update-activity records. Search History does not currently preserve matched Memory content, but an update record may preserve the Memory content as it existed before the recorded update. Those records remain subject to the retention rules in Section 8.

MemU Cloud currently receives the Memory prepared by the Agent rather than the raw conversations, tool-call records, or local session logs from which the Agent or CLI prepared it. Memory may nevertheless contain text derived from those sessions, including personal, confidential, or sensitive information that the Agent did not recognize as sensitive.

The management page does not currently provide a bulk export of all Memory. You may view and manually copy individual Memory, Search History, and update-record information made available through the relevant pages, but the standard Service does not currently provide a dedicated download or export function for those materials.

The CLI may use an internal endpoint that retrieves all Memory needed for the CLI's operation. That endpoint is not a committed public export API. memU does not guarantee that its availability, format, fields, behavior, or returned content will remain unchanged, and you must not rely on it as a permanent export or portability mechanism.

7. Content storage and access

MemU Cloud currently stores its content without encryption at rest, including Memory content, search history, update records, plaintext API-key copies, and associated stored index or embedding data. These materials are stored in a form that the Service can read and process and must not be treated as end-to-end encrypted or encrypted-at-rest content. The absence of storage encryption may increase the consequences of unauthorized access to the underlying systems or storage.

You should not use the standard Service to store information that your organization, applicable law, or another binding obligation requires to be encrypted at rest. You should also avoid submitting passwords, private keys, authentication tokens, financial-account credentials, or similarly sensitive secrets as Memory or retrieval queries.

Network communications between supported CLI or web clients and MemU Cloud use HTTPS. Communications from MemU Cloud to the external providers used to vectorize Memory segments and retrieval queries also use HTTPS. HTTPS protects information while it is transmitted but does not change the unencrypted-at-rest storage described above.

Access to production systems is limited to authorized service-operations personnel for legitimate operational, security, support, or legal purposes. Production access is logged and subject to periodic review under memU's internal security controls. Permission to access production infrastructure does not by itself authorize personnel to inspect Memory plaintext, search-history content, API-key plaintext, or bulk user content.

memU personnel do not routinely inspect your private Memory or retrieval queries. We will not use plaintext Memory, retrieval queries, or conversation content for troubleshooting, evaluation, or analysis unless you first give additional, affirmative authorization for the disclosed purpose. If you request support or report a problem that requires inspection, we will explain the intended use and limit access and use to what is reasonably necessary for that purpose. We will not expand that authorized purpose without obtaining further authorization.

This restriction does not prevent automated processing needed to provide the Services. It also does not prevent limited access or disclosure where reasonably necessary to protect the security and integrity of the Services, investigate suspected unlawful use or abuse, comply with law or valid legal process, respond to a valid government request, or address an emergency involving risk of serious harm, subject to applicable law.

Where such exceptional access or disclosure occurs, memU will limit it to information reasonably necessary for the applicable purpose and will notify the affected user. Notice may be delayed or omitted where applicable law prohibits notice, notice would compromise a security response or investigation, or prior notice cannot reasonably be given in an emergency. Where permitted and practicable, we will provide notice before disclosure; otherwise, we will provide notice afterward when the restriction or emergency no longer prevents it.

8. Memory retention and deletion

While your MemU Cloud account remains active, memU does not proactively delete your stored Memory under its ordinary retention practice. This does not constitute a guarantee of permanent storage, backup, integrity, availability, export, or recovery.

We may delete, preserve, restrict, or isolate Memory where reasonably necessary to comply with law, enforce these Terms, protect security, address abuse, respond to an emergency, or manage a suspended or terminated account.

You may delete an individual Memory through the supported management controls. When the deletion succeeds, memU immediately deletes the current Memory record, its text segments, embeddings, and vector-index entries. Deleting a Memory does not alter Search History or update-activity records. Search History does not currently contain matched Memory content, but an update record may retain the pre-update Memory content described below.

MemU Cloud also stores retrieval requests prepared and submitted through a host Agent or CLI as Search History so that you can review, troubleshoot, and audit your own activity at memu.so/search-history. A stored request reflects the host Agent's interpretation of what it needs to retrieve and is not necessarily text written directly by you. Search History may include the search time, complete Agent-prepared retrieval request, and related account, Memory, or operational identifiers needed to associate and present the record. Specific metadata fields may change as the Service evolves.

Under the current design, Search History does not store the content or a snapshot of matched Memory, similarity scores or ranking, Agent type, or operation result. Search History is ordinarily expected to be retained for approximately three months. This period is neither a guaranteed minimum nor a strict maximum: operational circumstances may cause us to retain it for a longer period or delete it earlier, including where a user's data volume is high.

Users cannot currently delete individual Search History entries or clear all Search History. Search History is maintained as a factual record of activity, subject to memU's retention practices and the account-closure process described below.

An update record preserves the Memory content as it existed before the applicable update. It does not currently preserve both the before-and-after content in the same snapshot. Update records are ordinarily expected to be retained for approximately 90 days. This is an operational expectation rather than a guaranteed minimum or strict maximum: technical or operational circumstances may cause memU to delete them earlier or retain them longer. The standard Service does not provide an SLA for this retention period.

You may view only the Search History and update records associated with your authenticated account through the standard Service. memU personnel may access those records only after your affirmative authorization for the disclosed purpose or under the security, abuse, emergency, and legal exceptions described in Section 7.

When you close your MemU Cloud account, all associated API keys become invalid immediately. memU then begins asynchronously deleting all data associated with the account from ordinary production systems, including Memory, text segments, embeddings, indexes, search history, update records, stored API-key plaintext and hashes, account-profile data, and raw usage records that remain linked to you. The operational target is to complete this ordinary production deletion within approximately three days. Actual completion may take less or more time because of the amount of data and technical, operational, security, or legal circumstances. The three-day period is a target and not a guaranteed deadline. Aggregated statistics that cannot be traced or linked back to you are not account-associated data and may remain.

Account closure and the resulting deletion are permanent and cannot be undone. Deletion may begin immediately after closure. Because the standard Service has no backup or restoration guarantee, you must preserve any information you need before closing the account.

After account closure, the data awaiting asynchronous deletion is no longer ordinarily associated with an active user account. However, Memory or a historical snapshot may still identify you or another person if its content itself contains a name, email address, contact detail, or other identifying information.

memU does not currently maintain separate service backups or a routine isolated legal-hold store for Memory, search history, or update records. The standard Service therefore does not offer restoration from backup. If a valid governmental, legislative, judicial, regulatory, or other legal requirement requires preservation or different handling, memU may preserve, restrict, disclose, or otherwise process the limited information required and will follow applicable law and the authority's requirements. If memU introduces routine backup functionality or a broader preservation practice, we will update these Terms and the applicable privacy disclosures.

9. Usage and behavioral statistics

memU collects limited information about how the Services are used to operate, secure, measure, and improve the product. Raw usage records currently include:

  • event time;
  • client or software version;
  • Agent type;
  • operating-system type;
  • operation type;
  • error type; and
  • a user identifier used to deduplicate daily active users.

Usage statistics do not include API keys or API-key identifiers, IP addresses, additional device information, Memory identifiers, token counts, Memory text, retrieval-query text, or the content of retrieved Memory.

Raw usage and behavioral statistics are expected to be retained for approximately 90 days. memU may delete them earlier for operational or other reasons, so this period is not a minimum-storage guarantee.

After the raw records are deleted, memU may retain aggregated statistics only in a form that cannot be traced or linked back to a specific user. During aggregation, user identifiers are removed, and memU does not retain an identifier or mapping intended to reconnect the aggregate result to an individual user. memU will not attempt to re-identify data that has been aggregated or de-identified in this manner.

These non-identifying aggregate statistics may be retained for the long term without a fixed deletion period. They are not subject to the approximately 90-day raw-record period and are not deleted merely because an account is closed.

memU may use aggregate statistics for internal product analysis, capacity planning, reliability improvement, and business planning and may publish overall usage, activity, and trend information. If a small group or narrow breakdown could reasonably permit indirect identification, memU will combine, generalize, suppress, or refrain from publicly disclosing that breakdown. Current analysis is primarily performed at the overall-Service level.

memU does not currently use a third-party analytics platform to store or process these statistics. They are stored and processed within memU's own Service.

The retrieval-query history described in Section 8 is user content retained for review and troubleshooting and is not governed by this 90-day usage-statistics period.

10. Embeddings and third-party services

The Services divide Memory into segments and create vector embeddings and index structures so that relevant Memory can be retrieved. In Cloud mode, this process sends both plaintext Memory segments and retrieval queries received through an Agent or CLI to an external model or embedding provider for vectorization. MemU Cloud currently uses Voyage AI (voyageai.com) for this purpose. The Services may also rely on hosting, monitoring, or other subprocessors. Local or self-hosted mode may use a provider and credentials selected by you.

memU does not intentionally attach your username, email address, API key, or other account identity fields to the text sent for vectorization. However, if you or an Agent includes identity, personal, confidential, or other sensitive information within Memory or a retrieval query, that information will be transmitted to the external provider as part of the text.

memU uses these external providers to deliver the Services and does not intentionally select or submit user data to them for model-training purposes. However, memU has not verified a contractual promise from the current vectorization provider concerning model-training exclusion, zero retention, a specific retention period, or processing only in a specified region. External providers operate under their own systems, practices, terms, and contractual obligations, and memU cannot guarantee every aspect of their handling of data. You should not submit Memory that you are not permitted or prepared to have processed through the provider chain.

MemU Cloud's primary infrastructure is hosted in the AWS Tokyo Region (ap-northeast-1), and most processing performed by memU's own Cloud environment occurs there. Data sent to Voyage AI or another external provider may be processed, retained, or transferred in other countries or regions selected by that provider.

memU may replace or add vectorization, hosting, monitoring, or other providers as the Services evolve. We do not undertake to send you a separate notice merely because a provider changes. We may update our Privacy Policy, provider disclosures, or service documentation to reflect the change and will provide notice or obtain consent where applicable law requires it. A provider change does not reduce any non-waivable right you have under applicable law.

Third-party services are governed by their own terms and privacy practices. In self-hosted mode, you are responsible for evaluating, configuring, and lawfully using the third-party services you select.

11. Model training and product improvement

memU does not use private Memory, raw Agent history, retrieval queries, or retrieved results to train models operated by memU or another party. memU does not intentionally provide those materials to a third party for that party's model training.

memU may use the limited usage and behavioral statistics described in Section 9 to guide product strategy and improve reliability, compatibility, retrieval quality, and performance, subject to the 90-day raw-data retention policy and de-identification requirements for retained aggregates.

Specific plaintext Memory, retrieval queries, or Agent content may be inspected or used for troubleshooting, evaluation, or analysis only after the user gives additional, affirmative, purpose-specific authorization. We will disclose the intended purpose and will not expand that use beyond the authorization, except for narrowly defined legal, security, abuse, and emergency access described in Section 7.

This commitment governs memU's own use and the purposes for which memU intentionally provides data to a supplier. As described in Section 10, memU cannot make an absolute guarantee about independent conduct by an external provider beyond the safeguards and remedies available to memU.

12. Acceptable use

You are responsible for your use of memU and must use the Services in accordance with Singapore law and the laws and regulations applicable where you access or use the Services. You are responsible for determining whether your content, processing, and use of Memory are lawful and for obtaining any rights, notices, permissions, and consents that are required.

You may not use memU to store, index, retrieve, transmit, or facilitate content or activity that:

  • is unlawful, fraudulent, deceptive, abusive, exploitative, or seriously harmful;
  • infringes intellectual-property, privacy, publicity, confidentiality, or other rights;
  • contains malware, stolen credentials, unlawfully obtained data, or instructions intended to compromise systems;
  • processes personal or sensitive data without an appropriate legal basis and required notices or consents;
  • interferes with, probes, overloads, or bypasses the Services or their access and usage controls; or
  • helps another person do any of the above.

Users may report suspected unlawful use or another violation to support@nevamind.ai.

memU does not proactively inspect Memory or search history for the purpose of determining whether each user's activity is lawful. This does not reduce your responsibility for your conduct and does not prevent the automated processing needed to provide or secure the Services, investigation following a report or identified security concern, or action required by law.

If memU reasonably believes that an account, API key, Memory, or activity presents a legal or security risk or seriously violates these Terms, memU may act immediately to restrict access or operations, revoke API keys, terminate the account, isolate content, or delete relevant Memory. The separate formal suspension state described in Section 16 is used for applicable authority requirements. memU will limit the action to what it reasonably considers appropriate in the circumstances.

memU will generally notify the affected user of the reason for enforcement and allow the user to appeal by contacting support@nevamind.ai. Notice or detailed reasons may be delayed, limited, or omitted where required by law, necessary to protect security or another person, or needed to avoid compromising an investigation or emergency response.

memU retains the right to make the final platform enforcement decision based on its reasonable assessment of the facts, these Terms, and applicable law. This provision does not exclude any right or remedy that applicable law does not permit the parties to exclude.

memU may cooperate with courts, regulators, law-enforcement bodies, and other authorities and may preserve, restrict, disclose, or delete user data where required by applicable law or valid legal process, subject to the notice and minimization provisions in Section 7.

13. Open-source software and intellectual property

The open-source memU repository is licensed under Apache License 2.0. The applicable licence governs your use, copying, modification, and distribution of that open-source software.

memU and its licensors retain rights in preinstalled or distributed SKILLs, host instructions, templates, hosted services, websites, non-open-source software, interfaces, documentation, trademarks, designs, and other materials not owned by users or licensed to them under an open-source licence or these Terms. An applicable licence grants use rights but does not transfer ownership.

Third-party and open-source components are governed by their applicable licences, which control over conflicting terms for those components.

You may not use the memU, Nevamind.AI, or associated names, logos, trademarks, or brand assets without prior written authorization, except to the extent permitted by applicable law or published brand guidelines. You may not state or imply that memU or Nevamind.AI sponsors, endorses, or has an official relationship with you, your content, or your products unless expressly authorized.

If you voluntarily provide a suggestion, idea, improvement request, or other feedback about the Services, you grant memU a non-exclusive, worldwide, perpetual, irrevocable, royalty-free, transferable, and sublicensable licence to use, reproduce, modify, develop from, commercialize, publish, and otherwise use that feedback to develop, improve, operate, and promote memU and its products, without compensation or an obligation to use it. You must not submit feedback that you do not have the right to provide or that you expect memU to treat as confidential.

If you submit code, documentation, or another contribution to an open-source repository, the repository's applicable open-source licence, contribution notices, and separate contribution process govern that submission. These Cloud Terms do not by themselves transfer ownership of your contributed code or documentation to memU.

14. Fees and plans

The publicly available standard Service is currently offered without charge. memU does not currently provide self-service paid plans or integrated billing, automatic renewal, refund, or tax-processing functionality.

The standard Service does not currently have stated limits on calls, stored Memory, or concurrency. This does not create a contractual right to unlimited use. memU may introduce or adjust reasonable usage, storage, concurrency, rate, or other operational limits based on actual usage, capacity, security, fairness, or service conditions. If a request exceeds an applicable limit, memU may reject or stop serving that request.

memU will update the applicable Terms or service documentation and provide any notice required by law before or when material new limits take effect. memU may seek to preserve free access for most ordinary users where practicable, but does not guarantee that every feature, capacity level, or future version will remain free.

Before charging for a public Service that was previously free, memU will provide advance notice and require you to affirmatively select or agree to the applicable paid offering and its commercial terms. We will not automatically begin charging you merely because you previously used the free Service.

Users with specific commercial, capacity, support, or service-level requirements may contact support@nevamind.ai to discuss a separate arrangement. Pricing, payment, renewal, cancellation, refund, tax, service-level, and other commercial terms apply only if stated in the separate written agreement.

15. Service availability and compatibility

The standard Service does not guarantee uninterrupted availability, a particular response time, permanent storage, backup, restoration, export, or compatibility with every host Agent, model, operating system, version, or third-party service.

The publicly available standard Service does not include a service-level agreement or guaranteed availability, support-response time, processing time, or recovery time. If you require a higher service level, contact support@nevamind.ai to discuss a separate cooperation arrangement. Any SLA applies only if expressly agreed in a separate written agreement, which controls for the matters it covers.

Standard support requests may be submitted to support@nevamind.ai. The free standard Service does not guarantee that we will acknowledge, investigate, respond to, process, correct, or resolve a request within any particular time, or that a reported issue can or will be resolved.

The standard Service does not guarantee a download, bulk-export, migration, portability, restoration, or recovery capability. Information displayed in the management pages may be viewed or manually copied, but that does not create a commitment to preserve a particular page, format, field, endpoint, or workflow.

memU does not currently maintain separate service backups of Cloud Memory or search history. You should retain your own copies of information you cannot afford to lose. The absence of backups means deleted, corrupted, or unavailable information may not be recoverable.

Host products and their data formats, permissions, instruction behavior, storage locations, and APIs may change without memU's control. An integration that works with one host or version may later stop working or behave differently.

When reasonably practicable, memU will seek to provide advance notice of a material feature retirement, API change, or discontinued compatibility. We do not guarantee a fixed deprecation, compatibility, migration, or notice period, and immediate changes may be necessary for law, security, abuse prevention, third-party changes, or urgent operational reasons.

memU may discontinue the free standard Service because of product closure, resource constraints, a business decision, or similar circumstances. When reasonably practicable, we will provide advance notice and seek to provide as long a transition period as reasonably possible. We do not guarantee a specific notice, export, migration, or continued-operation period, particularly where immediate action is required by law, security, a third-party dependency failure, or circumstances beyond our reasonable control.

16. Suspension and termination

You may stop using the Services at any time. Uninstalling local tooling does not by itself close a MemU Cloud account or delete Cloud Memory.

You may request account closure through available account controls or by contacting support@nevamind.ai. Memory deletion following account closure is described in Section 8.

The standard Service does not currently allow you to place your own account into a suspended state. memU's formal suspension state is currently used in response to a requirement from a competent administrative, legislative, or other governmental authority. While an account is suspended, all direct login, API-key authentication, and other access are denied.

During suspension, stored Memory remains subject to the ordinary active-account practice in Section 8. Search History and update records continue to expire and be deleted under their ordinary retention rules. If an appeal succeeds or the applicable restriction is lifted, access to the remaining account data is restored and existing unexpired API keys may be used again. Data already removed through ordinary expiration or another lawful process cannot be restored.

Separately from the formal suspension state, memU may immediately restrict operations, revoke API keys, block access, terminate an account, isolate content, or delete relevant Memory where reasonably necessary to address suspected illegality, a violation of these Terms, fraud, abuse, a security risk, serious harm, legal requirements, or governmental direction.

memU will generally provide notice of the reason and an opportunity to appeal through support@nevamind.ai, subject to the legal, security, investigation, and emergency exceptions described in Section 12. memU will make the final platform decision on an appeal based on its reasonable assessment and applicable law.

Permanent termination for serious illegality, attacks on the Services, or another material violation follows the same asynchronous deletion process as voluntary account closure under Section 8. Data may be deleted immediately or at any time during that process. The ordinary operational target is to complete deletion within approximately three days; it is not a promise to retain data for three days or a guaranteed deletion deadline. Legally required preservation remains subject to Section 8.

Suspension, termination, account closure, or discontinuation of the Cloud Service does not remove local software or data from your devices. You are responsible for uninstalling and securely deleting CLI software, SKILLs, host-Agent instructions or configuration, scheduled tasks, cached data, local Memory, environment variables, and local copies of API keys that you no longer need.

17. Privacy

The MemU Privacy Policy explains how memU collects, uses, stores, shares, transfers, and deletes personal data in connection with the Services. You must review and affirmatively agree to the Privacy Policy and these Terms before completing registration.

The Privacy Policy provides additional information about these practices, including Cloud storage, external providers, international processing, retention, and account deletion. If these Terms and the Privacy Policy address the same subject, they should be read together; these Terms govern your use of the Services, while the Privacy Policy governs our handling of personal data.

18. Disclaimers

To the maximum extent permitted by applicable law, the standard Service is provided “as is” and “as available.” memU does not warrant that the Services will be uninterrupted, timely, error-free, completely secure, compatible with every Agent or environment, or available for any particular period.

Memory may be generated, summarized, selected, modified, or used by an Agent or other automated system. memU does not guarantee that any Memory will be accurate, complete, current, timely, relevant, free from bias, or suitable for your intended purpose. We will make reasonable efforts to improve the product and welcome reports at support@nevamind.ai, but those efforts do not create a guarantee of investigation, response, correction, or resolution within a particular time.

You are responsible for reviewing and independently verifying Memory before relying on it. You must not treat Memory or an Agent's use of Memory as the sole basis for medical, legal, financial, employment, safety-critical, or other professional or high-impact decisions. Obtain appropriate qualified human advice or review where necessary.

memU does not guarantee that Memory, search history, update records, API-key information, indexes, local files, or other data will be preserved, accurate, uncorrupted, unmodified, exportable, recoverable, or continuously available. You are responsible for maintaining independent copies of information you cannot afford to lose.

Codex, Claude Code, OpenClaw, other Agents and host platforms, external vector-model providers, operating systems, and other third-party services are not controlled by memU. To the maximum extent permitted by law, memU does not warrant their availability, security, conduct, outputs, permissions, data handling, compatibility, or continued support. Their own terms and privacy practices apply separately.

These disclaimers do not exclude, restrict, or modify any warranty, liability, consumer protection, or other right that applicable law does not permit the parties to exclude, restrict, or modify.

19. Liability, indemnity, and disputes

To the maximum extent permitted by applicable law, memU and its affiliates, officers, employees, contractors, licensors, and service providers will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for loss of profits, revenue, business, goodwill, data, or use, even if advised that such loss is possible.

The standard Service is provided without charge and without a service-quality guarantee. You are responsible for testing and evaluating whether the Service and any Memory are sufficiently accurate, reliable, secure, and suitable for your intended use before relying on them. To the maximum extent permitted by law, you assume the risks of using the standard Service and of the commercial, operational, and legal results of that use.

To the maximum extent permitted by applicable law, the total aggregate liability of memU and the parties listed above arising out of or relating to the free standard Service or these Terms will not exceed SGD 100, regardless of the form or theory of the claim.

Any enhanced or paid service-quality, support, availability, recovery, data-handling, or liability commitment, including a different liability cap, applies only if expressly stated in a separate written agreement with NEVAMIND AI PTE. LTD. That agreement controls for the matters it covers.

To the extent permitted by law, if you use the Services on behalf of an organization or for business or commercial purposes, you will defend and indemnify memU and its affiliates, officers, employees, contractors, and licensors against third-party claims, losses, damages, judgments, and reasonable legal costs arising from:

  • Memory, queries, instructions, or other data submitted or controlled by you;
  • your violation of these Terms or applicable law;
  • your infringement of another person's privacy, intellectual-property, confidentiality, or other rights;
  • your misuse of credentials, personal data, confidential information, or regulated information; or
  • your products, services, decisions, communications, or business or legal outcomes based on Memory or the Services.

memU will give you reasonable notice of a covered claim and reasonable cooperation at your expense. You may control the defense and settlement, but you may not settle in a way that admits liability by, or imposes an obligation on, memU without our prior written consent.

memU does not proactively inspect the scope of user data or each use of the Services. If an affected person submits a credible report, memU may investigate and may cooperate with that person, a court, regulator, law-enforcement body, or other competent authority, subject to applicable law and the access, minimization, and notice rules in Sections 7 and 12.

These exclusions and the SGD 100 aggregate cap do not apply to liability for fraud, wilful misconduct, death or personal injury caused by negligence, or another liability that applicable law does not permit memU to exclude or limit. The indemnity obligations apply only to the extent permitted by law and do not require a consumer to indemnify memU where such an obligation would be prohibited or unenforceable under applicable law.

These Terms are governed by the laws of Singapore, without regard to conflict-of-law rules.

Before filing a claim, you and memU agree to make a reasonable effort to resolve the dispute informally. You must send a description of the dispute and the relief requested to support@nevamind.ai. We will use reasonable efforts to discuss the matter in good faith.

Subject to any non-waivable rights under applicable law, the courts of Singapore have exclusive jurisdiction over disputes arising out of or relating to these Terms or the Services.

Nothing in this section prevents either party from seeking urgent injunctive or equitable relief, reporting a matter to a regulator, or using a mandatory consumer-dispute process available under applicable law.

20. Changes, general terms, and contact

Changes to these Terms

memU may review and update these Terms as market conditions, the Services, our business, risk controls, suppliers, or applicable law change. When we do, we will update the Last updated date shown at the beginning of the published Terms. This statement does not promise a fixed public review schedule.

If a change is material, we may provide reasonable notice through the Services, by email, or through another reasonable channel, or require you to affirmatively accept the revised Terms, depending on the nature of the change and applicable law. A change required for legal, regulatory, security, fraud-prevention, or urgent operational reasons may take effect immediately. The revised Terms will state their effective date.

Where we do not require renewed affirmative acceptance, then, to the extent permitted by applicable law, your continued use of the Services after revised Terms take effect means that you accept them. If you do not agree to the revised Terms, you must stop using the Services and close your account. We will provide notice or obtain renewed consent where applicable law requires it. This clause does not limit any consent, notice, termination, or other right that applicable law requires.

Entire agreement and order of precedence

These Terms, the Privacy Policy, any feature-specific terms presented to you, and any separate written agreement applicable to your use constitute the agreement between you and memU concerning the Services. A separate written agreement expressly governing the same subject matter controls to the extent of a conflict. An applicable open-source licence controls your use of the software or component it covers.

Assignment

You may not assign or transfer these Terms, your account, or your rights or obligations under them without memU's prior written consent. memU may assign or transfer these Terms to an affiliate or in connection with a reorganization, financing, merger, acquisition, or sale of all or part of the business or assets associated with the Services, subject to applicable law.

Events beyond reasonable control

memU is not responsible for delay or failure caused by events beyond its reasonable control, including natural disasters, war, civil disturbance, government action, labour disputes, failures of electricity, telecommunications or the Internet, cyberattacks, or outages or failures of host Agents, Cloud infrastructure, model providers, and other third-party services. This clause does not exclude a responsibility that applicable law does not permit us to exclude.

Independent relationship and third parties

These Terms do not create a partnership, joint venture, fiduciary, employment, franchise, or agency relationship between you and memU. A host Agent, host platform, integrator, or other third party cannot make commitments on memU's behalf unless we expressly authorize it in writing. Except where these Terms expressly state otherwise, they do not create rights for a person who is not a party to them.

Waiver, severability, and survival

If either party does not enforce a provision immediately, that does not waive the right to enforce it later. Any waiver must be express and in writing.

If a court or other competent authority finds a provision unlawful, invalid, or unenforceable, that provision will be enforced to the maximum extent permitted or, where necessary, removed, and the remaining provisions will continue in effect.

Provisions that by their nature should continue after suspension, termination, or account closure—including provisions concerning ownership, licences, disclaimers, liability, indemnity, disputes, and these general terms—will survive.

Electronic communications and language

You agree that notices and other communications concerning the Services or these Terms may be provided electronically, including through the Services, the account interface, or the email address associated with your account. You are responsible for keeping that email address current. Electronic communications satisfy any written-notice requirement to the extent permitted by applicable law.

The English version of these Terms controls if a translation conflicts with it, except where applicable law requires otherwise.

Contact

Questions, legal notices, complaints, security reports, and appeals concerning these Terms or the Services may be sent to:

NEVAMIND AI PTE. LTD.

Email: support@nevamind.ai