Your data, close to you
Chats, attachments and optional memory are stored in the browser you use. They are not a cloud backup. Clearing site data, changing browsers or losing access to the device can remove them. Browser storage is not encrypted by Noema by default.
Where your request runs
A supported browser model processes locally after downloading its files. Your Machine connects to a local model server you configure. Cloud models process requests remotely. Optional web search and other external tools can send data online, even when a model runs locally.
What ZKR changes
ZKR masks detected sensitive values before supported requests and restores matching values in replies. Supported files use a protected copy that you review. Detection and text recognition can miss details. ZKR does not provide a guarantee of anonymity or replace your review.
Private cloud, clear controls
Noema Router Auto uses zero-retention routes. Enable ZKR to mask detected sensitive details and review supported files before they are sent. You do not need separate provider accounts or API keys. Direct model selections can have different retention policies, shown in their labels. Zero retention concerns prompt and reply storage; it does not mean a cloud request stays on your device or conceals all network and billing metadata.
Start without a personal identity
No name, email or personal signup is needed to enter the workspace. Local AI does not require a wallet. Cloud credits use a wallet-linked account. This reduces the personal information needed to get started, but is not a promise that all activity is untraceable.
Local AI, including on mobile
Open Noema on a computer, iPhone, iPad or Android device without installing an app. Compatible phones and tablets can run a browser model on the device itself. Model support depends on the browser’s graphics features and available memory. Cloud AI with ZKR remains a choice when local resources are limited.
Credits and wallet activity
Cloud credits use wallet-linked accounts and usage records. Billing metadata is separate from conversation content. Public blockchain transfers can connect a wallet with a payment. Using a wallet does not make payments anonymous.
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.
Your controls
Choose your route, use ZKR for supported content, review protected files and manage memory and saved conversations. Clearing local records does not erase public blockchain transactions or records held by external services.
Future network protections
Confidential GPU execution, hardware evidence and onion routing are planned. They are not currently applied to ordinary Noema cloud requests. See the roadmap for their place in the broader product.
For practical steps, read the data and controls guide.