Document version: 2026-09-04.2
This document explains the optional cloud AI processing that you consent to in Nemosine. It applies only when you select Luna (Cloud) or Grok (Cloud) and send a request. On-device AI is separate and sends nothing to Nemosine or a model provider.
1. What is sent
For each request, your device sends only the material assembled for that request. This may include:
- your prompt and relevant chat history
- note content or images that you chose to include
- available tool descriptions, tool calls, and tool results used to answer the request
- the selected model and generation settings
Free-form content may identify you or other people. Only send personal data that you are entitled to process and that you want the selected provider to handle.
2. Providers
The provider depends on the model you select:
- Luna (Cloud) uses OpenAI.
- Grok (Cloud) uses xAI (SpaceXAI LLC).
A request is sent only to the provider of the selected model. Nemosine uses a separate organisational API credential for each provider. We do not put your Nemosine user ID, email address, account details, or client IP address in the provider request.
This is pseudonymous processing, not guaranteed anonymity. The content itself may identify you.
3. Cache routing
Providers can temporarily reuse an unchanged prompt prefix to reduce processing time and cost.
For Grok, Nemosine may send an opaque per-conversation cache-routing value. Our server derives it with a keyed one-way function from your account and local conversation identifiers. xAI does not receive either underlying identifier and cannot use this value to link separate Nemosine conversations. It can recognise requests that carry the same derived value as belonging to the same conversation.
Nemosine currently sends no comparable explicit conversation cache key to OpenAI. OpenAI may still apply its automatic encrypted prompt cache.
Reasoning state
Grok generates internal reasoning and does not offer an off setting. Nemosine requests its lowest available reasoning effort. We use xAI's stateless Responses API with server-side storage disabled and ask xAI to return that reasoning as an opaque, xAI-encrypted item. Nemosine cannot read or display the encrypted reasoning.
Your device stores the encrypted item, the exact request context that preceded it, and related tool state with the completed assistant message. A later request to the same Grok model can send those items back so Grok retains its earlier reasoning context and the unchanged prefix can qualify for prompt caching. This can reduce repeated work and cost, but it does not guarantee a cache hit or prevent Grok from reasoning about a new question. New reasoning tokens are still charged as output tokens.
If cloud sync is enabled, this state is included inside the same end-to-end encrypted sync row as the chat message. Otherwise it remains in local app data. Deleting the chat deletes Nemosine's local copy through the normal chat-deletion and sync process. Switching models, clearing history, or losing the state can remove the reuse benefit.
Luna is requested with reasoning disabled because its current Chat Completions tool interface requires that setting. Nemosine does not receive reusable Luna reasoning state.
4. Provider retention and training
Nemosine does not opt in to provider model training with your cloud AI content.
- xAI: Nemosine enables Grok only through an xAI team with Zero Data Retention (ZDR). Under ZDR, request inputs and model outputs are not persisted to disk by xAI. Nemosine also verifies xAI's ZDR response header. Temporary in-memory processing and prompt caching may still occur while serving requests, and xAI may process operational metadata under its terms.
- OpenAI: Nemosine requests that API responses are not stored as application state. OpenAI may nevertheless retain customer content in abuse-monitoring logs for up to 30 days unless Nemosine's OpenAI organisation is separately approved and configured for ZDR. OpenAI may also hold encrypted prompt-cache state temporarily on its GPU infrastructure.
Nemosine does not use provider-hosted conversation history, files, collections, or batch processing for this feature. Grok conversation state is client-managed as described above rather than stored by xAI.
5. What Nemosine stores
Our server function relays each request and does not store or log the prompt, included note content, image, tool result, or model reply. We store a usage and billing record containing token counts, selected model, timing, status, and calculated cost. Those records are retained for 24 months and then aggregated into statistics that do not identify you.
Your copy of the chat remains in Nemosine's local app data and follows the sync choices you make separately. For Grok, that local copy also contains the exact request context used for replay and xAI-encrypted reasoning/tool state. Synced copies are end-to-end encrypted before upload.
6. Consent and withdrawal
Cloud AI content processing is based on your explicit consent under GDPR Article 6(1)(a). Consent is optional. Refusing or withdrawing it does not affect on-device AI or your locally stored notes.
You can withdraw consent in Nemosine's settings. Withdrawal prevents future cloud AI requests but does not undo processing that already occurred or remove billing records that Nemosine must retain for the stated period.
See the Privacy Policy, GDPR information, and Terms of Service for the rest of Nemosine's data handling and your rights.