The website
With your permission, we use Umami Cloud to understand visits to cexrun.com, which sections people reach, how long the page stays visible and focused, and which download or contact links they click. Analytics are off until you choose “Allow analytics.” Choosing “No thanks” does not affect the website.
We send the public page path, the referring website’s origin (not its page path), and a small set of named events: section viewed, visible-time milestone, platform selected, download interest, installer-link click, GitHub click, and contact-link click. We exclude URL query strings and fragments, form contents, email message text, recordings, and CEX desktop data. We do not assign account IDs or cross-device visitor IDs.
Umami receives ordinary network information such as your IP address and browser details. It uses request information to derive visit/session counts and reports such as browser, operating system, and approximate location. Umami uses hashed session identifiers, not analytics cookies. This is not the same as sending no data. See Umami’s privacy policy and how Umami groups sessions. We have not enabled session recordings, heatmaps, advertising trackers, or public dashboard sharing.
We save only your allow/decline preference in this browser’s local storage. You can change it here at any time. Declining stops new analytics events; it does not delete events already received. We also keep analytics off when the browser sends Do Not Track or Global Privacy Control.
Checking your analytics setting…
Reports cover consenting visits that reach the analytics service, not every visitor. Visible-time milestones are an estimate, not proof of attention. A download click does not prove the file finished downloading or was installed. The private dashboard is held in the operator’s Umami account; storage and retention follow the service and account settings.
The separate first-party download service, when enabled, records the requested artifact, an aggregate installer-request count, and the latest request time. That metric dataset does not store IP addresses, user agents, referrers, cookies, or stable visitor identifiers. It is not a unique-person count or a completed-install count.
The public website is hosted by Vercel at cexrun.com and requests a Google-hosted brand font. Release files use the applicable release host when downloads are enabled. These requests necessarily expose ordinary network information to the relevant hosting provider and its normal server logs. Website analytics choices do not change the desktop app’s separate privacy settings.
The desktop beta
The packaged beta starts with fresh local data stores. Runtime memory, workspace files, configuration, and credentials remain on the computer where CEX runs unless you choose an action that sends data elsewhere.
CEX does not bundle the developer's working databases into a release. Uninstalling the application may not remove every local workspace or runtime-data directory; review local files before discarding a machine or account.
Anonymous usage metrics do not include prompts, conversations, files, memories, credentials, API keys, generated work, or file contents.
Anonymous usage metrics
You can choose to share four narrow facts from Settings: a session started, visible active minutes, the CEX version, and the operating-system family. The app sends no stable installation ID and the first-party metric store keeps aggregate counts rather than person-level event histories.
The metric store does not retain IP addresses, user agents, referrers, account IDs, or cookies. Ordinary network requests can still expose an IP address and request metadata to the hosting provider and its short-lived server logs. Turning the setting off stops new usage events.
Crash reports
Automatic crash upload is off by default and is unavailable unless a desktop release has a configured crash-report endpoint. If available, you must turn it on separately in Settings.
A crash report contains a technical minidump, CEX version, Electron version, operating system, and process type. Minidumps can include fragments of process memory, so they may contain information that was in memory when the crash occurred even though CEX does not intentionally attach prompts or files. Use Feedback instead if you prefer to review and redact what you send.
Models, connectors, and tools
If you connect a cloud model or outside service, or approve a tool that accesses the network, the content required for that action can be sent to that provider. The provider handles that data under its own privacy terms and account settings.
CEX does not operate Ollama, llama.cpp, model-provider APIs, GitHub, Google Fonts, or other services you choose to connect. Review the destination and requested permission before approving an action.
Email and feedback
Feedback is separate from usage metrics. When you press Send, CEX saves the feedback locally and, when the hosted inbox is configured, sends the rating or report, environment fields shown in the form, and any logs, screenshots, or contact address you chose to add. Anonymous feedback omits the contact field.
If you email hello@cexrun.com, the message can contain your email address, message text, and attachments. Do not send passwords, API keys, access tokens, private model credentials, or unredacted workspace data.
Changes to this page
This notice will be updated before CEX adds new categories of product analytics, accounts, payments, or other data collection. Material changes will be reflected by the updated date below.
Questions or deletion requests can be sent to hello@cexrun.com. A retention period and operator identity must be added before public crash uploads are enabled.
Effective September 14, 2026