# Memroot

> Persistent engineering memory for your coding agents: save a durable lesson once and recall it in every agent you connect.

## What Memroot does

- Durable engineering lessons such as decisions, proven fixes, conventions, and failed approaches.
- Memory packs are designed for task-specific context instead of an unbounded history dump.
- Memroot is designed to keep engineering knowledge independent of any one coding agent.
- Engineering lessons belong in a typed memory graph, with evidence, provenance, and Git context.

## Trust

- Memories belong to the developer or project, not to one coding agent.
- Review and revoke each coding-agent connection from your console.
- Memroot stores structured engineering memories, not full coding-session transcripts.
- The memory graph records evidence, provenance, and explicit stale or superseded states.

## Workflow

1. Connect your coding agents through the Memroot MCP server. Each connection is authorized in the browser for one project.
2. Save structured engineering lessons with evidence and provenance.
3. Memory packs are designed to carry task-specific context, provenance, and staleness signals.

## Agent compatibility

Memroot is designed around agent-neutral contracts.

Works with: Claude Code, Codex, Grok.

## Pricing

Limits apply across your tenant. Monthly writes and retrievals reset each UTC calendar month. Total memory writes and total assertions are lifetime admissions; deleting memories does not restore them. An assertion is one atomic statement inside a memory; a memory can hold up to 8.

- **Free — $0 / month** (Available)
  - 1 project
  - 100 memory writes / month
  - 1,000 retrievals / month
  - 500 total memory writes
  - 1,000 total assertions
  - 30 data requests / minute
- **Basic — $9.99 / month** (Available)
  - 5 projects
  - 1,000 memory writes / month
  - 10,000 retrievals / month
  - 5,000 total memory writes
  - 15,000 total assertions
  - 60 data requests / minute
  - Monthly subscription in USD. Review your plan and complete secure checkout after signing in.
- **Pro — $19.99 / month** (Available)
  - 20 projects
  - 5,000 memory writes / month
  - 50,000 retrievals / month
  - 25,000 total memory writes
  - 75,000 total assertions
  - 120 data requests / minute
  - Monthly subscription in USD. Review your plan and complete secure checkout after signing in.
- **Max — $49.99 / month** (Available)
  - 100 projects
  - 15,000 memory writes / month
  - 200,000 retrievals / month
  - 75,000 total memory writes
  - 225,000 total assertions
  - 300 data requests / minute
  - Monthly subscription in USD. Review your plan and complete secure checkout after signing in.

Choose a paid plan, sign in, and confirm checkout. Subscription access is activated only after payment confirmation. Automated consolidation and processing-priority tiers are not offered.

## Privacy notice

Full notice: https://memroot.dev/privacy

Last updated October 11, 2026 at 11:26:21 UTC

### Who we are and what this notice covers

Memroot is an engineering-memory product operated from Ukraine. The operator of Memroot is the data controller for the personal data described in this notice. Contact privacy@memroot.dev about privacy or your data, and support@memroot.dev about anything else.

This notice covers the website memroot.dev, the console at console.memroot.dev, sign-in at auth.memroot.dev, the Memroot MCP server (the connection your coding agent uses), the command-line tool, and subscription billing.

If you store content in Memroot for a business or another organization, Memroot processes any personal data in that content on that organization’s instructions. An organization that needs a data processing agreement can request one at privacy@memroot.dev.

### The data we process

