Security built around tenant boundaries

Organization and project isolation

Every synchronized memory is associated with an organization and project. Authorization is established transactionally, row-level security is forced on tenant tables, and cross-tenant access is denied.

Authentication and credentials

Browser sessions use hardened cookies. CLI login uses expiring, single-use browser codes whose digests—not raw values—are stored. Generated keys are project-scoped and never receive platform-administrator authority.

Resilient synchronization

Local writes enter a durable outbox before network transfer. Server notifications contain project change signals rather than memory bodies, and clients fetch authorized deltas only when a version advances.

Responsible disclosure

Please report suspected vulnerabilities privately through the support channel. Do not access other users’ data or interrupt production services while investigating.