Privacy and security
Where data lives, who can read it, and the controls available.
On this page
This page explains how Jade handles data in plain terms. The legal text is the privacy notes.
Where data lives
- On the device
- Chats, memories, settings, files and tasks that run on the phone live in the app. API keys and saved passwords are in the Keychain. Nothing is sent to Jade’s servers unless a feature needs it.
- To the model
- A message goes to the model provider chosen in Settings (OpenAI, Anthropic, a local server, or Jade AI). That provider’s own policy applies to what it receives. On-device models send nothing anywhere.
- In Jade Cloud
- Only what a task needs, and only when tasks run there. See below.
- In iCloud
- If sync is on (Settings → Privacy & safety), chats and device tasks sync through the user’s own iCloud account (CloudKit). Jade has no copy. Some things never sync: API keys, saved passwords and device-only settings.
What Jade Cloud holds
Jade Cloud is a server run by Jade (the hosted one) or by the user (a self-hosted one). It holds an account’s tasks, files, settings, schedules and the secrets sent for them, and nothing about who the person is: an account is a random id with no name, email or password.
- Sealed per account. Each account’s data is encrypted with AES-256-GCM under a data key of its own. The data keys are wrapped by one master key that lives on the server, outside the database and outside the backups. A copy of the database alone shows nothing readable, and each stored value is bound to its account and slot, so values can’t be swapped between accounts.
- Keys. API keys the app sends for tasks are stored sealed, or kept in memory only if the app asks. They are never in an export, in a log, or in an error message (key-shaped text is stripped).
- Notifications carry no content. A push says that something happened, and the app fetches the details.
- Logs record events, not content: no prompts, no results, no page text.
- Deleting. Deleting an account (
DELETE /v1/me, or from the server) removes everything it holds. Tasks and files can be deleted one at a time. Backups on a self-hosted server age out on their own schedule.
Locking an account
By default, the server can open an account’s data when a task needs it, because the master key is on the server. Locking goes further: the app makes a key, keeps it in the iCloud Keychain, and the data is sealed under it. After that, the server can’t read the account’s data on its own. A device sends the key with its requests, and the server keeps it in memory only while tasks work.
- While locked and without a device’s key, the account’s data is unreadable and answers are
423. Schedules and webhook calls are held until a device unlocks. - A device that has the key unlocks it for later work when the server asks by push.
- The trade-off is real: lose every device that has the key and the iCloud Keychain copy, and the data can’t be recovered. Nobody, including the server’s operator, can open it.
What is shared with Jade Cloud
Routines and webhook runs start without a phone to ask, so the app can share two things on purpose: memories and a rough location. Each is a switch under Settings. The app sends only what is switched on and clears the rest. They are stored sealed, are used as background for tasks that start without a phone, and are removed when sharing stops. Tasks started from the app carry their own context instead.
Passwords and sign-ins
- The model never sees a password. It writes a stand-in, and the real value is typed only on the site the sign-in belongs to, over https.
- Saved sign-ins need Face ID or the passcode to use on the phone. They reach Jade Cloud only if turned on for that sign-in. On the server they are sealed and never exported.
- The browser’s cookies can be sent so a task is already signed in. They are sealed, never logged, and not in an export.
Outside content is not trusted
A web page, a search result, a file, an MCP tool’s answer or a webhook body can try to give the model orders. Jade treats all of it as data: it is quoted and labelled when it enters the model’s context, never placed in the instructions. A task that has read outside content asks again before a risky tool, even one the user allowed for good. Things that cost something (spending, sending, deleting, running code, typing on websites) always ask.
How Jade Cloud is kept apart
- The agent and the browser run as system accounts with no shell, no password and no sudo, in containers with read-only filesystems and no Linux capabilities.
- The browser and the code workspaces have no route to the internet except through a filtering proxy that refuses private addresses, so a page or a command can’t reach the server’s own network.
- Each code workspace runs as a user of its own, and is thrown away when its task ends.
- The runner listens on the local address only. A web server in front (nginx or Caddy) is the one door.
Control over the data
- Export
- Settings → Privacy & safety → Import & export, or
GET /v1/export: everything an account holds as one JSON file. Keys and passwords are never in it. - Audit log
GET /v1/auditlists security events on the account: pairing, unlocking, exports, approval answers, setting changes.- Devices
- Settings → Tasks → Devices lists paired devices and signs one out.
jade unpairdoes the same on a server. - Delete
DELETE /v1/medeletes the account and everything in it.jade delete-accountdoes it from the server.- Assistant changes
- When the assistant changes a setting, it asks first, lists what changes, and keeps an undo under Changes Jade made.