Trust & security

Useful memory needs
clear boundaries.

Memora’s local-first engineering foundation is built around inspectable knowledge, reviewed changes, and explicit runtime authority.

Knowledge you can read

Canonical project knowledge is stored as provider-neutral Markdown. Project knowledge can be shared separately from machine-local indexes, caches, and runtime state.

Evidence before updates

Captured observations and feedback are candidate evidence. Accuracy produces proposed changes; promoting those proposals requires the applicable review and governed publication steps.

Authority outside memory

Trusted runtime policy controls project scope and capabilities. Editable memory and model output do not grant permission to read, change, or send information.

Changes with context

The memory lifecycle keeps provenance and version lineage so reviewed changes can be inspected. Version history and governed rollback support understanding and correcting knowledge as a project evolves. Available history depends on the records retained or imported into the local project.

Local-first does not mean every workflow stays local

The current runtime operates within authorized local project scopes. Optional model features can process authorized content through configured providers, subject to runtime configuration and destination policy. Teams should review their configuration and the relevant provider’s terms before enabling that processing.

Connecting an AI host or provider also introduces that service’s own data handling. This website does not upload your local project memory simply because you visit it.

Current scope

Memora is early stage. Enterprise shared memory is a future direction, not a current hosted multi-tenant service. We do not claim security certifications, independent audits, or a guarantee that any system is free of vulnerabilities.

Report a security concern

Email a concise description and non-sensitive reproduction steps. Do not send passwords, API keys, private project memory, or personal records.

[email protected]

For website data handling, read our privacy notice.