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:
| Stored | Encrypted |
| Tasks: the goal, the plan, step results, tool calls and what they returned, the final result | yes |
| Approvals and the task activity log | yes |
| 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 zone | yes |
| API keys, only if you chose to store them; otherwise they're kept in memory until Jade Cloud restarts | yes |
| Schedules and webhooks | yes; webhook secrets are stored only as hashes |
| Saved sign-ins for the browser (the password vault): name, site, username and password | yes, 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 MB | yes, 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 token | yes |
| 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:
- Who you are. An account is a random id. There's no name, email, phone number, or password. App Store subscribers are matched by a keyed hash of Apple's transaction id, so the id itself isn't stored.
- Your phone's data. Jade Cloud can't read your calendar, photos, contacts, or messages. Tasks in Jade Cloud only see what you send with the task and what the agent looks up.
- Pairing codes and device tokens in readable form: both are stored as hashes.
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
- To your model provider, with your key: what the agent sends while it works (the goal, the plan, page text it read, tool results). Pick providers you trust with that. Jade Cloud only talks to providers over https when a key is involved.
- To the included models' servers, with Jade Cloud's own keys, when you use a model that comes with the plan (Jade AI) or with a Jade Cloud of your own: the chat as you send it (or what a task sends it), passed through as it happens. Jade Cloud doesn't keep those chats, only how many tokens they used. Whoever runs a model's server can see them, as with any provider. For Jade AI, Auto, Fast and Expert run on a model server the developer of Jade runs; a level can instead come from another provider, under that provider's privacy terms. On Jade Cloud that's Ultra, when it's offered: it comes with Jade Max, and only after you agree to OpenRouter's privacy policy in the app. It's optional: everything else works without agreeing, and you can take the agreement back at any time (Settings → Jade AI). It comes through OpenRouter, which passes requests on to the company that makes the model. Jade Cloud never sends your account, device, or anything else about you with them.
- To the image server, with Jade Cloud's own key, when you use Jade AI Images (in the app, or in a task): the tool call as it's made (the description of the picture, and a picture to change, if any). Jade Cloud passes it through and keeps only how many pictures were made; a task keeps the pictures it made with its results, encrypted like everything else. On Jade Cloud, the image server is the developer's model server, which passes the request on to Krea, under Krea's privacy terms. Nothing about you or your account goes with it.
- From the help chat, during the app's setup: the questions go to the model server's help model, as they're asked, and aren't kept. There's no account then; the device is only known by its App Attest key (a public key Apple vouches for, and a counter), and the network address counts questions for the rate limit, in memory.
- To Apple, for pushes: fixed wording ("A task needs your OK. Open Jade to review it."), a random task id, the kind of event, and for approvals the approval's random id (so Deny works right from the notification). Never a title, a goal, or a result. The app fetches the details from Jade Cloud when it opens.
- To Apple, for Live Activities: when a task shows on your Lock Screen or in the Dynamic Island, Jade Cloud updates it by push with where the task is and nothing more: working, needs you, waiting, finished, couldn't finish or stopped, and how many of its steps are done ("Working on step 2 of 4"). The words come from those, never from the task. What the task is about stays on your phone: the app puts it there itself.
- To Apple, for a locked account: a silent push with no text and no ids, only "unlock", when work is waiting for your key (at most every 10 minutes).
- Through the relay (a Jade Cloud on a server of its own, with a license): the same thing, plus your device's push token. The relay forwards it to Apple and keeps nothing.
- To the web: pages and searches the agent looks up, from Jade Cloud's address, in a browser profile that's thrown away when the task ends. Nothing is signed in, unless the task fills in a sign-in you saved in the vault or you've let Jade Cloud keep your browser's cookies (they go only to the sites they belong to, as a browser sends them).
- From code workspaces: repositories the agent copies in (a private GitHub one with the GitHub token you gave Jade Cloud, sent to GitHub only), and what its commands download or send, like packages from PyPI or npm. A workspace is a folder on the server that only its task's commands can open; it's deleted when the task ends, and only files the agent saves with the results (a patch, a report) are kept, encrypted like everything else.
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
- Approvals. Anything that changes something asks first unless you've said otherwise, and anything that spends money or places an order always asks, whatever your rules say.
- Outside content is data, not instructions. Web pages, search results, MCP replies, and webhook bodies reach the model fenced off as untrusted. A task that has read outside content asks again before high-risk actions, even ones you've allowed before, and asks before sending anything that matches your private details (emails, phone numbers, locations from the task) to an outside service. An MCP tool counts as high risk unless it only reads, as its server says or as you've told Jade ("It only reads"). Your word doesn't count for a tool its server says can change or delete things, or one whose name suggests spending money.
- No reaching in. A task can't reach the server's own network: private and local addresses are refused after DNS and on every redirect, and the browser only gets out through a proxy that applies the same rule. In the Docker setup the browser also runs in its own container, with no data, no keys, and no network of its own, and so do code workspaces: each task's commands run as a user of their own there, and nothing they start keeps running after a command ends. Running a command asks first, unless you've allowed it.
- No getting around people. The agent never types into payment card fields, and into a password field only a sign-in you saved in the vault (on its own site, with your OK each time); it never downloads files, and stops at CAPTCHAs and "are you human" checks instead of trying to pass them.
- Budgets. Each task has limits on model calls, tool calls, tokens, and time.
- Jade AI's rules. Every request to Jade AI (chats, tasks that use it, the help chat) starts with rules that nothing in the conversation can change: no helping anyone hurt other people, and no harming computer systems (attacks, malware, breaking into systems that aren't yours). They don't try to enforce every law. Whoever runs a Jade Cloud can change them for theirs.
Your controls
- Export: everything Jade Cloud has for your account in one JSON file, except the values of stored keys.
- Lock with your devices' key: the master key alone no longer opens your data (see "How it's encrypted"). You can change the key or remove the lock.
- Delete: one action removes the account, its devices, tasks, files, schedules, keys, cookies, and its data key.
- Cookies: "Sign out of all sites" in the app sends an empty list, which replaces what Jade Cloud kept, and deleting the account removes them too.
- Keys in memory only: Jade Cloud forgets them when it restarts, and tasks wait until the app sends them again.
- Devices: see which devices are paired and unpair any of them.
What this doesn't protect against
Being plain about the limits:
- Whoever runs the server. A server-side agent has to read your tasks to work on them, so this isn't end-to-end encryption. The operator holds the master key and could, by changing Jade Cloud, read the data. Locking with your devices' key narrows that: the master key alone doesn't open a locked account, but while your key is in memory (your tasks are working, or you used Jade in the last 15 minutes) a Jade Cloud changed to look could read it. Encryption protects copies of the data (backups, disk snapshots, a stolen database) and keeps accounts apart; it isn't a promise the operator can't look. For Jade Cloud, that operator is the developer of Jade. If that's not acceptable, host it yourself (Host it yourself, in the app): then the operator is you.
- A compromised server while it runs. Keys are in memory while Jade Cloud works.
- Your model provider, the included models' servers (Jade AI's, and any provider a Jade AI level comes from), MCP servers, and websites see what's sent to them.
- Backups made before you deleted your account keep an encrypted copy until they're rotated out. The same goes for locking: a backup made before you locked the account opens with the master key alone until it's rotated out. Backups don't include the master key.