Terms of service

These terms apply when you create a Memorable workspace, issue an API key, or send a request to the extraction API. If you are agreeing on behalf of a company, you are confirming you may bind it.

An enterprise engagement may be governed by a separate signed agreement. Where the two disagree, the signed agreement wins.

Memorable turns a finished agent session into a procedure. The parse is deterministic and model-free: the same trace produces the same steps, in the same order. Two small models run beside it, one to write the title and one to score whether a workflow is kept, and neither can rename, reorder or edit a step. Procedures from the coding path are written to your own store, and a copy of the title, the steps and the conditions is kept on ours so the dashboard can render them.

The dashboard, the CLI and the extraction API are the service. Anything described as not built is not part of it, and the dashboard marks those plainly rather than implying them.

You are responsible for the keys issued from your workspace and for what is done with them. A key is shown once, at creation; we hold only its hash and cannot recover it for you. Rotate or revoke from the dashboard.

Roles control who can change what. Owners and admins can see the audit log; a member cannot, and a count of nothing there may mean the role rather than the absence of events.

Do not use the service to break the law, to reach systems you are not authorised to reach, or to send content you have no right to send. Do not attempt to extract another workspace's data, defeat quotas, or resell the service as your own.

Quotas are enforced in code and per key. Sustained attempts to route around them are grounds for suspending a key.

Procedures are yours. We claim no ownership of what you send or of what extraction returns, and no licence beyond what running the service requires, receiving a request, answering it, and metering it.

We do not train models on your traces.

Plans are metered by counted sessions per billing period. Re-sending a session already counted within 48 hours does not count twice.

Past the allowance the extraction API refuses. The response still carries the draft, marked refused, and nothing is stored on either side. Nothing already stored is deleted or withheld because a period ran over, and capture resumes when the period resets or the plan changes.

Billing runs through Stripe, and the billing portal is the record for invoices, cards and cancellation. Fees already charged are not refunded on cancellation except where the law requires it.

The service is provided as it is. We do not promise it will be uninterrupted or that a given request will succeed, and no uptime commitment exists outside a signed enterprise agreement.

To the extent the law allows, we are not liable for indirect or consequential loss, and our total liability is limited to the fees you paid in the twelve months before the claim.

You can stop at any time: revoke your keys and delete the workspace. Deleting a workspace deletes its rows and everything that depends on them.

We may suspend a workspace that is breaking these terms or putting the service at risk, and will say why.

We may update these terms. Material changes will be dated here before they take effect, and continuing to use the service after that is acceptance.