Privacy on Jade Cloud

Jade Cloud is the server side of Jade: it works on your tasks while your phone is locked, so it has to hold what those tasks need. This page says exactly what that is, how it's protected, and what the protection doesn't cover. It applies to the Jade Cloud that comes with Jade Pro and Jade Max, and to a Jade Cloud people run on a server of their own (Host it yourself, in the app) alike; the difference is who runs the server.

What Jade Cloud stores

For each account:

StoredEncrypted
Tasks: the goal, the plan, step results, tool calls and what they returned, the final resultyes
Approvals and the task activity logyes
Files the agent saved (up to 200 MB)yes, and their paths are stored as keyed hashes
Settings: model providers (addresses and model names), search, rules for tools, time zoneyes
API keys, only if you chose to store them; otherwise they're kept in memory until Jade Cloud restartsyes
Schedules and webhooksyes; webhook secrets are stored only as hashes
Saved sign-ins for the browser (the password vault): name, site, username and passwordyes, each one sealed whole. A model never sees a password: it types a placeholder, and the browser fills in the real one only on an https page of the saved site, after your OK each time, then masks it in what the model reads back. Exports list sign-ins without passwords
The browser's cookies, only if you keep cookies in the app and leave "Signed in in Jade Cloud" on: the sign-ins your phone's browser has (name, value, site, path, expiry, and the secure, HTTP-only and same-site marks), up to 3,000 cookies or 1 MByes, as one sealed list. They're credentials: they're never logged, never in an export, and deleted with the account. They're put into a task's browser before its first page, so the task is signed in where you are, and what the browser ends with (a new sign-in, or a site signing you out) is kept and handed back to the app. Signing out of all sites in the app empties the list, and a cookie that was deleted stays as an expired one for a week, only so your devices hear about it
Devices: name, platform, push tokenyes
Usage counts per day (tasks, task time, model calls, tokens, and tokens of each included model), which also measure a plan's limits, and an audit log of account events (paired, exported, decided)the details are; the counts and event names aren't

What isn't encrypted is what Jade Cloud needs to find and schedule things: ids, timestamps, task states, change numbers, file sizes, and when a task should wake up.

What it never has:

How it's encrypted

Each account has its own random 256-bit data key. Every record is sealed with AES-256-GCM under that key, and bound to where it lives (a task's record can't be swapped in for another task's, or moved to another account). The data keys are themselves sealed under Jade Cloud's master key, which lives in a file or a Docker secret, not in the database.

Locked with your devices' key. The app can also lock your account with a 256-bit key it makes and keeps in your iCloud Keychain. Then your data key is sealed under that key as well as the master key, so the master key and the database together (a backup, a copied disk, a stolen server) no longer open your data. Jade Cloud can read it only after one of your devices sends the key. It keeps the key in memory, never on disk, while your tasks work and for 15 minutes after it was last used. While it's locked, Jade Cloud can still send your notifications, and it holds what arrives for you: a webhook call is sealed to your account's public key (only your account's private key, itself under your data key, opens it), and a due schedule waits. The app is woken to send the key, and they run then. If every copy of the key is lost, the data can't be recovered by anyone, including the operator; the account can only be deleted and started again.

Deleting an account deletes its data key along with its rows, and the database is set to overwrite deleted content and checkpoint its journal right away.

What leaves Jade Cloud

Live updates to the app (/v1/events) carry only a change number. Logs carry ids and event names, never content. The included Caddy setup keeps no access log, and neither does the nginx configuration the setup script writes for Jade Cloud's paths, unless you turn it on (request paths can hold webhook secrets).

What protects you from the agent itself

Your controls

What this doesn't protect against

Being plain about the limits: