Security

Write to nikhil@memorable.sh with enough detail to reproduce it. You will get a human reply. Please give us a reasonable window to fix an issue before publishing it, and do not access or alter data that is not yours while demonstrating one.

We will not pursue anyone acting in good faith under those conditions.

On the coding path, session content leaves through two endpoints and no others. Everything else carries account plumbing, a hostname, a handful of integers, a vendor key a customer chooses to store.

Trace arguments are filtered on your machine against a fixed allow-list of fields before the request is built: command, file path, path, notebook path, pattern, url, query, description, shell id, bash id. Nothing outside that list is sent, and credential-shaped strings are redacted before it is.

Quotas are enforced in application code rather than by an edge binding, because that is where they can be tested. Key issuance is throttled per IP address; requests are throttled per key.

The parse is deterministic and model-free, so no step of a procedure is written by a model and no step's shape depends on prose in a trace. The title and the judge are the two model calls, and neither writes a step.

We do not hold SOC 2 or ISO 27001 today, and the dashboard marks SSO, SCIM and audit export as not built rather than implying them.

What a third-party embedding vendor does with a line of text, where a workspace has chosen one, is that vendor's business and not something this page can promise.