Keys and privacy

Privacy: what leaves your machine

Your memories always stay on your machine. What else leaves it depends on which mode you use.

By mode

Mode	What leaves your machine	Who sees it
No keys	Nothing. Recall matches on words only, and new memories are not saved.	No one.
Your own keys	The text a model needs to save or recall a memory.	Voyage AI, TypeSafe and Anthropic, under your accounts. Nothing reaches us.
Oort Pro	The same text, through relay.oortcloud.dev.	The same providers. Our relay passes requests on and stores none of their content.

What each provider gets

Provider	Gets	When
TypeSafe	The text Oort is about to save.	To decide whether and how to keep it.
Anthropic	The same text.	So Claude Haiku can write the short memory.
Voyage AI	The memory text. On recall, your search text and the candidate memories.	To turn text into vectors, and to rank results.

Secrets are scrubbed before a turn is saved. A turn that is only a secret is skipped. To see what the scrubber would remove, without saving anything:

Terminal

$ oort observe --dry-run --user "my key is ..." --assistant "ok"

Oort Pro

The relay swaps your Oort key for ours and forwards the request. It does not store or log what you send or what comes back.
It keeps only monthly counts of saves and recalls, and when each key was last used.
Your account and billing live with Clerk and Stripe. The privacy notice lists every subprocessor.

Importing past sessions

oort import claude-code sends past turns through the same path as new ones. It prints an estimate first and asks before it starts.

Your memories, your control

Terminal

# every memory, as JSON Lines
$ oort export --out memories.jsonl
# delete one memory everywhere
$ oort forget <id>
# delete every memory
$ rm -r ~/.oort

Hosted memory in Oort Cloud is Planned. Nothing on this page sends memories to us.