Encryption
Memories. The title, summary and body of a memory are encrypted with AES-256-GCM before they're stored, under a key issued for the space they're in. Your personal space has its own key, and so does each shared space. A small number of older memories, saved before this encryption was introduced, are still being moved over; until then they're protected by our cloud provider's storage-level encryption.
Documents are encrypted with AES-256-GCM under a key issued for you, and decrypted only when they're read: by you, by a member you shared them with, or by our pipeline turning them into memories.
Those keys are themselves encrypted by a master key held in Azure Key Vault, which never leaves it. Keys can be rotated without re-encrypting your history.
Everything travels over TLS 1.2 or higher.
Where
JustOnce runs on Microsoft Azure in Australia under the Australian Privacy Act. The memory engine sits on a private network with no public address. The AI providers that process your content (see Is my data used to train AI?) may do so outside Australia.
Who can see what
Membership of a space decides who can read what's in it, and that's checked on every request. Encryption at rest protects your data from anyone who gets hold of the storage. It is not zero-knowledge: our processing pipeline reads your real content to classify it, extract entities and answer recall — that's the product. Internal access is role-restricted and written to an append-only audit log. What we don't do: sell your data, share your memories or documents with advertisers, or use them to train models. Full detail on justonce.ai/security and the Privacy Policy.
In ChatGPT and Codex, JustOnce holds back memories filed under credentials, identity, health or finance, memories that hold a password, card or ID number, and memories it hasn't confidently filed yet. It also won't save a password, PIN, card, bank or ID number typed there. You can still see and add all of these in the app. Other assistants see your whole vault.