How Enclave Uses Your Data
You can use Enclave with a model that runs on your device or choose an optional cloud model. The destination of a chat request depends on that choice.
Local models
Your prompts, attachments, and conversation are processed on your device when you use a local model. They are not sent to Enclave, OpenRouter, or an AI model provider to generate the reply. The app may still send the usage and diagnostic data described below.
Cloud models
When you send a message to a cloud model, the request goes from your device to Enclave's servers, then to OpenRouter, then to the provider serving the selected model. The response returns through the same services. We use the request to generate your reply and account for subscription credits.
A cloud request can contain:
- Your message and relevant earlier messages in the conversation
- Instructions from an assistant you have configured
- Text extracted on your device from files you attach
- Speech transcribed on your device when you use voice features
- Results from tools you enable for the conversation
Enclave stores your conversation history on your device and does not keep a server-side copy of that history. Our servers keep subscription and credit records, and record request metadata such as the model used and token usage. OpenRouter and the serving provider process the request under their own policies; logging and retention can vary by provider.
Who receives a cloud request?
- Enclave AI: Routes the request and manages subscription credits.
- OpenRouter: Routes the request to a model provider. See OpenRouter's privacy policy.
- Model provider: Runs the selected model. The serving provider can vary by model and routing. OpenRouter's provider directory lists current providers, their retention information, and links to their privacy policies.
The company named in a model's title may be its developer rather than the company operating the server that handles your request. If you do not want your chat content to leave your device for AI processing, choose a local model.
Other app data
Firebase Analytics receives app usage events, such as screen views, taps, and model selections. Firebase Crashlytics receives crash reports and device diagnostics. We do not intentionally include conversation content in analytics events. If you subscribe, Enclave receives an Apple transaction identifier and stores your subscription status and credit balance; Apple handles payment card details.
For retention, your rights, and contact information, read the full Privacy Policy.