Security
M.N.E.M.O. — short for Multidimensional Neural Elastic Memory Organization — is built for data teams can't afford to get wrong — customer records, case files, regulated business data. Security isn't a layer bolted on afterward; it's enforced at the same structural level as retrieval itself.
Tenant isolation
Each tenant's memory lives in its own independently-indexed structure. There is no query path that reaches across tenants by default.
Any cross-tenant sharing is opt-in and explicit — granted at the level of a named subject, never automatic, and revocable at any time.
Why it matters
Access control
Visibility rules are applied at the data layer itself, not as a filter applied at query time that someone could forget to add to a new endpoint. Restricting a role's access to a piece of memory is non-destructive and reversible — the underlying record isn't deleted, so access changes are auditable and don't risk data loss.
Authentication
Tokens are stored hashed, never in plaintext. Bring-your-own LLM provider keys are write-only — accepted once at setup, never returned by any subsequent API call.
Encryption
Tenant memory data is encrypted at rest with AES-256-GCM, using envelope encryption backed by AWS Key Management Service — each value gets its own encryption key, and only AWS KMS can unwrap it. This is baseline for every tenant, on every plan, not a feature reserved for a higher tier. Payment handling follows PCI DSS practice: card verification codes are never stored.
Shared memory
Publishing or granting access to memory is always something a user does on purpose. Borrowed memory is always read-only to the party that receives it. Nothing is automatically visible — even data marked public requires an explicit subscription before it can be queried.
Enterprise API access
Talk with Panaxon AI about enterprise API access to M.N.E.M.O.If you are building agents or pipelines over sensitive or regulated data, Panaxon AI can discuss fit, architecture, and access.
