Clear security boundaries.

Memory is useful because it persists. Its access controls should be just as deliberate.

Authentication and permissions

Clerk verifies identity. MarkdownMem checks the workspace, store, and requested action before accessing content. Workspace invitations use the person's verified email; a workspace administrator does not automatically receive content access to every private store.

Encryption at rest

The engine encrypts memory content before storing it. The service holds the keys required to decrypt authorized requests. This is service-managed encryption, not end-to-end encryption, and paths and control-plane metadata are not described as encrypted content.

Isolation and change integrity

Tenant-scoped references and integrity checks protect the relationship between workspaces, agents, and memory. Writes use versions and idempotency keys to prevent silent overwrites and duplicate operations.

Data protection and recovery

Daily database snapshots are retained for six days. Separate encrypted recovery archives include the application keys required to read the data. Keep an independent copy of important notes. MarkdownMem is designed for agent context, not as a credential vault or a system of record for regulated data.

Open engine

You can inspect the storage and authorization foundation in the public engine repository. We do not claim certifications or audits that have not been completed.