- **Account and sign-in:** WorkOS AuthKit hosts our sign-in pages at auth.memroot.dev and processes account information such as your name, email address, identity-provider identifier and authentication credentials. Memroot’s own databases hold identifiers for your account and for its isolated workspace (a tenant), a keyed hash of the provider identity used to route your account, and account status. They do not store your email address, and the account directory does not use your email address as its identity key. They store a display name only if you enter one in the console settings, and you can clear it there at any time.
- **Social sign-in:** If you choose Google sign-in when it is offered, Google shares basic profile information and email with WorkOS for authentication. If GitHub sign-in is offered and you choose it, GitHub shares your identity and email with WorkOS for the same purpose. Google and GitHub passwords stay with those providers; Memroot does not receive them. Email and password sign-in remains available through WorkOS.
- **Sessions:** A server-side session record keeps you signed in to the console. It holds WorkOS refresh credentials and the WorkOS session identifier in encrypted form. The browser receives only the cookies listed below.
- **Connections for agents and the command-line tool:** When you authorize a coding agent, the Memroot MCP server or the command-line tool, Memroot stores the client registration, your consent, a connection record, and the access and refresh tokens issued to that client. The command-line tool keeps its credentials in your operating system’s keychain.
- **Engineering memory:** The content that you or your authorized clients save: memory titles, summaries and statements, short evidence quotes, file paths, symbol names, repository identifiers, commit context, and where each memory came from. It is stored in our hosting provider’s databases and is visible to you in the console. It can include personal data if you put it there, such as a name in commit context. To make memories searchable by meaning, Memroot converts the titles, summaries and statements of your memories into embeddings (numeric representations that can reveal information about the text they were made from) with an embedding model hosted on Cloudflare’s Workers AI service, and stores the embeddings in Cloudflare’s vector database (Vectorize), a store for embeddings.
- **Similarity between your memories:** Memroot also compares the embeddings of the memories in a project with each other, so that the console graph can show which of your memories are close in meaning; the resulting similarity scores are stored in Memroot’s databases with the project, are treated as your content, and are removed after either memory is deleted or replaced.
- **Usage and limits:** Counts of projects, memory writes, total assertions, and retrievals, measured against your plan. An assertion is one atomic statement inside a memory.
- **Retrieval requests:** The query text is used to find matching memories: the same embedding model on Cloudflare’s Workers AI service converts it into an embedding, which is compared with the embeddings of your memories. Activity keeps the limited outcome metadata described below, not the query text or its embedding.
- **Activity history:** The console shows a limited history of new memory saves, completed retrievals (including requests with no matches), and some failed operations. Its records hold account and project identifiers, the time, operation and outcome, the agent and save source reported by the client, result counts, and up to 20 memory identifiers per event. These identifiers are your data even though they do not contain the memory text. Memory titles shown in Activity are read from memories you can currently access; titles and content are not copied into the history. Activity records contain no query text, transcripts or tokens. The history starts when recording is enabled and may have gaps: operations refused before they reach the project database, local capture status and background job status are not recorded, and recording limits or a recording failure can leave an event missing. Accepted session-extracted memories can appear as memory saves. A memory returned to an agent does not show whether the agent used it.
- **Network data:** Cloudflare, our hosting provider, processes IP addresses and request metadata to deliver and protect the service, including rate limiting. To limit sign-in and authorization attempts, Memroot keeps a hash of the IP address for a few minutes. Memroot runs no analytics or advertising trackers on its website or console.
- **Billing:** For paid subscriptions, Creem (Armitage Labs OÜ, Estonia) processes checkout and subscription payments as merchant of record. Creem collects your name, email address, billing address, payment details and order details as a controller, under its own privacy notice. Creem shares your name, country and email address and the order, customer and subscription identifiers with the operator, who uses them to handle billing, refunds and support; Creem also generates AI-based statistics for the operator, as described under Creem below. Memroot stores provider customer, transaction and subscription identifiers, the selected plan, subscription status and billing-period dates to manage access and usage limits. Memroot does not receive full payment-card details.
- **Support email:** If you email a memroot.dev address, Cloudflare forwards the message to the operator’s mailbox hosted by Google, where your address and message are stored. Replies may come from the operator’s personal email address.

### Cookies and local storage

Memroot uses only the cookies and browser storage needed to sign you in and remember display preferences. It uses no advertising or analytics cookies.

- **`__Host-memroot_session`:** Keeps you signed in to the console. It is an opaque, secure, HTTP-only cookie that lasts up to 12 hours.
- **`__Host-memroot_login`:** Protects the sign-in transaction. It lasts 10 minutes.
- **`sidebar_state`:** Remembers whether the console sidebar is open. It lasts 7 days.
- **`memroot-theme`:** Stores your light or dark theme preference in your browser’s local storage until you clear it.

