Effective date: May 20, 2026
Privacy policies exist because lawyers say they have to, and most of them are written to protect the company, not to inform you. We wanted to do ours differently — start with what we actually stand for, and let the legal language follow from that.
Here's our position in plain English:
The full policy below is the legal version of these same facts. If something ever contradicts this plain-English summary, the summary reflects our intent and we want to hear about it: [email protected]
Central-Intel LLC ("we," "us," or "our") operates the Central-Intel desktop application (available for macOS, Windows, and Linux), the Central-Intel mobile application (available on iOS and Android), and the associated web service at central-intel.ai. We provide a multi-provider AI assistant platform that lets you connect your own AI API keys, run local AI models, build personal knowledge bases, and run automated AI workflows.
For questions about this policy, contact us at [email protected].
Account information
When you sign in using a social login provider (Google, GitHub, or others supported by our authentication system), we receive your email address from that provider. This is the only piece of personally identifiable information stored on our servers. We do not receive your name, profile picture, or any other profile data from the OAuth provider unless you explicitly grant additional permissions.
Device name
When you first authenticate on a device, your device's name (e.g. "Kevin's iPhone") is sent to our server along with your authentication token. This is used to identify authorized devices in your account settings. You can revoke device access at any time.
Billing information
If you subscribe to a paid plan, payment processing is handled entirely by Stripe. We store only a Stripe customer ID on our servers — no card numbers, no billing addresses, no payment details of any kind.
Usage metadata (billing transparency)
When you use Central-Intel Cloud credits to make AI requests through our relay, we log the following metadata: the model name used, the request type (chat or extraction), prompt and completion token counts, estimated and actual cost, and a timestamp. This data powers the transaction history visible in your account settings. We never log the content of your messages, prompts, or AI responses — only the billing metadata described above.
Billing cost calculation
To calculate token costs accurately, we use LiteLLM, an open-source library (MIT license) that maintains a community-updated pricing database for AI models. LiteLLM runs entirely within our server process — it performs token counting and cost lookups locally and does not send your messages, tokens, or any user data to external servers. Its pricing database is a static JSON file bundled with the library.
Session cookie
When you sign in to the Central-Intel web portal, we set a single authentication cookie
called ci_session. This cookie is httpOnly, secure, and strict same-site,
with a maximum age of 7 days. It contains an opaque session identifier — no personal
data. We do not use any tracking, analytics, or advertising cookies.
Device identity keys
Each device you use with Central-Intel generates a unique cryptographic keypair (X25519 for encryption, Ed25519 for signing). The public keys are registered on our server so your devices can discover and verify each other during the pairing process. Private keys never leave your device — they are encrypted at rest and are not transmitted to us or any third party.
What we do NOT collect
Health data (Android — Health Connect)
If you grant permission, the Android app can read data from Health Connect: steps, heart rate, resting heart rate, heart rate variability (HRV), VO2 max, sleep sessions, nutrition, weight, body fat percentage, lean body mass, basal metabolic rate (BMR), active and total calories burned, exercise sessions, and floors climbed. This data is pulled at the time of your request only — it is injected into the AI prompt context so your assistant can provide personalized health insights. It is never stored on our servers, never written to any database, and never transmitted outside of the AI request you initiated. You can revoke health permissions at any time in the app settings.
Calendar data (Google Calendar)
If you connect Google Calendar, the app syncs your calendar events (read-only) into your local knowledge base for contextual responses. Calendar OAuth tokens are encrypted using Fernet symmetric encryption and stored on our server — the tokens allow the app to fetch your events, but your calendar data itself stays on your device. You control which calendars are connected, and you can disconnect at any time.
Email data
You can add emails to your local knowledge base for contextual AI responses. Email content is processed and stored entirely on your device — it is not transmitted to our servers.
Anonymous usage analytics (opt-in)
If you opt in (default: off), we collect anonymous usage data to understand feature adoption and improve the app experience. This includes: which screens are visited, how often, session duration, experience level selected, onboarding progress, feature usage patterns, and model selection. This data uses a random device UUID (not your hardware ID, IMEI, or any personal identifier), is not linked to your identity, and is auto-deleted after 90 days. We never collect message content, file content, personal information, or API keys through analytics. You can opt out at any time in Settings, which immediately clears any pending analytics events.
Anonymous benchmark results (opt-in, desktop only)
When you run a local model benchmark on the desktop app and analytics opt-in is enabled, we also collect: hardware class (e.g. "NVIDIA 24 GB"), model name, quantization format, tokens/sec, time-to-first-token, accuracy score, and app version. These fields are aggregated across devices, kept in a bounded recent-sample window, and auto-deleted after 90 days. No device identifier, no account, no message content, no personal information is included. This data is used solely to improve the model-compatibility predictions shown to all users.
We use the limited information we collect for the following purposes:
We do not use your information to train AI models, build advertising profiles, or sell data to any third party for any purpose.
The vast majority of Central-Intel data never leaves your device. The following is stored locally using iOS Core Data (on iPhone), Android Room (on Android), or SQLite and the local filesystem (on the desktop application), and is not synced to our servers unless you opt into cross-device memory sync (see below):
Important: Because this data is local-only, it is permanently lost if you uninstall the app. We cannot restore it for you. We recommend exporting any important data before uninstalling.
Cross-device memory sync
If you enable memory sync, your memory items are encrypted on your device using AES-256-GCM with a vault key that only your devices possess, then transmitted to our relay server as opaque encrypted blobs. Our server cannot decrypt these items — it stores them temporarily in RAM (with a 24-hour time-to-live) to facilitate delivery to your other devices. The server holds only the encrypted ciphertext, a random nonce, and a timestamp — never the plaintext. Encrypted sync data does not survive a server restart and is purged automatically when the TTL expires.
Central-Intel connects to AI providers that you explicitly configure. When you send a message, that message — along with any relevant context from your knowledge base or memory — is transmitted directly to the provider you selected. We do not intercept, log, or retain that content.
The providers you may connect, and links to their privacy policies, are:
| Provider | Privacy Policy |
|---|---|
| Central-Intel Cloud (default) | This document |
| OpenAI | openai.com/policies/privacy-policy |
| Anthropic | anthropic.com/privacy |
| Google Gemini | policies.google.com/privacy |
| Groq | groq.com/privacy-policy |
| Mistral AI | mistral.ai/privacy |
| Together AI | together.ai/privacy |
| Cohere | cohere.com/privacy |
| DeepSeek | deepseek.com/privacy_policy |
| xAI (Grok) | x.ai/legal/privacy-policy |
| OpenRouter | openrouter.ai/privacy |
| Azure OpenAI | Microsoft Privacy Statement |
| Ollama (optional, LAN/local) | Fully local inference — prompts stay on-device or your LAN. See ollama.com/privacy. |
| llama.cpp (default local engine) | Fully local inference — prompts never leave your device. See github.com/ggerganov/llama.cpp. |
Subscription authentication ("Sign in with Claude" / "Sign in with ChatGPT")
Some providers — currently Anthropic (Claude Pro / Max), OpenAI (ChatGPT Plus / Pro), and xAI (SuperGrok / X Premium+) — let you sign in to a personal AI subscription and route requests against that subscription instead of an API key. We support this so users with an existing subscription don't have to pay twice. This mode is intentionally different from the rest of the app, and you should understand the trade-off before turning it on.
api.x.ai/v1 with the OAuth Bearer token — no CLI subprocess. This is
the same approach used by other open-source community projects that integrate with
these subscriptions. If a provider publishes a dedicated third-party-client program
in the future, we will switch to it. Central-Intel does not bundle, distribute, or
modify the first-party CLIs — you install them directly from the provider (xAI has
no CLI prerequisite).Embeddings: When you add documents to your knowledge base, their text is sent to OpenAI's Embeddings API to generate vector representations for semantic search. This occurs only if you have connected an OpenAI API key. The text is sent under your API key, subject to OpenAI's privacy policy linked above.
Local network discovery (desktop)
The desktop application can scan your local network (the /24 subnet your device is connected to) for other Ollama instances running on your LAN. This scan sends TCP connection probes to port 11434 on addresses within your local network, followed by HTTP requests to any responding hosts to confirm they are running Ollama. This traffic stays entirely within your local network and is not routed through our servers. No information about discovered devices is sent to us.
Important: Central-Intel acts as a relay — we route your requests to the AI provider you choose, but we cannot guarantee how each provider handles your data, particularly international providers which may be subject to different data protection laws. We minimize the data we send (only the messages and context necessary for your request), but once data reaches a provider, their privacy policies govern its handling.
You are responsible for reviewing the privacy policies of the providers you choose to connect. You can use Central-Intel in a fully local mode by using llama.cpp or Ollama (which run on your own machine) and skipping all cloud provider integrations.
We do not sell, rent, or trade your personal information. We share data only in the following limited circumstances:
On our servers: We retain your email address, account record, device public keys, and usage metadata (transaction history) for as long as your account is active. Encrypted memory sync data is held in server RAM only, with a maximum 24-hour time-to-live — it is not written to permanent storage and does not survive a server restart. If you request account deletion, we will permanently delete your account and all associated server-side data (including usage logs, device identities, and any in-memory sync data) within 30 days.
On your device: Local data (chat history, knowledge base, memory items, pipelines) persists until you manually delete it within the app, or until you uninstall the app. Signing out clears your authentication credentials and API keys from the keychain but does not automatically delete conversation history or knowledge base content — that is in your control.
To request account deletion, email [email protected] with the subject line "Account Deletion Request."
We take reasonable measures to protect your information:
No method of transmission over the internet is 100% secure. While we work to protect your information, we cannot guarantee absolute security.
Central-Intel is not directed at children under the age of 13 (or 16 in the EU/UK). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us at [email protected] and we will delete it promptly.
Depending on where you live, you may have rights including:
To exercise any of these rights, email [email protected]. We will respond within 30 days.
We may update this policy from time to time. When we do, we'll update the effective date at the top of this page. For material changes, we'll notify you via email or in-app notice. Continued use of Central-Intel after a policy change constitutes your acceptance of the updated policy.
We will never make a "gotcha" change — if we ever decide to start collecting more data, we'll tell you clearly, in advance, and give you the option to opt out or close your account.
Questions, concerns, or requests about this privacy policy:
Email: [email protected]
Web: central-intel.ai/contact