Your privacy, built into the choices.
Start without a name, email or personal signup. Run AI on your own hardware, keep conversations in your browser, and use protected cloud access when you need it. ZKR and zero-retention Auto routing bring useful privacy controls to cloud AI, including on mobile.
Complete privacy and greater anonymity across the experience are the direction. The protections available today have a clear scope: local execution, outgoing content, retention and payment metadata are separate concerns.
| Control | What it does | What to keep in mind |
|---|---|---|
| Local AI | Runs a supported model in the browser or through your own server | Downloads and optional online tools can use the network |
| ZKR | Masks detected sensitive values in supported requests | Detection and recognition can miss details |
| File review | Lets you inspect and correct protected text before sending | It does not preserve every part of the original document or picture |
| Local storage | Keeps chats, files and optional memory in this browser | It is not encrypted by Noema by default and is not a cloud backup |
| Private cloud | Auto uses zero-retention routes; ZKR masks detected sensitive content when enabled | Cloud processing goes online; direct models may have different retention labels |
| No personal signup | Start without giving a name or email | Paid use is wallet-linked; this does not conceal all network or payment metadata |
| Credits | Make cloud costs and usage visible | Wallet billing and blockchain activity are not anonymous |
Local AI on your phone
On compatible phones and tablets, Your Browser runs the model on the device itself. No desktop helper is needed. Support depends on browser graphics features and available memory. Check mobile requirements.
Decide before sharing
Choose a suitable route and check which tools are enabled. If you attach a file, review the protected copy or understand that an unprotected original may be sent to a compatible cloud model.
In Settings → Chat → Execution privacy, choose a boundary for new AI requests:
| Policy | Allowed requests |
|---|---|
| Follow my selections | Your existing route, model, ZKR and tool choices |
| On-device only | AI in this browser |
| My hardware only | This browser or the server you connected |
| Zero-retention cloud | Local routes and zero-retention cloud chat |
Web search and cloud image, video and audio creation require Follow my selections. An incompatible request stops instead of falling back to a weaker policy. These policies do not automatically turn ZKR on or change the selected model.
The setting stays in this browser and applies across its Noema tabs. Changing it stops active requests where possible; already submitted cloud work may still complete and be charged. Existing video jobs can still be checked and downloaded. A connected server may be on another network, and its storage is controlled by its operator. Model downloads, wallet connections and links you open are separate from the AI request policy.
Manage saved data
Use the workspace’s data and memory controls to remove records you no longer need. Clearing local history does not remove external records of requests already made, wallet billing or public blockchain transfers.
Media and temporary work
Images, video and audio tools process the submitted prompt and files in the cloud under the selected model’s retention policy. Downloaded results and normal creation history stay in this browser. Temporary chats and creations keep work in the tab rather than persistent history; their processing and billing still follow the selected route.
ZKR can substitute detected text. It does not universally anonymise images or voices, and generated media keeps those substitutions rather than restoring the originals. Create and keep media.
Public page statistics
Some public pages use aggregate visit counts to understand which guides are useful. These counters do not contain chat text, visitor identifiers or stored IP addresses. Hosting and network services still process connection metadata.
Current receipts
Receipts describe what the app reports for an attempt. They are not independent hardware evidence. The confidential Network and onion routing are planned.