The sign-in pages at auth.memroot.dev are operated by WorkOS and may set the cookies needed to authenticate you. Checkout is operated by Creem. Paying for a subscription opens Creem’s checkout in your browser, which may set its own cookies; ordinary account sign-in does not open checkout.

### Optional session capture

Session capture is off unless you turn it on in the command-line tool, in releases that include it. You can turn it off again at any time.

When it is on, a worker on your machine redacts the session transcript locally and passes a redacted excerpt to your own coding-agent CLI, run without tools, to extract candidate memories. Your coding-agent vendor processes that excerpt under your account with them and their terms. Memroot does not receive it.

Only the resulting structured memories are uploaded: statements, short evidence quotes, repository-relative paths and symbols, the repository’s remote URL in normalized form, salted hashes, and the names of the extractor and model. The capture worker also sends one retrieval request that includes the repository name. Memroot never receives raw transcripts or tool output on this path. The service validates these memories, labels them as session-extracted, and may reject them.

### How we use data and our legal bases

- **To provide the service:** We use account, session, connection, memory, activity, usage and billing data to authenticate you, route your account, store, search and return your memories, show recent operation outcomes, and apply plan limits. The legal basis is our contract with you.
- **To keep the service secure:** We use network data, session records and rate limits to protect accounts and prevent abuse. The legal basis is our legitimate interest in a secure service.
- **To answer you:** We use support email to reply and to keep a record of your request. The legal basis is our contract with you or our legitimate interest in supporting users.
- **To meet legal obligations:** We keep billing identifiers and respond to lawful requests where the law requires it. The legal basis is a legal obligation.
- **To understand subscription sales:** When you buy a subscription, Creem generates AI-based statistics for the operator from your name, email address and IP address, acting as the operator’s processor. The legal basis is our legitimate interest in understanding how the service is bought. To object to this processing, write to privacy@memroot.dev; we pass your objection to Creem, which carries out the processing.

Where the law that applies to you requires consent, we ask for it before that processing starts. Optional features such as social sign-in and session capture run only if you choose them, and you can stop using them.

Memroot does not make decisions about you by automated means that have legal or similarly significant effects.

### What Memroot does not do

- Memroot does not send your memory content to any AI model provider other than Cloudflare, and does not use it to train models. Cloudflare, which already hosts Memroot’s service and databases, runs the embedding model that makes memories searchable by meaning (see “The data we process”). Embeddings are treated as your content and are removed after the memory they belong to is deleted. If you turn on session capture, your own coding-agent vendor processes the redacted excerpt as described above.
- Memroot uses your content only to serve the account and projects it belongs to. It is not shared between accounts.
- Memroot does not sell personal information, share it for cross-context behavioral advertising, or use it for advertising.
- Memroot does not sell Google identity data, use it for advertising, or send it to AI models for training.
- Signing in does not give Memroot access to Gmail, Google Drive, or GitHub repositories. Social sign-in is limited to identity information; it is not a connection for accessing those services on your behalf.

### Service providers and sharing

