Security
Your own key, under your own flag.
Every memory is encrypted with a key belonging to you alone, stored in Sweden, and destroyable on demand. Here is exactly how that works.
01 Encryption
A separate key for every tenant.
Each person and each workspace has its own data-encryption key, itself wrapped by a master key that never appears in our code, our images, or our environment variables.
Encrypted per tenant
Memories are encrypted with AES-256-GCM under a key belonging to that person or workspace alone. A flaw in one tenant's scope cannot expose another's.
Erasure that is permanent
Deleting a tenant destroys its key. The ciphertext that remains — including in older backups — is mathematically unrecoverable. Not a flag in a database.
Private database
Postgres is never published to the internet. It is reachable only from the application over a private network, on a host with default-deny outbound traffic.
We can technically read your memories
We run the service, so we hold the master key that wraps yours. This is not zero-knowledge encryption — and any vendor claiming it is, while also running search and AI over your content, is overstating it. What we offer instead is narrower and true: separate keys per tenant, nothing leaving Sweden, and erasure you can verify. Customer-managed keys are on the roadmap for exactly this reason.
02 Where it runs
Sweden for everything that touches your content.
Storage and compute
A dedicated instance at Cleura in Karlskrona, Sweden. EU-owned, EU-operated, outside the reach of the CLOUD Act.
AI models
Embeddings, reranking and synthesis run on Berget in Sweden. Your memories are never sent to a US model provider. US models are opt-in per tenant, never the default.
Infrastructure as code
The entire host is defined in OpenTofu and reproducible from source — which is also how a dedicated single-tenant instance becomes one command rather than a project.
Two services outside Sweden, neither holding your memories
Sign-in is handled by WorkOS (US), which sees your email address and issues the token that authenticates you — never your memories. This marketing site runs on Vercel (US) and stores nothing. Everything that touches memory content stays in Sweden, and we will name any future sub-processor here before it goes live.
03 Your rights
Export
Take your memories out in an open format whenever you want. No ticket, no sales call.
Erase
Remove a single memory, or destroy your entire Flow by shredding its key. Forgetting a memory also retracts the facts derived from it.
Tamper-evident audit
Security-relevant events are written to a hash-chained log, kept per tenant, so a retrospective edit is detectable.
Running a security review? We will send you the full picture, gaps included.