Security

Built for data that has to stay put.

Awareness is a memory database, so the security boundary is the customer's data, not just the login screen.

Encrypted transport

HTTPS with HSTS, secure cookies, strict frame policies and a restricted CORS origin. Admin endpoints require a separate token.

Tenant isolation

Each paid database box runs its own application and database stack. Tenant database passwords are unique and generated per box; secrets are never shared between tenants.

Key-only server access

Tenant SSH accepts public keys only. Password authentication and root password login are disabled. Customer keys are added after sign-in and can be revoked from the Access page.

Verifiable memory history

Supported memory transitions can be anchored as hash-chained audit records, so a later reader can verify ordering and detect a rewritten history.

Least-privilege MCP

MCP tools are token-scoped. The control plane issues and rotates tenant tokens; MCP and CLI access does not depend on a web session.

Operational controls

Daily billing reconciliation, provisioning failure notifications, backup status checks and rate limiting are monitored separately from customer-facing traffic.

Reporting a vulnerability

Email e@awareness.market with a reproduction and affected URL. Please do not include customer data in a report; use a synthetic example. We will coordinate disclosure before publication.

Machine-readable disclosure policy: security.txt.