- **Cloudflare:** Hosts the website, console, API and databases, and protects them from abuse. It processes service traffic, stores account records and memory content, runs the embedding model (Workers AI) that processes the text of memories and search queries, stores the resulting embeddings in its vector database, and routes email sent to memroot.dev addresses. Cloudflare’s Workers AI documentation says that Cloudflare does not use customer content to train the AI models offered on Workers AI or to improve Cloudflare or third-party services without explicit consent, and does not make it available to other Cloudflare customers. Cloudflare’s Workers AI documentation does not say how long the service keeps the text it processes or in which country the model runs, so Memroot cannot promise either. [Cloudflare privacy policy](https://www.cloudflare.com/privacypolicy/) · [Cloudflare Workers AI data usage](https://developers.cloudflare.com/workers-ai/platform/data-usage/)
- **WorkOS:** Hosts sign-in and stores account authentication data in the United States. [WorkOS privacy policy](https://workos.com/legal/privacy)
- **Google:** Stores email you send to memroot.dev addresses, in the operator’s mailbox hosted by Google. It also takes part in sign-in if you choose Google sign-in. Google acts under its own privacy practices. [Google privacy policy](https://policies.google.com/privacy)
- **GitHub:** Only if you choose GitHub sign-in. GitHub acts under its own privacy practices. [GitHub privacy statement](https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement)
- **Creem:** Merchant of record for paid subscriptions, operated by Armitage Labs OÜ in Estonia. Creem handles billing and payment information as a controller and shares your name, country, email address and order identifiers with the operator. To generate AI-based statistics for the operator, Creem also processes your name, email address and IP address as the operator’s processor, under its data processing agreement at creem.io/dpa. Annex 3 of that agreement lists Creem’s sub-processors and the countries where they process data; most process data in the United States. [Creem privacy notice](https://www.creem.io/privacy)

Your coding-agent vendor is chosen by you and is not our service provider. We may also disclose data when the law requires it, or to a successor that takes over the service and keeps to this notice.

### Where data is processed

The operator is in Ukraine. Cloudflare runs a global network and may process and store data in the United States and other countries; Memroot’s databases, the embedding model and the vector database are not restricted to one region. WorkOS stores and accesses account authentication data in the United States. Creem, the merchant of record for paid subscriptions, is established in Estonia and lists sub-processors in the European Union and the United States. Memroot is not an EU-only service.

Cloudflare’s and WorkOS’s published data processing terms include standard contractual clauses for transfers of personal data from the European Economic Area, the United Kingdom and Switzerland where those apply. Creem’s privacy notice says it uses safeguards such as standard contractual clauses for its service providers outside the European Union and the European Economic Area. Ukraine is not covered by a European Commission adequacy decision. When you buy a subscription, Creem shares your name, country and email address with the operator in Ukraine under its data sharing agreement at creem.io/dsa. That agreement makes the operator responsible for the safeguards on this sharing and includes no standard contractual clauses. The operator receives this data to handle billing, refunds and support for the subscription you bought; Memroot’s databases do not store it. A business customer that needs transfer terms can request them together with a data processing agreement. The safeguards named here are in the providers’ published terms; ask privacy@memroot.dev which of them apply to your data and where to read them.

### Retention and your choices

- **Account records:** Kept while your account exists. Session expiry or signing out ends session access; it does not delete your account or every stored record.
- **Engineering memory:** Kept until you ask us to delete it. It has no automatic expiry. Embeddings of a memory are kept only for as long as the memory is in use. When a memory is deleted or replaced, its embeddings stop being used for search immediately and are then removed from the vector database by a background process.
- **Session records:** A session stops working after 12 hours without use, or 30 days in total. Expired session records are not yet removed automatically; they are deleted with the account.
- **Connections and tokens:** Access tokens last 15 minutes and refresh tokens up to 30 days. Pending sign-in and consent records last about 10 minutes. A revoked connection can no longer be used. Connection records are deleted with the account.
- **Rate-limit records:** Hashed IP addresses used for rate limiting expire within a few minutes.
- **Usage counts:** Kept with the account. The count of total memory writes and the count of total assertions are not reduced when memories are deleted.
- **Activity history:** Events stop appearing in Activity after 30 days. Expired records are removed from the database by background cleanup in bounded batches; this is not a promise of physical erasure at exactly 30 days. Deleting a memory stops its title and content being shown in Activity, while the limited operation record and memory identifier may remain until the history expires. Account or project deletion stops access to its history and includes the activity records in deletion cleanup. Hosting-provider recovery copies may retain deleted data for a limited period.
- **Billing records:** Payment records may be retained to meet accounting, tax, fraud-prevention and legal obligations even after an account is closed.
- **Support email:** Kept for as long as needed to handle your request and keep a record of it.

There is no self-serve deletion or export yet. To request access, a copy, correction or deletion of your account or your content, email privacy@memroot.dev. Requests are handled by the operator, may require verification of account ownership, and are answered within 30 days.

When we delete an account, we delete its records and content in Memroot’s databases and its sign-in record at WorkOS; the embeddings of that content stop being used immediately and are then removed from the vector database by a background process. Deleted data may remain in our hosting provider’s short-term recovery copies for a limited period. Cloudflare’s documentation for its vector database does not say how long removed embeddings remain in its own systems. Creem keeps payment records for the periods in its own privacy notice, which gives seven years for accounting data.

In the console you can revoke a coding-agent or command-line connection yourself. You can also revoke a social sign-in authorization in your Google or GitHub account settings; revocation alone does not delete your Memroot account.

### Your rights

Depending on where you live, laws such as the Law of Ukraine “On Personal Data Protection” and the EU and UK General Data Protection Regulation give you rights over your personal data. You can ask us to:

- tell you what personal data we hold about you and give you a copy;
- correct data that is wrong or incomplete;
- delete your account and your content;
- give you your content in a portable format;
- restrict processing, or object to it;
- stop processing that relies on your consent.

Email privacy@memroot.dev to use these rights. We do not charge for a request and do not treat you differently for making one.

You can complain to the data protection authority where you live. In Ukraine this is the Ukrainian Parliament Commissioner for Human Rights.

You do not have to give us personal data, but you cannot have an account without signing in.

### Security

Data is encrypted in transit. Sign-in credentials that Memroot holds for your session are encrypted before they are stored, and the console session cookie cannot be read by page scripts. Each request is checked against your account, project and connection permissions, and stored data is separated by account. Access to production systems is limited to the operator.

No system is perfectly secure. Do not store secrets in Memroot. If we learn of a breach that affects your data, we will tell you as the law requires.

### Children

Memroot is for adults. It is not directed to anyone under 18, and we do not knowingly collect their personal data. Contact us if you believe a child has created an account.

### Changes and contact

We will update this notice when our data practices change, and post the new version on this page with a new date. New uses of Google data require an updated disclosure and any required consent before they begin.

For privacy questions, contact privacy@memroot.dev.

## Terms of service

### Who we are and these terms

Memroot is persistent engineering memory for developers and their projects, available at memroot.dev and console.memroot.dev. Memroot is operated from Ukraine. In these terms, “Memroot”, “we” and “us” mean the operator of the service.

These terms are an agreement between you and Memroot. You accept them when you create an account, connect a coding agent or the command-line tool, or otherwise use the service. If you do not agree, do not use Memroot.

You must be at least 18 years old. If you use Memroot for an employer or another organization, you confirm that you have authority to accept these terms for it, and “you” includes that organization.

Contact support@memroot.dev with account, service, billing or legal questions.

### The service and its alpha software

Memroot stores engineering knowledge that you or your coding agents save, and returns relevant memories to the clients you authorize.

The Memroot command-line tool and plugins are alpha software. Features, limits and interfaces may change, and parts of the service may be interrupted, changed or removed. We do not offer a service-level agreement or an uptime commitment.

Features described as planned or coming soon are not part of the service or of any purchase until they are released.

### Your account and credentials

You sign in through our authentication provider. Give accurate information and keep your sign-in method secure.

Connections you authorize for coding agents, the Memroot MCP server (the connection your coding agent uses) and the command-line tool act for your account. You are responsible for activity through your account and your connections. Authorize only clients you trust, and revoke connections you no longer use in the console.

Tell us at support@memroot.dev promptly if you believe your account or a connection has been used without your permission.

### Your content

You keep ownership of the engineering memory and other content that you or your authorized clients submit to Memroot (“your content”).

You give Memroot a limited, non-exclusive license to host, store, process, index and display your content to you and to the clients you authorize, only to provide, secure and support the service. We do not use your content to train models, and we do not share it between accounts.

You are responsible for your content. Submit only content you have the right to use and to store with us, including text derived from code that belongs to your employer or clients. Do not submit:

- passwords, API keys, tokens or other secrets;
- personal data about other people that is not needed for engineering work, or any sensitive personal data;
- content that is unlawful or that infringes someone else’s rights.

Memroot screens submissions for some common credential formats and rejects matches. This filter is a safeguard, not a guarantee, and you remain responsible for what you submit.

Memroot is not a backup or archive service. Keep your own copies of anything you cannot afford to lose.

The privacy notice explains how we handle personal data. If your organization needs a data processing agreement, request one at privacy@memroot.dev.

### Acceptable use

You must not, and must not let anyone else:

- bypass or try to bypass usage limits, including by creating multiple accounts;
- access or try to access another account’s data, or get around authentication, authorization or the isolation between accounts;
- probe, scan or test the service for vulnerabilities without our written permission, or disrupt or overload it;
- submit unlawful, infringing or harmful content, or malware;
- resell or sublicense the service, or offer it to third parties as your own;
- scrape the service, or use it to build a competing product or dataset;
- reverse engineer the hosted service, except where the law gives you that right;
- use Memroot in breach of the law.

If you find a security problem, report it to security@memroot.dev and give us reasonable time to fix it before you disclose it.

### Memories and coding agents

Memories are saved by you or by your coding agents. If you turn on optional session capture where it is available, memories can also come from an extraction step that runs on your machine through your own coding agent. Memories can be inaccurate, incomplete or out of date, and they can conflict with your current code.

Memroot provides context, not professional advice. Coding agents are third-party tools that you choose and control. You are responsible for reviewing what an agent does with a memory before you rely on it, including any change it makes to your code, systems or data.

### Third-party services

Memroot works with services we do not control: your coding agents and their vendors, the sign-in provider you choose, our hosting and authentication providers, and Creem for payments. Your use of those services is governed by their own terms and privacy policies. We are not responsible for third-party services, or for changes they make that affect an integration.

### Plans and usage limits

The pricing page describes the available plans and their usage limits. Limits apply to your whole account. A paid plan can be purchased only while the pricing page shows it as available, through checkout opened from the Billing page of the console.

Monthly usage allowances reset on UTC calendar months. Total memory-write and total assertion admissions do not reset when memories are deleted. A plan change does not erase usage already consumed.

Requests over a limit may be refused until the allowance resets or you move to a higher plan. Memroot may also refuse requests for a short time to protect the service.

We may change plans and limits. A change that reduces the limits of a paid plan you already have takes effect no earlier than your next billing period, with at least 30 days’ notice.

### Subscriptions and payment

Basic, Pro and Max subscriptions are priced monthly in USD at $9.99, $19.99 and $49.99 respectively. Paid plans have no free trial. The Free plan needs no payment details.

Payments for Memroot subscriptions are processed by Creem as the merchant of record. Creem is Armitage Labs OÜ, a company registered in Estonia. Creem sells the subscription to you, charges your payment method, issues the invoice, and calculates, collects and remits any applicable sales tax or VAT. Creem’s Buyer Terms, at creem.io/buyer-terms, apply to the purchase together with these terms. Memroot provides the service under these terms and handles support and refund requests.

Review the final amount and applicable tax information in checkout before paying. A subscription is billed in advance each month and renews automatically at the current price until you cancel. You authorize Creem to charge your payment method for each renewal.

We may change prices. A price change for an existing subscription takes effect no earlier than the next billing period after at least 30 days’ notice, given in the console or by email to the billing email address Creem holds for your subscription. You can cancel before it applies.

If a renewal payment fails, your paid limits continue for 72 hours while the payment is retried. After that the account moves to the Free plan limits. Paid limits return when the payment succeeds.

### Plan changes and cancellation

Plan changes are not made in the console itself. The Billing page may point you to Creem’s customer portal for a plan change; whether the portal offers one depends on Creem. If it does not, or if you would rather ask us, email support@memroot.dev: we make no change, and nothing is charged for one, until you have agreed to it. You can also cancel on the Billing page and choose another plan after the current billing period ends.

You can cancel at any time on the Billing page of the console. Cancellation stops future renewal charges. Your paid plan continues until the end of the current billing period, and then the account moves to the Free plan. You can also cancel in Creem’s customer portal, through the link in your Creem receipt email or at creem.io/my-orders/login. A cancellation made in Creem’s portal may take effect immediately. If a subscription is ended immediately, paid access ends at once.

When an account moves to a lower plan or to Free, your stored content is kept. The lower plan’s limits apply, so new writes, retrievals or projects may be refused until you are within them.

Canceling a subscription does not delete your account or content. Deletion is a separate request described in the privacy notice. Refunds are described in the refund policy.

### Suspension and termination

You can stop using Memroot at any time. To close your account and delete its content, email privacy@memroot.dev. Cancel any paid subscription first so that renewals stop.

We may suspend or limit access, or close an account, if:

- you breach these terms;
- your use creates a security or legal risk for Memroot or for other users;
- a payment is reversed or stays unpaid;
- the law requires it.

Where it is reasonable, we tell you first and give you a chance to fix the problem. Contact us if you believe a restriction is a mistake or a paid feature is not working.

We may remove content that breaches these terms, and we may delete the content of a closed account.

We may stop offering Memroot. Where practicable, we give at least 30 days’ notice on the website or in the console so that you can request a copy of your content. If we stop offering Memroot and you have paid for a period you can no longer use, you receive a pro-rata refund for the unused part.

When an account is closed, your right to use the service ends. Terms that by their nature should continue still apply, including those on your content, disclaimers, limits of liability, indemnity and governing law.

### Our software and your feedback

Memroot, its software, documentation, design and brand belong to Memroot or its licensors. These terms give you no rights in them other than the right to use the service.

We give you a limited, non-exclusive, non-transferable, revocable license to install and use the Memroot command-line tool and plugins, only to access the service for your own or your organization’s projects. Open-source components included in them stay under their own licenses.

If you send feedback or suggestions, we may use them without restriction or payment. Do not include confidential information in feedback.

### Disclaimers

Memroot is provided “as is” and “as available”. To the fullest extent the law allows, we give no warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, availability, and uninterrupted or error-free operation.

We do not promise that memories are correct or current, that stored content will never be lost, or that the service will meet your requirements or work with every agent or tool.

If you are a consumer, you keep the legal guarantees that the law of your country gives you and that cannot be excluded.

### Limits of liability

To the fullest extent the law allows, Memroot is not liable for indirect, incidental, special, consequential or punitive loss, or for lost profits, revenue, data or goodwill, or business interruption, even if we were told the loss was possible.

To the fullest extent the law allows, Memroot’s total liability for all claims connected with the service or these terms is limited to the greater of the fees you paid for Memroot in the 12 months before the event that gave rise to the claim, or US$100.

Nothing in these terms limits liability that cannot lawfully be limited, such as liability for fraud, intentional harm, gross negligence, or death or personal injury caused by negligence. Nothing in these terms limits your mandatory rights as a consumer.

### Indemnity

If you use Memroot for a business or another organization, you will defend Memroot against third-party claims that arise from your content or from your breach of these terms or the law, and cover the resulting losses and reasonable costs. This section does not apply to consumers.

### Governing law and disputes

If you have a dispute with us, contact support@memroot.dev first. We will each try in good faith to resolve it informally for 30 days before starting legal proceedings.

These terms are governed by the laws of Ukraine, and the courts of Ukraine have exclusive jurisdiction over disputes about them, except as stated below for consumers.

If you are a consumer, this choice does not take away the protection of the mandatory laws of the country where you live, and you may bring proceedings in the courts of that country.

Purchases processed by Creem are also subject to Creem’s Buyer Terms, which are governed by the laws of Estonia.

### Changes to these terms

We may update these terms as the service or the law changes. We post the new version on this page with a new date.

For a material change, we post a notice on the website or in the console at least 14 days before it takes effect, unless the change is needed sooner for legal or security reasons. Our own systems do not store your email address, so check this page or the console for notices.

If you keep using Memroot after a change takes effect, you accept the new terms. If you do not agree, stop using the service and cancel any subscription before the change takes effect.

### General

- Sanctions and export: you may not use Memroot if sanctions or export rules that apply to you or to us forbid it. You are responsible for following the export and sanctions laws that apply to you.
- Transfer: you may not transfer these terms without our consent. We may transfer them, with notice, to a successor that takes over the service.
- Severability and waiver: if part of these terms cannot be enforced, the rest still applies. If we do not enforce a term, we have not waived it.
- Whole agreement: these terms and the refund policy are the whole agreement between you and Memroot about the service.
- Events outside our control: we are not responsible for delay or failure caused by events outside our reasonable control, including provider or network outages, armed conflict and government action.
- Language: these terms are written in English. If they are translated, the English version controls.
- Copyright complaints: if you believe content on Memroot infringes your copyright, email support@memroot.dev with enough detail for us to find and assess it.
- Notices: send legal notices to support@memroot.dev. We give notices to you on the website or in the console.

## Refund policy

### Refunds within 14 days

If you ask within 14 days of a subscription charge, we refund that charge in full. This applies to your first payment and to each renewal payment. We may decline repeated or abusive requests where the law allows.

After 14 days we consider requests case by case, for example when a paid feature did not work and we could not fix it.

### When a subscription starts

Registration alone does not purchase a subscription. A paid subscription begins only after you complete checkout and payment is confirmed.

### Requesting a refund

Memroot purchases are processed by Creem, the merchant of record. To request a refund, email support@memroot.dev. We reply to refund requests within 3 business days and issue approved refunds through Creem.

Include the email address used for the purchase and the order ID from your receipt or from Creem’s customer portal. Do not send full card details.

If we do not resolve your request, you can contact Creem through its customer portal or at creem.io/contact. Creem may also issue a refund at its own discretion within 60 days of a purchase.

Creem pays approved refunds and notifies you by email. Card refunds usually arrive within 5 to 10 business days; the exact time depends on your payment provider.

### Rights that cannot be limited

Creem’s Buyer Terms also apply to payments it processes. Nothing on this page limits statutory withdrawal, refund or other mandatory consumer rights.

If you are a consumer in the European Union or the United Kingdom, the law may give you a 14-day right to withdraw from a purchase, and other rights if a service is faulty or not delivered. Creem’s Buyer Terms describe the right of withdrawal for consumers who live in the European Union, including when it does not apply. The 14-day refund on this page applies whether or not that right does. Contact us or Creem to use those rights.

### After a refund

A full refund or a chargeback ends paid access immediately, and the account moves to the Free plan limits. Your stored content is kept. Requests over the Free limits may be refused.

A refund does not always cancel the subscription. Cancel it as well if you do not want to be charged again.

### Cancellation and account data

Canceling stops future renewal charges at the end of your current billing period. A cancellation request and a refund request are separate.

Cancel on the Billing page of the console, or in Creem’s customer portal through the link in your Creem receipt email or at creem.io/my-orders/login. A cancellation made in Creem’s portal may end paid access immediately, as the terms of service explain. Account deletion is a separate request; see the privacy notice for retention and contact information.

### Before you dispute a charge

A Memroot charge appears on your statement with a descriptor that starts with “CREEM.IO*”, because Creem is the legal seller. If you do not recognize a charge or something went wrong, contact support@memroot.dev or Creem at creem.io/contact first. We can usually resolve it faster than a chargeback, and a chargeback ends paid access.

## Canonical links

- Website: https://memroot.dev/
- Product: https://memroot.dev/product
- How it works: https://memroot.dev/how-it-works
- Trust: https://memroot.dev/trust
- Pricing: https://memroot.dev/pricing
- Questions: https://memroot.dev/faq
- Terms: https://memroot.dev/terms
- Refunds: https://memroot.dev/refunds
- Privacy: https://memroot.dev/privacy
- Support: support@memroot.dev
- Privacy contact: privacy@memroot.dev
- Security reports: security@memroot.dev
- Register: https://console.memroot.dev/sign-up
- Sign in: https://console.memroot.dev/sign-in
- LLM index: https://memroot.dev/llms.txt
- Sitemap: https://memroot.dev/sitemap.xml