memoize.

effective August 31, 2026

Terms of service.

By using the hosted Memoize service, API, MCP server, CLI, or plugins, you agree to these terms.

Your responsibility

You are responsible for what you store, for keeping brain tokens secret, for reviewing agent actions, and for ensuring you have the right to process submitted content. Do not use Memoize for unlawful activity, abuse, service disruption, or content whose loss or disclosure could cause serious harm. Memoize does not accept payment-card data, protected health information, government identifiers. Credentials may be stored as memory at your request; detected credentials are classified as secret during consolidation. Automated rejection is a guardrail and does not transfer responsibility for submitted content.

Token ownership

Memoize has no account recovery. Possession of an owner token grants control of that brain. Connection tokens grant memory access until the owner revokes them, but cannot rotate ownership or change security settings. Treat both as secrets; keep the owner token like a password and revoke delegated access you no longer recognize or need.

Service limits and changes

Rate, size, storage, and working-memory limits may be enforced. Features, models, limits, endpoints, and availability may change as the service evolves. We may restrict abusive traffic or suspend a brain to protect the service and its users.

No warranty

The service is provided as available, without warranties of uninterrupted operation, permanent retention, fitness for a particular purpose, or error-free model output. Agents can recall incomplete or incorrect information; verify important decisions independently.

Liability

To the extent permitted by law, Memoize's operator is not liable for indirect, incidental, special, consequential, or punitive damages, or for lost data, profits, or opportunities resulting from use of the service.

Termination and deletion

You may stop using Memoize at any time and permanently delete a brain through the authenticated deletion endpoint described in the privacy policy. Access may be terminated for material abuse of these terms.

Changes

Material changes will be reflected by updating the effective date on this page. Continued use after a change means acceptance of the revised terms.