Privacy: what stays on your computer and what the server sees

No trackers on this site

These pages load only files hosted with them. They contain no scripts, analytics, cookies, tracking pixels, forms, frames or external asset loads.

What stays on your computer

At launch, Oak will keep its state in ~/.oak/. The directory will be readable only by your operating-system user (mode 0700, files 0600), and symlinks and hardlinks are rejected.

Where	What it holds
`~/.oak/wallet.enc`	Your wallet's private key, encrypted with AES-256-GCM.
Your system keychain, or a passphrase	The key that opens the wallet. Stored in macOS Keychain, Windows Credential Manager or the Linux Secret Service, or derived in memory from your passphrase with scrypt.
`~/.oak/config.json`	The endpoints and addresses you configured.
`~/.oak/<address>.pending.json` and `.cleared.json`	A journal of transactions in flight, used to recover if a process stops.
`~/.oak/recipes/`	Recipes you chose to import.

These never leave your computer: your 24 recovery words, your private key and your passphrase. The add-on and the server both reject any tool argument that contains one.

What the Oak server sees

At launch, the server will receive:

Your wallet address and a short-lived session signature, valid for up to 15 minutes. The server checks it in memory and never logs it.
The name of the tool and its arguments, such as an asset address and an amount you asked to quote.
The connecting IP address on some open requests, used only to rate-limit them. Counters live in memory for 60 seconds.

The server never sees your private key and never signs or sends a transaction. It has no user account database, no email list and no telemetry.

What network nodes (RPCs) and project services see

The network node (RPC endpoint) you configure can see the IP address making requests, the wallet address queried and any signed transaction you broadcast. Once a transaction is on Robinhood Chain, its sender, data and events are public and permanent.

Some modules use a project's own web service. At launch, the Oak server will send that service the details it needs: asset addresses, amounts, the chain ID and, where the action needs it, your wallet address. The list of services for each module publishes with the docs at launch.

How long data is kept

On your computer: until you delete ~/.oak/. Back up your recovery words or run oak export first, because Oak cannot recover a lost key.
On the server: session signatures are checked in memory and never written to disk. Rate-limit counters last 60 seconds. The state of a multi-step quote lives in memory only while it is active.
On the blockchain: transactions, balances, .hood names and on-chain agent identities are public ledger records that Oak cannot delete.

Questions

For privacy or documentation questions, contact @OakAgentKit on X. Do not post vulnerabilities in public. See how to report a vulnerability.